Update 4.0 and 4.5 Oracle databases manually
Overview
Manually update IBM Connections 4.0 or 4.5 databases to v5.0 in an existing IBM WebSphere Application Server and Oracle database environment.
Use the JRE under the Wizards directory. Update the PATH variable to point to this JRE. For example...
Wizards/jvm/linux/jre
IBM Connections does not support GNU Java.
Use a database administrator ID to run the Java migration utilities.
After running each command, review output closely for error messages. Resolve errors before proceeding.
Before applying updates, back up Connections.
Install supporting software for v5.0.
Set the Statement cache size for the data sources on WAS to be no larger than 50. A higher value could lead to Out Of Memory errors on the application server instance.
Connections databases use SMALLFILE tablespaces with a size limitation of 222 blocks. When using 8 KB blocks, this limit is approximately 32 GB. If we anticipate needing more space than this, add additional tablespace files to individual databases.
Use this procedure if you want an alternative to using the database wizard to update the databases.
Update Oracle databases manually
- Log on to the WAS console on the dmgr and go to...
Applications | Application types | WebSphere Enterprise Applications
- Stop all Connections applications.
- Ensure the Oracle driver on the system has the same version number as the Oracle database server.
- cd WP_PROFILEhe directory containing the scripts.
- For each application, manually create the application database table...
- Log on to Oracle
sqlplus /as sysdba
sql> spool on
sql> spool /path/to/output.log
- cd Wizards/connections.sql/homepage/oracle
- Check the database schema version...
select DBSCHEMAVER from HOMEPAGE.HOMEPAGE_SCHEMA
For version 110, run:
@upgrade-40-40CR2.sql
@upgrade-40CR2-45.sqlAlso, 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.sqlRun a java migration from 4.5 to 5.0.
Resume executing the upgrade commands
@appGrants.sql
For version 132, then enter the following command:
@upgrade-40CR2-45.sql
Also, 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.sqlrun a java migration from 4.5 to 5.0.
Resume executing the upgrade commands.
@appGrants.sql
For version 210, run:
@upgrade-45-45CR3.sql
@upgrade-45CR3-45CR4.sql
@upgrade-45CR4-50.sqlRun a java migration from 4.5 to 5.0.
Resume executing the upgrade commands.
@appGrants.sql
For version 211, run:
@upgrade-45CR3-45CR4.sql
@upgrade-45CR4-50.sqlRun a java migration from 4.5 to 5.0.
Resume executing the upgrade commands:
@appGrants.sql
For version 213, run:
@upgrade-45CR-50.sql
Next, run a java migration from 4.5 to 5.0.
Then, resume executing the upgrade commands:
@appGrants.sql
For version 475, run:
@appGrants.sql
- cd Wizards/connections.sql/activities/oracle
- Check DB schema version...
select DBSCHEMAVER from ACTIVITIES.OA_SCHEMA
For version 53, run:
@upgrade-40-45.sql
@upgrade-45-50.sql
@appGrants.sqlFor version 56, run:
@upgrade-45-50.sql
@appGrants.sql
@runstats.sqlFor version 69, run:
@appGrants.sql
- cd Wizards/connections.sql/blogs/oracle
- Check DB schema version...
select value from BLOGS.roller_properties where name='database.schema.version'
For version 43, run:
@upgrade-40-45.sql
@upgrade-45-45CR4.sql
@upgrade-45CR4-50.sql
@appGrants.sqlFor version 51, run:
@upgrade-45-45CR4.sql
@upgrade-45CR4-50.sql
@appGrants.sqlFor version 52, run:
@upgrade-45CR4-50.sql
@appGrants.sqlFor version 69, run:
@appGrants.sql
- cd Wizards/connections.sql/dogear/oracle
- Check DB schema version...
select DBSCHEMAVER from DOGEAR.DOGEAR_SCHEMA
For version 14, run:
@upgrade-40-45.sql
@upgrade-45-50.sql
@appGrants.sqlFor version 15, then enter the following command:
@upgrade-45-50.sql
@appGrants.sql
@runstats.sqlFor version 22, run...
@appGrants.sql
- cd Wizards/connections.sql/communities/oracle
- Check the database schema version...
select DBSCHEMAVER from SNCOMM.SNCOMM_SCHEMA
For version 76, run:
@pgrade-40-45.sql
@upgrade-45-50.sql
@appGrants.sqlFor version 77, run:
@upgrade-45-50.sql
@appGrants.sqlFor version 92, run:
@appGrants.sql
- cd Wizards/connections.sql/calendar/oracle
- Check the database schema version...
select DBSCHEMAVER from CALENDAR.CA_SCHEMA
For version 10, run:
@calendar-upgrade-40-45.sql
@calendar-upgrade-45-50.sql
@calendar-appGrants.sql
@calendar-runstats.sqlFor version 15, run:
@calendar-upgrade-45-50.sql
@calendar-appGrants.sql
@calendar-runstats.sqlFor version 29, run:
@calendar-appGrants.sql
@calendar-runstats.sql
- cd Wizards/connections.sql/files/oracle
- Check the database schema version
select SCHEMA_VERSION from "FILES"."PRODUCT"
For version 79, run:
@upgrade-40-45.sql
@upgrade-45-45CR3.sql
@upgrade-45CR3-50.sql
@appGrants.sqlFor version 82, run:
@upgrade-45-45CR3.sql
@upgrade-45CR3-50.sql
@appGrants.sqlFor version 89, run:
@upgrade-45CR3-50.sql
@appGrants.sqlFor version 106, run:
@appGrants.sql
- cd Wizards/connections.sql/forum/oracle
Check the database schema version:
select DBSCHEMAVER from FORUM.DF_SCHEMA
For version 21, run:
@upgrade-40-45.sql
@upgrade-45-50.sql
@appGrants.sqlFor version 27, run:
@upgrade-45-50.sql
@appGrants.sqlFor version 35, run:
@appGrants.sql
- cd Wizards/connections.sql/metrics/oracle
- Check the database schema
select SCHEMA_VERSION from "METRICS"."PRODUCT"
For version 29, run:
@upgrade-40-40CR3.sql
@upgrade-40CR3-45.sql
@upgrade-45-45CR2.sql
@fixup-LO77552.sql
@upgrade-45CR2-45CR3.sql
@upgrade-45CR4-50.sql
@appGrants.sqlFor version 30, run:
@upgrade-40CR3-45.sql
@upgrade-45-45CR2.sql
@fixup-LO77552.sql
@upgrade-45CR2-45CR3.sql
@upgrade-45CR4-50.sql
@appGrants.sqlFor version 34, run:
@upgrade-45-45CR2.sql
@fixup-LO77552.sql
@upgrade-45CR2-45CR3.sql
@upgrade-45CR4-50.sql
@appGrants.sqlFor version 37, run:
@fixup-LO77552.sql
@upgrade-45CR2-45CR3.sql
@upgrade-45CR4-50.sql
@appGrants.sqlFor version 38, run:
@appGrants.sql
- cd Wizards/connections.sql/mobile/oracle
- Check the database schema version...
select VALUE from MOBILE.ROLLER_PROPERTIES where NAME='database.schema.version'
For version 4.0.0.0.0, run:
@upgrade-40-45.sql
@upgrade-45-45CR4.sql
@upgrade-45CR4-50.sql
@appGrants.sqlFor version 4.5.0.0.0, run:
@upgrade-45-45CR4.sql
@upgrade-45CR4-50.sql
@appGrants.sqlFor version 2, run:
@upgrade-45CR4-50.sql
@appGrants.sqlFor version 7, run:
@appGrants.sql
- cd Wizards/connections.sql/profiles/oracle
- Check the database schema version...
select DBSCHEMAVER from EMPINST.SNPROF_SCHEMA
For version 33, run:
@upgrade-40-45.sql
@upgrade-45-50.sql
@appGrants.sql
@clearScheduler.sqlFor version 36, run:
@upgrade-45-50.sql
@appGrants.sql
@clearScheduler.sqlFor version 45, run:
@appGrants.sql
@clearScheduler.sql
- cd Wizards/connections.sql/wikis/oracle
- Check the database schema version...
select SCHEMA_VERSION from "WIKIS"."PRODUCT"
For version 79, run:
@upgrade-40-45.sql
@upgrade-45-45CR3.sql
@upgrade-45CR3-50.sql
@appGrants.sqlFor version 82, run:
@upgrade-45-45CR3.sql
@upgrade-45CR3-50.sql
@appGrants.sqlFor version 89, run:
@upgrade-45CR3-50.sql
@appGrants.sqlFor version 102, run:
@appGrants.sql
Parent topic:
Update 4.0 and 4.5 databases manually
Related: