Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Z111 Table Hit Maximum Record Key

    Z111 Table Hit Maximum Record Key

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Aleph
    • Product Version: 16.02

    Description:
    We're getting a lot of z111 "warnings" in our pc_server_log. When I checked the table, I get the following:

    SQL> select max(Z111_rec_key) from z111;

    MAX(Z111_
    ---------
    999999999

    I'm pretty sure that I need to rebuild the index. My question is this: should we be planning to rebuild this on a regular basis? Or is there some other problem?

    Resolution:
    The following SQL shows that, despite the high key being 999,999,999, that you actually have only 1,701,387!

    SQL> select count(*) from z111
    2 ;

    COUNT(*)
    ----------
    1701387

    So, yes, running p_manage_111 should give you a much lower high key and solve the problem.


    (keywords: p-manage-111 manage-111 manage_111)


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • z105h table: what is it? is it needed?
      • z114 in CJK character sorting; obtaining z114; Web Utilities for maintaining
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 16.02
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved