In restructure while adding new pointers in the new set getting below error
UT000029 Record CFR-TT Dbkey=******:* out-of-sync with subschema. Subschema Prefix=* data=***. Database Prefix=** data=***
Ran DBAN and resulted with ****** - DBKEY */********:* LI PREFIX LENGTH NE SS PREFIX LENGTH
Component: IDMS/DB
Release: 19.0
Running a restructure, which ends up in failure and rerunning it again without restoring the area
The purpose of both DBAN message and UT000029 are exactly the same .The prefix length of one or more records in the database does not match the prefix length in the Subschema load module.
One reason for this is that the RESTRUCTURE was run once but did not complete successfully and the user tried to restart the RESTRUCTURE without first Restoring the DB area to its original state.
Another reason for the error message is a developer/programmer , accidentally stored the record with the new subschema definition. New pointer positions added ( additional pointers were added) wrongly .
Use the new subschema definition (maybe a subschema with a temporary name) to obtain those records using the DBKEYs in DMLO or program, and see what the data says.
RESTRUCTURE will use the original subschema (record/prefix length) to read the records on the database, and will use the RSTT to modify the records to the new length
Restructure is successful by deleting the newly added pointers which was added using new subschema definition