Post-migration activities

After performing the migration, you must prepare and configure Sterling™ Order Management System Software according to your business requirements.

After performing the applicable post-migration tasks for Sterling Order Management System Software and any additional applications you are upgrading, create the EAR file.

If you are not planning to use the Staged Upgrade feature or have completed the migration of all instances using Staged Upgrade feature, follow the steps listed in "Phasing out an old version" to complete the migration to 10.0 and refer Phasing out an old version

Note: After the migration is completed, verify whether the tables have chained or migrated rows. To confirm that the tables have chained rows, run the following command in SQL*Plus for each table. For example, to locate the chained rows in the YFS_ORDER_HEADER table, run:

create a table to contain the chained rows @?/rdbms/admin/utlchain.sql

ANALYZE TABLE yfs_order_header LIST CHAINED ROWS;


   SELECT * FROM CHAINED_ROWS;

The Analyze command must be run for each table.

If a table has a significant number of chained rows, for example, over 10%, you must refer to the Oracle Metalink Note 122020.1 for detailed instructions about how to resolve chained or migrated rows.