Chat now with support
Chat with Support

Quest has tools and processes in place to identify, protect, detect, and remediate vulnerabilities and incidents when they occur, including external security partners. As part of our standard security operations, Quest does not use CrowdStrike in any of our operations. We are reviewing our third parties, and so far, there is minimal affect. It is Quest's policy not to provide further technical details unless they directly impact customer data.

Stat 6.3 - Install Notes

Installing Stat
Prepare for installation Unpack the 6.3.0 installer Install the Stat database Create a staging database (PeopleSoft Only) Install the Stat Client Configure the Stat database Update the System Maintenance table Install the Stat Central Agent Install the Stat Oracle Agent (Oracle E- Business Suite only) Configure the SYSTEM user account Update the PS Object Mover Instructions (PeopleSoft Only) Implement Stat

NORAv630-3.sql

1
Locate the script NORAv630-3.sql.
2
Find and replace the bracketed variables with the appropriate values.
•
Replace [DATABASENAME] with the name of database.
•
Replace [SPOOLPT] with the directory for the Session Log.

Execute the scripts

The Stat® database scripts are run via Oracle® SQL*Plus or Toad™ for Oracle.

1
For SQL*Plus, at the prompt, type: @ <drive:\> <path information>\ <filename>, and press Enter.
2
Execute NORAv630-1.sql.
3
Execute NORAv630-2.sql.
4
Execute NORAv630-3.sql.
5
Review the database logs and validate that the scripts ran without error.
Execute required Oracle E-Business Suite scripts (Oracle E-Business Suite only)

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.

Oracle patch compare support: Stat database (Oracle E- Business Suite Only)

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:

•
Oracle Note: 1112983.1 (11.2.0.x)
•
Oracle Note: 1612279.1 (12.1.0.x)

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:

$>loadjava –user [username]/[password]@[database] –force –resolve stat_db.jar
 
* 
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.
Also, for users who plan to compare form library files that have attached libraries, there are special configuration steps that must be performed. For more information, see Object compare support for form library files.

Running Stat with multiple Oracle versions

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:

set path=D:\oracle\non_default_oracle_client\BIN;%path% start stat.exe

This configures Stat to connect to the non-default Oracle client and allows other applications to connect to the version that is defined by ORACLE_HOME, even if that version is not supported by Stat, such as Oracle 8.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating