manage-12: Oracle delete, update, and write errors on xxx30 z103

Question

Running manage-12 in the XXX30 libraries leads to the following errors in XXX30:

Oracle error: io_z103_delete
Oracle error: update_cursor z103
Oracle error: io_z103_write
Oracle error: io_z103_delete
Oracle error: update_cursor z103
Oracle error: io_z103_write

What do they mean and how to solve?

Answer

These z103 errors are occurring because there are 13 xxx30 z103 records which have ABC50 as their LKR library:

xxx30@ALEPH19> select z103_rec_key, z103_rec_key_1 from z103 where z103_rec_key_1 like 'ABC50%';

Z103_REC_KEY Z103_REC_KEY_1
---------------- --------------
xxxx000000329602 ABC50001355905
xxxx000000329402 ABC50001355906
xxxx000000352702 ABC50001382554
xxxx000000342704 ABC50001426161
xxxx000000342902 ABC50001426171
xxxx000000351904 ABC50001426177
xxxx000000343502 ABC50001426180
xxxx000000342204 ABC50001426192
xxxx000000343006 ABC50001426194
xxxx000000343202 ABC50001426198
xxxx000000342302 ABC50001426233
xxxx000000343602 ABC50001426238
xxxx000000365702 ABC50001430314

Supposedly the v19 upgrade ran manage-12 on abc50. Since there is no abc50 z103, it would have failed in building that, but it would have succeeded in building the z103 records for ABC50 in XXX30.

There are 612 abc50 doc records:

>s+ abc50
SQL-ABC50> select z00_doc_number from z00;
612 rows

I believe that these are mistakes and should be deleted. After which, you should run manage-12 in the abc01, xxx30, abc60, and xxx50 libraries.

I think this is happening because the abc50 tab100 has:
DOC-TYPE-ADM=Y

while abc50 is, in fact, *not* an ADM library.

I think that changing this to DOC-TYPE-ADM=N will prevent the erroneous creation of abc50 doc records ... and possibly other errors.

[Later:]
The situation is this.... These two XXX30 records have SID fields linking them to ABC01 records:

xxx30@ALEPH18> select z11_rec_key, z11_doc_number from z11 where z11_rec_key like 'SID ABC01 00135590%';

Z11_REC_KEY Z11_DOC_N
---------------------------------------------------------------------------------------------- ---------
SID ABC01 001355905 DES0802 000003296 000003296SID ABC01 001355906 DES0802 000003294 000003294

And the two ABC01 records are linked to ABC50 records:

abc01@ALEPH18> select z103_rec_key, z103_rec_key_1 from z103 where z103_rec_key like 'ABC5000135590%';

Z103_REC_KEY Z103_REC_KEY_1
---------------- --------------
ABC5000135590502 ABC01001355905
ABC5000135590602 ABC01001355906

Thus, a new xxx30 z103 is generated when the xxx30 manage-12 is run.

To avoid this you need to delete the ABC50 doc records 001355905 and 001355906. (This *should* also delete the ABC01 z103's.)

As noted earlier you should delete *all* of the (612) ABC50 doc records. Deleting them in the GUI would automatically delete the ABC01 z103. If you were to delete them (the ABC50 z00's) with SQL, you would need to also delete the ABC01 z103's (with ABC50 as the z103_lkr_library).

KEYWORDS: manage_12 p-manage-12

• Article last edited: 22-July-2016