p_cir_12 (hold request) report doesn't have any data
- Article Type: General
- Product: Aleph
- Product Version: 20
Description:
We use circ-12 to run a report on our hold requests. Each day this week they have come back without any data.
I'm thinking the problem may stem from the time change this weekend. I didn't get the job list stopped this weekend, so we ended up with issues on our circ reports. I have been able to get the circ-51 reports to show data again, but circ-12 continues to have issues.
Do you have any suggestions?
Resolution:
We see this in $alephe_scratch:
aleph@lib-aleph2(a20_1) ABC50>ls -lrt *cir_12*
-rw-rw-r-- 1 aleph exlibris 18479 Nov 1 05:15 abc50_p_cir_12.03539
-rw-rw-r-- 1 aleph exlibris 4596 Nov 1 05:15 abc50_p_cir_12.03540
-rw-rw-r-- 1 aleph exlibris 18527 Nov 2 05:15 abc50_p_cir_12.03562
-rw-rw-r-- 1 aleph exlibris 15154 Nov 2 05:15 abc50_p_cir_12.03563
-rw-rw-r-- 1 aleph exlibris 18527 Nov 3 05:15 abc50_p_cir_12.03587
-rw-rw-r-- 1 aleph exlibris 4644 Nov 3 05:15 abc50_p_cir_12.03588
-rw-rw-r-- 1 aleph exlibris 18479 Nov 4 05:15 abc50_p_cir_12.03611
-rw-rw-r-- 1 aleph exlibris 4596 Nov 4 05:15 abc50_p_cir_12.03612
-rw-rw-r-- 1 aleph exlibris 18527 Nov 5 05:15 abc50_p_cir_12.03634
-rw-rw-r-- 1 aleph exlibris 4644 Nov 5 05:15 abc50_p_cir_12.03635
____________________________________________________________________
-rw-rw-r-- 1 aleph exlibris 18527 Nov 6 04:17 abc50_p_cir_12.03651
-rw-rw-r-- 1 aleph exlibris 4644 Nov 6 04:17 abc50_p_cir_12.03652
-rw-rw-r-- 1 aleph exlibris 4677 Nov 6 05:15 abc50_p_cir_12.03666
-rw-rw-r-- 1 aleph exlibris 4644 Nov 6 05:15 abc50_p_cir_12.03667
-rw-rw-r-- 1 aleph exlibris 18527 Nov 7 04:15 abc50_p_cir_12.03683
-rw-rw-r-- 1 aleph exlibris 4644 Nov 7 04:15 abc50_p_cir_12.03684
-rw-rw-r-- 1 aleph exlibris 4677 Nov 7 05:15 abc50_p_cir_12.03704
-rw-rw-r-- 1 aleph exlibris 4644 Nov 7 05:15 abc50_p_cir_12.03705
-rw-rw-r-- 1 aleph exlibris 18527 Nov 8 04:15 abc50_p_cir_12.03739
-rw-rw-r-- 1 aleph exlibris 15154 Nov 8 04:15 abc50_p_cir_12.03740
-rw-rw-r-- 1 aleph exlibris 4677 Nov 8 05:15 abc50_p_cir_12.03760
-rw-rw-r-- 1 aleph exlibris 4644 Nov 8 05:15 abc50_p_cir_12.03761
-rw-rw-r-- 1 aleph exlibris 18527 Nov 9 04:15 abc50_p_cir_12.03787
-rw-rw-r-- 1 aleph exlibris 4644 Nov 9 04:15 abc50_p_cir_12.03788
-rw-rw-r-- 1 aleph exlibris 4677 Nov 9 05:15 abc50_p_cir_12.03808
-rw-rw-r-- 1 aleph exlibris 4644 Nov 9 05:15 abc50_p_cir_12.03809
-rw-rw-r-- 1 aleph exlibris 18528 Nov 10 04:15 abc50_p_cir_12.03834
-rw-rw-r-- 1 aleph exlibris 4645 Nov 10 04:15 abc50_p_cir_12.03835
-rw-rw-r-- 1 aleph exlibris 4678 Nov 10 05:15 abc50_p_cir_12.03855
-rw-rw-r-- 1 aleph exlibris 4645 Nov 10 05:15 abc50_p_cir_12.03856
-rw-rw-r-- 1 aleph exlibris 4708 Nov 10 10:02 abc50_p_cir_12.03870
You will note that before the time-change there were just two runs at 5:15. Since the time-change there are four runs (two at 4:15 and two at 5:15).
The following grep shows that the job daemon was last restarted on Oct. 24:
aleph@lib-aleph2(a20_1) ABC50> ps -ef | grep jobd
aleph 16842 1 0 Oct24 ? 00:00:00 /exlibris/aleph/a20_1/aleph/exe/jobd a20_1
I believe the second (5:15) run each day is overwriting the correct output from the first (4:15) run with blank output.
This is like KB 5464. As noted there, you need to do util e/15/2 to stop the daemon, followed by util e/15/1 to restart it.
See also KB 8192-743.
- Article last edited: 10/8/2013