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

    locked by another user" messages

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

    Description:
    You are unable to update (or delete) a record because of "locked" messages, such as:
    "Record is locked by another user", 0092 in ./error_eng/global
    "Record is currently locked by another user", 0013 in ./error_eng/pc_cat_c0203
    "Resource is locked by another user", 0092 in ./error_eng/pc_com_c0110
    "Record updated by another user", 0014 in ./error_eng/pc_cat_c0203

    Resolution:
    In the case of a doc record (bib, authority, HOL, ADM, or Course Reserve), exit the record, do "Load record from server" to reload it, and then check the "Edit -- View record's catalogers" to see who has updated it.

    Is it "UE-01" or "BATCH"?

    Yes -- This can result from:
    * a tab_subfield_punctuation problem
    * "setenv UE_01_ENABLE_FIXDOC Y"

    No -- It's the login of another actual cataloger.

    In the case of a doc record with an actual-cataloger-CAT field or items, patrons, etc. consult Article 000038415 ("Record locked by another user") in regard to viewing/deleting z60 lock records. And Article 000043086 ("Lock periods in pc_server defaults") in regard to lock periods.

    Additional Information

    Record locked by another user
    Lock periods in pc_server defaults


    • Article last edited: 10/8/2013
    • Was this article helpful?