Updating 5.0 and 5.5 DB2® databases manually

Manually update IBM® Connections 5.0 and 5.5 databases to version 6.0 CR1 in an existing IBM® WebSphere® Application Server and DB2® database environment.

Before you begin

Before you apply updates, back up your databases. For more information, see Backing up IBM® Connections.

Make sure to configure the DB2® databases for unicode so that DB2® tools such as export and import do not corrupt unicode data.

Ensure that you install and configure all supporting software for version 6.0 CR1.

Notes:
  • 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.

About this task

Update IBM® Connections version 5.0 or 5.5 databases to version 6.0 CR1 manually. Use this procedure if you want an alternative to using the database wizard to update your databases.

Notes:
  • Use the Java™ Runtime Environment (JRE) under the Wizards directory in the installation media. Update your PATH variable to point to this JRE, by using the instructions for your operating system. For example, the relative path to the JRE on Microsoft™ Windows™ might be Wizards\jvm\win\jre. For AIX® or Linux™, the relative path might be Wizards/jvm/aix/jre and Wizards/jvm/linux/jre.
  • IBM® Connections does not support GNU Java™.
  • You need to use a database administrator ID to run the Java™ migration utilities that are described in this task.
  • After you run each command, examine the output of the command for error messages. If you find errors, resolve them before you continue with the update process.
  • To improve readability, some commands and file paths in are displayed on separate lines. Ignore these formatting conventions when you enter the commands.

To update databases manually, complete the following steps:

Procedure

  1. Log in to the WebSphere® Application Server Integrated Solutions Console on your Deployment Manager.
  2. Go to Applications > Application types > WebSphere enterprise Applications.
  3. Stop all IBM® Connections applications.
  4. (DB2® on Windows™ OS.) You must perform DB2® administration tasks with full administrator privileges.
    1. Logged in as the instance owner, open a command prompt and change to the DB2® bin directory. For example: C:\Program Files\IBM\SQLLIB\BIN.
    2. Enter the following command: db2cwadmin.bat. This command opens the DB2® command line processor while also setting your DB2® privileges.
  5. Log in as the database administrator.
  6. For each application, change to the directory where the SQL scripts are stored and then enter the commands for that application.
    Note: To capture the output of each command to a log file, append the following parameter to each command: >> /file_path/db_application.log

    where file_path is the full path to the log file and application is the name of the log file. For example:

    db2 -td@ createDb.sql >> /home/db2inst1/db_activities.log

    Ensure that you have write permissions for the directories and log files.

    Note: If your database version of IBM® Connections components are already at a given schema version, then start running scripts for that schema version level.
  7. Change to the Activities SQL scripts directory Wizards/connections.sql/activities/db2, and then check for the database schema version as follows: 
    db2 connect to OPNACT
db2 select DBSCHEMAVER from ACTIVITIES.OA_SCHEMA
    • If schema version is 69, then enter the following commands:
      db2 -td@ -vf upgrade-50-50CR1.sql
db2 -td@ -vf upgrade-50CR1-55.sql
db2 -td@ -vf upgrade-55-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 72, then enter the following commands:
      db2 -td@ -vf upgrade-50CR1-55.sql
db2 -td@ -vf upgrade-55-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 94, then enter the following commands:
      db2 -td@ -vf upgrade-55-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 98, then enter the following commands:
      db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
  8. Change to the Blogs SQL scripts directory Wizards/connections.sql/blogs/db2, and then check for the database schema version as follows: 
    db2 connect to BLOGS
db2 "select cast(VALUE as VARCHAR(20)) from BLOGS.roller_properties where name='database.schema.version'"
    • If schema version is 69, then enter the following commands:
      db2 -td@ -vf upgrade-50-50CR1.sql
db2 -td@ -vf upgrade-50CR1-50CR2.sql
db2 -td@ -vf upgrade-50CR2-55.sql
db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 70, then enter the following commands:
      db2 -td@ -vf upgrade-50CR1-50CR2.sql
db2 -td@ -vf upgrade-50CR2-55.sql
db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 72, then enter the following commands:
      db2 -td@ -vf upgrade-50CR2-55.sql
db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 75, then enter the following commands:
      db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
  9. Change to Bookmarks SQL scripts directory Wizards/connections.sql/dogear/db2, and then check for the database schema version as follows: 
    db2 connect to DOGEAR
db2 select DBSCHEMAVER from DOGEAR.DOGEAR_SCHEMA
    • If schema version is 22, then enter the following command:
      db2 -td@ -vf upgrade-50-55.sql
db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 24, then enter the following command:
      db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
  10. Change to the Communities SQL scripts directory Wizards/connections.sql/communities/db2, and then check the database schema version as follows: 
    db2 connect to SNCOMM
db2 select DBSCHEMAVER from SNCOMM.SNCOMM_SCHEMA
    • If schema version is 93, then enter the following commands:
      db2 -td@ -vf upgrade-50-50CR2.sql
db2 -td@ -vf upgrade-50CR2-55.sql
db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 98, then enter the following commands:
      db2 -td@ -vf upgrade-50CR2-55.sql
db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 104, then enter the following commands:
      db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
  11. Change to the Calendar SQL scripts directory Wizards/connections.sql/communities/db2, and then check the database schema version as follows: 
    db2 connect to SNCOMM
db2 select DBSCHEMAVER from CALENDAR.CA_SCHEMA
    • If schema version is 29, then enter the following commands:
      db2 -td@ -vf calendar-upgrade-50-50CR1.sql
db2 -td@ -vf calendar-upgrade-50CR1-55.sql
db2 -td@ -vf calendar-upgrade-55-60.sql
db2 -td@ -vf calendar-appGrants.sql
db2 -td@ -vf calendar-reorg.sql 
db2 -td@ -vf calendar-runstats.sql
    • If schema version is 30, then enter the following commands:
      db2 -td@ -vf calendar-upgrade-50CR1-55.sql
db2 -td@ -vf calendar-upgrade-55-60.sql
db2 -td@ -vf calendar-appGrants.sql
db2 -td@ -vf calendar-reorg.sql 
db2 -td@ -vf calendar-runstats.sql
    • If schema version is 34, then enter the following commands:
      db2 -td@ -vf calendar-upgrade-55-60.sql
db2 -td@ -vf calendar-appGrants.sql
db2 -td@ -vf calendar-reorg.sql 
db2 -td@ -vf calendar-runstats.sql
  12. Change to the Files SQL scripts directory Wizards/connections.sql/files/db2, and then check the database schema version as follows: 
    db2 connect to FILES
db2 select SCHEMA_VERSION from "FILES"."PRODUCT"
    • If schema version is 107, then enter the following commands:
      db2 -td@ -vf upgrade-50-55.sql
db2 -td@ -vf upgrade-55-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    • If schema version is 139, then enter the following commands:
      db2 -td@ -vf upgrade-55-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    • If schema version is 140, then enter the following commands:
      db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    Note: Do not run the following scripts for the Files application:
    • pns-createDb50.sql
    • pns-dropDb.sql
  13. Change to the push notification Wizards/connections.sql/pushnotification/db2 directory, and then check the database schema version as follows: 
    db2 connect to PNS
db2 select SCHEMA_VERSION from "PNS"."PRODUCT"
    • If you cannot connect to PNS, switch to Wizards/connections.sql/files/db2, and enter the following command: 
      db2 -td@ -vf pns-dropDb.sql

      Then switch back to Wizards/connections.sql/pushnotification/db2, and enter the following commands:

      db2 -td@ -vf createDb.sql
db2 -td@ -vf appGrants.sql
    • If schema version is 7, then enter the following commands:
      db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
  14. Change to the Forum SQL scripts directory Wizards/connections.sql/forum/db2, and then check the database schema version as follows: 
    db2 connect to FORUM
db2 select DBSCHEMAVER from FORUM.DF_SCHEMA
    • If schema version is 35, then enter the following commands:
      db2 -td@ -vf upgrade-50-50CR1.sql
db2 -td@ -vf upgrade-50CR1-55.sql
db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 36, then enter the following commands:
      db2 -td@ -vf upgrade-50CR1-55.sql
db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 38, then enter the following commands:
      db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
  15. Change to the home page SQL scripts directory Wizards/connections.sql/homepage/db2, and then check the database schema version as follows: 
    db2 connect to HOMEPAGE
db2 select DBSCHEMAVER from HOMEPAGE.HOMEPAGE_SCHEMA
    • If schema version is 475 , then enter the following commands:
      db2 -td@ -vf upgrade-50-50CR1
db2 -td@ -vf upgrade-50CR1-50CR2.sql
db2 -td@ -vf upgrade-50CR2-50CR3.sql
db2 -td@ -vf upgrade-50CR3-50CR4.sql
db2 -td@ -vf upgrade-50CR4-55.sql
db2 -td@ -vf upgrade-55-55CR1.sql
db2 -td@ -vf upgrade-55CR1-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    • If schema version is 477, then enter the following commands:
      db2 -td@ -vf upgrade-50CR1-50CR2.sql
db2 -td@ -vf upgrade-50CR2-50CR3.sql
db2 -td@ -vf upgrade-50CR3-50CR4.sql
db2 -td@ -vf upgrade-50CR4-55.sql
db2 -td@ -vf upgrade-55-55CR1.sql
db2 -td@ -vf upgrade-55CR1-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    • If schema version is 478 , then enter the following commands:
      db2 -td@ -vf upgrade-50CR2-50CR3.sql
db2 -td@ -vf upgrade-50CR3-50CR4.sql
db2 -td@ -vf upgrade-50CR4-55.sql
db2 -td@ -vf upgrade-55-55CR1.sql
db2 -td@ -vf upgrade-55CR1-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    • If schema version is 479, then enter the following commands:
      db2 -td@ -vf upgrade-50CR3-50CR4.sql
db2 -td@ -vf upgrade-50CR4-55.sql
db2 -td@ -vf upgrade-55-55CR1.sql
db2 -td@ -vf upgrade-55CR1-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    • If schema version is 705, then enter the following commands:
      db2 -td@ -vf upgrade-55-55CR1.sql
db2 -td@ -vf upgrade-55CR1-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    • If schema version is 706, then enter the following commands:
      db2 -td@ -vf upgrade-55CR1-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    • If schema version is 707, then enter the following commands:
      db2 -td@ -vf upgrade-55CR2-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql

    Next, you need to run a java migration from 5.0 to 5.5.

  16. Change to the Metrics SQL scripts directory Wizards/connections.sql/metrics/db2, and then check the database schema as follows: 
    db2 connect to METRICS
db2 select SCHEMA_VERSION from "METRICS"."PRODUCT"
    • If schema version is 38, then enter the following commands:
      db2 -td@ -vf upgrade-50-55.sql
db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    • If schema version is 41, then enter the following commands:
      db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
  17. Change to the Mobile SQL scripts directory Wizards/connections.sql/mobile/db2, and then check the database schema version as follows: 
    db2 connect to MOBILE
db2 "select cast(VALUE as VARCHAR(20)) from MOBILE.ROLLER_PROPERTIES where NAME='database.schema.version'"
    • If schema version is 7, then enter the following commands:
      db2 -td@ -vf upgrade-50-55.sql
db2 -td@ -vf upgrade-55-55CR2.sql 
db2 -td@ -vf upgrade-55CR2-60.sql 
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
    • If schema version is 10, then enter the following commands:
      db2 -td@ -vf upgrade-55-55CR2.sql 
db2 -td@ -vf upgrade-55CR2-60.sql 
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
  18. Change to the Profiles SQL scripts directory Wizards/connections.sql/profiles/db2, and then check the database schema version as follows: 
    db2 connect to PEOPLEDB
db2 select DBSCHEMAVER from EMPINST.SNPROF_SCHEMA
    • If schema version is 46, then enter the following commands:
      db2 -td@ -vf upgrade-50-55.sql
db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
db2 -td@ -vf clearScheduler.sql
    • If schema version is 55, then enter the following commands:
      db2 -td@ -vf upgrade-55-60.sql
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf runstats.sql
db2 -td@ -vf clearScheduler.sql
  19. Change to the Wikis SQL scripts directory Wizards/connections.sql/wikis/db2, and then check the database schema version as follows: 
    db2 connect to WIKIS
db2 select SCHEMA_VERSION from "WIKIS"."PRODUCT"
    • If schema version is 107, then enter the following commands:
      db2 -td@ -vf upgrade-50-55.sql
db2 -td@ -vf upgrade-55-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql 
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    • If schema version is 139, then enter the following commands:
      db2 -td@ -vf upgrade-55-55CR2.sql
db2 -td@ -vf upgrade-55CR2-60.sql 
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
    • If schema version is 140, then enter the following commands:
      db2 -td@ -vf upgrade-55CR2-60.sql 
db2 -td@ -vf appGrants.sql
db2 -td@ -vf reorg.sql
db2 -td@ -vf updateStats.sql
  20. Now update the Activities and Homepage databases to the CR1 level by completing the following steps.

    The following steps assume Windows as the operating system.

    1. Change to the following directory: C:\Install\CONNECTIONS-CR\IC-CR1.
    2. Locate the 60cr1-database-updates.zip file and extract it into the current folder.
    3. Change to the following directory: C:\Install\CONNECTIONS-CR\IC-CR1\60cr1-database-updates\60cr1-database-updates\From-60\db2.
    4. Rename the file readme-db2-updates-from-60.txt to readme-db2-updates-from-60.bat.
    5. Run the database update script in the DB2 command window:
      1. From the Windows Start menu, click IBM DB2 DB2COPY (Default) and select Command Window -Administrator.
      2. In the command window, run the following commands:
        cd C:\Install\CONNECTIONS-CR\IC-CR1\60cr1-database-updates\60cr1-database-updates\From-60\db2
readme-db2-updates-from-60.bat
      3. Review the output from the scripts to verify there are no errors, and then close the DB2 command window.

What to do next

Check that all the databases are working correctly.

(DB2® for Linux™ on System z® only.) To improve database performance, enable the NO FILE SYSTEM CACHING option. For more information, see the Enabling NO FILE SYSTEM CACHING for DB2 on System z topic.

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 web page in the DB2® information center.
Note:
  • If you migrated from IBM® Connections 5.0, the numdb parameter was set to 14, the maximum number of IBM® Connections 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:

    db2 UPDATE DBM CFG USING NUMDB nn

    where nn is a number of databases.