Install Oracle Database on the Database Server.
Open or download the installation guide for your operating system:
Refer to the Oracle Database Installation Guide for instructions.
As a part of the Oracle Database, Argus Safety requires:
Oracle Database Enterprise or Standard Edition
Oracle Database Client
Oracle Identity Manager (OIM) with WebGate
Follow the instructions in the Oracle Database Installation Guide, making selections appropriate for Argus Safety as noted in the following sections.
You can configure the database as part of the database software installation or after, using the Database Configuration Assistant (DBCA). Argus Safety supports installation on either a Container Database (CDB) containing a Pluggable Database (PDB) or a non-CDB database.
For an explanation of which options require an additional license, see the Database Licensing Information User Manual at
http://docs.oracle.com/database/121/DBLIC/toc.htm
During installation of the database software (binaries, or server code), select the following:
Advanced or Typical installation
Time Zone
Oracle Real Application Clusters (RAC) (Optional)
Oracle Partitioning (Optional)
Oracle Automatic Storage Management (Recommended)—To provide an alternative to conventional volume managers, file systems, and raw devices.
Character Set: Select AL32UTF8.
Automatic Memory Management (Recommended)—To manage instance memory to allow the Oracle Database instance to automatically manage and tune it for you.
Oracle Text (Required)—Included automatically if you install the database during server installation.
Oracle JVM (Required)
Oracle XML DB (Required)—Included automatically if you use the Oracle Database Configuration Assistant to create the database. http://docs.oracle.com/database/121/ADXDB/appaman.htm#ADXDB2700
We recommend that you evaluate each site before installation and on an ongoing basis to determine whether these settings are suitable for your business needs.
# |
Database Parameters | Small(under 30,000 cases reported per month) | Mid-Sized(30,000 to 200,000 cases reported per month) | Large(200,000 to 1,000,000 cases reported per month) | Very Large(over 1,000,000 cases reported per month) |
---|---|---|---|---|---|
1 | MEMORY_TARGET | 2 GB | 3 GB | 10 GB | >10 GB |
2 | PROCESSES | Expected concurrent users + 100 | Expected concurrent users + 100 | Expected concurrent users + 100 | Expected concurrent users + 100 |
3 | MEMORY_MAX_TARGET | >= value set
for MEMORY_TARGET |
>= value set
for MEMORY_TARGET |
>= value set
for MEMORY_TARGET |
>= value set
for MEMORY_TARGET |
4 | OPTIMIZER_SECURE_VIEW_MERGING | FALSE | FALSE | FALSE | FALSE |
5 | CURSOR_SHARING | EXACT | EXACT | EXACT | EXACT |
6 | WORKAREA_SIZE_POLICY | AUTO | AUTO | AUTO | AUTO |
7 | JOB_QUEUE_PROCESSES | 25 | 25 | 25 | 25 |
8 | SHARED_POOL_SIZE | 500 MB | 500 MB | 1 GB | 2 GB |
9 | DB_CACHE_SIZE | 500 MB | 500 MB | 1 GB | 2 GB |
10 | DB_BLOCK_SIZE (bytes) | 8192 | 8192 | 8192 | 8192 |
11 | PGA_AGGREGATE_TARGET | 500 MB | 500 MB | 1 GB | 2 GB |
12 | NLS_LENGTH_SYMANTICS |
# |
Setting | Small(under 30,000 cases reported per month) | Mid-Sized(30,000 to 200,000 cases reported per month) | Large(200,000 to 1,000,000 cases reported per month) | Very Large(over 1,000,000 cases reported per month) |
---|---|---|---|---|---|
1 | Number and Size of Redo Log Files | 5 Groups * 100 MB | 5 Groups * 100 MB | 5 Groups * 100 MB | 5 Groups * 100 MB |
2 | TEMP Tablespace Size | 8 GB | 16 GB | 32 GB | 64 GB |
3 | Undo Tablespace Size | 8 GB | 16 GB | 32 GB | 64 GB |
The system uses the time zone of the DB server to do GMT calculations. This time zone is initially loaded during the Argus database installation.
To set up the time zone:
Go to Argus Console > System Configuration > Database.
From the Database Server OS Timezone drop-down list, select a time zone.
Alternatively, update the DATABASE_TIMEZONE key in CMN_PROFILE table.
Make sure:
Argus is using function gss_util.gmt_offset to derive the GMT OFFSET which impacts the calculation of GMT date and time.
Daylight Savings Time. Assume that Daylight Savings Time starts on First Sunday of April at 2:00 AM and it ends on Last Sunday of October at 2:00 AM.
Partitioning of CMN_AUDIT_LOG table can significantly improve performance of the system on large Argus Safety databases. Range partitioning can be performed on the CMN_AUDIT_LOG table for the LOG_DATETIME_STAMP column.
We recommend create partitioning on a yearly basis. Partitioning must be performed and maintained by a qualified database administrator.
Partitioning is an optional Oracle Database feature that can be purchased separately.