6 Upgrading Oracle Thesaurus Management System to Release 5.2.1

6.4.1 Prevent Access to Oracle Thesaurus Management System Databases

You must ensure that no data entry is performed, and no jobs that update data (such as batch validation) run during the upgrade process.

To prevent users from accessing the data, place the database in restricted mode. Provide restricted session access to the following accounts:

• SYSTEM

• SYS

• OPA

• RXC

• TMS

• CTXSYS

• OPS$TMSBROWSER

• TDX

After you complete the upgrade, remove the restricted access from the databases and user accounts.

6.4.2 Upgrade to Oracle Database 12.1.0.2

Oracle recommends backing up your database(s) at this point.

Do one of the following:

• Upgrade in Place

• Clone Your Database

6.4.3 Gather Required Information

Before you start the Installer, be sure you have the information it prompts for:

1. Home Details: The full path to the OPA_HOME or similar application home name on your application server; by default:

   C:\opapps52

2. Oracle Database Client Home: Full path to the Oracle Database Client. (The Oracle Database Client Home is required for SQL Loader and LOADJAVA to work.)

3. TMS Server Code Home Directory: The system detects the location and enters the value for you. By default, it is C:\opapps52\tms.

4. Database Service Name to connect: Enter the database name. It must be a valid TNS entry in your tnsnames.ora file.

5. Database Details: Enter the database server name and database port number.

6. NLS Settings: Enter the NLS settings for the database; see Section 1.8, "Choose a Character Set". Oracle strongly recommends that you use UTF8. The default values are:

   • American_America.UTF8

   • DD-MON-RRRR

7. Directory for data tablespace data files: Enter the path to the directory on the database server where the data tablespace datafiles for the application should be created during the installation. The Installer does not validate the value and you must use the following syntax, including a trailing slash, depending on your operating system; for example:

   • UNIX: /u01/oradata/dbname/

   • Windows: drive:\oradata\dbname\

8. Enter and confirm passwords for the following accounts:

   • SYS

   • SYSTEM

   • RXC

   • OPA

   • TMS

   • CTXSYS

   • TMSPROXY

6.4.4 Stop PSUB Process (If Integrated with Oracle Clinical)

If your TMS installation is integrated with Oracle Clinical, you must stop the PSUB process before upgrading the database. See the Oracle Clinical Administrator's Guide for instructions.

6.4.5 Start the Installer

To upgrade a TMS database:

1. Log in to the application server as a user with system administrator privileges.

2. In the staging area, locate the directory where you downloaded and extracted Oracle Thesaurus Management System (see Section 1.6, "Download the Software").

3. Run the following file as an administrator:

   Disk1\install\setup.exe

   The Installer opens to the Welcome screen.

   Note:

   See Section 1.7, "Use the Silent Installer (Optional)" for instructions for running the Installer as a file with pre-entered parameter values.

   Note:

   Although there is a button for deinstalling products on the Welcome screen, Oracle does not support using the Installer to deinstall Oracle Thesaurus Management System.

4. In the Select a Product to Install page, select TMS Database Upgrade 5.2.1.0.x.

6.4.6 Attend to the TMS Database Upgrade Installer Screens

The Oracle Universal Installer guides you through the database upgrade. Provide the information you assembled in "Gather Required Information."

Ignore tablespace creation errors:

• Select Yes if the database already has the TMS tablespaces created.

• Select No if the TMS tablespaces do not exist.

The Installer gives you information that you should make a note of.

6.4.7 Set Initialization Parameters

After the upgrade completes, set the init.ora parameters according to the instructions in Section 4.2.7, "Set Initialization Parameters."

You must stop and then start the database to activate the changed init.ora parameters.

6.4.8 Check Installation Log for Errors

When you upgrade, the installation log file may report the following error:

".....
Connected.
BEGIN tms_dsi_xml_schema.InstallSchemas; END  

*
ERROR at line 1:
ORA-02303: cannot drop or replace a type with type or table dependents 
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 3
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 14 
ORA-06512: at "TMS.TMS_DSI_XML_SCHEMA", line 35 
ORA-06512: at line 1
 
finished TMSUPG 
TMS will now attempt to validate any invalidate objects... 
...."

This error occurs because the tmsupg.sql upgrade script executes tms_dsi_xml_schema.InstallSchemas before attempting to validate any invalid objects. Execution of tms_dsi_xml_schema.InstallSchemas fails if the database has invalid objects.

If this error occurs, you need to:

1. Run compile invalid until all database objects have been made valid.

2. Run tms_dsi_xml_schema.InstallSchemas manually. See Section 6.4.9, "Configure DSI Import" for details.

6.4.9 Configure DSI Import

If you plan to use disconnected system integration (DSI), enter following commands:

set LOCAL=databasename
sqlplus tms/password
exec tms_dsi_xml_schema.InstallSchemas;
 

6.4.10 Load Dictionaries

You can load dictionaries at any time. See the Oracle Thesaurus Management System User's Guide for information about loading dictionaries.

6.8.1 Install the Oracle Thesaurus Management System Front End and Reports Server

Follow instructions in Chapter 5, "Installing Oracle Thesaurus Management System Application Components."

6.8.2 Set Remote Method Invocation (RMI) JDBC Security to Secure

1. Log in to the WebLogic Server

2. Go to Summary of Servers, select OpaServer1, select General, and click Advanced.

3. Change the RMI JDBC Security setting to Secure.

4. Click Save.

5. Click Activate Changes.