Tuning Oracle Services; Tuning - Red Hat CLUSTER MANAGER - INSTALLATION AND Administration Manual

Section 5.2:Tuning Oracle Services
Disable service (yes/no/?) [no]: no
name: oracle
disabled: no
preferred node: ministor0
relocate: yes
user script: /home/oracle/oracle
IP address 0: 10.1.16.132
netmask 0: 255.255.255.0
broadcast 0: 10.1.16.255
device 0: /dev/sda1
mount point, device 0: /u01
mount fstype, device 0: ext2
force unmount, device 0: yes
device 1: /dev/sda2
mount point, device 1: /u02
mount fstype, device 1: ext2
force unmount, device 1: yes
Add oracle service as shown? (yes/no/?) y
notice: Starting service oracle ...
info: Starting IP address 10.1.16.132
info: Sending Gratuitous arp for 10.1.16.132 (00:90:27:EB:56:B8)
notice: Running user script '/home/oracle/oracle start'
notice, Server starting
Added oracle.
cluadmin>

5.2 Tuning Oracle Services

The Oracle database recovery time after a failover is directly proportional to the number of outstanding
transactions and the size of the database. The following parameters control database recovery time:
•
LOG_CHECKPOINT_TIMEOUT
•
LOG_CHECKPOINT_INTERVAL
•
FAST_START_IO_TARGET
•
REDO_LOG_FILE_SIZES
To minimize recovery time, set the previous parameters to relatively low values. Note that excessively
low values will adversely impact performance. Try different values in order to find the optimal value.
Oracle provides additional tuning parameters that control the number of database transaction retries
and the retry delay time. Be sure that these values are large enough to accommodate the failover time
91