Technical data

Configuration Guidelines
4-2 Oracle Utilities Meter Data Management Database Administrator’s Guide
Configuration Guidelines
This section includes general recommendations for configuring various database objects and
includes a brief syntax overview. It covers the general aspects of the database objects and does not
cover any specific implementation requirements.
Index
Index recommendations specify points that need to be considered when creating indexes on a
table.
1. Indexes on a table should be created according to the functional requirements of the table
and not in order to perform SQL tuning.
2. The foreign keys on a table should be indexes.
In an Oracle Utilities Application Framework environment, always make sure that the
optimization parameters are set as follows:
optimizer_index_cost_adj=1
optimizer_index_caching=100
This will make sure that the optimizer gives a higher priority to index scans.
Table Partitioning Recommendations
Oracle Utilities recommends using a minimum of 'n' partitions for selective database objects,
where 'n' is number of RAC nodes.
Transparent Data Encryption Recommendations
Oracle Utilities supports Oracle Transparent Data Encryption (TDE). Oracle 11gR1 supports
tablespace level encryption. The application supports tablespace level encryption for all
Application data. Make sure that the hardware resources are sufficiently sized for this as TDE uses
additional hardware resources. The Oracle Advanced Security license is a prerequisite for using
TDE.
Please consider the following when implementing TDE:
• Create a wallet folder to store the master key. By default, the wallet folder should be created
under $ORACLE_BASE/admin/<sid>.
• The wallet containing the master key can be created using the following command:
alter system set encryption key authenticated by "keypasswd"
• The wallet can be closed or opened using the following commands:
alter system set wallet open identified by "keypasswd";
alter system set wallet close;
• Column level encryption can be achieved using the following commands:
create table <table_name>
(name varchar2(200) default ' ' not null,
bo_data_area CLOB encrypt using 'AES128',
bo_status_cd char(12) encrypt using 'AES128')
lob (bo_data_area) store as securefile (cache compress)
tablespace <tablespace_name>;
• AES128 is the default encryption algorithm.