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

    Search redisplays Initial OPAC screen; no results

    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23

    Problem Symptoms:
    1. the initial OPAC screen displays, but when a word is entered in the Search box and "Go" is clicked, nothing happens
    2. Clicking on Advanced Search doesn't do anything
    3. updates *are* being made to the $LOGDIR www server log

    Cause:
    > dlib vir01
    > util a/17/14 for z63

    showed that the z63_id Oracle index was missing.

    And the most recent clear_vir01 log contains messages such as these:

    CREATE UNIQUE INDEX VIR01.Z63_ID ON VIR01.Z63 (Z63_REC_KEY ASC) *
    ERROR at line 1:
    ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found


    or

    CREATE UNIQUE INDEX VIR01.Z63_ID ON VIR01.Z63 (Z63_REC_KEY ASC)
    ERROR at line 1:
    ORA-00054: resource busy and acquire with NOWAIT specified


    In the latter case, the "resource busy" could be caused by a spider/robot initiating a session at the same time as clear_vir01 is trying to drop/create the z63.

    Note:  In almost every case "CREATE UNIQUE INDEX VIR01.Z63_ID" messages are seen in the www_server log.  But there has been at least one case where they were not.  Instead, the following "func" parameter was found on request lines in the log:  "func=find-b-0&amp=&amp=&amp=&amp=&amp=&amp=&amp=&amp=&amp=&amp=&amp=&amp<etc.> and the following message was seen at the end of the log:

    Execution error : file '/exlibris/aleph/a22_1/aleph/exe/www_load_file.gnt'
    error code: 114, pc=0, call=1, seg=0
    114     Attempt to access item beyond bounds of memory (Signal 11)



    Resolution:
    > dlib vir01
    > util a/17/1 for the z63.


    Additional information

    To prevent this problem:

    * run clear_vir01 when no one will be accessing the system. Or, better,

    * stop the pc server/ www server while clear_vir01 is running, as described in Article " Restart Servers from job_list ".

    To check the runs of clear_vir01 to make certain that they have run without error,

    > cd $alephe_scratch
    > grep ERROR *vir01*

    Additional Information

    To prevent this problem:

    * run clear_vir01 when no one will be accessing the system. Or, better,

    * stop the pc server/ www server while clear_vir01 is running, as described in Article 000044208 ( Restart Servers from job_list ).

    To check the runs of clear_vir01 to make certain that they have run without error,

    > cd $alephe_scratch
    > grep ERROR *vir01*

    If the "resource busy" was caused by a spider/robot, consult Article 000040921 (KB 6669) ( OPAC slow; Stopping bot (robot) activity on www_server ).

    Category: Web OPAC


    • Article last edited: 4/16/2014