Migrating Sybase Ase To Power7 - IBM Power7 Optimization And Tuning Manual

Miscellaneous
Miscellaneous specifications for Oracle are described in this section:
ulimits (run smit chuser or edit /etc/security/limits to create a stanza for Oracle)
should be set to -1 (unlimited) for all values except core.
The maximum number of PROCESSES allowed per user (run smit chgsys to set) should
be set to maxuproc >= 2048. 16 KB is a commonly suggested value for Oracle.
Environment variables should be set as follows:
– AIXTHREAD_SCOPE=S (set in Oracle profile)
– LDR_CNTRL=DATAPSIZE=64K@TEXTPSIZE=64K@STACKPSIZE=64K (set in the Oracle profile
and the Oracle listener's environment)
– There is an option to use ldedit to edit the Oracle binary files so that they use 64 KB
pages directly. Run the following command:
# ldedit –btextpsize=64k –bdatapsize=64k –bstackpsize=64k
$ORACLE_HOME/bin/oracle
Disk and adapter resources
– To set hdisk, run lsattr –El hdisk<>.
• The queue depth might vary among 8, 16, 20, and 24, depending on the storage
• max_transfer might need to be adjusted upward, depending on the largest I/O
– To set FC Adapter, run lsattr –El fcs<> and fcstat -e.
• max_xfer_size must be at least equal to max_transfer at the hdisk level.
• num_cmd_elems might need to be increased if fcstat -e reports a persistent
• If fcstat –e reports a persistent, non-zero value for No DMA Resource Count,

Migrating Sybase ASE to POWER7

Sybase ASE is widely used. In the past two years, many migrations of Sybase ASE to
POWER7 were completed or are in progress. Two published white papers provide
comprehensive documentation for general preferred practices and for migration to POWER7:
Optimizing Sybase Adaptive Server Enterprise (ASE) for IBM AIX, available on the IBM
Techdocs website and on the Sybase website:
– http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101429
–
http://www.sybase.com/detail?id=1096191
This paper is a joint IBM and Sybase publication that was originally written in 2006 and
has been updated twice since then, most recently in Spring, 2012. The authors of the
current version are Peter Barnett (IBM), Mark Kusma (Sybase), and Dave Putz (Sybase).
Using ldedit: Whenever a patch is applied or an Oracle relink is performed, the
ldedit command must be run again.
vendor. A queue depth of 2 on SAN devices usually indicates a driver mismatch, but
is the default for Hitachi HDS on AIX; increase this value to 8 as a starting point.
Queue wait and queue overflow that is detected by running iostat –Dl might
indicate a need to increase queue depth.
requested by Oracle; a typical starting point for Oracle on AIX is 0x100000.
non-zero value for No Command Resource Count.
contact support.
Appendix C. POWER7 optimization and tuning with third-party applications
193