Data Object Broker for z/OS commit errors may occur after loading table with S6BBRTBL /HRNBRTBL: S6BTC005E- Expected secondary index entry not found during COMMIT
book
Article ID: KB0088484
calendar_today
Updated On:
Products
Versions
TIBCO Object Service Broker for z/OS
-
Not Applicable
-
Description
Resolution: Data Object Broker for z/OS commit errors may occur after loading table with S6BBRTBL / HRNBRTBL: S6BTC005E- Expected secondary index entry not found during COMMIT
Environment TIBCO Object Service Broker for z/OS 5.0.0 running under z/OS
Symptoms The symptoms include COMMIT failures in the Data Object Broker region with message: S6BTC005E- Expected secondary index entry not found during COMMIT
Cause The failure occurs when null values are loaded by the S6BBRTBL (alias HRNBRTBL) offline table load utility for fields defined as Type "S" and Syntax "V" for which a secondary index is requested.
The index structure for the field is built and padded with spaces (X'40') rather than with binary zeroes (X'00'). Subsequent updating of the associated row may cause the index to be updated. The S6BTC005E failure happens when the secondary index is accessed to update the target row location and the secondary index entry is not found due to the improper padding value.
Resolution Customers experiencing the S6BTC005E failure or planning to use S6BBRTBL to load null values into secondary index fields defined as Type "S" and Syntax "V", should obtain the fix for CR 1-A9YHRU which is now available in Hotfix 11. See LBN1-ADQV7N for details regarding TIBCO Object Service Broker for z/OS 5.0.0 Hotfix 11.
References Change Request: CR 1-A9YHRU
Issue/Introduction
Data Object Broker for z/OS commit errors may occur after loading table with S6BBRTBL /HRNBRTBL: S6BTC005E- Expected secondary index entry not found during COMMIT