Bookshelf v8.0: Migrating a Repository Using the Database Configuration Wizard

Migrating a Repository Using the Database Configuration Wizard

Running the Database Configuration Wizard achieves the following results:

Exports the designated repository from the source database or reads the source repository from file.

Imports the designated repository into the target database

Exports the logical schema definition from the specified repository to a control file

Synchronizes the physical schema of the target database with this logical schema definition

NOTE: The Database Configuration Wizard skips the previous two schema-related steps if you select no schema changes while running the utility.

Take note of the following items before running a repository migration:

When migrating repositories over a wide area network (WAN) and running the Database Configuration Wizard from the target environment, only the process of exporting the source repository to a flat file takes place on the WAN. All other processing takes place on the local area network (LAN) of the target environment. Consider the export processing times when processing the export over a WAN. The most efficient option is to export the file on the source then transport the exported file to the target environment.

For multilingual installations where the source repository contains additional language strings, all languages are copied with the repository to the target environment.

Siebel Business Applications version 8.0 support customized database triggers, but these triggers are not migrated. If you have created customized triggers on your Siebel base tables, you must disable them before migrating the schema. You will then need to recreate the triggers after the migration is finished.

NOTE: If you have a custom table space defined on DB2 UDB for z/OS, the Database Configuration Wizard used in the migration process is tablespace-aware. For further information on z/OS, see Implementing Siebel Business Applications on DB2 UDB for z/OS.

To migrate a repository in a Windows environment

Stop all Siebel Servers by navigating to Start > Settings > Control Panel > Services.

NOTE: The Database Configuration Wizard runs in live mode only so you must be connected to the Gateway Name Server to run it. For further information on Siebel Configuration Wizard running modes, see the Siebel Installation Guide for the operating system you are using.

Select Start > Programs > Siebel Enterprise Server Configuration 8.0 > Database Server configuration.

The first screen of the Database Configuration Wizard appears.

Enter the information you are prompted for in each screen, and click Next to continue.

Select Migrate Repository when you are prompted for a database operation.

In the Source Repository Selection screen, select to read the source repository from the database or from a previously exported file.

If you select to read the source repository from file, the Repository File Selection screen appears.
Enter the path and filename of the source repository file and click Next. The Target Environment Status screen appears.

For background information on creating a source repository file, see Creating a Source Repository Migration File.
If you select to read the source repository directly from the database, the Target Environment Status screen appears.

In the Target Environment Status screen, select whether the target Siebel Enterprise will be online or offline, and click Next. For further information on this selection, see Preparing for Target Environment Status Selection.

In the Schema Changes screen, select whether there are new schema changes to be applied during the repository migration, and click Next. For further information on this selection, see Preparing for Schema Changes Selection.

In the Language Selection screen, select the appropriate language, and then click Next.

NOTE: The repository migration process migrates all language strings within the repository. Select the base language installation that applies for this screen.

The next succession of screens is dependent on the repository source selection:

If you chose to read the source repository from file, the Target Repository Name screen appears. Enter the target repository name, and click next.

If you chose to read the source directly from database, the following succession of screens appears to define the source database.


Screen	Description
ODBC Data Source Name	If you chose to read the source repository from the database, enter the ODBC data source name.
Database User Name	If you chose to read the source repository from the database, enter the source database user name and source database password.
Database Table Owner	If you chose to read the source repository from the database, enter the source database table owner and source table owner password.
Source Database Repository Name	If you chose to read the source repository from the database, enter the database repository name and the target database repository name.

Progress by completing the information in the following screens, and then clicking Next.


Screen	Description
Target RDBMS Platform	Select the target RDBMS platform.
Target Database Encoding	Select whether the target database is Unicode. Consult with your DBA on the setup of the target database.
Target Database ODBC Datasource	Enter the target database ODBC datasource.
Target Database User Name	Enter the target database user name and password.
Target Database Table Owner	Enter the target database table owner and table owner password.
Index Table Space Name (DB2-specific)	If you choose IBM DB2 for the target database platform, you get this screen. Enter the index table space name and 4-KB Table Space Name.
16-KB Table Space Name (DB2-specific)	If you choose IBM DB2 for the target database platform, you get this screen. Enter the 16-KB table space name and 32-KB table space name.
Index Table Space Name (Oracle-specific)	If you choose Oracle as the target database platform, you have only two questions about index and table space. There are no 4-KB, 16-KB, and 32-KB tablespaces in Oracle. For Microsoft SQL server, there are no screens about tablespaces.

When the Configuration is Complete screen appears, select one of the following options, and click Next:

Yes apply configuration changes now. The configuration information you entered is saved and you can choose to launch the Siebel Upgrade Wizard in Step 14.
No I will apply configuration changes later. The configuration information is saved but you can not choose to launch the Siebel Upgrade Wizard in Step 14.

On the Configuration Parameter Review screen, review the configuration values you entered on the previous screens. To change any of the values, click Back to return to the screen with the parameter you need to change. If the values are correct, click Next to continue.

You are prompted as to whether you want to execute the configuration:

Click No if you decide you do not want to continue with the upgrade process.The configuration information you have entered is not saved. You must enter the database configuration parameters again.
Click Yes to continue. The configuration information you have entered is saved.

Depending on the option you selected in Step 11, do one of the following:

If you selected the No I will apply configuration changes later option, click OK to finish. The configuration information is saved in a master file located in SIEBEL_ROOT\bin but the Upgrade Wizard is not launched. You can restart the configuration and run the Upgrade Wizard later. For more information on the Upgrade Wizard, see the Siebel Database Upgrade Guide.
If you selected the Yes apply configuration changes now option in Step 11, the configuration information you entered is saved. Click OK and the Siebel Upgrade Wizard is launched; it calls the SQL generator to create or populate SQL scripts.

To migrate the repository in a UNIX environment

Verify that the Siebel Server is stopped.

Make $SIEBEL_ROOT the current directory.

Source environment variables:

Korn: . siebenv.sh
C shell: source siebenv.csh

Review the values of the following environment variables and confirm the settings are correct:

SIEBEL_ROOT. This path must end in siebsrvr, for example /usr/siebel/siebsrvr.
LANGUAGE. This is the language in which the Database Configuration Wizard runs. The value of this variable is a language identifier string. For example, enu is the identifier string for English.
If either $SIEBEL_ROOT or $LANGUAGE is not set or is incorrect, you must correct them before proceeding.

Start the Database Configuration Wizard by running the following command:

$SIEBEL_ROOT/bin/ssincfgw -args MODEL_FILE=$SIEBEL_ROOT/admin/dbsrvr.scm MODE=LIVE

The first Database Configuration Wizard screen appears. Enter the information you are prompted for in this screen, and click Next to continue.

Enter the information you are prompted for in all subsequent screens. Use the Next and Back button to navigate between screens.

Select Migrate Repository when prompted for a database operation.

From the Source Repository Selection menu, select to read the source repository from the database or from a previously exported file.

If you select to read the source repository from file, the Repository File Name menu appears.
Enter the path and filename of the source repository file and click Next. The Target Environment Status menu appears.

For background information on creating a source repository file, see Creating a Source Repository Migration File.
If you select to read the source directly from the database, the Target Environment Status menu appears.
In the Target Environment Status menu, select whether the target environment will be online or offline, and click Next. For further information on this selection, see Preparing for Target Environment Status Selection.

In the Target Environment Status screen, select whether the target environment will be online or offline, and click Next. For further information on this selection, see Preparing for Target Environment Status Selection.

In the Schema Changes menu, select whether there are new schema changes to be applied during the repository migration, and click Next. For further information on this selection, see Preparing for Schema Changes Selection.

In the Language Selection screen, select the appropriate language, and then click Next.

NOTE: The repository migration process migrates all language strings within the repository. Select the base language installation that applies for this screen.

The next succession of screens is dependent on the repository source selection:

If you chose to read the source repository from file, the Target Repository Name screen appears. Enter the target repository name, and click next.

If you chose to read the source directly from database, the following succession of screens appears to define the source database.


Screen	Description
ODBC Data Source Name	If you chose to read the source repository from the database, enter the ODBC data source name.
Database User Name	If you chose to read the source repository from the database, enter the source database user name and source database password.
Database Table Owner	If you chose to read the source repository from the database, enter the source database table owner and source table owner password.
Source Database Repository Name	If you chose to read the source repository from the database, enter the database repository name and the target database repository name.

Progress by completing the information in each screen.


Screen	Description
RDBMS Platform	Select an RDBMS platform.
Target Database Encoding	Select whether or not the target database is Unicode.
Target Database Repository Name	Enter the target database repository name.
Target RDBMS Platform	Select the target RDBMS platform.
Target Database ODBC Datasource	Enter the target database ODBC datasource.
Target Database User Name	Enter the target database user name and password used by the server components.
Target Database Table Owner	Enter the target database table owner and table owner password.
Index Table Space Name (DB2-specific)	If you choose IBM DB2 for the target database platform, this screen appears. Enter the index table space name and 4-KB table space name.
16K Table Space Name (DB2-specific)	If you choose IBM DB2 for the target database platform, this screen appears. Enter the 16-KB table space name and 32-KB table space name.
Index Table Space Name (Oracle-specific)	If you choose Oracle as the target database platform, you have only two questions about index and table space. There are no 4-KB, 16-KB, and 32-KB tablespaces in Oracle. For Microsoft SQL server, there are no screens about tablespaces.

After you have entered all the requested information, the wizard displays the following message:

Configuration is complete: configuration parameters will be saved to <$Masterfile> file when the wizard completes. Please run the following command line after you exit from this configuration wizard. This command will deploy the process you configured to the database.

$SIEBEL_ROOT/siebsrvr/bin/srvrupgwiz /m $SIEBEL_ROOT/siebsrvr/bin/<$Masterfile>

Click Next to continue. The utility displays the Parameter Review screen listing all the values you have entered.

To amend any of the configuration values, click Back to return to the appropriate screen and make changes. Otherwise, click Next.

You are prompted as to whether or not you want to execute the configuration:

Click Yes, and the configuration information is saved in a master file located in $SIEBEL_ROOT/bin but the Upgrade Wizard is not launched. For more information on starting the Upgrade Wizard, see the Siebel Database Upgrade Guide.
Click No, and the configuration information you entered is not saved.

NOTE: The database administrator must update statistics after any repository migration, upgrade, or installation finishes.