+

Search Tips   |   Advanced Search

Migrate data side-by-side


Overview

Migrate the Connections 4.0 or 4.5 data in a side-by-side procedure so the original 4.0/4.5 data remains intact.


DB2 considerations

If we 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.

If we migrated from IBM Connections 4.5, the numdb parameter was set to 14, the maximum number of Connections 4.5 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 set:

where nn is a number of databases.

If the database wizard does not launch, check whether you have 32-bit DB2 installed. We need to have 64-bit DB2 on a 64-bit system.

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.


Oracle considerations

Set the Statement cache size for the data sources on WAS to be no larger than 50. A higher value could lead to Out Of Memory errors on the application server instance.

The 5.0 database wizards have the necessary updates to the 4.0/4.5 databases and will update the necessary schemas for Homepage and Metrics databases to the latest 5.0 version, then upgrade all databases to the 5.0 schema. It is not necessary to manually apply the 5.0 schema upgrades.


Migrate data side-by-side


Parent topic:
Migrate data from IBM Connections 4.0 or 4.5 databases to 5.0


Related:
IBM DB2 Database for Linux, UNIX, and Windows Information Center numdb - Maximum number of concurrently active databases
Directory path conventions
Update 4.0 and 4.5 databases to 5.0
Enable NO FILE SYSTEM CACHING for DB2 on System z