Database tier migration issues
If you encounter problems during the migration of the database tier, review the following issues:
- 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.- (DB2) Troubleshoot: Error message during database tier migration
Review this document for two problems with DB2 database migration.- AIX|Solaris|Windows:
(Oracle) Troubleshoot: Exception when running database migration
When migrating from WebSphere Commerce V5.6 to v6, an error is logged during database migration.- Troubleshoot: Error when deleting access group from Organization Administration Console
Review this document which describes two problems encountered when deleting an access group.- Troubleshoot: Message "couldn't set locale correctly"
The database migration on a Solaris system reports a locale specific error.- AIX|Solaris|Windows:
(Oracle) Troubleshoot: Error message in the database tier migration log
Oracle Database migration fails; unable to resolve service name.- AIX|(DB2) Troubleshoot: Error when running migratedb script
During a migration, the migratedb script fails because the database is not catalogued.- 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.- Troubleshoot: Error on CachedsubCategorysdisplay.jsp page
After migrating, an extra JSTL tag causes an error.- Troubleshoot: Error on OrderItemDisplay.jsp page
After completing migration of WebSphere Commerce, a problem is encountered when ordering items.- Troubleshoot: Error on OrderItemsCheckout.jsp page
After completing migration of WebSphere Commerce, a problem is encountered on the checkout page.