oclc_server creating OWN field with "0" or "1" as OWN value

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

Description:
This is an Aleph Version 20 problem for us. In Version 18, this is not an issue.
We are in the process of upgrading from version 18 to Version 20. Upon establishing a test environment for Version 20, we tested on exporting records from OCLC to our Aleph V.20 server. While the records went through ok, strange things happened:
1. The imported records all have an "OWN" field with a subfield $a and its content "1".
2. Under 001 control field, the imported records each has a prefix of "1-" to the record's system number.
3. System denied permissions on these records based on "OWN" fields to any users. So no changes could be made or saved to the records.
4. We looked at tab_oclc, tab_z30, tab_merge, tab_merge_overlay, tab_match, tab_fix, and tab_mapping, and found that they were all completely migrated to the new environment.
5. Upon checking on the logs, we found that apart from tab_oclc, tab_match, and tab_fix, none of the other tables mentioned in #4 above were loaded in the importing process.

Resolution:
The abc50 tab_loader table has values in column 2:

! 1 2 3 4 5 6 7 8
!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!-!-!-!-! XZLA 0 1 0 00 1011
DABC 1 1 0 00 1011
ABCO 0 0 0 00 1011
XZL4 1 1 0 00 1011
XZLM 1 1 0 00 1011
XZLP 1 1 0 00 1011


This means that it is creating an OWN field with either "1" or "0" in it.

You need to change all the column 2's to blank and restart the oclc_server.

• Article last edited: 10/8/2013