• Article Type: General
• Product: Aleph
• Product Version: 19.01

Description:
We do not use the z13u, therefore to save tablespace I have set it as a NA table according to KB 8192-5095.

When I run p_manage_07 to re-build z13, as I periodically do in the course reserve library, this job fails with repeated "Write Error" messages. Eventually the job is suspended and I'm left with no z13 data.

The service should check whether z13u is in use before trying to write to it, perhaps even before trying to drop and re-create it, though te util_a_17_b step does not fail, that process knows what to do with a NA table from file_list.

I don't think there's anything in the logs that indicates the problem is with z13u. I don't recall how I figured that out when I first hit this issue (and forgot to report it). But defining the table with normal parameters and re-running the job ends with success. I then dropped the table and made it NA again afterward.

Resolution:
Corrected by:

v20 rep_change 3382;
V21 rep ver 17196:

1) When tab22 (fields for short doc Z13 and Z13U records) is defined without using the user-defined fields (Z13U is not maintained), Manage-07 Service (Update Short Bibliographic Records) is creating an empty entries in Z13U. [Now empty z13u records are *not* written.]

2) Repeated "Write Error" messages are being displayed on the log of the Manage-07 Service.

• Article last edited: 10/8/2013