Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
migration failes because of V3.modifiedschema
70 views
Skip to first unread message
paolo....@gmail.com
Jun 24, 2019, 9:06:34 AM6/24/19
to
I was given the project to update some (very) old IBM TDS 6.1 servers to IBM SDS 6.4 servers... Obviously doing a direct migration is impossible so I first migrate the the IBM TDS 6.1 server to an IBM 6.3 TDS server and then from the IBM TDS 6.3 server to the IBM SDS 6.4 server...
But I'm encountering a problem when I do the migration... When I try to migrate the instance from IBM TDS 6.1 to IBM TDS 6.3 (using the command: "./idsimigr -I test_ds -u /tmp/ldapsaveconf -n") The command fails with the error:
06/22/19 10:19:21 GLPMIG004E Cannot read V3.modifiedschema file in the '/home/test_ds/idsslapd-test_ds/etc' directory.
and then goes on and removes the istance:
06/22/19 10:19:21 GLPIDP002I Deleting directory server instance: 'test_ds'.
We have modified the Schema inserting the changes into 'V3.modifiedschema'.
I noticed that at a certain point while the command "./idsimigr -I test_ds -u /tmp/ldapsaveconf -n" is executing the file 'V3.modifiedschema' gets emptied and immediately after that the migration fails...
Another thing I find interesting is that just before the error:
"06/22/19 10:19:21 GLPMIG004E Cannot read V3.modifiedschema file in the '/home/test_ds/idsslapd-test_ds/etc' directory."
The log shows the message:
"06/22/19 10:19:21 GLPMIG025I Successfully migrated the configuration file from version '6.2' to version '6.3'."
on the same TDS server I successfully migrated a different instance in which the schema wasn't modified...
Anyone knows why this is happening and how I can fix this?
TIA
Paolo Supino
But I'm encountering a problem when I do the migration... When I try to migrate the instance from IBM TDS 6.1 to IBM TDS 6.3 (using the command: "./idsimigr -I test_ds -u /tmp/ldapsaveconf -n") The command fails with the error:
06/22/19 10:19:21 GLPMIG004E Cannot read V3.modifiedschema file in the '/home/test_ds/idsslapd-test_ds/etc' directory.
and then goes on and removes the istance:
06/22/19 10:19:21 GLPIDP002I Deleting directory server instance: 'test_ds'.
We have modified the Schema inserting the changes into 'V3.modifiedschema'.
I noticed that at a certain point while the command "./idsimigr -I test_ds -u /tmp/ldapsaveconf -n" is executing the file 'V3.modifiedschema' gets emptied and immediately after that the migration fails...
Another thing I find interesting is that just before the error:
"06/22/19 10:19:21 GLPMIG004E Cannot read V3.modifiedschema file in the '/home/test_ds/idsslapd-test_ds/etc' directory."
The log shows the message:
"06/22/19 10:19:21 GLPMIG025I Successfully migrated the configuration file from version '6.2' to version '6.3'."
on the same TDS server I successfully migrated a different instance in which the schema wasn't modified...
Anyone knows why this is happening and how I can fix this?
TIA
Paolo Supino
Franz Wolfhagen
Jun 25, 2019, 6:37:32 AM6/25/19
to
I seem to remember that some changes to the standard schema was performed in some release - and that may conflict with v3.modifiedschema - i.e. there may be overlap or inconsistencies between attributes/objectclasses/oids etc.
HTH
Regards
Franz Wolfhagen
0 new messages