Download PDF - IBM Redbooks

SAP
application
Solution
Manager
Database server overhead
(GB/instance) development
versus production
40 100 80 N/A
To determine storage sizes:
1. Review the required VTOC, VVDS, or VTOC index sizes for SAP database volumes as
shown in Table B-5.
Table B-5 3390 DASD geometries
Geometry
versus SAP
required
Application
server allocations
(GB/instance)
Production
data (GB)
2. Review the ICF catalog size requirements for the DB2 data sets as shown in Table B-6:
– Primary allocation = 50 cylinders
– Secondary allocation = 5 cylinders
– DB2 table spaces or index spaces for SAP
Table B-6 Minimum volumes required for the SAP database
Development
data (GB)
QA data
(GB)
3390-9 3390-27 3390-54 3390-A (SAV) a
VTOC = 12% 1200 tracks 3920 tracks 8000 tracks Up to 32000 tracks
VVDS = 5.5% 540 tracks 1764 tracks 3600 tracks Up to 14400 tracks
VTOC Index = 1.5% 150 tracks 490 tracks 1000 tracks Up to 4000 tracks
DASD Capacity (GB) 8.5 28 56 Up to 223 tracks
a. SAV geometry can be flexible and defined for volumes greater than 65520 cylinders.
Restrictions apply. For more information, see the DB2 10 for z/OS manuals.
Minimum volumes Nonproduction instances Production instances
3390-9 3390-27 3390-9 3390-27
DB2 active logs 2 (minimum) 2 (minimum) 3+ 24h
capacity
DB2 Catalog, Directory,
bootstraps data sets
(BSDS)
1 1 2 1
DB2 DSNDB07 1 1 5 2
SAP basic data 20 8 50 20
2 (minimum)
24h capacity
SAP data 15% to 33% of production size Quick Sizer / 8 Quick Sizer / 27
DB2 archive Logs 2 2 3 2
DB2 FlashCopy backup 22 + SAP data 10 + SAP data 60 + SAP data 25 + SAP data
3. Determine the database DASD requirements based on geometry.
4. Review the job entry subsystem (JES) SPOOL Space Requirements. A minimum of 15
MB is required for the SAP workload. (An amount of 70 MB or more is common.)
Appendix B. Planning, preparing, and implementing the SAP landscape 161