HP XP Array Manager Software - Manual (Page 22)

HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
localhost horcm 1000 3000
HORCM_CMD
#dev_name dev_name dev_name
/dev/rdsk/c4t0d9s2
HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
oralog log1-1 CL1-E 0 0
oralog log1-2 CL1-E 0 1
oralog log1-3 CL1-E 0 2
oractl ctrl1-1 CL1-E 0 3
oractl ctrl1-2 CL1-E 0 4
oradata data1 CL1-E 0 5
oradata data2 CL1-E 0 6
oradata data3 CL1-E 0 7
orastok stokdata CL1-E 0 8
HORCM_INST
#dev_group ip_address service
oralog localhost horcm
oractl localhost horcm
oradata localhost horcm
orastok localhost horcm
Figure 6 Sample XP RAID Manager Configuration Definition File (horcm.conf)
Oracle Setup
The following steps must be performed before Database Validator checking is enabled:
• The Oracle database must run in Archive Log mode.
• The DB_BLOCK_CHECKSUM parameter of init.ora must be set to TRUE.
• In case of Tru64 UNIX or Windows platform, you must set the parameter in the init.ora file to
HARD_PROTECTION = TRUE.
Enabling Database Validator Checking
Figure 7 shows the XP RAID Manager raidvchkset commands used to enable Database Validator for
the sample configuration shown in Figure 5 :
• Parameters with −g specify the group of LDEVs with group name written in horcm.conf.
• Parameters with −vt specify the validation file type described in HP XP RAID Manager Parameters
for File Types and Oracle Versions .
• Parameters with −vs specify the Oracle data block size in units of 512 bytes. For example, 16
means 8KB.
Important: See the next section for important information on enabling Database Validator checking
with LVM considerations.
Performing Database Validator Operations 22