Update 2.5 databases side-by-side 

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

About this task

You can continue to use your 2.5 databases until you are ready to use IBM Connections 3.0.1.

To update the databases...

Procedure

1. Use the Lotus Connections 2.5 database wizard to create target 2.5 databases on a separate system. These new databases host your data for migration to the 3.0.1 databases. If the 2.5 database wizard is not on the target database system, copy it from the server hosting Lotus Connections 2.5.
2. Copy the 3.0.1 database wizard from the server hosting IBM Connections 3.0.1. You will need this wizard for the database migration.
3. (DB2 on Windows™ 2008 64-bit) On Windows 2008, perform DB2 administration tasks with full administrator privileges.
a. 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.
b. Enter the following command: db2cwadmin.bat. This command opens the DB2 Command Line Processor while also setting your DB2 privileges.

4. Prepare the target 2.5 databases to accept data migrated from the source 2.5 databases: Remove constraints from the target databases by executing the following SQL scripts for the applications that you are migrating:

Notes:

• Run these SQL scripts before transferring data to the target database.

• Run each script from the same directory that is used to create the target database.

• Lotus Connections uses the following database libraries, which are already on the target database server:

  • DB2

    • db2jcc.jar

    • db2jcc_license_cu.jar
      

  • Oracle

    • ojdbc5.jar
      

Repeat the following procedures for each application that you are migrating:

• DB2:
  a. Log in as the instance owner. The default owner on AIX and Linux™ is db2inst1. On Windows, the default is db2admin,
  b. For each application, change to the directory where the application scripts are stored and enter the appropriate commands, as shown in the following table:
  Table 1. DB2 commands for removing constraints

  Feature	Directory	DB2 commands
  Activities	/connections.sql/activities/db	db2 -tvf predbxfer25.sql
  Blogs	/connections.sql/blogs/db2	db2 -tvf predbxfer25.sql
  Communities	/connections.sql/communities/db2	db2 -td@ -vf predbxfer25.sql db2 -td@ -vf predbxfer25_forum.sql
  Dogear	/connections.sql/dogear/db2	db2 -tvf predbxfer25.sql
  Files	/connections.sql/files/db2	db2 -td@ -vf predbxfer25.sql
  Home page	/connections.sql/homepage/db2	db2 -tvf predbxfer25.sql
  Profiles	/connections.sql/profiles/db2	db2 -tvf predbxfer25.sql
  Wikis	/connections.sql/wikis/db2	db2 -td@ -vf predbxfer25.sql

• Oracle:
  a. Change to the directory containing the scripts, as shown in the following table.
  b. For each application, enter the following commands and then run the appropriate scripts:
  i. sqlplus /NOLOG
  ii. conn system/<password>@<SID>
  iii. @<SQL_script>.sql
  where <password> is the password for the user "system", <SID> is the Oracle System Identifier for Lotus Connections, and <SQL_script> refers to an SQL script.
  
  Table 2. Oracle commands for removing constraints

  Feature	Directory	Oracle commands
  Activities	/connections.sql/activities/oracle	@predbxfer25.sql
  Blogs	/connections.sql/blogs/oracle	@predbxfer25.sql
  Communities	/connections.sql/communities/oracle	@predbxfer25.sql @predbxfer25_forum.sql
  Dogear	/connections.sql/dogear/oracle	@predbxfer25.sql
  Files	/connections.sql/files/oracle	@predbxfer25.sql
  Home page	/connections.sql/homepage/oracle	@predbxfer25.sql
  Profiles	/connections.sql/profiles/oracle	@predbxfer25.sql
  Wikis	/connections.sql/wikis/oracle	@predbxfer25.sql

• SQL Server 2005
  a. Log in as the database administrator
  b. Change to the directory containing the scripts
  c. For each application, 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 in the table: -S <sqlserver_server_name>\<sqlserver_server_instance_name>
  
  Table 3. SQL Server commands for removing constraints

  Feature	Directory	SQL Server commands
  Activities	/connections.sql/activities/sqlserver	sqlcmd -U sa -P <password> -i "predbxfer25.sql"
  Blogs	/connections.sql/blogs/sqlserver	sqlcmd -U sa -P <password> -i "predbxfer25.sql"
  Communities	/connections.sql/communities/sqlserver	sqlcmd -U sa -P <password> -i "predbxfer25.sql" sqlcmd -U sa -P <password> -i "predbxfer25_forum.sql"
  Dogear	/connections.sql/dogear/sqlserver	sqlcmd -U sa -P <password> -i "predbxfer25.sql"
  Files	/connections.sql/files/sqlserver	sqlcmd -U sa -P <password> -i "predbxfer25.sql"
  Home page	/connections.sql/homepage/sqlserver	sqlcmd -U sa -P <password> -i "predbxfer25.sql"
  Profiles	/connections.sql/profiles/sqlserver	sqlcmd -U sa -P <password> -i "predbxfer25.sql"
  Wikis	/connections.sql/wikis/sqlserver	sqlcmd -U sa -P <password> -i "predbxfer25.sql"

5. Transfer data to the target databases, using the database transfer tool:

a. Copy the dbt.jar file from the Lotus_Connections_Install\ConfigEngine\lib directory to <DBT_HOME> on the target database server, where <DBT_HOME> is the path to the directory that contains the dbt.jar file.
Note:

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

• Lotus Connections does not support GNU Java.
  

b. 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="<application_db_schema_name>"
dbType="<dbType>"/>
<database role="target"
driver="<JDBC_driver>"
url="<JDBC_url>"
userId="database admin user ID" 
schema="<application_db_schema_name>" 
dbType="< dbType >"/>
</dbTransfer>

where <JDBC_driver> is one of the following types:

• 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 types:

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

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

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

where <application_database_name> is one of the following:

• Activities: OPNACT

• Blogs: BLOGS

• Communities: SNCOMM

• Dogear: DOGEAR

• Files: FILES

• Home page: HOMEPAGE

• Profiles: PEOPLEDB

• Wikis: WIKIS
  

where <application_db_schema> is one of the following:

• Activities: ACTIVITIES

• Blogs: BLOGS

• Communities: SNCOMM

• Dogear: DOGEAR

• Files: FILES

• Home page: HOMEPAGE

• Profiles: EMPINST

• Wikis: WIKIS
  

where <dbType> is one of the following:

• DB2: DB2

• Oracle: oracle

• SQL Server: sqlserver2005
  

c. Prepare the JDBC driver of the target databases for transfer:

• DB2:

  • Use the JDBC driver on the target database server.
    

• Oracle:

  • Use the JDBC driver on the target database server.

  • Ensure that the Oracle driver on your system has the same version number as your Oracle database server. Lotus Connections does not support the Oracle 10.2.0.1 JDBC driver.
    

• SQL Server

  • Download the http://www.microsoft.com/downloads/details.aspx?FamilyID=C47053EB-3B64-4794-950D-81E1EC91C1BA">SQL Server 2005 JDBC 1.2 driver from the Microsoft Web site and follow the instructions to extract the driver files.
    

d. 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/ojdbc5.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 directory where log files are stored. Create the <logs> directory 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\ojdbc5.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 directory where log files are stored.

  When the transfer is complete, you can restart the 2.5 applications to minimize service downtime.
  
  Note: Data that is generated after restarting the 2.5 environment is not migrated.

6. Reapply constraints to the target application databases by performing the procedures in the following table for the application databases that you migrated:

• DB2:
  a. Log in as the instance owner.
  b. For each application, change to the directory where the application script is stored and enter the appropriate commands for each application, as shown in the following table:
  Table 4. DB2 commands for reapplying constraints

  Application	Directory	DB2 commands
  Activities	/connections.sql/activities/db2	db2 -tvf postdbxfer25.sql db2 -tvf clearScheduler.sql
  Blogs	/connections.sql/blogs/db2	db2 -tvf postdbxfer25.sql
  Communities	/connections.sql/communities/db2	db2 -td@ -vf postdbxfer25.sql db2 -td@ -vf postdbxfer25_forum.sql db2 -td@ -vf clearScheduler.sql
  Dogear	/connections.sql/dogear/db2	db2 -tvf postdbxfer25.sql
  Files	/connections.sql/files/db2	db2 -td@ -vf postdbxfer25.sql
  Home page	/connections.sql/homepage/db2	db2 -tvf postdbxfer25.sql db2 -tvf clearScheduler.sql
  Profiles	/connections.sql/profiles/db2	db2 -tvf postdbxfer25.sql
  Wikis	/connections.sql/wikis/db2	db2 -td@ -vf postdbxfer25.sql

• Oracle:
  a. Change to the directory containing the scripts, as shown in the following table.
  b. For each application, enter the following commands and then run the appropriate scripts
  i. sqlplus /NOLOG
  ii. conn system/<password>@<SID>
  iii. @<SQL_script>.sql
  where <password> is the password for the user "system", <SID> is the Oracle System Identifier for Lotus Connections, and <SQL_script> refers to an SQL script.
  
  Table 5. Oracle commands for reapplying constraints

  Application	Directory	Oracle commands
  Activities	/connections.sql/activities/oracle	@postdbxfer25.sql @clearScheduler.sql
  Blogs	/connections.sql/blogs/oracle	@postdbxfer25.sql
  Communities	/connections.sql/communities/oracle	@postdbxfer25.sql @postdbxfer25_forum.sql @clearScheduler.sql
  Dogear	/connections.sql/dogear/oracle	@postdbxfer25.sql
  Files	/connections.sql/files/oracle	@postdbxfer25.sql
  Home page	/connections.sql/homepage/oracle	@postdbxfer25.sql @clearScheduler.sql
  Profiles	/connections.sql/profiles/oracle	@postdbxfer25.sql
  Wikis	/connections.sql/wikis/oracle	@postdbxfer25.sql

• SQL Server 2005
  a. Log in as the database administrator
  b. Change to the directory containing the scripts
  c. For each application, 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 in the table:
  -S <sqlserver_server_name>\<sqlserver_server_instance_name>
  
  Table 6. SQL Server commands for reapplying constraints

  Application	Directory	SQL Server commands
  Activities	/connections.sql/activities/sqlserver	sqlcmd -U sa -P <password> -i "postdbxfer25.sql" sqlcmd -U sa -P <password> -i "clearScheduler.sql"
  Blogs	/connections.sql/blogs/sqlserver	sqlcmd -U sa -P <password> -i "postdbxfer25.sql"
  Communities	/connections.sql/communities/sqlserver	sqlcmd -U sa -P <password> -i "postdbxfer25.sql" sqlcmd -U sa -P <password> -i "postdbxfer25_forum.sql" sqlcmd -U sa -P <password> -i "clearScheduler.sql"
  Dogear	/connections.sql/dogear/sqlserver	sqlcmd -U sa -P <password> -i "postdbxfer25.sql"
  Files	/connections.sql/files/sqlserver	sqlcmd -U sa -P <password> -i "postdbxfer25.sql"
  Home page	/connections.sql/homepage/sqlserver	sqlcmd -U sa -P <password> -i "postdbxfer25.sql" sqlcmd -U sa -P <password> -i "clearScheduler.sql"
  Profiles	/connections.sql/profiles/sqlserver	sqlcmd -U sa -P <password> -i "postdbxfer25.sql"
  Wikis	/connections.sql/wikis/sqlserver	sqlcmd -U sa -P <password> -i "postdbxfer25.sql"

7. (Profiles only.) Run the following commands to update the database sequence for DB2 or Oracle target databases:

• DB2
  Run the following commands on the 2.5 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 2.5 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 2.5 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 2.5 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 2.5 database.

8. Update the databases to IBM Connections version 3.0.1, using either the database wizard or the SQL scripts in the IBM Connections set-up directory or installation media. For more information, see the Update 2.5 databases with the wizard and Update 2.5 databases manually topics.

What to do next

Check that all the databases are working correctly, and then migrate Lotus Connections version 2.5 to version 3.0.1.

Note: Any data that you generate after restarting your 2.5 deployment will not migrated to the new environment.

(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 2.5 databases

Related tasks
Update 2.5 databases in-place
Update 2.5 databases with the wizard
Update 2.5 databases manually
Restore databases

+

Search Tips   |   Advanced Search