IBM DB2 9, DB2 V8 manual DB2 Preparation

Page 18

VDB2 Preparation

1.Install DB2 subsystem. A separate ICF catalog is recommended for each DB2 subsystem based on the High Level Qualifier for DB2 datasets. the ICF Catalog should contain only the catalogued objects for a single DB2 subsystem. However, with DB2 V8 and DB2 9 the recommendation is to have two ICF Catalogs, one for each Copy Pool. There is a DataBase Copy Pool, that will contain the SAP tablespaces, SAP indexspaces, DB2 Catalog, and DB2 Directory. There is also a Log Copy Pool that will contain the Active Log Datasets and the BSDS Datasets. The reason for this separation is that during a RESTORE SYSTEM only the DataBase Copy Pool will be restored to DASD, not the Log Copy Pool, and we do not want the ICF Catalog containing the Logs and BSDS restored. This is explained in Chapter 7 of the redbook SG24-7088.

Review all of the setup information in Chapter 3 of the SAP Database Administration Guide for SAP NetWeaver on IBM DB2 UDB for z/OS.

This chapter describes in detail the setup activities such as RRS, Stored Procedure Setup, and z/OS Unicode Conversion Services.

2.Apply all recommended PTFs from OSS Note 81737.

3.Modify group attach name in SYS1.PARMLIB(IEFSSNxx) if using data sharing. The recommendation is to use the SAP SID for the group attach name, and the SAP SID followed by a member number for each DB2 member within the group. See the recommended naming conventions in Section XIV.

4.Configure DB2 active log datasets and DSNDB07:

-for a nonproduction system (3) log datasets @ 1000 3390-3 cylinders each for LOGCOPY1 and LOGCOPY2 minimum on separate volumes

-for a production system (6) volumes are recommended for active log datasets (one dataset per volume)

-for installation disable archiving with the hidden zparm OFFLOAD=NO and use

(6)volumes for active log datasets (one dataset per volume)

-place active log datasets and BSDS datasets on separate controllers

for maximum availability

- recommended production initial definitions for DSNDB07 for a large installation (each should be on a separate volume, ~1300 logged in users) :

(7)4K TableSpaces @ 660 cylinders each

(5)4K TableSpaces @ 500 cylinders each

(3)32K TableSpaces @ 185 cylinders each , Total = 7675 cylinders

Copyright 2006 IBM Solutions Technical Sales (STS)

12/18/2007Page 18 of 51

12/18/2007

 

Image 18
Contents Albert D. Rodi Trademarks VII What is new with SAP Web Application Server 7.0 ? What is new with SAP Web Application Server 6.40 ?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 Required Required for High Availability ENQ/SCS SolutionIV z/OS Software Preparation 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 Maxro Timeout TermLonglog Drain Delay Drainwait Retry Retrydelay Drain ALLSapcl FAQ VI DB2 Related OSS Notes12/18/2007Page 24 AIX Software Preparation Highly Recommended for AIX Application ServersViii Windows Hardware/Software Preparation SAP Installation Preparation Sample BPXPRMxx Member MAXSHAREPAGES131072Forkcopycow Afinet Transport for TCP/IP IRLMSWT=300, * LRDRTHLD=10 Sample DB2 DsnzparmsDB2 = required/recommended value for SAP MAXKEEPD=8000, * MINSTOR=YES NPGTHRSH=10XLKUPDLT=TARGET DSN6ARVP ALCUNIT=TRK, CYL RECALL=YES RECALLD=120 RELCURHL=YESSYSOPR1=SYSOPR CATALOG=YESIDFORE=60 LBACKOUT=NO MON=YESAPPENSCH=EBCDIC MAXKEEPD=8000, * MINSTOR=YES MXDTCACH=128, * NPGTHRSH=10 PARTKEYU=YES RECALL=YES RECALLD=120 PROTECT=NOSECQTY=100 IDFORE=60 IDXBPOOL=BP3 IMPDSDEF=NO IMPTSCMP=YES LBACKOUT=NO, * LOGAPSTG=100 LOBVALA=1GB LOBVALS=50GBMGEXTSZ=YES MON=YES TSQTY=720 TIMELEN=0 END XII TCP/IP ConnectivityDR11DBM1 SapinstSAP SID DR1 DR11IRLMXIV XV Sample OSA-Express GB Configuration GatewayStart PORTGBF8 DB2 Backup/Recovery Notes OSS Note Recover TABLESPACE/RECOVER IndexspaceStop 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 Softw SYSSort 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.