Download PDF - IBM Redbooks

More documents

Recommendations

Info

11.After finishing the DB2 subsystem installation, review SAP Note 81737 for the recommended DB2 PUT level and PTFs. a. Check that the DB2 service level is current as specified in SAP Note 81737. b. Apply the SAP Automated PTF Check as explained in SAP Note 183311. 12.Verify the installation of the DB2 subsystem, as explained in 3.8 of the SAP DBA Guide: DB2 for z/OS (V10). 13.Verify that you applied all database server-related recommendations in 3.1, “Performance Tuning Considerations Before Installing an SAP System,” of the Planning Guide SAP on IBM DB2 for z/OS, version 2.50 - 2011-10-01. Continue with “Preparing SAP NetWeaver Application Server platforms” on page 182. SAP rules for the DBM1 address space virtual storage The general virtual storage rule for SAP is to set ECSA and ESQA to reserve approximately. 1700 MB of extended private (user) region for the DBM1 address space (in the range 1600 -1800 MB). However, this setting is less critical for DB2 10. Configuring temporary space in SAP The table spaces in the workfile database that have a zero secondary quantity are given preference for Sort Workfile to use. Additional sort workspace might be needed because of more frequent use of a 32K page-size table space in DB2 9 (and higher) compared to DB2 8. The table spaces in the workfile database that have a nonzero secondary quantity are given preference for DGTT use. Because of a change in the table space selection algorithm in DB2 9 (and later) based on record size, when a 32K table space is needed, for functional reasons, space might not be available. As a good practice, have 80% of table spaces as 32K and 20% as 4K page-size table spaces in DSNDB07. This installation uses the following initial allocations: ► 14 GB total for production ECC DSNDB07 ► 20 GB for production BW DSNDB07 Changes are required after installation depending on SAP application landscape and usage. DB2 provides instrumentation for workfile sizing. The counters for monitoring temporary space utilization at the DB2 subsystem level are included in the IFCID 2 (statistics record). For more information, see Chapter 13 in SAP on DB2 9 for z/OS: Implementing Application Servers on Linux for System z, SG24-6847. SAP database naming conventions With DB2 10, SAP introduces database implicit creation so that DB2 can create databases and table spaces when they are needed. All SAP tables are in single table spaces. For implicitly created objects, DB2 10 uses the default STOGROUP SYSDEFLT. DB2 10 uses the VCAT associated with SYSDEFLT for the high-level qualifier for all objects in this storage group. In 11.3 of the SAP DBA Guide: DB2 for z/OS (V10), SAP recommends assigning a separate VCAT name to SYSDEFLT through DB2 installation job DSNTIJTM: ► Change the VCAT name to a name you recognize, for example SAPCAT or CAT. The new name is used by the SAP table spaces and index spaces when you install the SAP application. 176 Running SAP Solutions with IBM DB2 10 for z/OS on the IBM zEnterprise System
– SAPINST implicitly creates a table space for SAP in the SMS storage group assigned to the SAP DB2 objects. – Consider also creating a DB2 default STOGROUP, for example: SAPDEFLT, and assign the VCAT name to that used by the DB2 catalog and directory table spaces. This step distinguishes the objects created by SAP from other objects. ► Based on DB2 Advanced Copy Services (ACS) routines, SMS can properly place the implicit databases or table spaces on the DASD allocated for SAP data. SMS cannot place them on the DASD volumes allocated for the DB2 catalog, directory, and other data sets that are not specific to SAP (DSNDB04 and DSNDB07). DFSMS storage management ACS routines for SAP DB2 10 requires SMS to manage the DB2 catalog and directory. New catalog and directory data sets created by the enabling new function mode (ENFM) process rely on SMS, with Extended Format (EF) and Extended Addressability (EA) enabled. During the SAP installation, some of the DB2 catalog and directory objects are converted to a partition by growth (PBG) with a data set size (DSSIZE) of 64G, which implies the following actions: ► VSAM objects that are greater than 4 GB must be SMS managed. ► The data class in the ISMF panel, with EF and EA, must be turned on. ► The data class ACS routine must set the DB2 catalog and directory objects to this data class with EF or EA enabled. Setting the value is done easily because we know that the third qualifier is DSNDB01 or DSNDB06. Other DB2 data sets, such as logs and the BSDS, are not implicitly created and require explicit creation during the installation process. In the ACS routine data set, create SMS definition members for data classes (DATACLAS), storage classes (STORCLAS), management classes (MGMTCLAS), and the SMS storage groups (STOGROUP). SMS support of the DB2 CREATE STOGROUP command: For allocations with non-guaranteed space, specify VOLUMES("*") with one asterisk (*) only. Using a real volume serial number without guaranteed space results in unpredictable results under certain conditions. By creating a STOGROUP and specifying VOLUMES("*"), SMS can choose a volume for allocation. SAP creates STOGROUPs with VOLUMES("*"). Therefore, ensure that your storage administrator adds an * to their test of device allocations in the ACS routines. SAP uses this implicit function with DB2 10. SMS storage groups for SAP With DB2, you must define several SMS storage groups for the SAP application. According to our naming schema, storage groups are required for the following purposes: CAT The DB2 catalogs, the work database, RUNLIB, SRCLIB, and DBRMLIB. SAP The SAP DB2 VSAM data sets for table space and index spaces. Logging alternatives Single-log LOG The DB2 active log data sets, DB2 BSDS data sets, DSNLOAD, DSNMACS, and DSNEXIT. Dual-log LG1 and LG2 Identical groups for LOGCOPY1 and LOGCOPY2. Appendix B. Planning, preparing, and implementing the SAP landscape 177
Page 1:
ibm.com/redbooks Front cover Runnin
Page 4 and 5:
Note: Before using this information
Page 6 and 7:
2.10.2 IBM zEnterprise BladeCenter
Page 8 and 9:
System software planning. . . . . .
Page 10 and 11:
Trademarks IBM, the IBM logo, and i
Page 12 and 13:
Maxim Kukarev is a Client Technical
Page 14 and 15:
xii Running SAP Solutions with IBM
Page 16 and 17:
1.1 IBM DB2 on System z and SAP The
Page 18 and 19:
technologies, it provides advanced
Page 20 and 21:
1.2.3 SAP Industry Solutions SAP In
Page 22 and 23:
8 Running SAP Solutions with IBM DB
Page 24 and 25:
2.1 SAP NetWeaver composition 2.1.1
Page 26 and 27:
Consequently, the central instances
Page 28 and 29:
► Data layer. The database instan
Page 30 and 31:
Integration ESB / Connectors Figure
Page 32 and 33:
2.4 Rolling maintenance Within one
Page 34 and 35:
2.7 Database server Another compone
Page 36 and 37:
Metro Mirror Figure 2-7 Metro and M
Page 38 and 39:
2.10.4 zEnterprise Ensemble System
Page 40 and 41:
System p or System x AIX, Linux on
Page 42 and 43:
SAP mixed 3-tier structure The data
Page 44 and 45:
3.1 Features implicitly used by SAP
Page 46 and 47:
3.1.4 Scalability improvements for
Page 48 and 49:
Insert time per row in msec. 500,00
Page 50 and 51:
New tables are automatically create
Page 52 and 53:
3.3 SAP modifications to optimize t
Page 54 and 55:
The solution is the Hybrid DBSL, wh
Page 56 and 57:
Figure 3-5 New DBM1 display Enhance
Page 58 and 59:
- Accumulated wait time for global
Page 60 and 61:
The view shown in Figure 3-8 for th
Page 62 and 63:
3.4.1 IN-list in-memory tables DB2
Page 64 and 65:
With DB2 10, the new access type NR
Page 66 and 67:
2. Ensure that the user who is crea
Page 68 and 69:
4.1 Installing Linux on System z, S
Page 70 and 71:
Installing the server from DVD We i
Page 72 and 73:
Verifying the installation In the I
Page 74 and 75:
Registration: To access the SAP Ser
Page 76 and 77:
Figure 4-4 Support Package list Fig
Page 78 and 79:
lnxsu11:t73adm 64> telnet wtsc59oe
Page 80 and 81:
2. Configure the JCL head. From the
Page 82 and 83:
4.2.2 Considerations for migration
Page 84 and 85:
Figure 4-8 DB2_V10_CHECK report Imp
Page 86 and 87:
4.2.4 Considerations for data shari
Page 88 and 89:
You must make the following changes
Page 90 and 91:
lnxsu11 Figure 4-12 SAP system land
Page 92 and 93:
Product Vendor Type Version SAP Net
Page 94 and 95:
5.1 Functions of Unified Resource M
Page 96 and 97:
5.2 Simplifying management tasks in
Page 98 and 99:
Figure 5-6 DBA Cockpit initial pane
Page 100 and 101:
Figure 5-8 Global Times panel Tip:
Page 102 and 103:
Figure 5-10 Buffer Pools The Buffer
Page 104 and 105:
Table 5-1 highlights the tasks or a
Page 106 and 107:
Tip: To enable the capture of syspl
Page 108 and 109:
Figure 5-14 AIX monitoring data Fig
Page 110 and 111:
► DB2 Network Stats ABAP report (
Page 112 and 113:
3. Enter the perfkit command to sta
Page 114 and 115:
You can also access monitoring data
Page 116 and 117:
Example 5-3 Linux memory utilizatio
Page 118 and 119:
In addition to user resource utiliz
Page 120 and 121:
In a high availability system, ever
Page 122 and 123:
7.1 Classifications of virtualizati
Page 124 and 125:
7.2 Resources to the virtual machin
Page 126 and 127:
112 Running SAP Solutions with IBM
Page 128 and 129:
8.1 Separation of duties for databa
Page 130 and 131:
authority is granted to an entire D
Page 132 and 133:
malicious or careless unauthorized
Page 134 and 135:
After starting each audit policy, D
Page 136 and 137:
8.3 Writing SQL to audit SAP tables
Page 138 and 139:
Example 8-13 shows the audit record
Page 140 and 141: The client and server perform the f
Page 142 and 143: Digital certificates: Digital certi
Page 144 and 145: The following rule conditions are a
Page 146 and 147: Example 8-24 shows the assigned val
Page 148 and 149: 8.5.3 Reasons for establishing trus
Page 150 and 151: Example 8-31 shows the results of a
Page 152 and 153: From the central log of the SAP sys
Page 154 and 155: 140 Running SAP Solutions with IBM
Page 158 and 159: The SAP implementation process from
Page 160 and 161: Typical roles and tasks for system
Page 162 and 163: Key documentation From the IT and C
Page 164 and 165: Then you see a list of SAP Notes th
Page 166 and 167: SAP Notes The SAP Note system is us
Page 168 and 169: ► SAP on DB2 9 for z/OS: Implemen
Page 170 and 171: participate in the failover automat
Page 172 and 173: As a best practice, use the SAP as
Page 174 and 175: ��
Page 176 and 177: System software planning SAP on the
Page 178 and 179: Software product Part number Commen
Page 180 and 181: Capability Software product Part nu
Page 182 and 183: � Decide which installation optio
Page 184 and 185: c. Disable the IEFUSI exit in membe
Page 186 and 187: 3. Optional: Make the directories a
Page 188 and 189: Additional information: For more in
Page 192 and 193: ARC The archive log data sets. CI T
Page 194 and 195: DB2 members of the same data sharin
Page 196 and 197: Figure B-4 illustrates how SAP uses
Page 198 and 199: OvercommitRatio Virtual Memory vers
Page 200 and 201: ► Set the following z/VM SRM para
Page 202 and 203: ► Separate the SAP private networ
Page 204 and 205: DB2 10 ZPARMS for SAP Important: Yo
Page 206 and 207: - SMS constructs and ACS routines -
Page 208 and 209: Downloading and extracting the web
Page 210 and 211: PI Process Integration PIT point-in
Page 212 and 213: SAP Notes Registration required: To
Page 216 and 217: DSNACCOX usage 45 dual-log LG1 and
Page 218 and 219: untime environment 13 software 162
Page 222: Running SAP Solutions with IBM DB2
show all

Download PDF - IBM Redbooks

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?