Running Oracle OLTP workloads in HP Integrity VM 4.3

6
Integrity VM guest configuration
The Integrity VM guest was configured as follows:
Hardware configuration
• 8 virtual CPUs with 100 percent entitlement
• 64 GB RAM with dynamic memory disabled
• All storage is presented to the guest using AVIO whole LUNs
– 8 LUNs used for holding Oracle binaries
– 16 LUNs used for holding Oracle redo logs
– 32 LUNs used for holding Oracle data files
– 16 LUNs used for holding Oracle archive logs
– 16 LUNs used for holding “clean” copies of the Oracle database
Software configuration
• HP-UX 11i v3 March 2011 Data Center OE
• HP Integrity VM 4.3 guest kit
• HP OnlineJFS 5.0.1
• HP-UX patches installed in the VM guest:
– PHCO_41194 – OnlineJFS 5.0.1 fixes
– PHKL_41728 – OnlineJFS 5.0.1 fixes
– PHSS_37042 – Required by Oracle
• kctune parameters
– The “/opt/tuneserver/bin/tuneserver –o” command (part of the Tune-N-Tools product) loads an
optimized set of kernel tunable values for Oracle workloads.
– Oracle also requires other kernel tunables be set to specific values:
Ο ncsize>=35840
Ο ninode>=34816
Ο maxfiles_lim>=63488
Ο shmseg>=512
Network configuration
• All virtual NICs are created using AVIO.
• The following NDD parameters are required by Oracle and added to the /etc/rc.config.d/nddconf file:
– tcp_smallest_anon_port=9000
– udp_smallest_anon_port=9000
– tcp_largest_anon_port=65500
– udp_largest_anon_port=65500