Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Upgrade Express, v18 - v19, step 1002: z13 user-defined fields not carried over

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

    Description:
    Step 1002 is to move the 5 user defined fields from the z13 to the z13u. It failed to do this. The 5 user-defined fields are no longer in the abc01.z13 -- nor in the abc01.z13u.

    When I look at v18 using SQL, for the z13_user_defined_1 in ABC01, I get 1528355 rows returned with data. On v19, the rows are all empty.

    This is with UE kit 1.07.

    Resolution:
    This is like KB 16384-8593, which was fixed locally (by Ex Libris).

    As seen in util a/17/5/1, the abc01 z13 has a synonym pointing to abc21:

    Z13 ABC21 Z13

    The following lines in the log file (logs/log.20081026.104003/1002.log) refer to ABC21 (we admit it's hard to figure it out - we'll make it clearer in the new version of the UE):

    A_ERROR: The old table z13 description does not match the expected description.
    3c3
    < Z13_REC_KEY CHAR(9)
    ---
    > Z13_REC_KEY NOT NULL CHAR(9)

    So... abc21.z13 was not upgraded since it was a little different than what it should have been (compared to the description in source/1002/z13_new_desc.dat) - the "NOT NULL" was missing.

    abc21@ALEPH19> desc z13 shows this:

    Z13_REC_KEY CHAR(9)


    while the $alephm_root/sql_tab/z13_create.sql has this:

    Z13_REC_KEY CHAR(9) NOT NULL,


    and usm01@ALEPH19> desc z13 this:

    usm01@ALEPH19> desc z13
    Name Null? Type
    ----------------------------------------------------------------------- -------- -------------------------------------------------
    Z13_REC_KEY NOT NULL CHAR(9)

    Aside from the z13_rec_key NOT NULL, the v19 z13 should not have the Z13_USER_DEFINED fields (which have moved to the Z13U table). I see that the abc21 z13 *does* have these fields.

    A comparison of the v18 to the v19, shows that the above differences are the only differences. It's possible that you could drop the USER-DEFINED fields from the z13 and then do this SQL:

    SQL> ALTER TABLE Z13 MODIFY (Z13_REC_KEY NOT NULL);

    The other approach would be to:

    1. do util a/17/1 for the abc21 z13

    2. confirm that the SQL "desc z13" shows the correct values

    3. rerun the Upgrade Express step 1002 for abc21.


    • Article last edited: 10/8/2013
    //Feedback