Update DB2 databases manually 

Manually update Lotus Connections 3.0 databases to version 3.0.1 in an existing IBM WAS and DB2 database environment.

Before starting

Before applying updates, back up your databases. For more information, see the Backing up IBM Connections topic.

Ensure that you have installed and configured all supporting software for version 3.0.1.

About this task

This topic describes how to manually update Lotus Connections version 3.0 databases to version 3.0.1. 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, using the instructions for your operating system. For example, the relative path to the JRE on the Microsoft™ Windows™ operating system might be C:\IBM\Lotus_Connections\Wizards\jvm\win\jre. For the AIX or Linux™ operating systems, the relative path might be /Wizards/jvm/aix/jre and /Wizards/jvm/linux/jre.

• IBM Connections does not support GNU Java.

• You do not need to use a database administrator ID to run the Java migration utilities described in this task. You can use a database user ID, such as lcuser.

• To improve readability, some commands and file paths in this topic are displayed on separate lines. Ignore these formatting conventions when entering the commands.

• After running each command, examine the output of the command for error messages. If you find errors, resolve them before continuing with the update process.

To update databases manually...

Procedure

1. Log in to the WAS admin console.

2. Go to Applications -> Application types -> WebSphere enterprise Applications.

3. Stop all Lotus Connections applications.

4. (DB2 on Windows 2008 64-bit) On Windows 2008, 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. 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 -tvf createDb.sql >> /home/db2inst1/db_activities.log

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

6. Activities: Wizards/connections.sql/activities/db2

   1. db2 -td@ -vf upgrade-30-301.sql

   2. db2 -td@ -vf appGrants.sql
      

7. Blogs: Wizards/connections.sql/blogs/db2

   1. db2 -td@ -vf upgrade-30-301.sql

   2. From a command prompt, change to the Wizards directory and enter the following text as a command on a single line:
      

      • AIX or Linux:
        jvm/<OS>/jre/bin/java -classpath

        <jdbc_library_location>/db2jcc.jar:

        <jdbc_library_location>/db2jcc_license_cu.jar:

        lib/lc.dbmigration.default.jar:

        lib/blogs.migrate.jar:

        lib/commons-lang-2.0.jar:

        lib/commons-logging-1.0.4.jar

        com.ibm.lconn.blogs.migration.MigrationFrom30To301

        -dburl jdbc:db2://<dbHost>:<dbPort>/BLOGS

        -dbuser <dbUser> -dbpassword <dbPassword>

        where <OS> is the operating system on which the database is hosted.
        

      • Windows:
        jvm\win\jre\bin\java -classpath

        <jdbc_library_location>\db2jcc.jar;

        <jdbc_library_location>\db2jcc_license_cu.jar;

        lib\lc.dbmigration.default.jar;

        lib\blogs.migrate.jar;

        lib\commons-lang-2.0.jar;

        lib\commons-logging-1.0.4.jar

        com.ibm.lconn.blogs.migration.MigrationFrom30To301

        -dburl jdbc:db2://<dbHost>:<dbPort>/BLOGS

        -dbuser <dbUser> -dbpassword <dbPassword>
        

      where
      

      • <jdbc_library_location> is the location of your JDBC driver

      • <dbHost> is the name of the system hosting your database

      • <dbPort> is the communications port for the database

      • <dbAlias> is the reserved name of the database, if applicable

      • <dbUser> is the database user ID

      • <dbPassword> is the administrator password

   3. db2 -td@ -vf appGrants.sql
      

8. Communities: Wizards/connections.sql/communities/db2

   1. db2 -td@ -vf upgrade-30-301.sql

   2. db2 -td@ -vf appGrants.sql
      

9. Dogear: Wizards/connections.sql/dogear/db2

   1. db2 -td@ -vf upgrade-30-301.sql

   2. db2 -td@ -vf appGrants.sql
      

10. Files: Wizards/connections.sql/files/db2

    1. db2 -td@ -vf upgrade-30-301.sql
       

    2. db2 -td@ -vf appGrants.sql
       

11. Forum: Wizards/connections.sql/forum/db2

    1. db2 -td@ -vf upgrade-30-301.sql
       

    2. db2 -td@ -vf appGrants.sql
       

12. Home page: Wizards/connections.sql/homepage/db2

    1. db2 -tvf upgrade-30-301.sql
       

    2. db2 -tvf appGrants.sql
       

13. Profiles: Wizards/connections.sql/profiles/db2

    1. db2 -tvf upgrade-30-301.sql
       

    2. db2 -tvf appGrants.sql
       

14. Wikis: Wizards/connections.sql/wikis/db2

    1. db2 -td@ -vf upgrade-30-301.sql
       

    2. db2 -td@ -vf appGrants.sql
       

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 Enable NO FILE SYSTEM CACHING for DB2 on System z topic.

Parent topic

Update 3.0 databases manually

   

 

});

+

Search Tips   |   Advanced Search