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

    Keyword searches take long time then give "Page cannot be displayed"

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    Keyword searches give no response for a minute or so and then display the "Page cannot be displayed" screen.
    But the Browse is working OK.

    Resolution:
    I found that Word searching in USM01 was working OK.

    The www_server log did not give any clue. (It showed just the FIND-B or FIND-C command, no error of any kind.)

    I did "dlib vir01" and util f/4 for the z05. The searches went flying by, but the last was mine (since it showed my search term). And, using the number found in the z05, I checked the z110. (The z110 is the list of doc numbers retrieved by the search.) These both seemed OK. And they could not have been successfully produced if the SYS01 Word tables (z97, z98, and z95) were also not OK.

    The (CCL) command search "sys = nnnnnnnnn" brought up a record successfully.

    It seemed to be a problem in displaying the Brief List, but the sys01 www_tab_short.eng looked OK.

    At a loss for anything else to check, I used the SQL to check the Oracle indexes for a bib library in KB 8192-6423. It showed that the sys01 z101_id index was missing. (The z101 is the "Sort index", used for sorting Brief List entries.)

    When I tried to do util a/17/2 to build the z101_id, I got the "such column list already indexed" described in KB 16384-2514. util a/17/14 showed this:

    Defined in file_list:
    __________________________________________________________
    !IND z101_id 960M 0K TS4X
    __________________________________________________________
    Exist in the Database:

    INDEX_NAME STATUS INDEX_TYPE UNIQUENESS COLUMN_NAME
    --------------- ------- ---------- ----------- --------------------
    IOT_Z101 VALID IOT - TOP UNIQUE Z101_REC_KEY

    As described in KB 16384-2514, the IOT_Z101 was a special construct used in some cases in v16 and defined in the z101_create.sql. There is no reason for it in v18 -- and the v18 z101_create.sql does not include it.

    I uncommented the entry for z101_id in the file_list and ran p_manage_27. That successfully rebuilt the z101 (and the z101_id) and solved the problem.

    • Article last edited: 10/8/2013