Copying data from a CMS installed on UNIX

Note:    Prior to Crystal Enterprise 10, the CMS was known as the Automated Process Scheduler (APS).

Use this procedure if your CMS is installed on UNIX and you are copying data from Crystal Enterprise versions 8.5, 9, or 10.

Then proceed to Completing a CMS database migration.

Note:    

• On UNIX you can not migrate directly from a source environment that uses an ODBC connection to the CMS database. If your source CMS database uses ODBC, you must first migrate that system to a supported native driver. (See Copying data from a CMS on Windows.)
• If your CMS is installed on UNIX, you cannot migrate directly from a Crystal Enterprise version 8 APS.

To copy data from a CMS installed on UNIX

1. Use ccm.sh to stop the Crystal Management Server. (See ccm.sh for details.)
2. Run cmsdbsetup.sh. When prompted, enter the name of your CMS or press enter to select the default name.

   Tip:    For information on finding the name of your CMS, see ccm.sh.

3. Type copy to begin the database migration.
4. The script prompts you to confirm that all data in the destination database will deleted. Type yes, and then press enter to proceed.
5. Next the script asks you for the version of your source Crystal Enterprise installation. You can also select autodetect to have the version of the source detected automatically. Press Enter.
6. Now the script asks you if you want to use the current CMS database as your destination.

   If you type no, you are first asked for information about the new destination database, and are then prompted for information on the source database. If you type yes, you are prompted for information about the source CMS database.

7. After entering the source information, the script will begin the migration process.

   Note:    Migration of a large source database could take several hours.

8. The script notifies you when migration is complete.

   If errors occurred during the migration, the script gives you the location of a log file explaining the migration results.

9. Proceed to "Completing a CMS database migration" on page 320.