Checklist—Planning a migration

Migration tasks

þ	Task		Information

q	1	Export the Central Designer database user.	Caution: You must perform this step. If the migration is not successful, you might need to restore the database to attempt to install again. Depending on the size of the database, this process could take several hours. Note: Use the following command to export a user: exp designer@db1_dev1 file=file_to_export.dmp buffer=99999 In this example, the user has the following information: User name—designer Database—db1_dev1: Note: When you execute this command, you are prompted for the user password.
q	2	If you are migrating from an Oracle 11g database, create a new database instance with a 16k block size for the DESIGNER tablespace.	Create the database and tablespace.
q	3	Import the database user into the destination database server.	Use the following command to import a database user into the destination database server: imp designer@db1_dev1 fromuser=designer touser=designer file=file_to_export.dmp In this example, the user has the following information: User name—designer Database—db1_dev1 Note: When you execute this command, you are prompted for the user password.
q	4	If you are migrating from an Oracle 11g database, re-map the tablespaces.	Use the following command to import a database user into the destination database server: imp designer@db1_dev1 fromuser=designer touser=designer REMAP_TABLESPACE=DESIGNER_BIGINDEX:DESIGNER file=file_to_export.dmp In this example, the user has the following information: User name—designer Database—db1_dev1 Note: When you execute this command, you are prompted for the user password.
q	5	Make sure that the Cursor Sharing setting for the database instance is set properly.	Configuring the Cursor Sharing setting for a database instance.
q	6	Unlock statistics for specific tables.	Unlock statistics for the following tables: IC_OBJECT IC_OBJECT_REVISIONS IC_OBJECT_BACK_REFERENCES IC_OBJECT_FORWARD_REFERENCES IC_BLUEPRINT_OBJECT_MAP The migration process drops non-primary key indexes on the tables affected by the migration and recreates the indexes at the end of the process. If the index was originally defined with the COMPUTE STATISTICS clause, the recreation also attempts to COMPUTE STATISTICS. If statistics are locked, this process fails.
q	7	Make sure that: The database UNDO_MANAGEMENT initialization parameter is set to AUTO. The UNDO and TEMP tablespaces are set to autoextend.	These settings are necessary for a successful migration.
q	8	If you added any new indexes to the database, you must drop them before migrating the application server to ensure that they do not cause conflicts with new indexes that have been added to the product.	After the migration is finished, you can add the indexes back.
q	9	Export custom reports definitions from the Central Designer Administrator application.	Upgrading custom reports definitions.
q	10	Update data mappings with the PhysicalMappingType property set to All.	Updating data mappings with PhysicalMappingType set to All.
q	11	(Recommended) Run the DetectStudiesWithUnitsWithSpaces.sql script to determine if any studies contain unit names with spaces.	A validation check produces an error if a unit name contains a space. Running the DetectStudiesWithUnitsWithSpaces.sql script.
q	12	Prepare the new application server and install Central Designer 6.2.	Checklist—Planning the server installation. During the installation, select the Update setup type and provide the connection information for the existing database.
q	13	If you dropped indexes from your database before migrating, add them back in after you finish migrating.	No additional information.
q	14	Recompile user-defined functions and sign and secure user-defined function assemblies as needed.	Upgrading user-defined functions.
q	15	Re-import custom reports definitions.	Upgrading custom reports definitions.
q	16	If you are migrating to this release from release 2.0 or 2.0.1, recompile all user-defined function assemblies to reference the latest version of Oracle.Designer.ExternalFunctions.dll (found in the Central Designer\bin folder of the installation directory) and re-import them into any study or library that contains function objects that reference the assemblies.	No additional information.
q	17	If the web service authorization and deployment authorization certificates have expired, upgrade them. Note: If the certificates are current, you can skip this step.	Updating certificates without reinstalling the Central Designer software.
q	18	Inform users that they can resume using the client applications.	Starting the Central Designer client application. Starting the Central Designer Administrator client application.