Migrating data side-by-side

Migrate IBM® Connections 4.5 or 5.0 data in a side-by-side procedure to keep your data intact and available while you set up a separate IBM Connections 5.5 deployment.

Before you begin

(DB2® only) If you use only one database instance and if that instance includes other databases besides IBM Connections, configure the numdb parameter to match the total number of databases on the instance. For more information, go to the numdb webpage in the DB2 information center.
  • If you migrated from IBM Connections 4.5 or 5.0, the numdb parameter was set to 14, the maximum number of IBM Connections 4.5 or 5.0 databases. If the instance has additional databases, increase the value of the numdb parameter to match the total number of databases on the instance. To change the parameter, enter the following command:


    where nn is a number of databases.

  • Before removing (or dropping) a database, stop Connections first to ensure that no database connection is in use; otherwise you will not drop the user and the database removal will not occur.
  • If you run dbWizard.bat but the database wizard does not launch, check whether you have 32-bit DB2 installed. You need to have 64-bit DB2 on a 64-bit system.

(Oracle only) Ensure that the Statement cache size for the data sources on WebSphere Application Server is no larger than 50. A higher value could lead to Out Of Memory errors on the application server instance.

About this task

Follow these general steps to complete a side-by-side data migration:
Note: An alternative to the side-by-side instructions provided here is to use import/export or backup/restore tools specific to your database to create a copy of the database for a side-by-side update.
  • Create Connections 4.5 or 5.0 databases and run the 4.5 or 5.0 database wizard to update them with the latest Connections 4.5 or 5.0 database updates.
  • Transfer your production data to the new Connections 4.5 or 5.0 databases.
  • Update the new databases to the Connections 5.5 level as you would do for an in-place migration. You can either use the Connections 5.5 database wizard or use SQL scripts.