Summary
Symptom
This note describes all the steps which are necessary to prepare an SAP system for DB2 10 for z/OS, including:
- Prerequisites that need to be fulfilled in order to install on or migrate your SAP system to DB2 10.
- Kernel patches, support packages & corrections that have to be checked and/or applied to an SAP system to be fully functional on DB2 10.
DB2 zos os390 os/390
To switch to DB2 10 for z/OS you need to make sure that the following prerequisites are fulfilled:
- SAP Release of DB2 10
- Make sure that the SAP Basis or NetWeaver Release of your system has been released for DB2 10.
- For more information, see SAP Note 1452370.
- Database host
- System z hardware: z990, z890, z9, z10, z196, or later
- Operating system: z/OS 1.10 or later
- Extended addressability enabled for the data sets for DB2 catalog/directory and SAP tables/indices
- Lock Manager: IRLM 2.3 or later
- SMS environment for DB2 activated
- Adjust z/OS HVCOMMON since DB2 10 uses 64-bit common storage
- Application server
- DB2 Connect 9.7 FP3a or later (only 6.20 & higher)
- Minimum operating system levels: AIX 5.3 TL9 (Technical Level), SuSE 10, Red Hat 5, Windows 2003 (32-64 bit)
- With DB2 10, the full Web Application Server 6.40 running on z/OS is not supported anymore (note that the SAP central services with enqueue and message server can continue to run on z/OS). You have to switch to one of the other supported operating systems (AIX, zLinux, xLinux, Windows).
- Mininum JDK level (only for zLinux): IBM JDK 142 SR13 FP9
To prepare your system for DB2 10 proceed as follows:
- 1. Limitations
Check the following limitations:
| Basis Release . | Limitation |
|---|---|
| 4.6C | - No Unicode support |
| - Support for ST04 with RFCOSCOL only | |
| | - CCMS support very limited (SAP Note 717215) |
| 6.20/6.40 | - Full application server on z/OS USS not |
| | supported any more with DB2 10. Migrate |
| | to AIX, zLinux, xLinux or Windows |
| | - No Unicode-Support for Basis Release 6.20, 64bit only |
| 7.0x | - ABAP support for 32-bit application servers |
| | restricted to non-Unicode |
| 7.1x and higher | - 64-bit application server required |
- 2. Database connectivity
Update the database connectivity to the versions listed below:
| Basis Release . | Version/Comment |
|---|---|
| 4.6C | latest available ICLI (see SAP Note 81737) |
| 6.20 and higher | DB2 Connect 9.7FP3a |
- 3. SAP J2EE JDBC URL
SAP Java applications rely on being able to process LOBs in a transaction until the commit point is reached. With DB2 progressive streaming protocol, LOBs are freed when cursors are closed. Therefore, it is required to disable progressive streaming for JDBC connections. With DB2 9, this was accomplished by setting the ZPARM PRGSTRIN to DISABLE. With DB2 10, progressive streaming needs to be disabled by setting the JDBC connection property progressiveStreaming to NO. This parameter needs to be specified in the URL that the JDBC driver uses to connect to the DB2 for z/OS server. To modify the URL in the SAP ConfigTool, proceed as follows:
- a) Go to 'Secure Store'.
- b) Choose key jdbc/pool/
- c) Add the following phrase (separated by a semi-colon!):
progressiveStreaming=NO
- d) Choose 'Add'.
- e) Save your changes in the SAP Java ConfigTool.
- 4. Kernel Patches
Update the kernel to the following minimum patch level(s):
| Kernel Release . | Module/Executable . | Patch Level |
|---|---|---|
| 4.6D | lib_dbsl | 2539 |
| 6.40 | lib_dbsl | 389 |
| | R3load | tbd |
| | db2radm | 029 |
| | rfcoscol | 026 |
| 7.00 | db2radm | 31 |
| | lib_dbsl | 324 |
| | R3load | 134 |
| | R3ldctl | 28 |
| | R3szchk | 28 |
| | saplicense | 266 |
| | SAPCL | 720/5 (1) |
| 7.01 | db2radm | 13 |
| lib_dbsl | 165 | |
| | R3load | 45 |
| | R3ldctl | 9 |
| | R3szchk | 13 |
| | saplicense | 104 |
| | SAPCL | 720/5 (1) |
| 7.10 | db2radm | 14 |
| | lib_dbsl | 259 |
| | R3load | 56 |
| | R3ldctl | 17 |
| | R3szchk | 17 |
| | saplicense | 138 |
| | SAPCL | 720/5 (1) |
| 7.11 | db2radm | 7 |
| | lib_dbsl | 146 |
| | R3load | 33 |
| | R3ldctl | 3 |
| | R3szchk | 9 |
| | saplicense | 25 |
| | SAPCL | 720/5 (1) |
| 7.20 (2) | db2radm | 92 |
| | lib_dbsl | 109 |
| | R3load | 88 |
| | R3ldctl | 3 |
| | R3szchk | 5 |
| | SAPCL | 720/5 |
(1) Download SAPDB2CL which is part of the 7.20 Kernel within the NetWeaver 7.3 Software Marketplace section.
(2) 7.20 Kernel is used by SAP products based on SAP NetWeaver 7.02, 7.20 & 7.30.
- 5. Support Packages
Implement the following support packages (only ABAP and Double-stack systems):
| Release . | SAP_BASIS . | SAP_BW |
|---|---|---|
| 4.6C | - | - |
| 6.20 | 69 | - |
| 6.40 / BW 3.5 | 28 | 28 |
| 7.00 | 22 | 24 |
| 7.01 | 07 | 07 |
| 7.02 | 06 | 06 |
| 7.10 | 11 | 08 |
| 7.11 | 06 | 05 |
| 7.30 | - | - |
- 6. ABAP Corrections
Apply the corrections attached to the following SAP Notes:
1480594 - this note
183311 - PTF Check Tool
1486360 - Readiness Check (only 6.20 & higher)
1543292 - Incremental Conversion enhancements (only 6.20 & higher)
1301446 - Incorrect return code for mass activation during transport
1354957 - Tables with more than 3 long string fields
1452830 - BW Support for DB2 10
- 7. DB2 Level
Ensure that all fixes recommended in SAP Note 81737 have been applied to the DB2 subsystem. This can be done using the PTF check tool as described in SAP Note 183311.
- 8. Readiness Check (only 6.20 and higher)
Perform the readiness check as describted in SAP Note 1486360 and resolve any additional requirement that might appear there.
After finishing the above preparational steps you may perform the actual database migration to DB2 10. For more information, see SAP Note 1528309 (and the Migration Guide which is attached to that note).
Header Data
| Release Status: | Released for Customer |
| Released on: | 10.11.2011 17:45:59 |
| Master Language: | English |
| Priority: | Recommendations/additional info |
| Category: | Special development |
| Primary Component: | BC-DB-DB2 DB2 for OS/390 |
No comments:
Post a Comment