Stat 6.2 - Install Notes

Install the Stat database

This section contains instructions for the scripts that need to be run against the Development (optional), and Production databases. The scripts are located under a scripts directory on the Stat® CD. Each script, which is supplied with the Stat Installation CD, must be edited to replace certain variables prior to its execution. Because they perform actions such as granting access to the Stat User ID and creating database objects, the path information supplied in the scripts is critical.

Read all instructions included within the scripts before proceeding with script execution.

NOTE: The Stat user password is set in the first new install script. This password can be modified after the installation is completed. At least one administrative user needs to be logged into the Stat application at the time. For more information, see the section Changing the Database Password, in the Stat System Administration Guide, Chapter 3, Stat Security.

Stat on Oracle

Locate the necessary scripts.

Oracle® install scripts are located in <installation package>\scripts\Oracle\Install. Run the first three scripts to create the Stat® database regardless of your change management module. See the comments in each script for a complete description of its purpose.

•

NORAv620-1.sql

•

NORAv620-2.sql

•

NORAv620-3.sql

Modify the scripts as noted below.

Execute the appropriate scripts for your development environment using SQL*Plus or Toad® for Oracle only (Do not use other third-party tools).

CAUTION: Each script should be run one-time only.

NORAv620-1.sql

Locate the script NORAv620-1.sql.

Find and replace the bracketed variables with the appropriate values from the database pages of the Pre-Installation Checklist completed by the customer:

•

Replace [DATABASENAME] with the name of the database.

•

Replace [SYSTEMPWD] with the password of the Oracle® user SYSTEM.

•

Replace [SPOOLPT] with the directory for the Session Log.

•

Replace [MOUNTPT] with the directory path for the data file. If possible, spread MOUNTPT over multiple disks.

NOTE: We recommend the use of locally managed tablespaces and, if running Oracle 11g or 12c, Automatic Segment Space Management as included in the script.

You must have Automatic Undo Management enabled on your database.

Auto-extensibility is enabled by default in this script. The Database Administrator may choose to alter the Tablespace create statements to disable Auto-extensibility.