06.01.2013 Views

Download PDF - IBM Redbooks

Download PDF - IBM Redbooks

Download PDF - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4.2.2 Considerations for migration<br />

4.2.3 Prerequisites<br />

Keep in mind the following considerations when planning a migration to DB2 10:<br />

► Online migration is only supported from DB2 9. Customers who are running DB2 8 can<br />

perform skip-level migration. However, in this case, the SAP system must be down during<br />

the entire process until DB2 is in DB2 10 NFM.<br />

► For customers who are running SAP Basis 6.40 or earlier, the SAP NetWeaver AS on<br />

z/OS UNIX System Services is not supported with DB2 10. Central Services Components<br />

(SAP Message Server, Enqueue Server, and Web Dispatcher) are supported on z/OS<br />

UNIX System Services on all releases as before.<br />

► Because the DB2 catalog is system-managed space (SMS) with DB2 10, SMS is required<br />

for operating DB2 10. You must configure SMS to enable extended addressability for<br />

catalog data sets and table spaces or indexes.<br />

► With DB2 10, SAP switches to an implicit layout starting with SAP Basis release 6.20. All<br />

newly created objects and objects that are subject to an SAP table conversion are<br />

implicitly created. All other objects remain untouched. For details about the different<br />

naming and allocation schemes, see 3.3.1, “Full implicit layout” on page 38.<br />

Adapt your DB2 Advanced Copy Services (ACS) routines to cover all cases and ensure<br />

that the VCAT associated with the SYSDEFLT storage group points to a catalog and data<br />

sets that are intended for SAP data.<br />

► DB2 10 uses common storage for certain load modules and control blocks. The amount of<br />

common storage in a z/OS LPAR is controlled by the HVCOMMON parameter in the IEASYSxx<br />

parmlib member. Reserve at least 6 GB for each DB2 subsystem.<br />

► The real storage requirements for DB2 10 can be 5% - 10% higher compared to DB2 9.<br />

► As explained in “ADMIN stored procedures” on page 45, with DB2 10, the Control Center<br />

stored procedures were replaced by the ADMIN stored procedures. Because they are<br />

already available with DB2 8 and 9, enable them before you begin the migration.<br />

DB2 10 requires the following minimum levels for the system environment:<br />

► Hardware: <strong>IBM</strong> System z890 or System z990, System z9®, System z10, zEnterprise 196, or<br />

later<br />

► Operating system: z/OS 1.10 or later<br />

► IRLM: 2.3<br />

► DB2 Connect: Version 9.7 FP 3a<br />

You can find general information about the prerequisites for DB2 10 in SAP Note 1480594.<br />

This note describes all the requirements for hardware, operating system software, IRLM, and<br />

SAP component levels. Check this note regularly for updates and details about the SAP<br />

component levels.<br />

The following sections describe details about the various SAP stacks.<br />

SAP ABAP stack<br />

To facilitate the migration preparations, SAP created a readiness check that checks the most<br />

important runtime components of an SAP ABAP stack. This report is available for SAP Basis<br />

7.0 and later. You must run it before performing the actual migration. The readiness check is<br />

described in SAP Note 1486360, which you can install by using the snote transaction.<br />

Releases that are enabled for Version 10 already contain a version of the readiness check.<br />

68 Running SAP Solutions with <strong>IBM</strong> DB2 10 for z/OS on the <strong>IBM</strong> zEnterprise System

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!