DB2 z/OS: Overview of transports and corrections

[] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []

Related:

  1. DB2-z/OS: Transports & Support Packages (7.0 and higher)Symptom This is a release-dependent attachment to note 101217. It...
  2. 640PC Edition May 2008:Installation IBM DB2 on z/OSSymptom This SAP Note is valid for the following releases:...
  3. DB6: Installation of FixPaks for DB2 V9.5 (Windows)Symptom This note relates to installing FixPaks for DB2 V9.5...
  4. DB6: Installation of FixPaks for DB2 V9.5 (UNIX+Linux)Symptom This note relates to installing FixPaks for DB2 V9.5...
  5. DB6: Installing V8.2 FixPaks (as of FP9) on Win NT/Win 2000Symptom To install FixPakslower than FixPak 9, see Note 940550....
  6. Overview Note for Add-on NRX 331_500 (VIP 4.4, ECC 5.0)Symptom This note provides an overview for the ECC Add-on...
  7. Overview Note for Add-on NRX 330_470 (VIP 4.4, R/3 4.7)Symptom This note provides an overview for the R/3 Add-on...
  8. Overview Note for Add-on NRX 332_600 (VIP 4.4, ECC 6.0)Symptom This note provides an overview for the ECC Add-on...

Symptom

This note contains an overview of all transports and corrections necessary for a certain R/3 release. It is updated on a regular basis.
The following areas are affected:
Errors in the R/3 system (Data Dictionary, tp, R3trans, R3up, saposcol, CCMS, and so on)Missing functions (database monitor, and so on)Checks for Going-Live service
Other terms

DB2/390, DB2 390, DDIC, tp, R3trans, R3up, Upgrade, Conversion, Activation, SE14, Data Dictionary, ABAP, NAMETAB, Import, Transport, Migration, Export, Installation, UNIX, Windows NT, Primary Key Index, Table, Storage Group, SQL Error, Database Object Check, Problem, CCMS, Saposcol, Correction, Fix

Reason and Prerequisites

Correction transports that have not been implemented are responsible for the majority of problems occurring during R/3 installations on DB2 for OS/390.

Solution

When you start to deal with each problem, you should check whether all corrections made available by SAP up to now have been transported into the R/3 system.
This check is also an important part of the Going Live check.
Procedure:
1. You will find a list of all corrections and function enhancements – depending on your release – in the following notes:Release 3.1I: Note 101303Release 4.0B: Note 103707Release 4.5A: Note 118901Release 4.5B: Note 151394Basis release 4.6A: Note 166083Basis release 4.6B : Note 191215Basis release 4.6C: Note 217093Basis release 4.6D: Note 324739Basis release 6.10: Note 417920Basis release 6.20: Note 493577Basis release 6.40: Note 661260Basis release 7.0: Note 823245Basis release 7.10: Note 943146
Classification of the corrections is as follows:Without all transports that are marked as “mandatory”, the R/3 system is not fully functional.For “optional” transports, you may decide yourself whether you need the functions or not.2. Verify the successful import of the transports usingtransaction SE01 (menu option: Request -> Find -> Transport Request)of report “RTCCTOOL” (start it from the ABAP/4 editor, transaction SA38). Beforehand, install the newest version of this report as described in Note 187939. This report automatically compiles a list of missing transports, and controls their implementation. Important: At the moment, RTCCTOOL only works for the transports from areas “Installation”, “DDIC corrections” and “CCMS functionality”.
There is also information on imported transports for a heterogeneous or homogeneous system copy.3. Note 13719 describes how to download corrections and function enhancements and transport them into the R/3 system.4. Make sure that you only import transports whose release matches that of your system.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment