Best practices for install Database server that requires a high transactions rate such as Control-M/Server or Enterprise Manager that has a high execution count and or a high job count.
 

This KA replaces SLN000000181318

Users Affected: Users of an Database vendors

Description
-----------------
CONTROL-M/Server  8.x, 9.0, 9.0.x and CONTROL-M/Enterprise Manager 8.x, 9.0, 9.0.x 
when using an Oracle database, Sybase database, MS SQL database, or PostgreSQL database, be aware of the following:
1. Too much workload can be put on too few hard disks. 
2. When RedoLog files, WAL, Transaction log are placed on RAID-5 disks
3. When Rollback tablespace is placed on RAID-5 disks 


To optimize your system:

1. Firstly install Oracle, Sybase, PostreSQL on a disk other than the one on which the Unix SWAP 
file resides. (At least two hard disks).

2. Secondly assign the Redo Log, WAL, Transaction logs to a separate disk drive.

3. Thirdly make sure that the Redo Log, WAL, Transacitons logs  file is not using a RAID-5 disk. (No RAID.
RAID 0, RAID 0+1, RAID 10 are OK).

4. Fourthly assign the Rollback tablespace Log to a separate disk drive.

5. Fifthly make sure that the Rollback tablespace file is not using a RAID-5 disk. 
(No RAID. RAID 0, RAID 0+1, or RAID 10 are OK).

6. Sixthly assign the Control Files Log to a separate disk drive.

7. Seventhly make sure that the Control Files are not using a RAID-5 disk. 
(No RAID. RAID 0, RAID 0+1, or RAID 10 are OK).

Note that each and everyone of these steps will improve the performance of the 
database. It is more likely that the ones at the top of the list will improve the 
performance than those lower down. 

Network Latency between the application and an External database can greatly impact the throughput and capacity of your Control-M environment.
the recommended latency is provided as a guideline the higher number of execution the lower latency value you will require.