HP StorageWorks XP24000/XP20000 Database Validator User's Guide Abstract This guide provides information about configuring the HP StorageWorks Database Validator product on the HP StorageWorks XP family of storage systems for an Oracle database environment.
Legal and notice information © Copyright 2008-2009 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Overview of HP Database Validator ..................................................... 7 2 About Database Validator Operations .................................................. 9 HP Database Validator Components ............................................................................................. 9 Overview of Oracle HARD and Database Validator Operations ...................................................... 10 3 Preparing for Database Validator Operations ............................
Subscription Service .................................................................................................................. 34 HP Websites ............................................................................................................................ 34 Documentation Feedback ........................................................................................................... 34 Index ............................................................................................
Figures 1 Database Validator Overview ..................................................................................... 7 2 Database Validator Components ................................................................................. 9 3 Typical Database System Configuration ...................................................................... 10 4 Typical Database System Configuration with Database Validator .................................. 11 5 Sample Database Validator System Configuration .....
Tables 1 Range That Database Validator Checks When the Capacity of Virtual Volumes Is Increased by Using XP Thin Provisioning Software ...................................................................... 14 2 Volume Setup for Sample Configuration ..................................................................... 20 3 XP RAID Manager Parameters for File Types and Oracle Versions .................................. 23 4 Error Code and Error Contents when Operating RAID Manager ............................
1 Overview of HP Database Validator The HP Database Validator function of the XP24000 Disk Array and the XP24000 Disk Array is designed for the Oracle database platform. Database Validator prevents data corruption between the database and the storage system and protects existing Oracle data on the storage system. Figure 1 shows a functional overview of Database Validator operations.
Overview of HP Database Validator
2 About Database Validator Operations HP Database Validator Components Figure 2 shows the HP Database Validator system components and their functions for Oracle data validation checking. XP RAID Manager is used to specify the logical units (LUs) to be checked and the type of check to be performed (the type depends on the Oracle version). The files that are checked include data files (including tablespace files), redo log files, and control files. The files must be stored on raw volumes.
very robust data protection capabilities that can prevent data corruption within both DBMS and the storage system, but until now, they could not detect data corruption that occurred between DBMS and the storage system. The other data corruption risk is a non-Oracle application overwriting the Oracle data files on the storage system. The Database Validator function also protects existing Oracle data files from being overwritten by data from other applications.
Hardware acceleration: The new storage system channel adapters (CHAs) include hardware acceleration of Database Validator checksum computation. HP implementation of checksum validation using hardware acceleration minimizes performance impact (the impact depends on the system environment). Multiple levels of checking: In addition to the verification of checksums for overall database blocks, the storage system also performs checksum validation for lower-level data structures specific to the type of file.
About Database Validator Operations
3 Preparing for Database Validator Operations Requirements and Restrictions To use HP Database Validator, you need the following: • A supported storage system (see “Requirements and Restrictions” on page 13) • Host server that supports Oracle database software • Oracle-data validation service Requirements for the Storage System For HP Database Validator operations, you need a storage system that has all settings of the required hardware, microcode, and the Database Validator: • Microcode: The minimum micro
• Table 1 on page 14 shows the range that Database Validator checks when the capacity of virtual volumes is increased by using XP Thin Provisioning Software.
Note: The Oracle database needs to be constructed on raw devices (for example, no file system). Also, you need to set the DB_BLOCK_CHECKSUM parameter to TRUE. Note: Oracle database functionality of check data is slightly enhanced with Oracle9i Release2. Database Validator has two distinct modes: one mode for Oracle8i and Oracle9i databases and another mode for Oracle9i Release2 (and later) databases.
• • • • • • • Once the LUs are configured, the LVM does not issue any more writes so Database Validator checking can be enabled. If you need to change the LVM configuration of an LU that is set as a target of Oracle data checking, first delete the settings of the target LUs and disable the Oracle check function (Database Validator). Then, change the configuration. After changing the configuration, you can re-enable Database Validator and reset the LUs as targets of Oracle data checking.
Installing and Configuring XP RAID Manager After you have prepared for Database Validator operations, you are ready to install and configure XP RAID Manager (if it is not already installed and configured): • Installing XP RAID Manager: XP RAID Manager is installed on the host server. For instructions on installing XP RAID Manager, see the HP StorageWorks XP RAID Manager User's Guide.
Preparing for Database Validator Operations
4 Performing Database Validator Operations Starting Database Validator Operations Database Validator operations are controlled through XP RAID Manager commands. No other program product or application can be used. XP RAID Manager provides the raidvchkset, raidvchkdsp, and raidvchkscan commands to set and verify the parameters for Oracle data validation checking at the LU level. For detailed information on these commands, see the HP StorageWorks XP RAID Manager User's Guide.
Figure 5 Sample Database Validator System Configuration Volume Setup Table 2 shows the volume setup for the sample configuration shown in Figure 5. All mapping operations must be completed with Database Validator disabled. Notes: • This document does not describe storage system device configuration. See the configuration guide for the host platform (for example, the HP StorageWorks XP Disk Array Configuration Guide for Sun Solaris).
XP24000/XP20000 Disk Array CU: LDEV LUN VxVM Type * Raw Device Name** VxVM Settings Volume Name Concatenated /mnt/oractl1 Concatenated, and divided /mnt/oradata1, 00:03 3 OPEN-V /dev/dsk/c4t0d3 00:04 4 OPEN-V /dev/dsk/c4t0d4 00:05 5 OPEN-V /dev/dsk/c4t0d5 00:06 6 OPEN-V /dev/dsk/c4t0d6 00:07 7 OPEN-V /dev/dsk/c4t0d7 00:08 8 OPEN-V /dev/dsk/c4t0d8 Divided 00:09 9 OPEN-V /dev/dsk/c4t0d9 None Purpose Oracle control file (block size=8KB) /mnt/oradata2 Oracle data files
HORCM_MON #ip_address service poll(10ms) timeout(10ms) localhost horcm 1000 3000 HORCM_CMD #dev_name /dev/rdsk/c4t0d9s2 HORCM_DEV #dev_group dev_name oralog log1-1 oralog log1-2 oralog log1-3 oractl ctrl1-1 oractl ctrl1-2 oradata data1 oradata data2 oradata data3 orastok stokdata dev_name HORCM_INST #dev_group oralog oractl oradata orastok dev_name port# TargetID LU# MU# CL1-E 0 0 CL1-E 0 1 CL1-E 0 2 CL1-E 0 3 CL1-E 0 4 CL1-E 0 5 CL1-E 0 6 CL1-E 0 7 CL1-E 0 8 ip_address localhost localhost localhost lo
# # # # raidvchkset raidvchkset raidvchkset raidvchkset −g −g −g −g oralog −vt redo9 −vs 1 oractl −vt data9 −vs 16 oradata −vt data9 −vs 16 orastok −vt data9 −vs 4 Figure 7 Enabling Database Validator Checking for Sample Configuration Table 3 XP RAID Manager Parameters for File Types and Oracle Versions Oracle Version File Type Data file Oracle9i Release 2 data9 Control file Redo log file Data file Oracle9i prior to Release 2 Parameter for -vt Option redo9 data8 Control file Oracle8i Redo log f
# raidvchkset -g oradata -d data -vt data9 -vs 4 2880 71184960 # raidvchkset -g oralog -d log1 -vt redo9 -vs 1 2880 4799520 Note: 2879 + 1 = 2880 The SLBA and the ELBA is the offset from "vxdisk list" command. Example for the redo log # fire-2 >vxdisk list c4t0d9s2 Device: c4t0d9s2 devicetag: c4t0d9 type: sliced hostid: fire-2 disk: name=dg901_1 id=1031839952.2594.fire-2 group: name=dg901 id=1031840145.2607.
# ls /dev/rdsk/c4t0d* | .
raidvchkscan -p CL1-A -v cflag PORT# /ALPA/C TID# LU# Seq# CL1-A / ef/ 0 0 0 2332 CL1-A / ef/ 0 0 1 2332 CL1-A / ef/ 0 0 2 2332 CL1-A / ef/ 0 0 3 2332 CL1-A / ef/ 0 0 4 2332 Num LDEV# 1 0 1 1 1 2 1 3 1 4 BR-W-E-E D E B R D E B R D E B R D E B R D E B R MR-W-B D D D D D D D D D D D D D D D BR-W-B D E E D E E D E E D E E D E E SR-W-B-S D E D D D E D D D E D D D E D D D E D D Figure 11 Raidvchkscan Command Example with -v cflag Option Disabling and Restarting Database Validator Checking You can disable
vgcreate vgdata /dev/dsk/c4t0d1 /dev/dsk/c4t0d2 vgcreate vglog /dev/dsk/c4t0d3 /dev/dsk/c4t0d4 lvcreate -r n -m 1 -L 12 -n control01.ctl vgdata lvcreate -r n -m 1 -L 12 -n control02.ctl vgdata lvcreate -r n -m 1 -L 500 -n system01.dbf vgdata lvcreate -r n -m 1 -L 500 -n log01.log vglog lvcreate -r n -m 1 -L 500 -n log02.log vglog chown oracle:oinstall /dev/vgdata/r* chown oracle:oinstall /dev/vglog/r* Logical volumes are created with Bad Block Relocation turned off.
6. Enable integrity checking on all devices with the appropriate XP RAID Managerraidvchkset –vt [type] –vs bsize slba elba command, either for data or redo, and the appropriate start LBA and end LBA. This example shows how to set and display the validation parameters for the Oracle data files. Bsize units are bytes. For raidvchkset, STLBA and ENLBA units are in decimal; for raidvchkdsp, units are in hexadecimal, as specified by the –fx option.
The storage system outputs the error information in three ways: a service information message (SIM), a syslog (on the host), or a storage system internal sense byte (SSB): • SIM: Users can view the SIMs using XP Remote Web Console software. SIMs are automatically reported to the maintenance center (if contracted). Note: The default storage system setting is the SIM reporting for Database Validator is disabled.
4. 30 Finally, if the error cannot be resolved with the above steps, the error may have been caused by the OS, LVM, driver layer, or an intermittent hardware error. In this case, you should contact each vendor to resolve the problem. Database Validator protects your database from these rare error conditions, demonstrating the value of this functionality.
5 Troubleshooting Troubleshooting Oracle database: For troubleshooting information on Oracle database operations, see the Oracle user documentation or contact Oracle customer support. XP RAID Manager: For troubleshooting information on XP RAID Manager, see the HP StorageWorks XP RAID Manager User's Guide. Storage System: For troubleshooting information on the storage system, see the HP StorageWorks XP24000 Disk Array Owner's Guide or the HP StorageWorks XP20000 Disk Array Owner's Guide.
1. Find the error code from the logs displayed on the RAID Manager window. Figure 15 shows an example of a log displayed on the RAID Manager window. Figure 15 Example of a Log Displayed on the RAID Manager Window Error codes appear on the right of SSB=. The alphanumeric characters of last four digits on the left of the comma(,) indicates SSB1 (for example, B9E1), and the alphanumeric characters of last four digits on the right of the comma (,) indicates SSB2 (for example, B901). 2.
6 Support and Other Resources Related Documentation • • • • • • • • HP StorageWorks XP24000 Disk Array Owner's Guide HP StorageWorks XP20000 Disk Array Owner's Guide HP StorageWorks XP24000/XP20000 Remote Web Console User’s Guide HP StorageWorks XP RAID Manager User's Guide HP StorageWorks XP Disk Array Configuration Guide for Sun Solaris HP StorageWorks XP Disk Array Configuration Guide for HP-UX HP StorageWorks XP24000/XP20000 LUN Manager User's Guide HP StorageWorks XP Command View Advanced Edition Soft
HP Technical Support For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: • • • • • • Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions Subscription Service HP recommends that you register your product at the Subscriber’s Choice for Business website: http://www.hp.
Index I A acceleration, hardware, 11 inqraid command, 24 C O checksum validation, multiple level, conventions storage capacity values, 33 corrupt data, detecting, 10 operations, preparing for, 16 Oracle Data Validation Service, 15 Oracle database, creating, 28 Oracle setup, 22 D R data validation checking, Oracle, Database Validator checking, restarting, Database Validator checking, disabling, Database Validator checking, enabling, Database Validator checking, LVM considerations for, document relat
X XP RAID Manager setup, 21 XP RAID Manager, installing and configuring, 36
