Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Circulation Logs - Error Message - "Log transaction does not exist"

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

    Description:
    Why does this error message occur: "Log transaction does not exist"?
    The error message appears even though there are valid Circulation Logs available.
    I suspect this could be due to file loading, since we have loaded Z309 as part of the migration plan.

    Resolution:
    The error:
    Remote Service Error (c0178 get11)
    Log transaction does not exist

    happens because the Z309_ID index was missing.
    This can be demonstrated by running UTIL-A-17-14 (List Existing Indexes for a Table)

    Enter Table Name : z309
    Defined in file_list:
    __________________________________________________________
    IND z309_id 128K 0K TS1X
    IND z309_id2 128K 0K TS1X
    IND z309_id3 128K 0K TS1X
    IND z309_id4 128K 0K TS1X
    IND z309_id5 128K 0K TS1X
    __________________________________________________________

    Exist in the Database:
    INDEX_NAME STATUS INDEX_TYPE UNIQUENESS COLUMN_NAME
    --------------- ------- ---------- ----------- --------------------
    Z309_ID2 VALID NORMAL NONUNIQUE Z309_REC_KEY_2
    Z309_ID3 VALID NORMAL NONUNIQUE Z309_REC_KEY_3
    Z309_ID4 VALID NORMAL NONUNIQUE Z309_REC_KEY_4
    Z309_ID5 VALID NORMAL NONUNIQUE Z309_DATE_X

    It can be fixed by running UTIL-A-17-2 (Create Index).
    Enter table name to Create all tables' indexes
    OR
    index name to Create a specific index (all/table-name/index-name): z309_id
    enter yes to Create z309_id indexes for NPL50 yes

    The results can be checked by running UTIL-A-17-14 again:

    Enter Table Name : z309
    Defined in file_list:
    __________________________________________________________
    IND z309_id 128K 0K TS1X
    IND z309_id2 128K 0K TS1X
    IND z309_id3 128K 0K TS1X
    IND z309_id4 128K 0K TS1X
    IND z309_id5 128K 0K TS1X
    __________________________________________________________
    Exist in the Database:
    INDEX_NAME STATUS INDEX_TYPE UNIQUENESS COLUMN_NAME
    --------------- ------- ---------- ----------- --------------------
    Z309_ID VALID NORMAL UNIQUE Z309_REC_KEY
    Z309_ID2 VALID NORMAL NONUNIQUE Z309_REC_KEY_2
    Z309_ID3 VALID NORMAL NONUNIQUE Z309_REC_KEY_3
    Z309_ID4 VALID NORMAL NONUNIQUE Z309_REC_KEY_4
    Z309_ID5 VALID NORMAL NONUNIQUE Z309_DATE_X


    • Article last edited: 10/8/2013
    //doorbell.io feedback widged