Benutzeranleitung / Produktwartung DB2 V8 des Produzenten IBM
Zur Seite of 51
Planning And Preparation Guide For SAP NetWeaver 7.0: z/OS Implementation: DB2 V8 DB2 9 Albert D. Rodi Consulting IT Specialist IBM Solution Technical Sales International Business Machines Corporation 1503 LBJ Freeway Dallas, TX 75234 (972) 280-4791 or TieLine 8-542-4791 E-mail: adrodi@us.
Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries AIX* On Demand Business Logo CICS* PR/SM DB2* Parallel Sysplex* D.
C ontents I General Preparation Steps II z/OS Hardware Preparation III AIX Hardware Preparation IV z/OS Software Preparation V DB2 and DB2 Connect Preparation VI DB2 Related OSS Notes VII AIX Software.
What is new with SAP Web Application Server 7.0 ? • The z/OS USS Application Server is no longer supported. However you can install the Central Services on USS as part of a High Availability solution.
1. Identify the technical implementation team members: z/OS System Programmer z Linux Administrator Security Administrator Unix System Serv ices Administrator Storage Administrator Network Administrator AIX/Windows Administrator DB2 DBA DB2 Systems Programmer R/3 Administrator z/OS Capacity Planning & Performance Administrator 2.
- Installation of SAP Solution Manager - Configuration of SAP Solution Manager - Front End Installation - Homogeneous and Heterogeneous System Copy for SAP Systems based on NetWeaver 2004s 3.
(IBM SG24- 6287) - DB2 UDB for z/OS V8: Through the Looking Glass and What SAP Found There (IBM SG24- 7088) - Disaster Recovery with DB2 UDB for z/OS (SG24- 6370) - DB2 Performance Expert for z/OS (SG.
5. Important OSS Notes: (service.sap.com/ notes ) 660528: Requirements to run SAP NetWeaver on zSeries 661260: Transports and Support Pac kages for 6.40 728743: zSeries: Release of DB2 V8 for SAP Comp.
797084: SUSE Linux Enterprise Server 9: Installation Note 892818: Application servers on Linux for zSeries: Settings 821904: Separating SCS instances for ABAP and J2EE 686905: DB2 for z/OS: DDIC Corrections (6.40, 7.0) 818291: zSeries: Windows 64 bit app server 144864: SAP Remote Services: Technical preparation 6.
II z/OS Hardware Preparation 1. Review Checklist in Installation Manual and at service.sap.com/platforms for supported z/OS server models . 2. Determine Hardware Configuration by completing the SAP sizing questionnaire for R/3 .
1.2 GB (Temporary installation disk space) 2 x zLinux Guest Memory (Swap Space) 4.3 GB (temporary disk space for every Installation DVD to be copied locally for installation) 13GB (disk space for the SAP filesystems ) 8-12GB (Linux) 200MB (CMS and the Linux boot disk) 4.
III AIX Hardware Preparation 1. Review Checklist in theComponent Installation Guide : SAP ERP 2005 ABAP+Java on AIX: IBM DB2 UDB for z/OS for base Hardware Requirements . 2. Determine Hardware Configuration by completing the SAP sizing questionnaire for R/3 .
IV z/OS Software Preparation 1. Review Software Checklist in Installation Manual. REQUIRED • z/OS 1.6* or higher with the following components installed: UNIX System Services, DFSMS, TCP/IP, LE370, DFSORT • JES2 or JES3 • z/OS Security Server (RACF V 2.
**Documentation and sample scripts for TSA are available from IBM. If the customer chooses an equivalent product they take full responsibility for configuring and testing that product with mySAP.
4. Define the necessary users via RACF definitions (review the SAP Security Guide for IBM DB2 UDB for z/OS) : - define z/OS groupid <SCHEMA> as this will be the creator of all DB2 objects (Defau.
9. Configure the TCP/IP protoco l for GB Ethernet : A. Define the z/OS I/O configuration for the OSA-Express Card: - Define channel path ID for OSA-Express channel with type=OSA - Define OSA-Express control unit with type=OSA - Define 2 OSA-Express devices - Define Unit Addresses for the Control Unit (2 Devices for LCS (D118,D119) B.
SAPCL as per Chapter 4 of the SAP Planning Guide for SAP NetWeaver for IBM DB2 UDB for z/OS. These processes run under Unix System Services (USS). 17. For z/OS V1.
V DB2 Preparation 1. Install DB2 subsystem. A separate ICF catalog is recommended for each DB2 subsystem based on the High L evel 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.
- recommended production initial definitions for DSNDB07 for an initial installation (each should be on a separate volume) : (4) 4K TableSpaces @ 200 cylinders each (2) 32K TableSpaces @ 200 cylinders each , Total = 1200 cylinders 5. Define archive log environment .
10. Install the Control Center Stored Procedures required by SAP as described in described in Chapter 3 of the SAP Database Administration Guide for SAP NetWeaver on IBM DB2 UDB for z/OS. The procedures are used for Database administration and replace the FTP submission of JCL streams used in previous releases.
15. Establish and test DB2 Backup/Recovery Procedures. These procedures should include a combination of DB2 and non-DB2 utilities in order to handle various recovery scenarios. In addition, DB2 V8 provides two new utilities for providing DB2 controlled system wide backup and a point in time recovery.
16. The recommendation is to develop a DB2 system libraries configuration that allows each DB2 subsystem to be migrated to a new level of DB2, or DB2 maintenance, individually. For instance, if this is a DB2 data sharing group, you want to migrate members one at a time.
VI DB2 Related OSS Notes 1043951: Release of DB2 9 for SAP components 1072066: DBA Cockpit: New function for DB Monitoring 1027452: DB2 z/OS CCMS: DBA Cockpit 746299: Recommended Settings for Linux fo.
509529 DB2 Changing the DB Host 513750 DB2 Data Sharing Topology 390016 DB2/390 BW: DB Settings and Performance 758550 DB2 System Parameter Check (DB16) 686905 History of statement cache statistics in.
VII AIX Software Preparation 1. Review Checklist in the Installation Guide: SAP ERP 2005 ABAB+Java on AIX: IBM DB2 UDB for z/OS for base Software Requirements. HIGHLY RECOMMENDED FOR AIX APPLICATION SERVERS • AIX Performance Toolbox and Performance AIDE for POWER Version 3.
VIII Windows Hardware/Software Preparation 1. Review Checklist in Component Installation Guide: SAP ERP 2005 SR1 ABAP+Java on Windows:IBM DB2 UDB for z/OS for base Software Requirements. 2. Certified Hardware is required for application servers. Current certified IBM models are: IBM eServer xSeries IBM BladeCenter Servers 3.
IX SAP Installation Preparation 1. Order SAP Installation Kit. 2. Build project plan for installation. 3. Setup OSS connection to SAP and test FTP capability to sapserv. * Pre-Install Check* 4. Obtain all necessary OSS notes. 5. Gather the information necessary to respond to the SAPinst system parameters required for the installation.
X Sample BPXPRMxx Member MAXPROCSYS(4096) MAXPROCUSER(200 ) MAXTHREADTASKS( 1000 ) MAXTHREADS(1000) MAXUIDS(200) MAXFILEPROC(2 000) MAXFILESIZE (omit) MAXPTYS(256) CTRACE(CTIBPX00) IPCMSGQMNUM(20000) .
FILESYSTYPE TYPE(HFS) ENTRYPOINT(GFUAINIT) ROOT FILESYSTEM('OMVS.ROOT') TYPE(HFS) MODE(RDWR) PARM('') MOUNT FILESYSTEM('OMVS.SAP.<SID>') TYPE(HFS) MODE(RDWR) MOUNTPOINT('/sap/<sid>') MOUNT FILESYSTEM('OMVS.
XI Sample DB2 DSNZPARMS DB2 V8 * = required /recommended value for SAP DSN6ENV MVS=XA DSN6SPRM RESTART, ALL, ABEXP=YES, ABIND=YES, AUTH=YES, AUTHCACH=4096, BINDNV=BINDADD, BMPTOUT=0, * CACHEDYN=YES, *.
RECALL=YES, RECALLD=120, * RELCURHL=YES, * RETLWAIT= 1, (Data Sharing only) RGFCOLID=DSNRGCOL, * RETVLCFK=NO, RGFDBNAM=DSNRGFDB, RGFDEDPL=NO, RGFDEFLT=ACCEPT, RGFESCP=, RGFFULLQ=YES, RGFINSTL=NO, RGFN.
DSN6LOGP DEALLCT=( 1440), MAXARCH=500, MAXRTU=2, * OUTBUFF=4000, * TWOACTV=YES, * TWOARCH=YES DSN6SYSP AUDITST=NO, * ACCUMACC=5, * CHKFREQ =10, CONDBAT=64, (>= MAXDBAT) * CTHREAD=1900 , (sum of TSO users + IDBACK) DLDFREQ=5, * IDBACK=1800 , 1.
* IDTHTOIN=0, RESYNC=2, RLFERRD=NOLIMIT, TCPALVER=YES DSN6GRP DSHARE=NO, GRPNAME=S4A, MEMBNAME=DNX1, COORDNTR=NO, ASSIST=NO END DSNHDECM CHARSET=ALPHANUM, * ASCCSID=819, AMCCSID=65534, AGCCSID=65534, .
DB2 9 * = required /recommended value for SAP DSN6ENV MVS=XA DSN6SPRM RESTART, ALL, ABEXP=YES, ABIND=YES, AUTH=YES, AUTHCACH=4096, BINDNV=BINDADD, BMPTOUT=0, * CACHEDYN=YES, * CACHEDYN_FREELOCAL=1, CA.
* PARTKEYU=YES, RECALL=YES, RECALLD=120, * RETLWAIT= 1, (Data Sharing only) RGFCOLID=DSNRGCOL, * RETVLCFK=NO, RGFDBNAM=DSNRGFDB, RGFDEDPL=NO, RGFDEFLT=ACCEPT, RGFESCP=, RGFFULLQ=YES, RGFINSTL=NO, RGFN.
TSTAMP=YES, UNIT=CART, UNIT2=CART DSN6LOGP DEALLCT=( 1440), MAXARCH=500, MAXRTU=2, * OUTBUFF=4000, * TWOACTV=YES, * TWOARCH=YES DSN6SYSP AUDITST=NO, * ACCUMACC=5, * ACCUMUID=11, * CHKFREQ =2, CONDBAT=64, (>= MAXDBAT) * CTHREAD=200 , (sum of TSO users + IDBACK) DLDFREQ=5, * IDBACK=50 , (>=20 and at least1.
STATIME=30, STORMXAB=5, STORTIME=180, * SYNCVAL=30, TRACSTR=NO, TRACTBL=16, * TBSBPOOL=BP2, * TBS BPLOB=BP40, * TSQTY= 720, * URLGWTH=100, * URCHKTH=1 DSN6FAC * DDF=AUTO, * CMTSTAT= INACTIVE, * IDTHTO.
TIMELEN=0 END Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 38 of 51 12/18/2007 Planning and Preparation Guide for SAP NetWeaver Version 6.
XII TCP/IP Connectivity - required for S AP NetWeaver - strategic communications protocol - any HW supporting standard TCP/IP can be used - ongoing enhancements are planned - take advantage of standar.
XIII Naming Conventions 1. The following elements should be part of an overall naming convention plan: SAP SID DR1 DB2 Started Task Names for MSTR, DBM1,DIST, IRLM DR11MSTR DR1 1DBM1 DR11IRLM DR11DIST.
XIV Application Server On z/OS Considerations * Note that only the SAP Central Services ASCS and SCS are now supported on Unix System Services under z/OS * 1. The following OSS Notes shoul d be reviewed : 595331 - z/OS enhanced ascii support & FTP updates 1009521 - Central Services does not start 2.
XV Sample OSA-Express GB Configuration SYS1.VTAMLST(XXTRL) XXTRL VBUILD TYPE=TRL * TRLEGBF8 TRLE LNCTL=MPC, READ=600,WRITE=601, DATAPATH=602, PORTNAME=PORTGBF8, MPCLEVEL=QDIO TCPIP.PROFILES(PROFILXX) ;OSA GIGABIT ETHERNET CHP F8 LG06 DEVICE PORTGBF8 MPCIPA NONROUTER LINK GIGAF8 IPAQGNET PORTGBF8 HOME 10.
XVI DB2 Backup/Recovery Notes (OSS Note 83000) NOTE: The procedures described here are applicable to DB2 Version 8. Version 8 provides two new utilities for backup and point in time recovery that provides a more robust solution that is less prone to errors, and reduces recovery time and labor time.
Recover to prior point in time - A recovery of all tablespaces, indexspaces, DB2 catalog, and DB2 Directory to a previous log RBA (three ways to acomplish this) - Conditional Restart to recover to any.
- Recover to a prior point in time corresponding to the time of FlashCopy - Reset volumes using FlashCopy, including BSDS and logs - Restart DB2 - Use transaction SM13 to resolve R/3 units of work - Recover to a prior point in time using FlashCopy + logs - Reset volumes using FlashCopy , but use current BSDS and active logs.
DB2 Version 8 Enhancements DB2 Version 8 enhances the SAP backup and recovery process by providing two new system utilities for system level backup and a point in time recovery for the entire SAP system. These are the BACKUP SYSTEM and RESTORE SYSTEM.
XVII SAP Automation And High Availability Solution 1. The following OSS Notes shoul d be reviewed : 569996 (Redbook Updates) 524816 2. Indicate at the time of the sizing that the SAP Central Services instance will run on z/OS, since this will affect the processing and memory requirements.
XVIII SAP A pplication Server on zLinux Considerations 1. Review the latest version of OSS Note 81737 for the supported Linux distribution. 2. Hardware requirements: - IBM eServer zSeries z800, z900, z990, z890, z9, z9 BC, z9 EC - Each Linux image requires disk space for boot and swap(20GB) - Minimum 512 MB Central Storage 3.
7. Recommendations from the j oint 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 lis.
XIX Sample SMS Storage Group Assignments 1. Here is a sample assignment methodology for setting up SMS Storage Groups. One recommendation is to name the storage groups starting with the 3 character SAP <SID> followed by the type of dataset.
ICF Catalog Names: CATALOG.SAPDB2.DR1LOG CATALOG.SAPDB2.DR1USR CATALOG.SAPDB2.DR1DB2 CATALOG.SAPDB2.DR1IC Catalog Structure: Catalog Alias ACS Dataset Name DR1USR DR1U DR1U.* DR1IC DR1IC DR1IC.** DR1DB2 DR1 DR1.SRCLIB DR1.DBRMLIB DR1.RUNLIB.LOAD DR1.DSNDB*.
Ein wichtiger Punkt beim Kauf des Geräts IBM DB2 V8 (oder sogar vor seinem Kauf) ist das durchlesen seiner Bedienungsanleitung. Dies sollten wir wegen ein paar einfacher Gründe machen:
Wenn Sie IBM DB2 V8 noch nicht gekauft haben, ist jetzt ein guter Moment, um sich mit den grundliegenden Daten des Produkts bekannt zu machen. Schauen Sie zuerst die ersten Seiten der Anleitung durch, die Sie oben finden. Dort finden Sie die wichtigsten technischen Daten für IBM DB2 V8 - auf diese Weise prüfen Sie, ob das Gerät Ihren Wünschen entspricht. Wenn Sie tiefer in die Benutzeranleitung von IBM DB2 V8 reinschauen, lernen Sie alle zugänglichen Produktfunktionen kennen, sowie erhalten Informationen über die Nutzung. Die Informationen, die Sie über IBM DB2 V8 erhalten, werden Ihnen bestimmt bei der Kaufentscheidung helfen.
Wenn Sie aber schon IBM DB2 V8 besitzen, und noch keine Gelegenheit dazu hatten, die Bedienungsanleitung zu lesen, sollten Sie es aufgrund der oben beschriebenen Gründe machen. Sie erfahren dann, ob Sie die zugänglichen Funktionen richtig genutzt haben, aber auch, ob Sie keine Fehler begangen haben, die den Nutzungszeitraum von IBM DB2 V8 verkürzen könnten.
Jedoch ist die eine der wichtigsten Rollen, die eine Bedienungsanleitung für den Nutzer spielt, die Hilfe bei der Lösung von Problemen mit IBM DB2 V8. Sie finden dort fast immer Troubleshooting, also die am häufigsten auftauchenden Störungen und Mängel bei IBM DB2 V8 gemeinsam mit Hinweisen bezüglich der Arten ihrer Lösung. Sogar wenn es Ihnen nicht gelingen sollte das Problem alleine zu bewältigen, die Anleitung zeigt Ihnen die weitere Vorgehensweise – den Kontakt zur Kundenberatung oder dem naheliegenden Service.
