Update 4.0 and 4.5 databases with the wizard

Overview

We can use the database wizard to migrate Connections 4.0 or 4.5 databases for versions...

• 4.0 GA
• 4.0 with CRs
• 4.5 GA
• 4.5 with CRs

Back up IBM Connections DBS and file systems.

You should update the Home page database manually. The manual method allows one to back up the Home page database after each step. This precaution is useful because updating the Home page database, if it is large, can take considerably more time than the other databases. If we update manually, update the Home page database before updating any other database. After updating the Home page database, use the wizard to update the remaining databases.

If two different instances are used for the Home page and Profiles databases, updating the Home page DB first is required, using either wizard or manual method.

Oracle only

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

DB2 only

If we use only one database instance, and if that instance includes other databases besides IBM Connections, configure the numdb 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:

  db2 UPDATE DBM CFG USING NUMDB nn

  where nn is a number of databases.

• Before removing (or dropping) a database, stop Connections first and ensure that no database connection is in use; otherwise you will not drop the user and the database removal will not occur.

• If we run dbWizard.bat but 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.

SQL Server only

Ensure the name of the Home page database instance is not null. If it is null, rename it to HOMEPAGE.

Ensure that Named Pipes is enabled in the SQL Server Network Configuration for all instances. For more information, refer to the SQL Server documentation.

Attempting to delete existing 4.5 databases on a Microsoft SQL 2012 EE deployment will fail because the Database wizard does not recognize the install path. IBM Connections 4.5 did not support Microsoft SQL Server 2012 but Connections 5.0 does. The Database wizard does not support upgrading 4.5 databases to 5.0 automatically for Microsoft SQL 2012 EE. Instead, perform a manual upgrade.

Update Connections 4.x databases to Connections 5.0 databases

1. Stop the IBM WAS instances hosting IBM Connections version 4.0 or 4.5.

2. From Connections v5 host, copy the v5.0 database wizard to system hosting Connections databases.

3. Log on to the Connections DB host as the database administrator.

4. Ensure database administrator has all permissions for...
   INSTALL_MEDIA/Wizards

5. Start the Database Wizarard...
   cd INSTALL_MEDIA/Wizards/
   ./dbWizard.sh

6. Select the Update task and click Next.

7. Specify the database type, database instance, and the installation location, and then click Next.

   The wizard detects the current database version.

8. Select the databases to update and click Next:

   Activities	OPNACT
   Blogs	BLOGS
   Bookmarks	DOGEAR
   Communities	SNCOMM
   Files	FILES
   Forum	FORUM
   Home page	HOMEPAGE
   Metrics	METRICS
   Mobile	MOBILE
   Profiles	PEOPLEDB
   Wikis	WIKIS

   The database wizard disables the selection of any applications that were not released in Connections 4.0 or 4.5. If any application databases were created in an earlier release of Connections than 4.0 or 4.5, update that database using the Connections 5.0 database wizard.

9. (SQL Server only) Enter the password for the Home Page database user.

10. If we are updating the Home Page database, provide the port, administrator ID, and administrator password for the database.

11. Review the Pre Configuration Task Summary and ensure the values entereded are correct.

    To change any values, click Back to edit the value. To continue, click Update.

    To display the commands, click...

    Show detailed database commands

    To save the commands, ensure the user who is running the database wizard has write access to the destination folder. Click Execute to run the commands.

    If the database wizard encounters any unexpected SQL error, it will stop execution and display the Post Configuration Task Summary with details of the error. It also shows which database upgrades were aborted so that we can correct the error immediately, and then rerun the wizard to resume processing database upgrades.

12. After the update task finishes, review the Post Configuration Task Summary. Click Finish to exit the wizard.

13. Run the database wizard again to create databases for Connections Content Manager.

What to do next

(DB2 for Linux on System z only.) To improve database performance, enable the NO FILE SYSTEM CACHING option. See Enable NO FILE SYSTEM CACHING for DB2 on System z topic.

If we have error when upgrading the database, review log in...

db_user_home/lcWizard/log/dbWizard

Parent topic:
Update 4.0 and 4.5 databases to 5.0

Related:
Create databases
Access the News configuration file
Enable NO FILE SYSTEM CACHING for DB2 on System z