| 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 how to create a new Oracle database for use with Oracle Thesaurus Management System (TMS).
Your Oracle Database 11g Release 2 (11.2.0.2) Patch Set 1 installation must be complete before you can install the TMS database. In addition, you must first install the TMS database server code in the application tier; see Section 5.4, "Installing the TMS Database Server Code."
Single TMS Database or Master Database in a Distributed Environment If you plan to use only one TMS database, or if you are using replication to distribute data among multiple databases, perform the steps in the following sections on the single or master database:
Section 6.1, "Review Database Requirements and Recommendations (All Databases)"
Section 6.2, "Install TMS Database Objects (Single or Master Database)"
Section 6.6, "Create a TMS Administrator User Account (All Databases)"
Section 6.7, "Register Databases Integrated with Oracle Clinical" (This step is required only if you are integrating TMS with Oracle Clinical.)
Section 6.8, "Load Dictionaries (Single or Master Database)"
Note:
For master databases, see also Section 6.9, "Complete Distributed Environment Setup."Slave Databases If you are installing multiple databases in a distributed environment, perform the steps in the following sections on each slave database:
Section 6.1, "Review Database Requirements and Recommendations (All Databases)"
Section 6.3, "Install TMS Database Objects (Slave Databases Only)"
Section 6.9, "Complete Distributed Environment Setup" This section includes tasks to be done on both the master and slave databases.
Section 6.6, "Create a TMS Administrator User Account (All Databases)"
Before you install the TMS database component, review the following requirements and recommendations — such as SID names, tablespace sizes, memory management, and initialization parameters — for each TMS database you plan to install.
Note:
Repeat these requirements for each new database you create.Oracle recommends that you set up a new database instance so that neither TMS nor its installation process interferes with other applications. However, you can install TMS on an existing database instance.
If you are integrating your TMS environment with Oracle Clinical, ensure that the SID name uses lowercase letters only. SIDs with uppercase letters cause conflicts in the Oracle Clinical Data Extract module.
Table 6-1 lists the tablespaces, along with their minimum size, required for TMS. Make sure the database contains these tablespaces. The best practice is to create them with the Autoextend On option, to avoid running out of space.
In addition, you may need to increase the minimum sizes for your installation.
To create a new database, use the Database Configuration Assistant. For instructions about the Database Configuration Assistant, see the Oracle Database 11g Release 2 (11.2.0.2) Patch Set 1 documentation, including online help and the Oracle Database Installation Guide 11g Release 2 (11.2) for the appropriate operating system.
When you create a TMS database, select the following mandatory components:
Oracle Text
Oracle JVM
Oracle XML DB
Oracle recommends that you use Oracle Database 11g Release 2 (11.2.0.2) Patch Set 1's Automatic Memory Management feature for a new or an upgraded TMS database.
Table 6-2 lists the required and recommended initialization parameters in the init.ora file for TMS. For those parameters that accept a value from within a range, the values in the table are minimum values.
Tip:
Table 6-2 arranges the parameters in alphabetical order. In the Database Configuration Assistant, you can select the Parameter column to sequence the parameters in the same order.Note:
If you make any changes to the initialization parameters, be sure to stop and restart the database in order to acquire the new parameter settings.Table 6-2 Required and Recommended Initialization Values in the init.ora File
| Parameter | Value | Comments |
|---|---|---|
|
COMPATIBLE |
11.2.0.2.0 |
Specifies the release with which the Oracle server must maintain compatibility. |
|
DB_BLOCK_SIZE |
16384 bytes |
You cannot change this value after you create the database. |
|
DB_CACHE_SIZE |
150 MB |
Recommended value for 50 to 60 concurrent users. Adjust this value according to your organization's needs. |
|
DB_DOMAIN |
company.com |
Make this value the same as your company domain name. |
|
DB_FILES |
200 |
Oracle adds needed space to the control files up to the number specified in the DB_FILES parameter. |
|
EVENT |
31151 trace name context forever, level 0x100 |
Required for HTML generation. NOTE: Do not include the EVENT parameter when you create the database. Once the database is created, you can add the EVENT parameter to the init.ora file. |
|
JAVA_POOL_SIZE |
50 MB |
Recommended value for 50 to 60 concurrent users. You can change the value of this parameter after installation. |
|
JOB_QUEUE_PROCESSES |
10 |
Developer-specific parameter. You can change the value of this parameter after installation. |
|
LARGE_POOL_SIZE |
50 MB |
Recommended value for 50 to 60 concurrent users. |
|
MEMORY_MAX_TARGET |
1000 MB (minimum) |
Adjust this value according to your organization's needs. |
|
MEMORY_TARGET |
1000 MB (minimum) |
Adjust this value according to your organization's needs. |
|
NLS_DATE_FORMAT |
DD-MON-RRRR (default value) |
Determines the format in which client applications running on the Windows server transfer date information to and from the database. The format must specify the year as RRRR. |
|
NLS_LENGTH_SEMANTICS |
BYTE |
The CHAR value for this parameter is not supported. |
|
OPEN_CURSORS |
800 or greater |
You can change the value of this parameter after installation. |
|
OPTIMIZER_FEATURES_ENABLE |
9.2.0 |
Acts as an umbrella for enabling a series of optimizer features based on an Oracle release number. TMS uses the optimizing features of Oracle9i. |
|
OPTIMIZER_MODE |
CHOOSE |
If you run Oracle Clinical's statistics-gathering scripts, the CHOOSE value sets Oracle9i's Optimizer to apply the execution plan that best minimizes response time. See the Oracle9i Concepts Guide and the Oracle9i Tuning Guide for more information. (CHOOSE is the default value when you specify 9.2.0 as the value of OPTIMIZER_FEATURES_ENABLE.) |
|
OS_AUTHENT_PREFIX |
"OPS$" |
Enter the double quotes symbol ("). |
|
PGA_AGGREGATE_TARGET |
200 MB |
Recommended value for 50 to 60 concurrent users. You can change the value of this parameter after installation. |
|
REMOTE_LOGIN_PASSWORDFILE |
EXCLUSIVE |
The database must be set up to use password file authentication. |
|
REMOTE_OS_AUTHENT |
FALSE |
NOTE: Do not include the REMOTE_OS_AUTHENT parameter when you create the database. Once the database is created, you can add the REMOTE_OS_AUTHENT parameter to the init.ora file. REMOTE_OS_AUTHENT is an obsolete parameter. When you start up a database that has this setting, TMS displays the following warning:
You can safely ignore this warning. |
|
SEC_CASE_SENSITIVE_LOGON |
FALSE |
Lets you enter passwords without case sensitivity. |
|
SESSIONS |
500 |
You can change the value of this parameter after installation. |
|
SGA_MAX_SIZE |
600 MB (minimum) |
Recommended value for 50 to 60 concurrent users. Adjust this value according to your organization's needs. |
|
SGA_TARGET |
600 MB (minimum) |
Recommended value for 50 to 60 concurrent users. Adjust this value according to your organization's needs. |
|
SHARED_POOL_SIZE |
150 MB (minimum) |
Recommended value for 50 to 60 concurrent users. You can change the value of this parameter after installation. |
|
UNDO_MANAGEMENT |
AUTO |
Specifies which undo space management mode the system uses. When set to AUTO, the instance starts in Automatic Undo Management (AUM) mode. |
|
UTL_FILE_DIR |
opa_home\ xmltemp |
Specifies each directory you access. If this environment is exclusively an Oracle Thesaurus Management System environment, you do not have to set this parameter. However, if you share this environment with Oracle Clinical or Oracle Adverse Event Reporting System (AERS), you must specify entries to support Oracle Clinical PDF layout generation and Oracle AERS. In a Windows environment, samples of the valid syntax are as follows:
In a UNIX environment, UTL_FILE_DIR requires an entry with two specified paths: one with and one without a trailing slash. Add these lines before any other UTL_FILE_DIR entries:
|
Add an entry to the tnsnames.ora file for the database. Add the tnsnames entry to the tnsnames.ora file on any existing Oracle Thesaurus Management System Forms Servers or Reports Servers. The tnsnames.ora entry must match the Oracle SID. In addition, if you are installing TMS with Oracle Clinical, the tnsnames.ora entry must be in lowercase.
This section describes how to add TMS database objects to each Oracle database that you will use for TMS.
About the Master Database Terminology
The procedures in this section describe how to install a database that you will use either as a single database in a non-distributed environment or as the master database in a distributed environment. These procedures and the Oracle Universal Installer screens use the term master database even when you are installing in a non-distributed environment.
About Installing New Databases in a Standalone Environment
If you plan to run TMS in a distributed environment and if you install a new database in a TMS standalone environment — that is, one not integrated with Oracle Clinical — you must run the following replication scripts after completing the installation:
opasrc01.sql
opasrc02.sql
For information about running these scripts, see Section 6.9.5, "Setting Up and Starting Symmetric Replication."
You do not have to run these replication scripts for a non-distributed standalone TMS database, or when you add a new database to a replicated TMS installation that is integrated with Oracle Clinical.
The Installer prompts you for passwords to several system accounts. In Oracle Database 11g Release 2 (11.2.0.2) Patch Set 1, some accounts are locked. Before you run the Installer, check these accounts. Unlock them if necessary. You will need to set their passwords when you run the Installer.
Make sure the following accounts are unlocked: SYSTEM, CTXSYS, XDB, and SYS.
When you have finished installing the database, relock any accounts that were locked except for SYSTEM and SYS, which should not be locked.
To start to install the TMS database:
Log in to the server computer using an account with system administrator privileges.
Insert the Oracle Clinical 4.6.2 and Oracle Thesaurus Management System 4.6.2 disk.
Locate and run the setup.exe file:
tms\install\setup.exe
The Installer opens to the Welcome screen.
Follow the instructions on the installation screens. For additional information about each screen, see Section 6.2.3, "Attend to the TMS Database Installation Screens."
The Oracle Universal Installer guides you through the installation and configuration of a TMS database.
Click Next to continue the installation.
Select TMS Database Install 4.6.2.0.XX (where XX is the build number).
Click Next.
Select Installation Type TMS Database Install 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 Install TMS Server Code Home Directory
Accept the default value for the directory path of the database server code. Click Next.
TMS Database Install Enter database connect string
Enter the database name. An alias must exist in tnsnames.ora for this database.
|
Note: The Installer sets the LOCAL registry setting to default all connections to this database. |
TMS Database Install 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 Install 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 Install 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 Install Directory for index tablespace datafiles
Enter the directory for TMS index tablespace files in the appropriate syntax for your operating system, including a trailing slash. The Installer enters the path you entered for tablespace datafiles as the default.
TMS Database Install Enter Password for schema
In a series of Installer screens, enter the passwords for SYS, SYSTEM, CTXSYS, OPA, RXC, TMS, TDX, BC4J_INTERNAL, and OPS$TMSBROWSER. You will need these passwords later.
TMS Database Install 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 installation. The screen confirms the name of the database installation, the location of the scripts used for the installation, and the location of the log file that you can view for the progress of the installation. Click Next.
Summary TMS Database Install 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.
If you are not using TMS in a distributed environment, skip this section. If you plan to use TMS in a distributed environment, use the instructions in this section to install each slave database in the environment.
As in the master database installation, you can modify the initial tablespace sizes. See Section 6.1.3, "Check Required Tablespaces" for information.
About Installing New Databases in a Standalone Environment
If you plan to run TMS in a distributed environment and if you install a new database in a TMS standalone environment — that is, one not integrated with Oracle Clinical — you must run the following replication scripts after completing the installation:
opasrc01.sql
opasrc02.sql
For information about running these scripts, see Section 6.9.5, "Setting Up and Starting Symmetric Replication."
You do not have to run these replication scripts for a non-distributed standalone TMS database, or when you add a new database to a replicated TMS installation that is integrated with Oracle Clinical.
In Oracle Database 11g Release 2 (11.2.0.2) Patch Set 1, some accounts are locked. You must unlock the accounts and verify their passwords before installing a database.
Locked accounts include the CTXSYS account, which is the database account that owns the interMedia context indexes.
To install the slave database objects:
Log in to the server computer using an account with system administrator privileges.
Insert the Oracle Clinical 4.6.2 and Oracle Thesaurus Management System 4.6.2 disk.
Locate and run the setup.exe file:
tms\install\setup.exe
The Installer opens to the Welcome screen.
Follow the instructions on the installation screens.
To install a slave database, follow the installation screens described for a master database installation in Section 6.2.3, "Attend to the TMS Database Installation Screens" with these exceptions:
In the Select Installation Type installer screen, select Slave.
In the Master Database installer screen, specify the master instance you installed.
To load the TMS jar file into each database:
Connect to the TMS application server as the opareps user.
Point to the database by setting the environment variables.
Change to the following directory:
OPA_HOME\tms\install
Load the tms_http.jar file manually into each database:
ORACLE_AS10gR2_HOME\bin\loadjava -user tms/password -force -definer -verbose -resolve tms_http.jar
If you installed TMS in the database using the full Oracle AS10gR2 installation then you can skip this manual procedure. You may verify the reports have been loaded successfully.
If you have installed TMS in the database using the Oracle AS10gR2 Forms and Reports Services, you must perform this manual procedure:
Transfer directory OPA_HOME\tms\install\reports to the database server.
Point to the database by setting the environment variables.
Change directories to the directory above the report folder.
Load the reports by entering the following command:
sqlldr opa/opa_password control=reports/tmsreports.ctl log=reports/tmsreports_database.log
This section describes creating an administrator-level TMS user, which is defined as a user with the OPA_ADMIN role. Users with this role have access to the Define Users window in TMS, which enables them to create additional users in the database.
Note:
If the user already has an Oracle Clinical OPS$ user account in the same database, you only need to grant the user the OPA_ADMIN role (see Step 4 only).To create a new Oracle account for a user:
Connect to SQL*Plus as system and run the following script:
OPA_HOME\tms\install\tmsadduser.sql
Enter a user ID. If the user account also accesses Oracle Clinical, enter the string OPS$ at the beginning of the user ID.
Enter a password for this user. Do not use the identified externally clause; explicitly assign a password.
Grant the user the OPA_ADMIN role:
grant OPA_ADMIN to user_id
If you are installing TMS in the same database as Oracle Clinical, you must register the database by running the TMS Installer.
Note:
Run TMS database registration on slave databases only after you have followed instructions in Section 6.9.5, "Setting Up and Starting Symmetric Replication."To register databases that are integrated with Oracle Clinical:
Log in to the server computer using an account with system administrator privileges.
Insert the Oracle Clinical 4.6.2 and Oracle Thesaurus Management System 4.6.2 disk.
Locate and run the setup.exe file:
tms\install\setup.exe
The Installer opens to the Welcome screen.
Follow the instructions on the installation screens. For additional information about each screen, see Section 6.7.2, "Attend to the TMS Database Registration Screens."
The Oracle Universal Installer guides you through registering a TMS database.
Click Next to continue the installation.
Select TMS Database Registration 4.6.2.0.XX (where XX is the build number).
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 Registration TMS Server Code Home Directory
Accept the default value for the directory path of the database server code. Click Next.
TMS Database Registration Enter Password for schema
In a series of Installer screens, enter the passwords for the SYSTEM, RXC, and TMS accounts. You will need these passwords later.
TMS Database Registration Enter the global name of TMS database
Enter the global name of the TMS database; for example, tms462.us.oracle.com. A SQL*Net TNS alias must exist with the same name; see Section 4.5, "Setting Up the SQL*Net Connections for Existing Databases."
To find the global name, connect to SQL*Plus and enter:
select * from global_name
TMS Database Registration Enter the global name of Oracle Clinical database
Enter the global name of the Oracle Clinical database. A SQL*Net TNS alias must exist with the same name.
To find the global name, connect to SQL*Plus and enter:
select * from global_name
The Information screen reports that the Installer will start a SQL*Plus session to complete the database registration. The screen confirms the location of the scripts used and the location of the log file that you can view for the progress of the installation. Click Next.
Summary TMS Database Registration 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.
See the Oracle Thesaurus Management System User's Guide for information about loading dictionaries.
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.
You can load dictionaries at any time. However, if you are installing TMS in a distributed environment, even without AERS, you may want to load dictionaries now so as to avoid doing another export/import later.
This section applies only if you are setting up a distributed environment. It includes the following topics:
Section 6.9.4, "Complete the Creation of the Slave Database"
Section 6.9.5, "Setting Up and Starting Symmetric Replication"
Section 6.9.6, "Register Slave Databases Integrated with Oracle Clinical"
If you are installing a distributed environment, you must create an export file of the master database, which you then import into the slave database.
To export data from the master database:
Log in to the master database server.
Set up a physical directory as follows:
Create a new directory. For example: /u01/app/dmp.
Grant read and write permission to the Oracle database.
Verify that the tmsrepexp.dmp file does not exist in the directory. The Data Pump export will fail with an error if the tmsrepexp.dmp file already exists.
Create directory object on the master database:
Connect to the master database as the SYS user:
sqlplus sys/password as sysdba
Create a directory object called TMS_REP_DIR and then map it to the physical directory you created in the previous step.
CREATE OR REPLACE DIRECTORY TMS_REP_DIR AS 'PHYSICAL_DIR_ON_MASTER';
For example:
CREATE OR REPLACE DIRECTORY TMS_REP_DIR AS '/u01/app/dmp';
Grant directory privilege to TMS:
GRANT READ, WRITE ON DIRECTORY TMS_REP_DIR TO TMS;
Place tms.par in your working directory.
Point local variables to the database.
Invoke the Data Pump Export utility:
expdp tms/password PARFILE=tms.par
By default, the Data Pump Export utility creates a log file named export.log. Note that you can use the LOGFILE parameter to customize the name of the log file. For example:
expdp tms/password PARFILE=tms.par LOGFILE=my_export.log
Verify that the tmsrepexp.dmp file and an export log file are created in the physical directory you created in Step 2.
Open the export log file and verify that no errors occurred.
At every slave database, import the export file from the master database.
To import data to the slave database:
Log in to the slave database server.
Set up a physical directory as follows:
Create a new directory. For example: /u01/app/dmp.
Grant read and write permission to the Oracle database.
Transfer the tmsrepexp.dmp file from the master database server to this directory.
Create directory object on the slave database:
Connect to the slave database as the SYS user:
sqlplus sys/password as sysdba
Create a directory object called TMS_REP_DIR and then map it to the physical directory you created in the previous step.
CREATE OR REPLACE DIRECTORY TMS_REP_DIR AS 'PHYSICAL_DIR_ON_MASTER';
For example:
CREATE OR REPLACE DIRECTORY TMS_REP_DIR AS '/u01/app/dmp';
Grant directory privilege to TMS:
GRANT READ, WRITE ON DIRECTORY TMS_REP_DIR TO TMS;
Point local variables to the database.
Invoke the Data Pump Import utility:
impdp tms/password CONTENT=ALL DIRECTORY=TMS_REP_DIR DUMPFILE=tmsrepexp.dmp TABLE_EXISTS_ACTION=SKIP
By default, the Data Pump Import utility creates a log file named import.log. Note that you can use the LOGFILE parameter to customize the name of the log file. For example:
impdp tms/password CONTENT=ALL DIRECTORY=TMS_REP_DIR DUMPFILE=tmsrepexp.dmp TABLE_EXISTS_ACTION=SKIP LOGFILE=my_export.log
Open the import log file and verify that no errors occurred.
To clean database objects and log files after you export and import data:
Drop directory object as SYS user:
REVOKE READ, WRITE ON DIRECTORY TMS_REP_DIR FROM tms; DROP DIRECTORY TMS_REP_DIR;
Delete the dump and log files from the physical directory.
Complete this procedure on each master database and each slave database.
For additional information about Oracle Data Pump, see the Oracle Database Utilities 11g Release 2 (11.2) documentation.
On the TMS application server for each slave database, set the local variable and run the TMSUPGSLAVE.SQL script. This script generates a log file in the install directory called tmsupgslave_database_name.log.
Note:
Despite the "UPG" in its name, TMSUPGSLAVE.SQL is the correct script for initial TMS slave database installations.To set the local variable and run TMSUPGSLAVE.SQL, enter:
set LOCAL=database_name
cd OPA_HOME\tms\install
sqlplus system/password
start tmsupgslave.sql
This section describes how to set up symmetric replication for the first time (for new installations), and how to resume it (for upgrades). The steps required depend on your installation configuration.
If you do not plan to use TMS in a distributed environment, skip this section.
If you are creating a new installation, perform all the steps in this section.
If you are upgrading, proceed to Section 6.9.5.2, "Start Replication on the Master Database."
If you choose to utilize symmetric replication, refer to the Oracle database manual that describes symmetric replication in detail. The instructions in this section provide the minimal list of the required tasks.
If you are establishing a distributed environment, you should enable symmetric replication for every TMS database.
Database Link and Privileges Changes
TMS users who use TMS for omission management and all users who perform replication must have a TMS database user account on either the master or local databases. In previous versions, TMS required that such users have accounts on both the master and local instances, but this is no longer necessary.
If you plan to integrate TMS with Oracle Clinical in a replicated environment, you must delete the Oracle Clinical RXA_READ public database link. Make sure you suspend Oracle Clinical replication, and then delete the RXA_READ link.
TMS creates its own public database link that does not contain connection information such as user ID and password. Oracle Clinical replication will use the TMS public link instead of RXA_READ.
To start replication following an initial installation of Release 4.6.2 (that is, you are not upgrading from a previous TMS release), complete the steps described in the following sections:
For every database in your TMS installation, check that the initdbname.ora file contains the following specifications:
JOB_QUEUE_PROCESSES — At least 1
GLOBAL_NAMES — TRUE
The opasrc01.sql script sets up common symmetric replication components for one database. You run this script once for each database in your installation.
To run the opasrc01.sql script:
Connect to the database as the SYSTEM user.
Run opasrc01.sql:
@OPA_HOME/tms/install/opasrc01
Respond to the prompts as follows:
Enter the name for local database: Enter the name of the database to which you are connected.
Enter the name for remote database: Press Enter. This script does not require the name of the remote instance.
Repeat these steps for every database in your TMS installation.
The opasrc02.sql script sets up common symmetric replication components. You run this script from each database location for each database location. For example, if you have three databases — A, B, and C — you must run the script six times: A for B, B for A, A for C, C for A, B for C, and C for B.
To run the opasrc02.sql script:
Connect to one of the databases as the SYSTEM user.
Run opasrc02.sql:
@OPA_HOME/tms/install/opasrc02
Respond to the prompts as follows:
Enter the name for local database: Enter the name of the database to which you are connected.
Enter the name for remote database: Enter the name of the remote database for which you want to create linkage.
Enter password: Enter the passwords for the SYSTEM and REPSYS schema on the local database, and the REPSYS schema on the remote database.
You may ignore errors indicating that database links already exist.
Repeat from each database location for each database location. Each time you run the script, enter the database to which you are connected at the "local database" prompt and the remote database at the "remote database" prompt.
This section describes how to start replication on the master instance in a distributed environment. Complete this procedure when you are starting replication for the first time after an initial installation and when you are starting symmetric replication after upgrading to TMS 4.6.2.
To start replication on the master database:
Connect to the master site as the REPSYS user.
Create the master replication group, generate support, and resume symmetric replication activity on the master site:
start tmsmsrdefine start tmsmsrgeneratesupport start tmsmsrresumeactivity
Connect as the TMS user.
Create the materialized view logs on the master site:
start tmsmsrmvlog
This section describes how to start replication on a slave instance in a distributed environment. Complete this procedure on each slave instance when you are starting replication for the first time after an initial installation and when you are starting replication after the upgrade to TMS 4.6.2.
For setting up multiple slave instances, suspend the master replication group for setting up slave 2, and later resume the replication activity for both Oracle Clinical (if suspended) and TMS.
To start replication on a slave instance in a distributed environment:
On each Materialized View Site (slave site), connect to SQL*Plus as the REPSYS user and create the materialized view group:
start tmsssrdefine
When the system prompts for the master database, enter master_site.
On each slave site, connect as the TMS user and create the materialized views:
start tmsssrcmv
When the system prompts for the master database, enter master_site.
On each Materialized View Site (slave site), connect as the REPSYS user and add the materialized views to the Materialized View and Refresh Groups:
start tmsssrmvrep start tmsssrmvref
On each Materialized View Site (slave site), connect as the SYSTEM user and compile all invalid:
start compile_all_invalid
On each Materialized View Site (slave site), connect as the REPSYS user and refresh the Materialized View Group:
exec dbms_refresh.refresh('TMS');
On each Materialized View Site (slave site), connect as the TMS user and run the following script to complete TMS processing:
start tmsscomplete
If you are completing an initial installation, this script populates the TMS_DEF_INSTANCES table.
If you are upgrading your installation, this script reports for which X_areas you need to run batch validation (or its equivalent). See Example 6-1, "Results of tmsscomplete Script" for more details.
Example 6-1 Results of tmsscomplete Script
For Oracle Clinical (System=OCL) Source Data, run batch validation for the following X_Areas. For non-Oracle Clinical Source Data, run the equivalent of Oracle Clinical's batch validation for the following X_areas
| SYSTEM | X_AREA |
|---|---|
| ES1 | 0 |
| ES2 | 1 |
| OCL | 101 |
| OCL | 102 |
Based on these sample results, you need to run batch validation for the studies with a CLINICAL_STUDY_ID of 101 and 102, and the equivalent of batch validation for external systems ES1 and ES2.
This step is required only if you are integrating TMS with Oracle Clinical. Follow instructions in Section 6.7, "Register Databases Integrated with Oracle Clinical."
|
 Copyright © 2000, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|