Updating 4.0 and 4.5 Oracle databases manually

Manually update IBM® Connections 4.0 or 4.5 databases to version 5.0 in an existing IBM WebSphere® Application Server and Oracle database environment.

Before you begin

Before applying updates, back up your databases. For more information, see Backing up IBM Connections.

Ensure that you have installed and configured all supporting software for version 5.0.

(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 2²² blocks. When you use 8 KB blocks, this limit is approximately 32 GB. If you anticipate needing more space than this, add additional tablespace files to individual databases. For detailed information, refer to your Oracle documentation.

About this task

This topic describes how to update IBM Connections version 4.0 or 4.5 databases to version 5.0 manually. Use this procedure if you want an alternative to using the database wizard to update your databases.

Notes:

This topic applies to all releases of version 4.0 and 4.5
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 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 need to use a database administrator ID to run the Java migration utilities described in this task.
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 improve readability, some commands and file paths in this topic are displayed on separate lines. Ignore these formatting conventions when entering 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 Applications > Application types > WebSphere enterprise Applications.
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 containing 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 start running scripts from that schema version level. For example, if the Activities database is schema version 56, enter the commands for schema version 56 and version 69.
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 the schema version is 53, then enter the following commands:
```
@upgrade-40-45.sql
@upgrade-45-50.sql
@appGrants.sql
```
- If schema version is 56, then enter the following commands:
```
@upgrade-45-50.sql 
@appGrants.sql
```
- If schema version is 69, then enter the following commands:
```
@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 the schema version is 43, then enter the following commands:
```
@upgrade-40-45.sql
@upgrade-45-45CR4.sql
@upgrade-45CR4-50.sql
@appGrants.sql
```
- If schema version is 51, then enter the following commands:
```
@upgrade-45-45CR4.sql
@upgrade-45CR4-50.sql
@appGrants.sql
```
- If schema version is 52, then enter the following commands:
```
@upgrade-45CR4-50.sql
@appGrants.sql
```
- If schema version is 69, then enter the following commands:
```
@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
```
- If the schema version is 14, then enter the following commands:
```
@upgrade-40-45.sql
@upgrade-45-50.sql
@appGrants.sql
```
- If schema version is 15, then enter the following command:
```
@upgrade-45-50.sql
@appGrants.sql
```
- If schema version is 22, then enter the following commands
```
@appGrants.sql
```
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 the schema version is 76, then enter the following commands:
```
@pgrade-40-45.sql
@upgrade-45-50.sql
@appGrants.sql
```
- If schema version is 77, then enter the following commands:
```
@upgrade-45-50.sql
@appGrants.sql
```
- If schema version is 92, then enter the following commands:
```
@appGrants.sql
```
Change to the Calendar SQL scripts directory Wizards/connections.sql/calendar/oracle, and then check the database schema version as follows:
```
select DBSCHEMAVER from CALENDAR.CA_SCHEMA
```
- If schema version is 10, then enter the following commands:
```
@calendar-upgrade-40-45.sql
@calendar-upgrade-45-50.sql 
@calendar-appGrants.sql 
```
- If schema version is 15, then enter the following commands:
```
@calendar-upgrade-45-50.sql
@calendar-appGrants.sql 
```
- If schema version is 29, then enter the following commands:
```
@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 the schema version is 79, then enter the following commands:
```
@upgrade-40-45.sql
@upgrade-45-45CR3.sql
@upgrade-45CR3-50.sql
@appGrants.sql
```
- If schema version is 82, then enter the following commands:
```
@upgrade-45-45CR3.sql
@upgrade-45CR3-50.sql
@appGrants.sql
```
- If schema version is 89, then enter the following commands:
```
@upgrade-45CR3-50.sql
@appGrants.sql
```
- If schema version is 107, then enter the following commands:
```
@appGrants.sql
```
In addition, create the tables for Push notification by running the following commands:
@application_subdirectory/pns-createDb.sql password

@application_subdirectory/pns-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 the schema version is 21, then enter the following commands:
```
@upgrade-40-45.sql
@upgrade-45-50.sql
@appGrants.sql
```
- If schema version is 27, then enter the following commands:
```
@upgrade-45-50.sql
@appGrants.sql
```
- If schema version is 35, then enter the following commands:
```
@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 the schema version is 110, then enter the following commands:
```
@upgrade-40-40CR2.sql
@upgrade-40CR2-45.sql
```
  Also, you need to run a java migration from 4.0 to 4.5.
  
  Then, resume executing the upgrade commands.
```
@upgrade-45-45CR3.sql
@upgrade-45CR3-45CR4.sql
@upgrade-45CR4-50.sql
```
  Next, you need to run a java migration from 4.5 to 5.0.
  
  Then, resume executing the upgrade commands
```
@appGrants.sql
```
- If schema version is 132, then enter the following command:
```
@upgrade-40CR2-45.sql
```
  Also, you need to run a java migration from 4.0 to 4.5.
  
  Then, resume executing the upgrade commands.
```
@upgrade-45-45CR3.sql
@upgrade-45CR3-45CR4.sql
@upgrade-45CR4-50.sql
```
  Next, you need to run a java migration from 4.5 to 5.0.
  
  Then, resume executing the upgrade commands.
```
@appGrants.sql
```
- If schema version is 210, then enter the following commands:
```
@upgrade-45-45CR3.sql
@upgrade-45CR3-45CR4.sql
@upgrade-45CR4-50.sql
```
  Next, you need to run a java migration from 4.5 to 5.0.
  
  Then, resume executing the upgrade commands.
```
@appGrants.sql
```
- If schema version is 211, then enter the following commands:
```
@upgrade-45CR3-45CR4.sql
@upgrade-45CR4-50.sql
```
  Next, you need to run a java migration from 4.5 to 5.0.
  
  Then, resume executing the upgrade commands:
```
@appGrants.sql
```
- If schema version is 213, then enter the following commands:
```
@upgrade-45CR-50.sql
```
  Next, you need to run a java migration from 4.5 to 5.0.
  
  Then, resume executing the upgrade commands:
```
@appGrants.sql
```
- If schema version is 475, then enter the following commands:
```
@appGrants.sql
```

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"

If the schema version is 29, then enter the following commands:

@upgrade-40-40CR3.sql
@upgrade-40CR3-45.sql
@upgrade-45-45CR2.sql
@fixup-LO77552.sql
@upgrade-45CR2-45CR3.sql
@upgrade-45CR4-50.sql
@appGrants.sql

If schema version is 30, then enter the following commands:

@upgrade-40CR3-45.sql
@upgrade-45-45CR2.sql
@fixup-LO77552.sql
@upgrade-45CR2-45CR3.sql
@upgrade-45CR4-50.sql
@appGrants.sql

If schema version is 34, then enter the following commands:

@upgrade-45-45CR2.sql
@fixup-LO77552.sql
@upgrade-45CR2-45CR3.sql
@upgrade-45CR4-50.sql
@appGrants.sql

If schema version is 37, then enter the following commands:

@fixup-LO77552.sql
@upgrade-45CR2-45CR3.sql
@upgrade-45CR4-50.sql
@appGrants.sql

If schema version is 38, then enter the following commands:
```
@appGrants.sql
```

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'
```
- If the schema version is 4.0.0.0.0, then enter the following commands:
```
@upgrade-40-45.sql
@upgrade-45-45CR4.sql
@upgrade-45CR4-50.sql
@appGrants.sql
```
- If schema version is 1, then enter the following commands:
```
@upgrade-45-45CR4.sql
@upgrade-45CR4-50.sql
@appGrants.sql
```
- If schema version is 2 or 3, then enter the following commands:
```
@upgrade-45CR4-50.sql
@appGrants.sql
```
  Disregard any warnings about duplicate foreign keys.
- If schema version is 7, then enter the following commands:
```
@appGrants.sql
```
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
```
- If schema version is 33, then enter the following commands:
```
@upgrade-40-45.sql
@upgrade-45-50.sql
@appGrants.sql
@clearScheduler.sql
```
- If schema version is 36, then enter the following commands:
```
@upgrade-45-50.sql
@appGrants.sql
@clearScheduler.sql
```
- If schema version is 45, then enter the following commands:
```
@appGrants.sql
@clearScheduler.sql
```
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 79, then enter the following commands:
```
@upgrade-40-45.sql
@upgrade-45-45CR3.sql
@upgrade-45CR3-50.sql
@appGrants.sql
```
- If schema version is 82, then enter the following commands:
```
@upgrade-45-45CR3.sql
@upgrade-45CR3-50.sql
@appGrants.sql
```
- If schema version is 89, then enter the following commands:
```
@upgrade-45CR3-50.sql
@appGrants.sql
```
- If schema version is 102, then enter the following commands:
```
@appGrants.sql
```

What to do next

Check that all the databases are working correctly.