IBM DB2 V8, DB2 9 manual 12/18/2007Page 49

Page 49

7. Recommendations from the joint IBM/SAP Platform Team:

￿Always use the latest z/VM release available , currently z/VM 5.3

￿Apply z/VM 5.1 APAR 63636 (PTF UM31312)

￿Apply all z/VM APARs listed in OSS Note 81737

￿Additional z/VM Considerations (these are specific to the customer configuration and the workload characteristics) :

￿Consider HiperSockets , Vdisk, Vlan for network/swapping optimization

￿Consider workload distribution techniques such as add/reduce CPUs dynamically as LPAR load changes and distribute workload over day/night/weekend

￿Disable unused Linux guests to eliminate resource consumption (memory, CPU)

￿Limit number of CPUs per Linux guest to reduce overhead cycles for unused CPUs

￿Use FCP/SCSI devices instead of FICON/ECKD or ESCON to improve throughput

￿Use Quick Dispatch for dialog intensive Linux guests to improve response time

￿Review possible overcommitment of memory to avoid paging in z/VM

￿Apply the Fixed I/O Buffers Fix (SLES 9 SP1) available at

http://www.128.ibm.com/developerworks/linux/linux390/perf/tuning_rec_fixed_io_buffers.html

￿For additional fixes and tuning hints please see:

http://www.128.ibm.com/developerworks/linux/linux390/index.html

￿Use multiple swap volumes to avoid I/O bottlenecks.

￿Always use the latest available Linux kernel (currently SLES 10 SP1)

￿Configure swap volumes on the disk subsystem so that multiple channels are used. If for example 15 of the 2.3 GB logical swap volumes are being mapped to a single 72 GB physical drive the throughput rate will be low.

￿FICON can support more swap volumes than channels. For example if you are using 8 FICON channels then define 16-24 swap devices.

￿In Linux set the priority equal for all swap volumes.

￿Minimize paging and swapping. Define the Linux guests as small as possible without having Linux swapping occur on a regular basis.

￿If using extended memory for z/VM avoid paging in and out of extended memory.

￿Do not use z/VM TCP/IP as an IP router, this results in high CPU consumption.

￿Do not use MDC for SAP, this will conserve memory.

￿Tune the number of SAP work processes using SAP transaction SM50 or SM66.

￿For the HiperSocket definition to the DataBase LPAR use an MTU size of 16K or larger.

Copyright 2006 IBM Solutions Technical Sales (STS)

12/18/2007Page 49 of 51

12/18/2007

 

Image 49
Contents Albert D. Rodi Trademarks VII What is new with SAP Web Application Server 6.40 ? What is new with SAP Web Application Server 7.0 ?General Preparation Steps DB2 DBA 12/18/2007Page 6 12/18/2007Page 7 12/18/2007Page 8 12/18/2007Page 9 II z/OS Hardware Preparation 12/18/2007Page 11 III AIX Hardware Preparation IV z/OS Software Preparation Required for High Availability ENQ/SCS SolutionRequired Highly Recommended12/18/2007Page 14 12/18/2007Page 15 Class Nameiggcas 12/18/2007Page 17 DB2 Preparation MLMT=4 MAXCSA=0 DEADLOK=5,1 12/18/2007Page 20 System Longlog Drain Delay Drainwait Retry Retrydelay Timeout TermMaxro Drain ALLVI DB2 Related OSS Notes Sapcl FAQ12/18/2007Page 24 Highly Recommended for AIX Application Servers AIX Software PreparationViii Windows Hardware/Software Preparation SAP Installation Preparation MAXSHAREPAGES131072 Sample BPXPRMxx MemberForkcopycow Afinet Transport for TCP/IP DB2 = required/recommended value for SAP Sample DB2 DsnzparmsIRLMSWT=300, * LRDRTHLD=10 MAXKEEPD=8000, * MINSTOR=YES NPGTHRSH=10SYSOPR1=SYSOPR RECALL=YES RECALLD=120 RELCURHL=YESXLKUPDLT=TARGET DSN6ARVP ALCUNIT=TRK, CYL CATALOG=YESMON=YES IDFORE=60 LBACKOUT=NOAPPENSCH=EBCDIC MAXKEEPD=8000, * MINSTOR=YES MXDTCACH=128, * NPGTHRSH=10 PROTECT=NO PARTKEYU=YES RECALL=YES RECALLD=120SECQTY=100 LBACKOUT=NO, * LOGAPSTG=100 LOBVALA=1GB LOBVALS=50GB IDFORE=60 IDXBPOOL=BP3 IMPDSDEF=NO IMPTSCMP=YESMGEXTSZ=YES MON=YES TSQTY=720 TIMELEN=0 END TCP/IP Connectivity XIISAP SID DR1 SapinstDR11DBM1 DR11IRLMXIV Gateway XV Sample OSA-Express GB ConfigurationStart PORTGBF8 Recover TABLESPACE/RECOVER Indexspace DB2 Backup/Recovery Notes OSS NoteStop DB2 12/18/2007Page 45 12/18/2007Page 46 Xvii SAP Automation And High Availability Solution NFS 12/18/2007Page 49 XIX Sample SMS Storage Group Assignments Sort SYSSoftw HFS

DB2 V8, DB2 9 specifications

IBM DB2 is a family of data management products that provide powerful capabilities for managing large amounts of data. Among its various versions, DB2 9 and DB2 V8 stand out due to their advanced features and technologies that cater to both enterprise needs and modern database requirements.

DB2 9, also known as "Viper," was a significant release that brought substantial enhancements to the database management system. One of its standout features is its support for XML data. This version introduced a native XML storage architecture, allowing users to store, retrieve, and manage XML data efficiently. The advanced query capabilities for XML data made it easier to integrate both structured and unstructured information into applications.

Another notable aspect of DB2 9 is its enhanced security features. It introduced features like label-based access control, ensuring that sensitive data could be properly managed according to the security policies of an organization. This version also included a transparent data encryption mechanism, protecting data at rest without impacting performance.

DB2 V8, released prior to DB2 9, presented several key features that had a lasting impact on database technology. One of its major advancements was the introduction of pureXML, which laid the groundwork for handling XML data. DB2 V8 also provided improved performance through enhancements such as table partitioning, which allowed for more efficient data organization and retrieval.

Additionally, DB2 V8 emphasized high availability and disaster recovery, incorporating features like DB2 HADR (High Availability Disaster Recovery). This allowed organizations to ensure data continuity even in the event of system failures, a critical aspect for enterprise environments that rely on uninterrupted access to their data.

Both versions of DB2 leveraged advanced technologies such as multi-version concurrency control (MVCC), which enhanced transaction integrity and performance. Their ability to support various platforms, including Linux, UNIX, and Windows, demonstrated IBM's commitment to providing flexible solutions tailored to different environments.

In summary, both IBM DB2 9 and DB2 V8 established a strong foundation in the database management ecosystem. With features focused on XML data management, enhanced security, performance improvements, and high availability, these versions have equipped organizations with the tools necessary to handle contemporary data challenges efficiently and effectively. Their legacy continues to influence database technology today, highlighting IBM's enduring impact on data management solutions.