Considerations for migration

When you are migrating from a previous version of IBM Security Verify Directory to a current version, you must consider the following conditions before migration:

• Ensure that the previous version from which you are migrating is supported for direct migration.
• Specify a valid backup directory, encryption key, and encryption salt for an instance that you intend to migrate.
• Ensure that the required files are available in the backup directory.
• The source and target versions of IBM Security Verify Directory are supported versions for migration.
• Ensure that the ldapdb.properties file in the DS_instancehome/etc is present and valid.

If error conditions are encountered during migration, the tool attempts to restore schema and configuration files to their original state and exits with error messages. Some of the likely causes for exit of migration are:

• If the parsing of schema or configuration files fails.
• On Windows™, if the migration of services files fails.

To identify the reasons for migration failure, you must examine the following messages and trace output:

• Use the error messages that are displayed on the console when the migration fails to determine the cause of failure.
• Run migration with trace mode ON and redirect the trace output to a file. This trace output can be used to determine the reason for migration failure.
• If an ibm-slapdInvalidLine message is displayed during server startup, then you must check whether the configuration file is corrupted.
• The idsdbmigr.log file must be checked for any failure in database migration.
• If the server fails to start after migration, you must set the trace mode ON. The following files must be examined to determine the cause of failure.
  • trace file (output from trace)
  • db2diag.log
  • db2cli.log