Skip Headers
Oracle® Thesaurus Management System Installation Guide
Release 5.0.1
E37007-02
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
PDF · Mobi · ePub

7 Upgrading Oracle Thesaurus Management System to Release 5.0.1

This chapter describes the recommended approach to upgrading an existing Oracle Thesaurus Management System installation to Release 5.0.1.

Be sure you are using the latest documentation:

Review Chapter 1, "Preparing to Install Oracle Thesaurus Management System" for system requirements and planning information.

This chapter includes the following topics:

7.1 Upgrade to Release 4.6.2 If Necessary

If you are currently using a release prior to Release 4.6.2, you must first upgrade Oracle Database, the TMS Database Server and TMS databases to Release 4.6.2.

Note:

You do NOT need to install the 4.6.2 application tier because the technology stack is new in Release 5.0.x and you must do a fresh install of the whole application tier.

  1. Open a Service Request (SR) on My Oracle Support at https://support.oracle.com to download the Release 4.6.2 media, which are no longer publicly available.

  2. Download the most recent version of the 4.6.2 Installation Guide from http://www.oracle.com/technetwork/documentation/hsgbu-clinical-407519.html.

  3. Read Chapter 1 of the Release 4.6.2 and Release 5.0.1 versions of the Oracle Thesaurus Management System Installation Guide to plan your installation.

  4. In the upgrade chapter of the Release 4.6.2 Oracle Thesaurus Management System Installation Guide follow all database-related sections that apply to your installation.

    Note:

    Do NOT follow Section 6.3, "Upgrading the Application Tier."

    Note:

    Where the TMS 4.6.2 installation guide mentions patch 4.6.0.32, it should say 4.6.0.31. The information is correct except for the patch number.

  5. Follow the instructions below.

7.2 Upgrade to Oracle Database 11.2.0.4

You must upgrade Oracle Database to 11.2.0.4.

7.2.1 Upgrade Oracle Database in UNIX

To upgrade on UNIX, follow these instructions:

  1. Section 2.2.1, "Install Oracle Database 11.2.0.4 Enterprise Edition"

  2. Section 2.2.2, "Install Oracle Database Examples"

7.2.2 Upgrade Oracle Database in UNIX

To upgrade on Windows, follow these instructions:

  1. Section 3.1, "Install Oracle Database 11.2.0.4 Enterprise Edition"

  2. Section 3.2, "Install Oracle Database Examples"

7.3 Install the TMS Database Server Code

Follow instructions in Section 5.2, "Installing the TMS Database Server Code".

7.4 Upgrade a Single or Master TMS Database

Follow the instructions in this section when you are upgrading a single TMS database or, if you have a distributed environment, to upgrade the master TMS database. You must perform the tasks described in previous sections first.

Note:

Even if you have Oracle Clinical integrated with TMS, re-registering databases is not required during an upgrade.

To upgrade the TMS databases, complete the following tasks:

7.4.1 Suspend Symmetric Replication (Distributed Environment Only)

If you are running in a distributed environment, suspend symmetric replication and drop the replication group before you patch the Oracle Database 11g or the TMS databases by following the instructions in this section. Ensure that you use the suspend scripts that are in your TMS server code area.

Table 7-1 Symmetric Replication Suspend Scripts and Instructions

Run Script Where? For Where? Parameters Purpose and Comments

tmsmupgsrsuspend.sql

Master instance

Master instance

None

Purpose: Suspends replication activity for all sites.

Comment: Wait until the dba_repgroup view has a status of QUIESCED on the master instance and all slave instances.

tmsmupgsrdrop.sql

Master instance

Master instance

None

Purpose: Drops replication group for all sites.

Comment: Wait until the dba_repcatlog view is empty on the master instance and on all slave instances.

To suspend replication:

  1. Log in to the server using an account with system administrator privileges.

  2. Open a MS-DOS command window.

  3. Change to the OPA_HOME directory where the install scripts are located, for example:

    cd c:\opapps50\tms\install

  4. Set the local name for your master site:

    set local=Master_Site

    Note:

    Ensure that you explicitly set the local name so that the system does not use the Oracle local registry variable by mistake. For this reason, it is best to run the upgrade scripts from the Command window, rather than from SQL*Plus.

  5. Issue these commands:

    sqlplus repsys/password
    start tmsmupgsrsuspend

  6. Unschedule the push operation from each slave site to the master site and from the master to each slave. Unschedule as many jobs as necessary to ensure that no scheduled push jobs remain.

    Connect to each site as REPSYS and issue this command:

    exec dbms_defer_sys.unschedule_push('remote_site');

  7. Connect as REPSYS at each slave site and run the following script. On each updateable snapshot site (slave site), this script drops the TMS Snapshot Replication and Refresh Groups.

    start tmsssrdrop
     

  8. Connect as TMS at each slave site and run the following script. This step drops the TMS replicated tables on all sites.

    start tmsssrdroptables
     

  9. Connect as TMS at the master site and run the following script, which drops the TMS Snapshot Logs at the master site.

    start tmsmsrdropmvlog
     

  10. Connect as REPSYS on the master site and issue the following command, which drops the TMS Master Replication Group.

    start tmsmupgsrdrop

    Note:

    You must follow steps in Section 7.4 to upgrade the master database before proceeding to the next step.

7.4.2 Upgrade the Database to Oracle Database 11.2.0.4

Upgrade the database to 11.2.0.4 following instructions in the patch readme file and Oracle Database 11g Release 2 (11.2) Installation Guide for your operating system at http://www.oracle.com/pls/db112/portal.portal_db?selected=11&frame=

7.4.3 Gather Required Information

Before you start the installer, be sure you have the information it prompts for; see Section 7.4.6, "Attend to the TMS Database Upgrade Installer Screens".

7.4.4 Stop PSUB Process (If Integrated with Oracle Clinical)

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

7.4.5 Start the Installer

To upgrade a TMS database:

  1. Log in 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.4, "Downloading and Extracting the Software").

  3. Run the following file:

    Disk1\install\setup.exe

    The Installer opens to the Welcome screen.

    Note:

    See Section 1.5, "Using the Silent Installer" 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.

7.4.6 Attend to the TMS Database Upgrade Installer Screens

The Installer guides you through the database upgrade.

  1. Product to install: TMS Database Upgrade.

  2. What type of installation do you want?

    • Select Master if you are planning to use only one database or if you have a distributed environment (using data replication) and this is the master database.

    • Select Slave only if you have a distributed environment and this is a slave,or local, database.

  3. Home Details: The full path to the Oracle Forms/Reports Home location on your application server; by default:

    C:\app\oracle\Middleware\Oracle_FRHome1

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

  5. Database Connect String: Enter the database name. It must be a valid TNS entry in your tnsnames.ora file.

  6. NLS Settings: Enter the NLS settings for the database; see Section 1.7, "Choosing 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

    • CTXSYS

    • OPA

    • TMS

    • RXC

  9. Ignore tablespace creation errors:

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

    • Select No if the TMS tablespaces do not exist.

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

  11. When you are ready, install.

7.4.7 Check Installation Log for Errors

When you upgrade from TMS 4.6.1 to TMS 4.6.2, 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 7.4.8, "Configure DSI Import" for details.

7.4.8 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;

7.4.9 Load Dictionaries

If you need to upgrade any dictionaries or load new dictionaries and are installing a distributed environment, this is a good time to do it since you have suspended replication and will next do an export/import. However, you can load dictionaries at any time.

If you are installing TMS with AERS in a distributed environment, you must load the AERS-TMS dictionaries onto the master database before creating an export file and importing it to the slave databases.

See the Oracle Thesaurus Management System User's Guide for information about loading dictionaries.

7.4.10 Create an Export File (Distributed Environments Only)

If you are upgrading a distributed environment, follow instructions in Section 5.8.1, "Export Data from the Master Database."

7.5 Upgrade Slave TMS Databases (Distributed Environments Only)

Follow the instructions in this section to upgrade existing TMS 4.6.2 slave databases to Release 5.0.1 in a distributed environment.

7.5.1 Upgrade Slave Databases

To upgrade each slave instance to TMS Release 4.6.2:

  1. Start the Oracle Universal Installer on the TMS application server. (See Section 7.4, "Upgrade a Single or Master TMS Database" for details.) Choose the Slave Installation type from the Product Installer screen.

  2. Import data from the master instance. Perform this task on the database server. At every slave database, import the export file you created in the previous task .

    See Section 5.8.2, "Import Data to the Slave Database" for more information.

    Note:

    You must first create an export file of the master database; see Section 5.8.1, "Export Data from the Master Database."

  3. On the TMS application server, set the LOCAL variable and run the tmsupgslave.sql script by entering the following commands in a MS-DOS window:

    cd OPA_HOME\tms\install
sqlplus system/password
start tmsupgslave.sql

The script generates a log file in the install directory named tmsupgslave_database_name.log.

Note:

When upgrading a slave database to Release 5.0.1, the following types of errors occur in the tmsupg_database_name.sql log file: 
Warning: Package created with compilation errors. (and appended PLSQL errors with line numbers) 
Warning: Package Body created with compilation errors. (and appended PLSQL errors with line numbers) ORA-00942: table or view does not exist 
ORA-01775: looping chain of synonyms 
ORA-04063: view "TMS.view_name" has errors

As long as there are no errors in the log file, tmsupgslave_database_name.sql, and there are no invalid OPA/TMS objects in the database after the ugprade, the upgrade can be considered successful and these errors can be ignored.

7.5.2 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;

7.5.3 Start Symmetric Replication

Start replication, following instructions in Section 5.8.6.2, "Start Replication on the Master Database" and Section 5.8.6.3, "Start Replication on Each Slave Instance."

7.6 Upgrade Cloned Databases

If you have cloned a database, access the following document on My Oracle Support:

Cloning Oracle Clinical and TMS 4.6.x DatabasesArticle ID: 883213.1

Be sure to follow all the instructions in the document, including running the tmschown.sql script, the opachown.sql script, and if you are using Oracle Clinical with TMS, the chown.sql script, before doing the upgrade.

7.7 Run Scripts to Gather Schema Statistics for the 11g Optimizer

After upgrading to TMS 5.0.1 and setting initialization parameter optimizer_features_enable to 11.2.0.4 (see Section 5.3.7, "Set Initialization Parameters"), you must gather statistics required for the Oracle 11g Optimizer to be effective for accounts used internally by TMS.

Failure to execute these scripts can negatively impact performance.

Scripts opastats.sql and tmsstats.sql, are available for this purpose. If your database contains large amounts of data, the scripts may take a long time to run. You may want to edit the scripts; for information on opastat.sql and tmsstats.sql parameters see the following documentation of the DBMS_STATS package that they call: http://docs.oracle.com/cd/B19306_01/appdev.102/b14258/d_stats.htm#i1036456.

tmsstats.sql Since TMS already has a procedure, AnalyzeTable in tmspb_user_analyze.sql, that runs as part of every activation job, you may prefer to edit it if required and call it from tmsstats.sql to keep the two synchronized.

The tmsstats.sql script prompts for the password of the account it processes: TMS.

To change how TMS analyzes tables and ensure that tmsstats and AnalyzeTable remain in synch:

  1. Modify the Analyze procedure in tmspb_user_analyze.sql.

  2. Edit tmsstats.sql to call tms_user_analyze.AnalyzeTable. Replace the section that analyzes tables with:

    exec tms_user_analyze.AnalyzeTables

  3. Run tmsstats.sql.

opastats.sql captures new statistics in the OPA application account used by TMS. It is also used by Oracle Clinical and RDC Onsite.

7.8 Install the Application Tier Technology Stack

Install and configure the required application tier technology stack. Follow instructions in Chapter 4, "Installing and Configuring the Application Tier."

7.9 Install the TMS Front End and Reports Server

Install the TMS front end following instructions in Chapter 6, "Installing Oracle Thesaurus Management System Application Components" to install the TMS Front End and Reports Server.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us