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

Description:
We are finding Z00r records in both the xxx01 and xxx60 libraries where the fields are duplicated.

This gives misleading results in SQL run against the z00r table.

Resolution:
The Z00R_ID (built on the Z00R_DOC_NUMBER) and the Z00R_ID1 (built on the Z00R_SEQUENCE) are both defined as NONUNIQUE.

I was thinking that Aleph wants to enforce uniqueness on the following combination: z00r_doc_number, z00r_sequence, z00r_field_code, z00r_text, but the following SQL in usm01 gets "489 rows selected":

usm01@ALEPH201> select z00r_field_code, z00r_text, z00r_doc_number, z00r_sequence from z00r group by z00r_field_code, z00r_text, z00r_doc_number, z00r_sequence having count(*) > 1;

I'm quite confident that after running p_manage_07 to build the z00r, the result of the preceding query would be zero.

{ In fact, I think that the result of the query even without the z00r_sequence:

usm01@ALEPH201> select z00r_field_code, z00r_text, z00r_doc_number from z00r group by z00r_field_code, z00r_text, z00r_doc_number, z00r_sequence having count(*) > 1;

would also be zero. }

If these duplications are giving you misleading results in SQL run against the z00r, I suggest that you periodically rebuild the z00r via p_manage_07.

• Article last edited: 3/4/2015