Update Oracle databases manually 

Manually update Lotus Connections 3.0 databases to version 3.0.1 in an existing IBM WAS and Oracle 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. Ensure that the Oracle driver on your system has the same version number as your Oracle database server. IBM Connections does not support the Oracle 10.2.0.1 JDBC driver.
   

5. Change to the directory containing the scripts.

6. For each application, enter the following command and then run the appropriate scripts:
   
   sqlplus /as sysdba

   Note: To capture the output of each command to a log file, run the following commands before starting this task:

   sql> spool on

   sql> spool <output_file>

   where <output_file> is the full path and name of the file where the output is captured.

   When you have completed this task, run the following command: sql> spool off
   

7. Activities: Wizards/connections.sql/activities/oracle

   1. @upgrade-30-301.sql

   2. @appGrants.sql
      

8. Blogs: Wizards/connections.sql/blogs/oracle

   1. @upgrade-30-301.sql

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

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

        <jdbc_library_location>/ojdbc5.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:oracle:thin:@//<dbHost>:<dbPort>/<ServiceName> | -dburl jdbc:oracle:thin:@<dbHost>:<dbPort>:<SID>

        -dbuser <dbUser> -dbpassword <dbPassword>

        Note: Enter the appropriate dburl parameter depending on whether you are using SERVICE_NAME or SID.
        

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

        <jdbc_library_location>\ojdbc5.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:oracle:thin:@//<dbHost>:<dbPort>/<dbInstance> | -dburl jdbc:oracle:thin:@<dbHost>:<dbPort>:<SID>

        -dbuser <dbUser> -dbpassword <dbPassword>

        Note: Enter the appropriate dburl parameter depending on whether you are using SERVICE_NAME or SID.
        

      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. @appGrants.sql
      

9. Communities: Wizards/connections.sql/communities/oracle

   1. @upgrade-30-301.sql

   2. @appGrants.sql
      

10. Dogear: Wizards/connections.sql/dogear/oracle

    1. @upgrade-30-301.sql
       

    2. @appGrants.sql
       

11. Files: Wizards/connections.sql/files/oracle

    1. @upgrade-30-301.sql
       

    2. @appGrants.sql
       

12. Forum: Wizards/connections.sql/forum/oracle

    1. @upgrade-30-301.sql
       

    2. @appGrants.sql
       

13. Home page: Wizards/connections.sql/homepage/oracle

    1. @upgrade-30-301.sql
       

    2. @appGrants.sql
       

14. Profiles: Wizards/connections.sql/profiles/oracle

    1. @upgrade-30-301.sql
       

    2. @appGrants.sql
       

15. Wikis: Wizards/connections.sql/wikis/oracle

    1. @upgrade-30-301.sql
       

    2. @appGrants.sql
       

What to do next

Check that all the databases are working correctly.

Parent topic

Update 3.0 databases manually

+

Search Tips   |   Advanced Search