Manually update IBM® Connections 5.0 or 5.5
databases to version 6.0 in an existing IBM
WebSphere® Application Server and Oracle database
environment.
Before you begin
Before you apply updates, back up your
databases. For more information, see Backing up IBM Connections.
Ensure that you install and configure all
supporting software for version 6.0 CR1.
(Oracle only) Ensure
that the Statement cache size for the data sources on WebSphere Application
Server is no larger than 50. A higher value could lead to Out Of Memory
errors on the application server instance.
(Oracle only) IBM Connections databases use SMALLFILE
tablespaces that have a size limitation of 222 blocks. When you use 8 KB blocks, this
limit is approximately 32 GB. If you anticipate needing more space, add tablespace files to
individual databases. For detailed information, refer to your Oracle documentation. Also, please
consult the following tech note that contains a collection of fixes for older wizard packages: http://www-01.ibm.com/support/docview.wss?uid=swg21969290
About this task
Update IBM Connections version 5.0 or 5.5 databases to version 6.0 CR1 manually. 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, by using the instructions for your operating
system. For example, the relative path to the JRE on Microsoft
Windows might be Wizards\jvm\win\jre.
For AIX® or Linux, the
relative path might be Wizards/jvm/aix/jre and
Wizards/jvm/linux/jre.
- IBM Connections
does not support GNU Java.
- You need to use a database administrator ID to
run the Java migration utilities that are described in this
task.
- After you run each command, examine the output of the command for error messages. If you find
errors, resolve them before you continue with the update process.
- To improve readability, some commands and file paths in are displayed on separate lines. Ignore
these formatting conventions when you enter the commands.
To update databases manually, complete the
following steps:
Procedure
- Log in to the WebSphere Application Server
Integrated Solutions Console on your Deployment Manager.
- Go to .
- Stop all IBM Connections applications.
- Ensure that the Oracle driver on your system has the same version number as your Oracle
database server.
- Change to the directory that contains the scripts.
- 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
To manually create the application database
tables, complete the following steps:
Note: If your database version of IBM Connections components
are already at a given schema version, then run scripts from that schema version level.
- Change to the Activities SQL scripts directory
Wizards/connections.sql/activities/oracle, and then check for the database
schema version as follows:
select DBSCHEMAVER from ACTIVITIES.OA_SCHEMA
- If schema version is 69, then enter the following
commands:
@upgrade-50-50CR1.sql
@upgrade-50CR1-55.sql
@upgrade-55-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 72, then enter the following
commands:
@upgrade-50CR1-55.sql
@upgrade-55-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 94, then enter the following
commands:
@upgrade-55-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 98, then enter the following
commands:
@upgrade-55CR2-60.sql
@appGrants.sql
- Change to the Blogs SQL scripts directory
Wizards/connections.sql/blogs/oracle, and then check for the database schema
version as follows:
select value from BLOGS.roller_properties where name=
'database.schema.version'
- If schema version is 69, then enter the following
commands:
@upgrade-50-50CR1.sql
@upgrade-50CR1-50CR2.sql
@upgrade-50CR2-55.sql
@upgrade-55-60.sql
@appGrants.sql
- If schema version is 70, then enter the following
commands:
@upgrade-50CR1-50CR2.sql
@upgrade-50CR2-55.sql
@upgrade-55-60.sql
@appGrants.sql
- If schema version is 72, then enter the following
commands:
@upgrade-50CR2-55.sql
@upgrade-55-60.sql
@appGrants.sql
- If schema version is 75, then enter the following
commands:
@upgrade-55-60.sql
@appGrants.sql
- Change to Bookmarks SQL scripts directory
Wizards/connections.sql/dogear/oracle, and then check for the database schema
version as follows:
select DBSCHEMAVER from DOGEAR.DOGEAR_SCHEMA
- Change to the Communities SQL scripts directory
Wizards/connections.sql/communities/oracle, and then check the database schema
version as follows:
select DBSCHEMAVER from SNCOMM.SNCOMM_SCHEMA
- If schema version is 93, then enter the following
commands:
@upgrade-50-50CR2.sql
@upgrade-50CR2-55.sql
@upgrade-55-60.sql
@appGrants.sql
- If schema version is 98, then enter the following
commands:
@upgrade-50CR2-55.sql
@upgrade-55-60.sql
@appGrants.sql
- If schema version is 104, then enter the following
commands:
@upgrade-55-60.sql
@appGrants.sql
- Change to the Calendar SQL scripts directory
Wizards/connections.sql/communities/oracle, and then check the database schema
version as follows:
select DBSCHEMAVER from CALENDAR.CA_SCHEMA
- If schema version is 29, then enter the following
commands:
@calendar-upgrade-50-50CR1.sql
@calendar-upgrade-50CR1-55.sql
@calendar-upgrade-55-60.sql
@calendar-appGrants.sql
- If schema version is 30, then enter the following
commands:
@calendar-upgrade-50CR1-55.sql
@calendar-upgrade-55-60.sql
@calendar-appGrants.sql
- If schema version is 34, then enter the following
commands:
@calendar-upgrade-55-60.sql
@calendar-appGrants.sql
- Change to the Files SQL scripts directory Wizards/connections.sql/files/oracle, and then check the database schema version as
follows:
select SCHEMA_VERSION from "FILES"."PRODUCT"
- If schema version is 107, then enter the following
commands:
@upgrade-50-55.sql
@upgrade-55-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 139, then enter the following
commands:
@upgrade-55-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 140, then enter the following
commands:
@upgrade-55CR2-60.sql
@appGrants.sql
Note: Do not run the following scripts for the Files application:
- pns-createDb50.sql
- pns-dropDb.sql
- Change to the push notification scripts directory
Wizards/connections.sql/pushnotification/oracle, and check the database schema
version as follows:
select SCHEMA_VERSION from PUSHNOTIFICATION.PRODUCT
- If you cannot connect to PUSHNOTIFICATION, switch to
Wizards/connections.sql/files/oracle, and enter the following command:
@pns-dropDb.sql
Then switch back to
Wizards/connections.sql/pushnotification/oracle, and enter the following
commands:
@createDb.sql
@appGrants.sql
- If schema version is 7, then enter the following
commands:
@upgrade-55-60.sql
@appGrants.sql
- Change to the Forum SQL scripts directory
Wizards/connections.sql/forum/oracle, and then check the database schema
version as follows:
select DBSCHEMAVER from FORUM.DF_SCHEMA
- If schema version is 35, then enter the following
commands:
@upgrade-50-50CR1.sql
@upgrade-50CR1-55.sql
@upgrade-55-60.sql
@appGrants.sql
- If schema version is 36, then enter the following
commands:
@upgrade-50CR1-55.sql
@upgrade-55-60.sql
@appGrants.sql
- If schema version is 38, then enter the following
commands:
@upgrade-55-60.sql
@appGrants.sql
- Change to the home page SQL scripts directory
Wizards/connections.sql/homepage/oracle, and then check the database schema
version as follows:
select DBSCHEMAVER from HOMEPAGE.HOMEPAGE_SCHEMA
- If schema version is 475 , then enter the following
commands:
@upgrade-50-50CR1
@upgrade-50CR1-50CR2.sql
@upgrade-50CR2-50CR3.sql
@upgrade-50CR3-50CR4.sql
@upgrade-50CR4-55.sql
@upgrade-55-55CR1.sql
@upgrade-55CR1-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 477, then enter the following
commands:
@upgrade-50CR1-50CR2.sql
@upgrade-50CR2-50CR3.sql
@upgrade-50CR3-50CR4.sql
@upgrade-50CR4-55.sql
@upgrade-55-55CR1.sql
@upgrade-55CR1-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 478 , then enter the following
commands:
@upgrade-50CR2-50CR3.sql
@upgrade-50CR3-50CR4.sql
@upgrade-50CR4-55.sql
@upgrade-55-55CR1.sql
@upgrade-55CR1-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 479, then enter the following
commands:
@upgrade-50CR3-50CR4.sql
@upgrade-50CR4-55.sql
@upgrade-55-55CR1.sql
@upgrade-55CR1-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 705, then enter the following
commands:
@upgrade-55-55CR1.sql
@upgrade-55CR1-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 706, then enter the following
commands:
@upgrade-55CR1-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 707, then enter the following
commands:
@upgrade-55CR2-60.sql
@appGrants.sql
Next, you need to run a java migration from 5.0 to 5.5.
- Change to the Metrics SQL scripts directory
Wizards/connections.sql/metrics/oracle, and then check the database schema as
follows:
select SCHEMA_VERSION from "METRICS"."PRODUCT"
- Change to the Mobile SQL scripts directory
Wizards/connections.sql/mobile/oracle, and then check the database schema
version as follows:
select VALUE from MOBILE.ROLLER_PROPERTIES where NAME='database.schema.version'
- Change to the Profiles SQL scripts directory
Wizards/connections.sql/profiles/oracle, and then check the database schema
version as follows:
select DBSCHEMAVER from EMPINST.SNPROF_SCHEMA
- Change to the Wikis SQL scripts directory
Wizards/connections.sql/wikis/oracle, and then check the database schema
version as follows:
select SCHEMA_VERSION from "WIKIS"."PRODUCT"
- If schema version is 107, then enter the following
commands:
@upgrade-50-55.sql
@upgrade-55-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 139, then enter the following
commands:
@upgrade-55-55CR2.sql
@upgrade-55CR2-60.sql
@appGrants.sql
- If schema version is 140, then enter the following
commands:
@upgrade-55CR2-60.sql
@appGrants.sql
- Next, update databases to the CR1 level as explained in the IBM technote, Updating the IBM Connections 6.0 databases to the required schema versions for Cumulative Refresh 1
(CR1).
What to do next
Check that all the databases are working
correctly.