After Updating Index Tables: "Request is beyond last heading in ACCess file"
- Article Type: General
- Product: Aleph
- Product Version: 18.01
We are trying to set up a new Browse index ("SGN") in our test instance. After several table changes, and re-starting ue-01, browse searches in the CAT GUI are giving the message:
"Request is beyond last heading in ACCess file"
This is happening not just for the new index, Genre, but for all browse searches. What's wrong?
(Browse searches in the OPAC are OK).
I see the following in the current $LOGDIR/pc_server_6991.log:
You will note the "^M" as part of the scan code.
This is the result of editing ./lnl01/pc_tab_sear.eng on a pc and then FTP-ing it to your server without specifying "ascii" as the mode.
Since the Web OPAC doesn't use pc_tab_sear.eng, it isn't a problem there.
You can correct this either by re-FTP-ing pc_tab_sear.eng as ascii or using the dos2unix command, and then restarting ue_01 and the pc_server -- as described in KB 16384-1537.
Note: Though ue_01 will add an individual SGN index entry when you add/update a BIB record containing this field, if what you want/expect is for *all* 655's to be indexed, that will require rerunning the Headings sequence (p_manage_102, p_manage_02, etc.) for abc01.
- Article last edited: 10/8/2013