1 |
Locate the script NORAv630-3.sql. |
• |
Replace [DATABASENAME] with the name of database. |
• |
Replace [SPOOLPT] with the directory for the Session Log. |
The Stat® database scripts are run via Oracle® SQL*Plus or Toad™ for Oracle.
1 |
For Oracle® E-Business Suite users only, execute the NORAv630oa.sql script, located in the <installation package>\Scripts\Oracle\Install directory.
Modify the bracketed variables in a similar manner to the prior mandatory scripts.
If you are running Oracle® E-Business Suite and plan to use the object compare feature for developer objects (form, form libraries and reports) in patches, the Oracle JVM must be installed with your Stat® Repository. Refer to the Oracle Metalink document appropriate for the Oracle release of your Stat Repository:
After installing the Oracle JVM, you need to install the stat_db.jar file, located in the directory, <installation package>\scripts\Oracle. To do this, execute the following command, adding the appropriate connection parameters:
NOTE: For Oracle 12c , execute the loadjava command this way:
$>loadjava –force –resolve –user [username]/[password]@[database] stat_db.jar |
After loading the Java® classes, you need to recompile invalid PL/SQL modules in the database by running the script, utlrp.sql located in the <ORACLE_HOME>/rdbms/admin directory.
NOTE: Each Stat Client that will use the object compare feature for developer objects must be properly configured. For more information, see Oracle developer object compare support: Stat Client.
|
If you have more than one version of Oracle® installed on the same machine, Stat® connects by default to the client that is defined by ORACLE_HOME.
However, you may select an alternative Oracle client by creating a batch file, for example:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center