Home

 

Updating databases side-by-side


Overview

Update your Lotus Connections 2.0.1 databases to release 2.5 in a side-by-side procedure where your Lotus Connections 2.0.1 deployment remains intact.

Create a database instance on a new system.

You can continue to use your 2.0.1 databases until you are ready to migrate to Lotus Connections 2.5.


Update the databases

  1. Use the Lotus Connections 2.0.1 database wizard to create new destination databases on a separate system.

  2. If you are updating the Profiles database and changing the source database type from Oracle to IBM DB2 or Microsoft SQL Server, copy the fixup201prexfer.sql file from...

      Wizards/connections.sql/profiles/oracle

    ...on the Lotus Connections 2.5 installation media to the database server hosting your Lotus Connections 2.0.1 database for Profiles and run...

      sqlplus /NOLOG
      conn system/<password>@<sid>
      @fixup201prexfer.sql

  3. Remove constraints from the new databases by executing the following SQL scripts for the features that you are migrating. Run the SQL scripts from the Lotus Connections 2.0.1 installation media.

    • DB2:

      1. Log in as the administrator.

      2. For each feature, change to the where the feature scripts are stored and enter the appropriate commands, as shown in the following table:

        Feature Directory DB2 commands
        Activities /connections.sql/activities/db2 db2 -tvf uninteg.sql db2 connect to OPNACT
        cd /connections.sql/activities/shared
        db2 -tvf predbxfer.sql
        db2 connect reset
        Blogs /connections.sql/blogs/db2 db2 -tvf disableFK.sql
        db2 -tvf predbxfer.sql
        db2 connect reset
        Communities /connections.sql/communities/db2 db2 -tvf integOff.sql
        db2 -tvf uninteg_forum.sql
        db2 -tvf predbxfer.sql
        db2 -tvf predbxfer_forum.sql
        db2 connect reset
        Dogear /connections.sql/dogear/db2 db2 -tvf integOff.sql
        db2 -tvf predbxfer.sql
        db2 connect reset
        Home page /connections.sql/homepage/db2 db2 -tvf integOff.sql
        db2 -tvf deleteAllRows.sql
        db2 connect reset
        Profiles /connections.sql/profiles/db2 db2 connect to PEOPLEDB
        db2 -tvf predbxfer.sql
        db2 connect reset

    • Oracle:

      1. Change to the containing the scripts, as shown in the following table.

      2. For each feature, enter the following commands and then run the appropriate scripts:

          sqlplus /NOLOG conn system/<password>@<sid>

        where <password> is the password for the user "system" and <sid> is the Oracle System Identifier for Lotus Connections.


        Oracle commands for removing constraints

        Feature Directory Oracle commands
        Activities /connections.sql/activities/oracle @oraIntegOff.sql
        cd /connections.sql/activities/shared Run the following commands:
        @predbxfer.sql
        quit
        Blogs /connections.sql/blogs/oracle @disableFK.sql
        @predbxfer.sql
        quit
        Communities /connections.sql/communities/oracle @oraIntegOff.sql
        @oraIntegOff_forum.sql
        @predbxfer.sql
        @predbxfer_forum.sql
        Dogear /connections.sql/dogear/oracle @oraIntegOff.sql
        @predbxfer.sql
        quit
        Home page /connections.sql/homepage/oracle @integOff.sql
        @deleteAllRows.sql
        quit
        Profiles /connections.sql/profiles/oracle @predbxfer.sql
        quit

    • SQL Server 2005

      1. Login in as administrator

      2. Change to the containing the scripts

      3. For each feature, run the appropriate scripts by entering the commands shown in the following table:

        In these commands, <password> is the password for the SQL Server user "sa". If your database server has multiple SQL Server instances installed, add the following parameter as the first parameter to each command below:

          <sqlserver_server_name>\<sqlserver_server_instance_name>

        SQL Server commands for removing constraints

        Feature Directory SQL Server commands
        Activities /connections.sql/activities/sqlserver sqlcmd -U sa -P <password> -i integOff.sql sqlcmd -U sa -P <password> -i deleteAllRows.sql
        Blogs /connections.sql/blogs/sqlserver sqlcmd -U sa -P <password> -i integOff.sql sqlcmd -U sa -P <password> -i deleteAllRows.sql
        Communities /connect ons.sql/communities/sqlserver sqlcmd -U sa -P <password> -i integOff.sql sqlcmd -U sa -P <password> -i integOff_forum.sql sqlcmd -U sa -P <password> -i predbxfer.sql sqlcmd -U sa -P <password> -i deleteAllRows_forum.sql
        Home page /connections.sql/homepage/sqlserver sqlcmd -U sa -P <password> -i integOff.sql sqlcmd -U sa -P <password> -i deleteAllRows.sql
        Dogear /connections.sql/dogear/sqlserver sqlcmd -U sa -P <password> -i integOff.sql sqlcmd -U sa -P <password> -i predbxfer.sql
        Profiles /connections.sql/profiles/sqlserver sqlcmd -U sa -P <password> -i integOff.sql sqlcmd -U sa -P <password> -i deleteAllRows.sql

  4. Transfer data to the new databases, using the database transfer tool:

    1. Copy the dbt.jar file from the Lotus_Connections_Install\ConfigEngine\lib to <DBT_HOME> on the production database server, where <DBT_HOME> is the path to the that contains the dbt.jar file.

    2. Create an XML configuration file under <DBT_HOME>:

        <dbTransfer xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <database role="source" driver="<JDBC_driver>" url="<JDBC_url>" userId="database admin user ID" schema="<feature_db_schema_name>" dbType="< dbType >"/>
        <database role="target" driver="<JDBC_driver>" url="<JDBC_url>" userId="database admin user ID" schema="<feature_db_schema_name>" commitFrequency="50" dbType="< dbType >"/>
        </dbTransfer>

      where <JDBC_driver> is one of the following:

      • DB2: com.ibm.db2.jcc.DB2Driver

      • Oracle: oracle.jdbc.driver.OracleDriver

      • SQL Server: com.microsoft.sqlserver.jdbc.SQLServerDriver

      where <JDBC_url> is one of the following:

      • DB2: jdbc:db2://<host_IP>:<port>/<feature_database_name>

      • Oracle: jdbc:oracle:thin:@<host_IP>:<port>:<SID>

      • SQL Server: jdbc:sqlserver://<host_IP>:<port>;databaseName=<feature_database_name>

      where <feature_database_name> is one of the following:

      where <feature_db_schema> is one of the following:

      • Activities:

        ACTIVITIES

      • Blogs:

        BLOGS

      • Communities:

        SNCOMM

      • Dogear:

        DOGEAR

      • Home page:

        HOMEPAGE

      • Profiles:

        EMPINST

        ,

        SNCORE

        ( transfer data twice for these two schemas)

      where <dbType> is one of the following:

      • DB2:

        DB2

      • Oracle:

        oracle

      • SQL Server:

        sqlserver2005

    3. Prepare the JDBC driver of the 2.5 databases for transfer:

      • DB2:

        • Use the JDBC driver on the 2.5 database server.

      • Oracle:

        • Use the JDBC driver on the 2.5 database server.

      • SQL Server

        • Use the Microsoft SQL Server 2005 JDBC 1.1 driver (download the driver from the Microsoft Web site).

    4. To perform the data transfer, run the dbt.jar file:

      • Linux

          "<JAVA_HOME>/bin/java" 
          -cp <DBT_HOME>/dbt.jar:
          <DB2_HOME>/java/db2jcc.jar:
          <DB2_HOME>/java/db2jcc_license_cu.jar:
          <SQLSERVER_DRIVER_PATH>:
          <ORACLE_HOME>/jdbc/lib/ojdbc14.jar  com.ibm.wps.config.db.transfer.CmdLineTransfer 
          -logDir <DBT_HOME>/logs 
          -xmlfile <DBT_HOME>/<dbt_config_file_name> 
          -sourcepassword <source_db_password> 
          -targetpassword <target_db_password>
          

        where <dbt_config_file_name> is the name of the XML configuration file you created for the dbt.jar file, and <logs> is the where log files are stored. You should create the <logs> before running this file.

      • Windows

          "<JAVA_HOME>\bin\java" 
          -cp <DBT_HOME>\dbt.jar;
          <DB2_HOME>\java\db2jcc.jar;
          <DB2_HOME>\java\db2jcc_license_cu.jar;
          <SQLSERVER_DRIVER_PATH>;
          <ORACLE_HOME>\jdbc\lib\ojdbc14.jar  com.ibm.wps.config.db.transfer.CmdLineTransfer 
          -logDir <DBT_HOME>\logs 
          -xmlfile <DBT_HOME>/<dbt_config_file_name> 
          -sourcepassword <source_db_password> 
          -targetpassword <target_db_password>
          

        where <dbt_config_file_name> is the name of the XML configuration file that you created for the dbt.jar file, and <logs> is the where log files are stored.

      When the transfer is complete, you can restart the 2.0.1 features to minimize service downtime.

      If the update fails and you receive an error message with DB2 SQLCODE -1476, the log file is full. Increase the size of the log file and run the update again. You can check the current size of the log file by running the following command:

      db2 get db cfg for <feature_db_name>|grep -i logfilsiz

      Increase the size of the log file by running the following command:

      db2 update db cfg for <feature_db_name> USING logfilsiz 5000

      db2 update db cfg for <feature_db_name> using logprimary 25

      db2 update db cfg for <feature_db_name> using logsecond 50

      where <feature_db_name> is one of the following:

  5. Reapply constraints to the new 2.0.1 databases by executing the following SQL scripts for features that you are migrating. Run the SQL scripts from the Lotus Connections 2.0.1 installation media.

    You must use the Java™ Virtual Machine (JVM) under the Wizards in the installation media. To use your own JVM, ensure that the build date of the JVM is later than 20070831.

    • DB2:

      1. Log in as the administrator.

      2. For each feature, change to the where the feature script is stored and enter the appropriate commands for each feature, as shown in the following table:


        DB2 commands for reapplying constraints

        Feature Directory DB2 commands
        Activities /connections.sql/activities/db2 db2 -tvf integ.sql
        Blogs /connections.sql/blogs/db2 db2 -tvf enableFK.sql
        Communities /connections.sql/communities/db2 db2 -td@ -vf integOn.sql
        db2 -tvf integ_forum.sql
        db2 connect reset
        Dogear /connections.sql/dogear/db2 db2 -tvf iteg.sql
        Home page /connections.sql/homepage/db2 db2 -tvf integOn.sql
        Profiles /connections.sql/profiles/db2 db2 connect to PEOPLEDB
        db2 -tvf postdbxfer.sql
        db2 connect reset

    • Oracle:

      1. Change to the containing the scripts, as shown in the following table.

      2. For each feature, enter the following commands and then run the appropriate scripts:

          sqlplus /NOLOG conn system/<password>@<sid>

        where <password> is the password for the user "system" and <sid> is the Oracle System Identifier for Lotus Connections.


        Oracle commands for reapplying constraints

        Feature Directory Oracle commands
        Activities /connections.sql/activities/oracle @oraIntegOn.sql
        Blogs /connections.sql/blogs/oracle @enableFK.sql
        quit
        Communities /connections.sql/communities/oracle @oraIntegOn.sql
        @oraIntegOn_forum.sql
        quit
        Dogear /connections.sql/dogear/oracle @oraIntegOn.sql
        quit
        Home page /connections.sql/homepage/oracle @integOn.sql
        quit
        Profiles /connections.sql/profiles/oracle @postdbxfer.sql
        quit

    • SQL Server 2005

      1. Login in as administrator

      2. Change to the containing the scripts

      3. For each feature, run the appropriate scripts by entering the commands shown in the following table:

        In these commands, <password> is the password for the SQL Server user "sa". If your database server has multiple SQL Server instances installed, add the following parameter as the first parameter to each command below:

          S<sqlserver_server_name>\<sqlserver_server_instance_name>


        SQL Server commands for reapplying constraints

        Feature Directory SQL Server commands
        Activities /connections.sql/activities/sqlserver sqlcmd -U sa -P <password> -i integOn.sql
        Blogs /connections.sql/blogs/sqlserver sqlcmd -U sa -P <password> -i integOn.sql
        Communities /connect ons.sql/communities/sqlserver sqlcmd -U sa -P <password> -i integOn.sql sqlcmd -U sa -P <password> -i integOn_forum.sql
        Dogear /connections.sql/dogear/sqlserver sqlcmd -U sa -P <password> -i integOn.sql
        Home page /connections.sql/homepage/sqlserver sqlcmd -U sa -P <password> -I integOn.sql
        Profiles /connections.sql/profiles/sqlserver sqlcmd -U sa -P <password> -i integOn.sql

  6. (Profiles only.) Run the following commands to update the database sequence for DB2 and Oracle databases:

    • DB2

      • Run the following commands on the source database:

          SELECT NEXT VALUE FOR EMPINST.CHG_EMP_DRAFT_SEQ AS CHG_EMP_DRAFT_SEQ FROM SYSIBM.SYSDUMMY1; SELECT NEXT VALUE FOR EMPINST.EMP_DRAFT_SEQ AS EMP_ DRAFT_SEQ FROM SYSIBM.SYSDUMMY1; SELECT NEXT VALUE FOR EMPINST.EXT_DRAFT_SEQ AS EXT DRAFT_SEQ FROM SYSIBM.SYSDUMMY1;

        Run the following commands on the target database:

          ALTER SEQUENCE EMPINST.CHG_EMP_DRAFT_SEQ RESTART WITH <query_result>; ALTER SEQUENCE EMPINST.EMP_DRAFT_SEQ RESTART WITH <query_result>; ALTER SEQUENCE EMPINST.EXT_DRAFT_SEQ RESTART WITH <query_result>;

    • Oracle

      • Run the following commands on the source database:

          SELECT EMPINST.EXT_DRAFT_SEQ.NEXTVAL FROM DUAL; SELECT EMPINST.EMP_DRAFT_SEQ.NEXTVAL FROM DUAL; SELECT EMPINST.CHG_EMP_DRAFT_SEQ1.NEXTVAL FROM DUAL; SELECT EMPINST.CHG_EMP_DRAFT_SEQ2.NEXTVAL FROM DUAL; SELECT SNCORE.STRUCT_IDENTITY_SEQ.NEXTVAL FROM DUAL;

        Run the following commands on the target database:

          DROP SEQUENCE EMPINST.EXT_DRAFT_SEQ; CREATE SEQUENCE EMPINST.EXT_DRAFT_SEQ START WITH <query_result>; DROP SEQUENCE EMPINST.EMP_DRAFT_SEQ; CREATE SEQUENCE EMPINST.EMP_DRAFT_SEQ START WITH <query_result>; DROP SEQUENCE EMPINST.CHG_EMP_DRAFT_SEQ1; CREATE SEQUENCE EMPINST.CHG_EMP_DRAFT_SEQ1 START WITH <query_result>; DROP SEQUENCE EMPINST.CHG_EMP_DRAFT_SEQ2; CREATE SEQUENCE EMPINST.CHG_EMP_DRAFT_SEQ2 START WITH <query_result>; DROP SEQUENCE SNCORE.STRUCT_IDENTITY_SEQ; CREATE SEQUENCE SNCORE.STRUCT_IDENTITY_SEQ START WITH <query_result>;

    where <query_result> is the result of the corresponding SELECT command that you ran on the source database.

  7. Update the databases to Lotus Connections release 2.5, using either the database wizard or the SQL scripts on the Lotus Connections installation media. For more information, see the Updating databases with the wizard and Updating databases manually topics.

If you plan to install the Files and Wikis features, create databases for them now, using the Lotus Connections 2.5 database wizard. Check that all the databases are working correctly, and then migrate Lotus Connections release 2.0.1 to release 2.5.

Data that you generate after restarting your 2.0.1 deployment will not migrated to the new environment.


Updating databases

 

Related tasks

Updating databases in-place

Restore databases


+

Search Tips   |   Advanced Search