A fix is available
APAR status
Closed as program error.
Error description
1. Took an image copy 2. The table was versioned (Altered) 3. The tablespace was REORGed Then all rows in the table became version 1 format. The image copy which was taken after the REORG had 'OLDEST VERSION = 0001'. 4. MODIFY utility deleted all image copies with 'OLDEST VERSION = 0000'. Then the prime OBD was deleted. 5. UNLOAD using the image copy in (1) cause 0c4 and overlay DB2OVRLAY/K
Local fix
do not run Unload on an Image copy that no longer exists in SYSCOPY
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 9 for z/OS utility users of UNLOAD * * from an image copy * **************************************************************** * PROBLEM DESCRIPTION: UNLOAD encountered ABEND0C4 RC00000004 * * in DSNUULCA + x'6E42' when unloading * * from an image copy that no longer had * * a SYSCOPY entry and was taken prior to * * when versioning was active * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** UNLOAD encountered ABENDS0C4 RC00000004 at DSNUULCA +x'6E42' in the following scenario: 1. Image copy taken prior to when versioning was active 2. ALTERed table and INSERTed data to add versioning 3. REORGed table space to consolidate versions 4. MODIFY RECOVERY to delete SYSCOPY entry for image copy taken in Step 1, which also deletes OBD prime information for version 0. 5. UNLOAD from image copy taken from Step 1 UNLOAD was not able to resolve the OBD information for version 0 records, because it had been deleted due to the MODIFY RECOVERY. UNLOAD should not try to unload a row if the version information for the row being unloaded is not found. Additional keywords: FROMCOPY FROMCOPYDDN Additional symptoms: ABEND04E RC00E20028 at DSNSVSTK +x'01F0'
Problem conclusion
UNLOAD from image copy code has been modified to issue message MSGDSNU1239I - 'VERSION version OBDREC WAS NOT FOUND IN OBID obid' when the OBD information for a version 0 row is not available in the image copy or OBD. This APAR/PTF updated the Messages and Codes book to describe existing message DSNU1239I as follows: DSNU1239I csect-name - VERSION version-number OBDREC WAS NOT FOUND IN OBID obid Explanation The version information for the record being unloaded is unavailable in the OBD and/or the system pages from the image copy are not available. System action The record in error will not be unloaded to the output data set. The UNLOAD utility continues until the total number of records in error reaches the value specified by the MAXERR option (the default is 1). If the total number of records reaches the MAXERR value, the UNLOAD utility issues the DSNU1219I message and terminates with the return code 8. Problem determination This message is issued when the version information for a record being unloaded from an image copy is not available in the OBD or the system pages found in the image copy. This could occur if the SYSTEM PAGEs are not available in the image copy or if MODIFY RECOVERY had been run to delete the version 0 OBD information User response UNLOAD from an image copy requires that the image copy data set was taken with the SYSTEMPAGES YES option on the COPY utility statement. UNLOAD needs the system pages to unload versioned data. If the DDL including ALTERs of the table at the time the image copy was taken is available, users are recommended to do the following to rebuild OBD information: 1. Recreate the table to the same state it was at the time the image copy was taken. 2. DSN1COPY with OBDIXLAT may need to be used to update the dbid, psid, obid information in the image copy to match with the newly recreated table. 3. UNLOAD from the updated image copy. Severity 4 (Warning)
Temporary fix
Comments
APAR Information
APAR number
PK98850
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-16
Closed date
2009-12-03
Last modified date
2011-02-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK52508
Modules/Macros
DSNUULCA
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
R910 PSY UK52508
UP09/12/18 P F912
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
15 February 2011