Troubleshoot and support > Migrate
Database tier migration issues
If you encounter problems during the migration of the database tier, review the following issues:
- Troubleshoot: Feature information removed during migration
If you installed and enabled any WebSphere Commerce feature packs, the entries in the SITE table are removed during migration of the database.
- Troubleshoot: Error when restoring database
During database migration errors are encountered when upgrading to a higher DB2 version.
- Troubleshoot: Running the database tier migration script with the precheck option
Pre-checking the database migration might reveal problems with database column lengths.
- Troubleshoot: Conflicting message type in the MSGTYPES table
- Troubleshoot: Error message during database tier migration
Review this document for two problems with DB2 database migration.
- Troubleshoot: Error when deleting a member group or removing an approval type from an organization in Organization Administration Console
Review this document which describes three problems encountered when deleting a member group or removing an approval type.
- Troubleshoot: Message "couldn't set locale correctly"
The database migration on a Solaris system reports a locale specific error.
- Troubleshoot: Error message in the database tier migration log
Oracle Database migration fails; unable to resolve service name.
- Troubleshoot: Warning message in migratedb log
An SQL exception is logged during database migration.
- Troubleshoot: Error message in the database tier migration log
Database migration logs an error after running an SQL statement for member roles.
- Error "content of the database manager configuration file is not valid"
After migrating the DB2 database to a higher version, you get an error message when you run the updatedb or enablefeature command.