| Oracle® Thesaurus Management System Installation Guide Release 4.6.2 Part Number E18826-03 |
|
|
View PDF |
| Oracle® Thesaurus Management System Installation Guide Release 4.6.2 Part Number E18826-03 |
|
|
View PDF |
This chapter describes the recommended approach to upgrading an existing Oracle Thesaurus Management System (TMS) installation to Release 4.6.2. You can use the instructions in this chapter to upgrade from one of the following releases:
Release 4.5.2
Release 4.6.0
Release 4.6.1
This chapter includes the following topics:
Section 7.1, "Upgrade to Oracle Database 11g Release 2 (11.2.0.2) Patch Set 1"
Section 7.7, "Upgrade Slave TMS Databases (Distributed Environments Only)"
Section 7.8, "Applying the Latest Patch Set"
Note:
Even if you have TMS integrated with Oracle Clinical, re-registering databases for integration with Oracle Clinical is not required during an upgrade.Upgrade the database to Oracle Database 11g Release 2 (11.2.0.2) Patch Set 1. Install all the Enterprise Edition options. For details, see Chapter 2, "Installing Oracle Database 11g Release 2 (11.2.0.2) Patch Set 1 on UNIX."
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.
Install and configure the required Oracle Application Server technology stack, including Oracle Application Server 10g Release 2 and its Patch Set 3, and Oracle Application Server 10g Release 3 and its Patch Set 5. Follow instructions in Chapter 4, "Installing and Configuring Oracle Application Server."
Install the TMS front end, including the server code; follow instructions in Chapter 5, "Installing the TMS Front End Components."
Ensure that you applied the data diagnostic and repair patches (or their successors) listed in this section to your TMS 4.6.1 or TMS 4.6.0 data.
Follow the patch instructions to apply the following patches to each TMS 4.6.1 database in your entire TMS installation:
Patch TMS_4.6.1.8 (or its successor). Includes scripts to find and fix the data affected by Bug 10131304. When VTA approval was required, omissions that matched a nonapproved VTA were not displayed in the Distinct Verbatim Term Omissions tab of the Classify VT Omissions window.
This error occurred, in part, because the system assigned such terms an internal DEF_SEARCH_ID of 2, which means it was manually classified, instead of an internal DEF_SEARCH_ID of 11, which means it matched an unapproved VTA. Terms with an internal DEF_SEARCH_ID of 2 are not displayed in the Distinct Verbatim Term Omissions tab. This patch corrects the processing of new terms. The Find script finds all existing affected terms and populates a Find table with these records. The Fix script updates the DEF_SEARCH_ID to 11 for the terms identified by the Find script.
Patch TMS_4.6.1.3 (or its successor). Includes scripts to find and fix the data affected by Bug 9171740. This patch fixes the following error that occurs when you import Oracle Clinical accounts into OPA accounts in the Define Users window:
ORA-0001: unique constraint (OPA.OPA_ACCOUNTS_UK1) violated
The error is due to duplicate records in the OPA_ACCOUNTS table. A duplicate record has a different account ID for the same account_name and instance_name. You use the Find and Fix scripts to identify and fix existing duplicate records.
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.
To upgrade the TMS databases, complete the following tasks:
Section 7.6.1, "Suspend Symmetric Replication (Distributed Environment Only)"
Section 7.6.3, "Attend to the TMS Database Upgrade Installation Screens"
Section 7.6.8, "Create an Export File (Distributed Environments 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:
Log in to the server using an account with system administrator privileges.
Open a MS-DOS command window.
Change to the OPA_HOME directory where the install scripts are located, for example:
cd c:\opapps46\tms\installSet the local name for your master site:
set local=Master_SiteNote:
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.Issue these commands:
sqlplus repsys/passwordstart tmsmupgsrsuspendUnschedule 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');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 tmsssrdropConnect as TMS at each slave site and run the following script. This step drops the TMS replicated tables on all sites.
start tmsssrdroptablesConnect as TMS at the master site and run the following script, which drops the TMS Snapshot Logs at the master site.
start tmsmsrdropmvlogConnect as REPSYS on the master site and issue the following command, which drops the TMS Master Replication Group.
start tmsmupgsrdropNote:
You must follow steps in Section 7.6 to upgrade the master database before proceeding to the next step.To begin the database upgrade:
Log in as a user with system administrator privileges.
Insert the Oracle Clinical 4.6.2 and Oracle Thesaurus Management System 4.6.2 disk.
Locate and run the following file:
tms\install\setup.exe
The Installer opens to the Welcome screen.
Follow the instructions on the installation screens. For more information about each screen, Section 7.6.3, "Attend to the TMS Database Upgrade Installation Screens."
The Oracle Universal Installer guides you through the process of upgrading a TMS database.
Click Next to continue the installation.
Select TMS Database Upgrade 4.6.2.0.XX (where XX is the build number).
Click Next.
Select Installation Type TMS Database Upgrade 4.6.2.0.XX
Select Master and click Next.
Enter values for the Oracle Home location you created when you installed Oracle Application Server 10g Release 2. This installation guide refers to this location as ORACLE_AS10gR2_HOME.
Name: Select the name of the correct Oracle Home; for example, AS10gR2.
Path: Browse for the path to the correct Oracle Home; for example, D:\Oracle\AS10gR2.
Click Next.
TMS Database Upgrade TMS Server Code Home Directory
Accept the default value for the directory path of the database server code. Click Next.
TMS Database Upgrade Enter database connect string
Enter the database name. An alias must exist in your tnsnames.ora file for this database.
|
Note: The Installer sets the LOCAL registry setting to default all connections to this database. |
TMS Database Upgrade NLS Settings
NLS_LANG — Enter the NLS language setting that is appropriate for your database character set. Oracle recommends the AMERICAN_AMERICA.UTF8 setting. For information about the guidelines and requirements for character sets, see Section 1.4, "Choosing a Character Set."
NLS_DATE_FORMAT — Enter a valid date value. All Oracle Health Sciences applications require a date format with a four-digit year. Oracle recommends DD-MON-RRRR.
Click Next.
TMS Database Upgrade Warning: Stop PSUB process
If you are integrating TMS with Oracle Clinical, stop the PSUB process on the database at this point, restarting it only after you have completely installed TMS.
TMS Database Upgrade Directory for data tablespace datafiles
Enter the directory for TMS data tablespace files in the appropriate syntax for your operating system, including a trailing slash. Use the same database name you entered as the connect string. For example, /u01/oradata/database_name/.
TMS Database Upgrade Enter Password for schema
In a series of Installer screens, enter the passwords for SYS, SYSTEM, CTXSYS, OPA, TMS, and RXC. You will need these passwords later.
TMS Database Upgrade Ignore Tablespace Creation Errors
This setting controls whether the Installer ignores errors that occur when creating the tablespaces. Tablespace creation can fail for several reasons.
The default value is No. In general, you do not want the Installer to ignore tablespace creation errors. For example, you want the Installer to report an error if there is not enough space to create the tablespace.
On the other hand, if you are reinstalling into an existing TMS database, the tablespace creation fails because the tablespace already exists. In this case, you do not need to know about the error.
Click Next.
The Information screen reports that the Installer will start a SQL*Plus session to complete the database upgrade. The screen confirms the name of the database installation and the location of the log file that you can view for the progress of the installation. Click Next.
Summary TMS Database Upgrade 4.6.2.0.XX
The Summary screen provides information about the global settings, languages, space requirements, and products for this installation.
Click Install. The Installer starts an SQL*Plus session to complete the installation.
The End of Installation screen provides information about the installation, including whether the processes completed without errors.
When you have finished reviewing the installation information, click Exit. At the confirmation prompt, click Yes to exit from Oracle Universal Installer.
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:
Run compile invalid until all database objects have been made valid.
Run tms_dsi_xml_schema.InstallSchemas manually. See Section 7.6.6, "Configure DSI Import" for details.
Follow instruction in this section only if you are upgrading from TMS 4.6.1. If you are upgrading from 4.5.2 or 4.6, following instructions in Section 6.5, "Load Reports (All Databases)" instead.
To upgrade reports, run a script that deletes the existing seeded reports and then loads new ones:
In the MS-DOS command window, change directories to OPA_HOME\tms\install.
Log in to SQL*Plus as the opa user:
set LOCAL=database_name
sqlplus opa/opa_password
Define variables and run opa_xdo_seeddata.sql:
SQL> define product=TMS
SQL> define oracle_home=ORACLE_10GR2_HOME
SQL> start opa_xdo_seeddata.sql
Enter opa password when prompted. Press enter once if the script pauses.
Load the reports from the database server, following instructions in Section 6.5, "Load Reports (All Databases)".
If you plan to use disconnected system integration (DSI), enter following commands:
set LOCAL=databasename sqlplus tms/password exec tms_dsi_xml_schema.InstallSchemas;
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; it does not need to be within the context of a TMS upgrade.
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.
If you are upgrading a distributed environment, follow instructions in Section 6.9.1, "Export Data from the Master Database."
Follow the instructions in this section to upgrade existing TMS 4.5.2 or TMS 4.6 slave databases to Release 4.6.2 in a distributed environment.
Note:
TMS 4.6.1 does not support replication. If you are upgrading from TMS 4.6.1, you can skip this section.To upgrade each slave instance to TMS Release 4.6.2:
Start the Oracle Universal Installer on the TMS application server. (See Section 7.6, "Upgrade a Single or Master TMS Database" for details.) Choose the Slave Installation type from the Product Installer screen.
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 6.9.2, "Import Data to the Slave Database" for more information.
Note:
You must first create an export file of the master database; see Section 6.9.1, "Export Data from the Master Database."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 4.6.2, 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.
Follow instruction in this section only if you are upgrading from TMS 4.6.1. If you are upgrading from 4.5.2 or 4.6, following instructions in Section 6.5, "Load Reports (All Databases)" instead.
To upgrade reports, run a script that deletes the existing seeded reports and then loads new ones:
In the MS-DOS command window, change directories to OPA_HOME\tms\install.
Log in to SQL*Plus as the opa user:
set LOCAL=database_name
sqlplus opa/opa_password
Define variables and run ops_xdo_seeddata.sql:
SQL> define product=TMS
SQL> define oracle_home=ORACLE_10GR2_HOME
SQL> start opa_xdo_seeddata.sql
Enter opa password when prompted. Press enter once if the script pauses.
Load the reports from the database server, following instructions in Section 6.5, "Load Reports (All Databases)".
If you plan to use disconnected system integration (DSI), enter following commands:
set LOCAL=databasename sqlplus tms/password exec tms_dsi_xml_schema.InstallSchemas;
Start replication, following instructions in Section 6.9.5.2, "Start Replication on the Master Database" and Section 6.9.5.3, "Start Replication on Each Slave Instance."
Check My Oracle Support article Oracle Thesaurus Management System Patches (Article ID 132626.1) for the latest patch set (4.6.4 or its successor) and apply it. See the patch set release notes for more information.
If you are installing your database on Windows, you must apply the latest patch set. Oracle Thesaurus Management System 4.6.2 is not supported on Windows without Patch Set 4.6.4 or later.
|
 Copyright © 2000, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|