Technical data

Configuration Guidelines
Database Implementation Guidelines 4-3
• Tablespace level encryption is also supported using the following command:
Create tablespace <tablespace_name> logging datafile '<datafile
location>' size <initial size> reuse autoextend on next <next size>
maxsize unlimited extent management local uniform size
<uniform size> encryption using 'AES128' default storage(encrypt) ;
• Indexed columns can only be encrypted using the NO SALT Option. Salt is a way to
strengthen the security of encrypted data. It is a random string added to the data before it is
encrypted, causing repetition of text in the clear to appear different when encrypted.
Data Compression Recommendations
Oracle Utilities supports Advanced Data Compression, available with Oracle 11gR1 onwards, to
reduce the database storage footprint. Make sure that your resources are sufficiently sized for this
as it uses additional system resources. Compression can be enabled at the Tablespace level or at
the Table level.
For Exadata hardware the compression recommendations are:
• For the Final Measurement table (D1_MSRMT), keep the current table partition
uncompressed. All of the older partitions will be compressed based on QUERY HIGH
compression.
• For the Initial Measurement Data table (D1_INIT_MSMRT_DATA), always keep CLOBs in
securefile and medium compressed. Also keep the current table partition uncompressed. All
of the older partitions will be compressed based on QUERY HIGH compression.
• Load data into the uncompressed table partitions using a conventional load and then, once
data is loaded using a CTAS operation, load into a temporary heap table. Then truncate the
original partition. Alter the original partition into HCC compressed and then partition
exchange this with the temporary heap table.
• All multi column Indexes (primary as well as secondary) will be compressed using the default
compression. HCC or OLTP compression is not applicable on the top of compressed
Indexes.
For non-Exadata hardware the recommendations are the same as above, except that you cannot
use HCC compression (it is only available in Exadata database machine). Instead of HCC you can
use any other compression tool available to you for non-Exadata hardware.
All CLOB fields should be stored as SecureFiles and Medium compressed. This requires a
separate license for Advanced Data Compression. As a part of the schema, we create the product-
owned tables with compression turned OFF at the LOB level . If you have the license for
Advanced Data Compression, you can enable compression by updating the storage.xml.
Database Vault Recommendations
We support Database Vault from the Oracle Utilities Application Framework 4.1.0. All non-
application User IDs can be prevented from using DDL or DML statements against the
application schema. So SYS and SYSTEM cannot issue DDL or DML statements against
CISADM schema.
The application-specific administration account can issue DDL statements but should not be able
to perform any DML or DCL statements.
Application user must be given DML only permissions.
Database Vault can be used to control access during patch process and Install/Upgrade process.
Configuration is also supported beginning with the Oracle Utilities Application Framework 4.1.0
patch application with Database Vault.