Issue with Database Organizer resequence routine at RELOAD SORT Phase
Article ID: 91707
Updated On:
Products
Issue/Introduction
Running Database Organizer 're-sequence' routine at RELOAD/SORT Phase.
Getting the following:
DBO Reload found the segment sequence error and reported that with messages
DBO3605E, DBO3606I and DBO3607I.
DBO3605E SEQUENCE CORRECTION WAS REQUESTED BUT CANNOT BE PERFORMED FOR SEGMENT "
DBO3606I A DUPLICATE KEY VALUE WITH A UNIQUE KEY FIELD IS UNCORRECTABLE.
DBO3607I KEY:X'002FC6F0'
DBD NAME: YEB5D9I0 HDAM/OSAM
Something is different between Production and Test Environment, but, not from a LOAD Module Perspective, where we just compared
CA Utilities LOAD Library between Production and Test Environment with no differences. and also from an UNLOAD Dataset Contents
Perspective either, because RELOAD just completed successfully at Production Side with no issues. Besides, also seems there being
NO problems from a DBDLIB Perspective either....
Resolution
Located the problem.....the main difference between production and test regards COMPRESS RELOAD Parm('YES' being used in TEST and 'NO' being used in PROD).
CA RELOAD seems able to identify and automatically switch between COMPRESS(YES) and COMPRESS(NO) only if input comes from CA UNLOAD. In this case,
input just came from IBM Standard UNLOAD Utility, so, the COMPRESS Parameter specified in the CA RELOAD had to explicitly match with Input Data Format,
which seemed to be in a compressed format already. In Summary, seems the error being caused by CA RELOAD trying to 're-compress' the data, which probably
messed up with Prefix Information, causing false-duplicates being reported. After change override COMPRESS(YES) with COMPRESS(NO), everything just worked
fine and RELOAD completed successfully.
Additional Information
The documentation indicates that;
COMPRESS (DBO) -- Compress Segments during Reload
The COMPRESS control statement calls the DBD-defined segment edit/compression exit during a reload. The COMPRESS control statement lets you suspend segment data compression for the reload input file that already contains compressed segments but CA Database Organizer™ for IMS for z/OS cannot determine the same. This happens for example when the unload file was created by HSSR or another non-CA Database Organizer™ for IMS for z/OS utility that did not mark each record as expanded or compressed. The RELOAD function always compresses segment data in the unload file created by CA Database Organizer™ for IMS for z/OS, regardless of the value of the COMPRESS control statement.
If you have a database whose data is compressed and you have no requirement for the unload file to contain uncompressed data, the unload and reload process runs faster if the data is not expanded during unload and compressed during reload. This can be achieved by using the default settings of EXPAND=N for unload and COMPRESS=N for reload.
This control statement is valid only with the RELOAD function.
Feedback
