![]() The OWNING_LOCATION and LOCATION_CODE have a limit of maximum 15 characters. Further, the OWNING_LOCATION and LOCATION_CODE in several tables must match the DB_NAME. The DB_NAME in OCL_STATE reference codelist must match the service name. You can successfully install Oracle Clinical in a pluggable database only if the database is configured to receive connections as SERVICE rather than the SID. If you are upgrading an existing database: To do so, leave DB_DOMAIN null when you create the target database instance. Make sure GLOBAL_NAME does not include the domain name. If you are upgrading your database through export and import:Ī. If you are upgrading your database using export and import, do the following: If you are upgrading to a RAC environment, you must import your database(s) to a single RAC node before running the Installer to upgrade it. If you use disconnected replication you must insert credentials for this account manually. If your installation includes multiple databases using either replication or RAC, each database needs an OCPSUB account and its credentials are created in this Wallet on the database server during Oracle Clinical database installation. The OCPSUB proxy account, which is used for database access for parameterized submission (PSUB) jobs. ![]() The database Wallet stores the password for two accounts: The Installer uses these to create the database Wallet in the location you specify. SAS View: The directory where Oracle Clinical will generate SAS views Oracle recommends: OPA Home: The directory where Oracle Clinical will be installed Oracle recommends: Home Details: The ORACLE_HOME location, which is where you installed Oracle Database 12.1.0.2 for example:ĭrive:\app\oracle\ product\12.1.0.2\ dbhome You must have the following information ready to enter in the Installer screens:
0 Comments
Leave a Reply. |