When you migrate the IBM® Connections home page
database schema from 5.0 to 5.5, you must run a Java™
migration. You do not need to perform an equivalent 5.5 to 6.0 migration.
Procedure
-
Change to the directory where the database wizard is stored. The default location is the
Wizards directory on the installation media.
-
Run the migration command. See the examples for the syntax:
Note: Run the command on a single line and not as displayed, the examples are for
illustration.
-
DB2 LINUX/AIX
java
-Dfile.encoding=UTF-8
-Xmx1024m
-classpath
jdbc_library_location/db2jcc4.jar:
lib/news.migrate.jar:
lib/news.core.data.jar:
lib/lc.dbmigration.default.jar:
lib/commons-logging-1.0.4.jar
com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration
jdbc:db2://dbHost:dbPort/dbinstance
dbUser
dbPassword
db production > java.out.log 2>&1
-
DB2 Windows
jvm\win\jre\bin\java
-Dfile.encoding=UTF-8
-Xmx1024m
-classpath
jdbc_library_location\db2jcc.jar;
lib\news.migrate.jar;
lib\news.core.data.jar;
lib\lc.dbmigration.default.jar;
lib\commons-logging-1.0.4.jar
com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration
jdbc:db2://dbHost:dbPort/dbinstance
dbUser
dbPassword
db production > java.out.log 2>&1
-
Oracle Linux
java
-Dfile.encoding=UTF-8
-Xmx1024m
-classpath
jdbc_library_location/ojdbc6.jar:
lib/news.migrate.jar:
lib/news.core.data.jar:
lib/lc.dbmigration.default.jar:
lib/commons-logging-1.0.4.jar
com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration
jdbc:oracle:thin:@dbHost:dbPort/dbinstance
dbUser
dbPassword
oracle production > java.out.log 2>&1
-
Oracle Windows
jvm\win\jre\bin\java
-Dfile.encoding=UTF-8
-Xmx1024m
-classpath
jdbc_library_location\ojdbc6.jar;
lib\news.migrate.jar;
lib\news.core.data.jar;
lib\lc.dbmigration.default.jar;
lib\commons-logging-1.0.4.jar
com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration
jdbc:oracle:thin:@dbHost:dbPort/dbinstance
dbUser
dbPassword
oracle production > java.out.log 2>&1
-
SQL Server Windows
jvm\win\jre\bin\java
-Dfile.encoding=UTF-8
-Xmx1024m
-classpath
jdbc_library_location\sqljdbc4.jar;
lib\news.migrate.jar;
lib\news.core.data.jar;
lib\lc.dbmigration.default.jar;
lib\commons-logging-1.0.4.jar
com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration
jdbc:sqlserver://dbHost:dbPort;databaseName=HOMEPAGE
dbUser
dbPassword
sqlserver production > java.out.log 2>&1
Where:
- jdbc_library_location is the location of your JDBC driver.
- dbHost is the name of the system that hosts your database.
- dbPort is the communications port of the database.
- dbinstance is the DB instance "HOMEPAGE".
- dbUser is the database administrator ID.
- dbPassword is the administrator password.
Note: Additional parameters:
- "production" or "debug" are accepted values. Use the log produced with the debug option to debug
errors. If the output is correct, and is without errors, you can run the command again using
"production" instead of "debug".
- In Linux or AIX environments, use ':' instead of ';' as classpath separator.
- Verify the user grants for performing the script. The user must be able read the DB schema
value.
- The db schema version for HOMEPAGE database must be 475 or higher.
An example of the command for DB2 on Windows is as follows:
jvm\win\jre\bin\java -Dfile.encoding=UTF-8 -Xmx1024m -classpath C:\IBM\SQLLIB\java\db2jcc.jar;lib\news.migrate.jar;lib\news.core.data.jar;
lib\lc.dbmigration.default.jar;lib\commons-logging-1.0.4.jar com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration jdbc:
db2://dslvm1115.mul.ie.ibm.com:50000/HOMEPAGE db2admin passw0rd db production > java.out.log 2>&1
-
Verify the output in the java.out.log file created by the command. An
example of the output is as follows:
5-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrate
INFO: Using mode: production
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrate
INFO: Detected schema version: 706
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrate
INFO: Migrating entries to NR_COMMUNITIES_VIEW
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrateReaders
INFO: Found 15 missing readers in NR_COMMUNITIES_VIEW
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration restoreReaders
INFO: Restored 15 records.
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrate
INFO: Migrating comments to NR_COMMUNITIES_VIEW
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrateReaders
INFO: Found 0 missing readers in NR_COMMUNITIES_VIEW
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrate
INFO: Migrating entries to NR_PROFILES_VIEW
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrateReaders
INFO: Found 0 missing readers in NR_PROFILES_VIEW
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrate
INFO: Migrating entries to NR_STATUS_UPDATE_READERS
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrateReaders
INFO: Found 78 missing readers in NR_STATUS_UPDATE_READERS
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration restoreReaders
INFO: Restored 78 records.
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrate
INFO: Migrating comments to NR_PROFILES_VIEW
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrateReaders
INFO: Found 0 missing readers in NR_PROFILES_VIEW
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrate
INFO: Migrating comments to NR_STATUS_UPDATE_READERS
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration migrateReaders
INFO: Found 9 missing readers in NR_STATUS_UPDATE_READERS
15-Dec-2016 16:21:12 com.ibm.lconn.news.migration.next60.RestoreStatusUpdateMigration restoreReaders
INFO: Restored 9 records.