| Oracle® Clinical Installation Guide Release 5.0.1 E36499-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Clinical Installation Guide Release 5.0.1 E36499-02 |
|
|
PDF · Mobi · ePub |
The Parameterized SUBmission process (PSUB) schedules and runs jobs, reports, and batch processing for Oracle Clinical. In order to support using Oracle Real Application Clusters (RAC), the implementation of PSUB has changed in Oracle Clinical 5.0. See Chapter 11, "Upgrading an Oracle Clinical Installation to Release 5.0.1" for more information about changes and Section 8.1, "Setting Up PSUB" for information about the revised requirements.
You must start one PSUB service for each Oracle Clinical database on the same server as the database.
This chapter includes the following topics:
The following steps are required to set up the parameterized submission process in Oracle Clinical 5.0.
You must create several directories on the PSUB Server and enter their paths in the OCL_STATE local reference codelist, with a few related values; see the "Setting Up Batch Job File Viewing" section of the "Setting Up File and Image Viewing" chapter of the Oracle Clinical Administrator's Guide for more information.
These reference codelist settings are new in Release 5.0.
Note:
See Chapter 9, "Setting Up SAS" for information about new OCL_STATE settings related to SAS configuration.Beginning in Release 5.0, PSUB users no longer need:
their own OS account
a user name beginning with OPS$
their own directory for PSUB outputs
New Users To add new users, use the 5.0 ocl_add_user.sql script, indicating which new users need to run PSUB jobs; for more information see the Oracle Clinical Administrator's Guide.
Existing Users If you are upgrading from an earlier version of Oracle Clinical, use the migration script oclupg50migrateusers.sql to give users who need to run PSUB jobs access to the opapps account; see the Oracle Clinical Administrator's Guide.
PSUB Administrator User You can give a user the role RXC_VWJOBS (new in 5.0) to allow him or her to:
View all users' jobs
View the output from those jobs.
Stop any job.
You can use either of the following scripts to grant this role to a user:
ocl_add_user
ocl_grant_revoke_rxc_vwjobs.sql (This script can also be used to revoke the role.)
See the Oracle Clinical Administrator's Guide for more information.
In Release 5.0.1 the Installer automatically installs the PSUB service on the database server. You must start it manually using the instructions below.
Instructions for starting and stopping PSUB automatically and manuallyare included in theOracle Clinical Administrator's Guide.
To start the PSUB service on UNIX:
Log in as the opapps user. By default, the opapps uses the C shell.
Set up the environment:
opa_setup <database_name> <code_environment>
For example:
opa_setup prod 50
Start the PSUB service:
start_psub database_name code_environment wallet_alias
For example:
start_psub prod 50 <wallet_alias>
where prod is the connect string for the database instance to which the PSUB service connects;
where 50 is the name of the code environment;
where wallet_alias is the name of the Wallet specified during installation. By default it is the same as the database name.
Check the following log files in the $RXC_CENTRAL_LOG directory:
rxcpsd_instance_environment_1.log
rxcpsd_instance_environment_2.log
To start the PSUB service on Windows:
Log in as opapps. (You set up the PSUB service to start as the opapps user, but in Windows you can start the service when logged on as another user.)
Set the PSUB service parameters:
In the Start menu, navigate to Administrative Tools, then Services.
From the list of services in the Services dialog box, double-click the name of the database for this service. It is in this form:
PSUB Service database
Enter values for the Log On parameters:
database code_environment [verbose | noverbose] value-of-RXC_ROOT wallet_alias
For example: prod 50 verbose c:\\opapps\\oc\\50 <Wallet_name>
where prod is the connect string for the database instance to which the PSUB service connects;
where 50 is the name of the code environment;
where wallet_alias is the name of the Wallet specified during installation.
Note:
If your entry requires a backslash (\), you must enter two (\\). Alternatively, you can enter the path using single forward slashes, for example, c:/OPA_HOME/oc/50.Click Start.
Exit from the Services dialog box.
Check the PSUB service log file in <RXC_ROOT>/log for any warning or error messages.
To test your PSUB installation:
Open Oracle Clinical.
Submit a 3GL job such as Batch Validation or a PL/SQL job such as Study Unfreeze.
Verify that Oracle Clinical creates the log and output files by clicking on the View log and View output buttons.
If you encounter problems or errors, review the messages in the PSUB log files created in the following directory:
You can customize the PSUB service as follows:
Automatic Startup — By default, the PSUB service does not start automatically when you restart a server computer. However, you can configure the PSUB service to start automatically.
Job Numbering — You can change Oracle Clinical's default job numbering algorithm.
For more information about managing and customizing the PSUB servicePSUB service, see the Oracle Clinical Administrator's Guide.
PSUB considerations in a RAC installation:
In a RAC installation, Oracle recommends installing the Oracle Clinical Database Server, which includes the PSUB Server, on at least two RAC nodes. If PSUB goes down on one node, or if the node itself goes down, you can start PSUB on the other node with little interruption of service.
You must start one and only one PSUB service for each database. Oracle Clinical cannot detect if more than one PSUB service is running, so results are unpredictable in that case.
Create the same directory structure for PSUB files on each computer where PSUB may run. That way you do not have to change the OCL_STATE reference codelist value for the five PSUB directories.
Note:
However, you do have to change the OCL_STATE SERVER_NAME value when you start PSUB on a different server.If you use NFS to share the files, users will still be able to access files for jobs performed on the other node unless the node itself fails.
PSUB supports the following scenarios in a RAC environment:
If the database instance on the PSUB server goes down, but its server is still active, PSUB will transparently continue to process jobs for the other database instances in the RAC environment.
If one PSUB service or server fails, PSUB can be started for that database on another server.
If another node is added or removed, PSUB continues to work.
If the PSUB server goes down or is removed, an administrator can manually start the PSUB service on another server with minimum downtime.
In the event of a PSUB failure, current PSUB jobs are affected differently based on their state at the time of PSUB failure:
SCHEDULED or ENTERED jobs are picked up by the newly started PSUB service.
SUBMITTED jobs will likely need to be re-submitted.
STARTED jobs continue to run, regardless of PSUB status.
Note:
There is no notification if a PSUB service fails. In this case, a user's job does not complete and he or she must contact the administrator. The administrator checks the log file, starts PSUB on another node, and changes the SERVER_NAME value in the OCL_STATE reference codelist.See Section 1.4, "Supported Configurations with Oracle Data Guard and RAC" for more information.
|
 Copyright © 1996, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
