Running Oracle OLTP workloads in HP Integrity VM 4.3

7
Filesystem configuration
Each of the Oracle filesystems is created using OnlineJFS 5.0.1 and disk layout version 7. Each filesystem resides in a
separate LVM 2.2 volume group. The filesystems were created using LVM Distributed Extent Allocation and 1 MB extents.
• /oracle
– Contains the Oracle binaries
– Comprised of eight AVIO LUNs in HP 4400 EVA disk group 1
– Created with an 8 KB block size (bsize=8192)
– Mounted with default VxFS mount options
• /oracle/fast_recovery_area
– Contains the Oracle archive log files
– Comprised of 16 AVIO LUNs in HP 4400 EVA disk group 1
– Created with a 1 KB block size (bsize=1024)
– Mounted with default VxFS mount options
• /oracle/pristine
– Contains a “clean” inactive copy of the Oracle database
– Comprised of 16 AVIO LUNs in HP 4400 EVA disk group 1
– Created with an 8 KB block size (bsize=8192)
– Mounted with default VxFS mount options
• /oracle/oradata
– Contains the active Oracle database files
– Comprised of 32 AVIO LUNs in HP 4400 EVA disk group 1
– Created with an 8 KB block size (bsize=8192)
– Mounted with the “cio” mount option, enabling concurrent I/O
• /oracle/redo
– Contains the Oracle redo log files
– Comprised of 16 AVIO LUNs in 4400 EVA disk group 2
– Created with a 1 KB block size (bsize=1024)
– Mounted with the “cio” mount option, enabling concurrent I/O
Oracle configuration
In general, application software should be configured on a VM just as it would be on a physical Integrity system.
Oracle is configured on the Integrity VM as follows:
• Oracle 11gR2 Enterprise Edition (patch level 11.2.0.2.0)
• Automatic Memory Mode enabled
• Automatic Maintenance Tasks enabled
• Archive Mode enabled
• Three redo log groups, each 1 GB in size
• Datafiles created with “bigfile” option to allow growth beyond 32 GB
• init.ora Parameters
– db_block_size=8192 (8 KB Database Block Size)
– filesystemio_options=setall (Use Concurrent I/O When Possible)
– memory_target=42949672960 (40 GB Memory Target)