| Oracle® Thesaurus Management System Installation Guide Release 5.1 E53656-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Thesaurus Management System Installation Guide Release 5.1 E53656-03 |
|
|
PDF · Mobi · ePub |
Your Oracle Database and TMS Server installations must be complete before you install the TMS database.
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, do the following on the single or master database:
Section 4.1, "Restart Computer and Stop All Servers and Services"
Section 4.3, "Review Database Requirements and Recommendations (All Databases)"
Section 4.5, "Create a TMS Administrator User Account (All Databases)"
Section 4.6, "Register Databases Integrated with Oracle Clinical" (This step is required only if you are integrating TMS with Oracle Clinical.)
Section 4.7, "Load Dictionaries (Single or Master Database)"
Section 4.8, "Complete Distributed Environment Setup" (This step is required only in a distributed environment.)
Local (Slave) Databases If you are installing multiple databases in a distributed environment, perform the steps in the following sections on each local (slave) database:
Section 4.1, "Restart Computer and Stop All Servers and Services"
Section 4.3, "Review Database Requirements and Recommendations (All Databases)"
Section 4.5, "Create a TMS Administrator User Account (All Databases)"
Section 4.8, "Complete Distributed Environment Setup" This section includes tasks to be done on both the master and slave databases.
Restart the computer and then stop all servers and services:
Restart the computer.
In the Windows Services control panel, find Oracle Node Manager service and stop it.
From the Windows Start menu, go to All Programs, then Oracle Classic_asinst_1, then:
Forms Services, then Stop WLS_FORMS
Reports Services, the Stop WLS_REPORTS
Stop Admin Server: NOTE: This is required if you are installing the Front End and the Server (database server code), but if you are installing the Report Server the Admin Server must be running.
TMS database server code must be installed on Windows on the same computer as the TMS Front End. You must install the server first, then create one or more databases, and then install the Front End.
Make sure you have the information below, which is arranged in the order it is prompted for by the Installer during a fresh installation. The order for upgrades is somewhat different.
Note:
You must install the Oracle Thesaurus Management System database server before you install or upgrade the Oracle Thesaurus Management System database.OPA Home: the directory where Oracle Thesaurus Management System will be installed; by default:
C:\opapps51
Home Details: Select the Oracle Home that corresponds to the Oracle Forms and Reports home, similar to C:\oracle\middleware\Oracle_FRHome1.
To install the TMS Server:
Log in as a user with system administrator privileges.
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").
Run the following file as an administrator:
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.In the Select a Product to Install page, select Oracle Thesaurus Management System Server 5.1.0.0.x.
The Installer guides you through the installation and configuration of the TMS database server. Provide the information you assembled in "Gather Required Information."
A TMS database can be installed on Windows or UNIX. You must install the TMS database server (always on Windows) before installing a TMS database.
Before you install the TMS database component, review the following requirements and recommendations — such as service names, tablespace sizes, memory management, and initialization parameters — for each TMS database you plan to install.
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.
Choose to configure the database to accept connections as a service instead of a SID. Service name requirements for Oracle Thesaurus Management System include:
The service name must be less than 15 characters long.
It must not include the domain.
It must be all lowercase.
Note:
If you are installing the Oracle Thesaurus Management System database on a pluggable Oracle 12.1.0.1 database (PDB), see My Oracle Support article ID 1910177.1, How To Configure TNS / SQLNET using the local_listener parameter for Pluggable Database In Oracle 12c, Allowing a SQLNET Connection to the PDB. See "Finding Information on My Oracle Support".Table 4-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 Oracle Database Configuration Assistant. For instructions about the Database Configuration Assistant, see the Oracle Database 12c Release 1 (12.1.0.1) documentation, including online help and the Oracle Database 12.1.0.1 Installation Guide for the appropriate operating system.
Note:
Use the Custom Database installation option.
The following parameters are not listed under All Initialization Parameters. Click Show Advanced Parameters to set the following parameters as described in Section 4.3.7, "Set Initialization Parameters":
Db_cache_size
Db_files
Java_pool_size
Job_queue_process
Large_pool_size
The Custom installation option allows access to the Database Storage screen, where you can expand the Tablespaces folder in the tree on the left side of the screen and edit the following tablespaces as required; see Section 4.3.3, "Check Required Tablespaces"
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 12c Release 1 (12.1.0.1)'s Automatic Memory Management feature for a new or an upgraded TMS database.
Table 4-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 4-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 4-2 Required and Recommended Initialization Values in the init.ora File
| Parameter | Value | Comments |
|---|---|---|
|
COMPATIBLE |
11.2.0.4 |
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 |
null |
DO NOT set this value. In Release 5.1 onward, setting this value causes problems. |
|
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:
|
|
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 |
11.2.0.4 |
Acts as an umbrella for enabling a series of optimizer features based on an Oracle release number. NOTE: Oracle Thesaurus Management System 5.1 is certified on Oracle Database 11g optimizer features; see Section 7.7, "Run Scripts to Gather Schema Statistics for the 11g Optimizer." |
|
OPTIMIZER_MODE |
CHOOSE |
If you run TMS's statistics-gathering scripts, the CHOOSE value sets Oracle Optimizer to apply the execution plan that best minimizes response time. See Oracle Database documentation for more information. (CHOOSE is the default value when you specify 11.2.0.4 as the value of OPTIMIZER_FEATURES_ENABLE.) |
|
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. After 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 or greater |
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:
|
The tnsnames.ora file must have an entry for each database that matches the database's Oracle SID. There is a tnsnames.ora file in at least two locations in the installation. Oracle recommends maintaining a master file and copying it to each location whenever you add a database. If the database server has multiple Oracle Homes, the tnsentries for all databases should be maintained in a central location; for example: /etc/tnsnames.ora.
The tnsnames.ora file is on each database server at: oracle_home/network/admin. See Section 5.8, "Modify the tnsnames.ora File on the Application Server" for the application server locations.
This section describes how to add TMS database objects to each Oracle database that you will use for TMS.
The Installer prompts you for passwords to several system accounts. In Oracle Database, 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.
Before you start the installer, be sure you have the information it prompts for; see Section 4.4.5, "Attend to the TMS Database Installer Screens".
Home Details: The full path to the Oracle Home location on your application server; by default:
C:\app\oracle\Middleware\Oracle_FRHome1
TMS Server Code Home Directory: The system detects the location and enters the value for you. By default, it is C:\opapps51\tms.
Database Connect String: Enter the database name. It must be a valid TNS entry in your tnsnames.ora file; see Section 4.3.8, "Modify the tnsnames.ora File on the Database Server".
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
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\
Directory for index tablespace data files: Enter the path to the directory on the database server where the index 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\
Enter and confirm passwords for the following accounts:
SYS
SYSTEM
CTXSYS
OPA
RXC
TMS
TDX
BC4J_INTERNAL
OPS$TMSBROWSER
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.
When you are ready, install.
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.
To install a TMS database:
Log in as a user with system administrator privileges in the application tier.
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").
Run the file as an administrator:
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.In the Select a Product to Install page, select TMS Database Install 5.1.0.0.x.
The Installer prompts for the type of installation 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.
The Installer guides you through the installation and configuration of the TMS database server.
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 TMS 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\51\install\tmsadduser.sql
Enter a 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, register the single or master database by running the TMS Installer.
Note:
Run TMS database registration on slave databases only after you have followed instructions in Section 4.8.6, "Setting Up and Starting Symmetric Replication" as directed in Section 4.8.7, "Register Slave Databases Integrated with Oracle Clinical."Before you start the installer, be sure you have the information it prompts for; see Section 4.6.3, "Attend to the TMS Database Registration Screens".
To register your TMS database for use with Oracle Clinical:
Log in to the application tier server as a user with system administrator privileges.
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").
Run the following file as an administrator:
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.The Installer guides you through registering a TMS database.
Product to install: TMS Database Registration 5.1.0.0.x.
Home Details: The full path to the Oracle Home location on your application server; by default:
C:\app\oracle\Middleware\Oracle_FRHome1
TMS Server Code Home Directory: The system detects the location and enters the value for you. By default, it is C:\opapps51\tms\51.
Enter and confirm passwords for the following accounts:
SYS
TMS
RXC
Global name: Enter the global name of the TMS database; for example:
service_name
To find out the global name, log in to SQL*Plus and enter:
select * from global_name
Enter the global name of the Oracle Thesaurus Management System database. A SQL*Net TNS alias mustexist with the same name.
The Installer gives you information that you should make a note of.
When you are ready, install.
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:
Section 4.8.4, "Complete the Creation of the Slave Database"
Section 4.8.6, "Setting Up and Starting Symmetric Replication"
Section 4.8.7, "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 a 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 privileges 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
If you plan to use disconnected system integration (DSI), enter following commands:
set LOCAL=databasename sqlplus tms/password exec tms_dsi_xml_schema.InstallSchemas;
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 4.8.6.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 fresh installation of Oracle Thesaurus Management System (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.
You do not have to run this replication script when you add a new database to a replicated TMS installation that is integrated with Oracle Clinical.
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 TMS.
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 a TMS upgrade.
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 4-1, "Results of tmsscomplete Script" for more details.
Example 4-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 4.6, "Register Databases Integrated with Oracle Clinical."
|
 Copyright © 1999, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|