CIR51 generated core dumps while running for two of our ADM's

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Article Type: General
Product: Aleph
Product Version: 18.01

Description:
One of our ADM's reported not receiving any overdue notices this morning. Upon examination, the process had run but had generated the following errors:

Load: /exlibris/aleph/u18_3/alephe/tab/tab100
Load: /exlibris/aleph/u18_3/nfg50/tab/tab100

Oracle error: handle_connection
ORA-12545: Connect failed because target host or object does not exist
Load: /tmp/utf_files/exlibris/aleph/u18_3/nfg50/tab/tab32

Oracle error: handle_connection
ORA-12545: Connect failed because target host or object does not exist

and further down almost to end of output:

Load: /exlibris/aleph/u18_3/odn50/tab/bib_format
ENTER check_library_relation
LIBRARY-RELATION = PID
SOURCE-LIBRARY = NFG50
Bus Error (core dumped)

and also:

Load: /tmp/utf_files/exlibris/aleph/a18_3/aleph/error_eng/circ_logger

I/O error : file '/exlibris/aleph/a18_3/tmp/usm504288992'
error code: 4/6 (ANS85), pc=0, call=12, seg=0
146 No current record defined for sequential read

mv: cannot access cir_51_4.scr

Attached is the complete contents of the file (can also be found online on our libserv4 at /exlibris/aleph/u18_3/alephe/scratch/nfg50_p_cir_51.00805. I also see the "Bus Error (core dumped)" error within the execution log exlibris/aleph/u18_3/alephe/scratch/und50_p_cir_51.00960 which ran around the same time. We have not altered start times within job_list for these jobs and they have never created conflicts for each other that we know of.

Please let us know what caused the error, how to fix and if we will have to back out the transactions or if they will just be picked up in tomorrow's run. Note: other cir-51 processes that ran both before and after these jobs completed without problem.

Resolution:
As can be seen from the following, p_cir_51's in five different ADMs are set to run at 05:50:00 :

libserv4.odin.nodak.edu-a18(3) >>grep 'W1 05:50:00' job_list
W1 05:50:00 Y UND50 p_cir_51 UND50,undma-cir51-overd-%D%H,Y,,Y,,UNDMA,,00,00,Y,N,O,4,
W1 05:50:00 Y NMI50 p_cir_51 NMI50,nmi-cir51-overdue-%D%H,Y,,Y,,,,00,00,Y,N,O,2,
W1 05:50:00 Y NFG50 p_cir_51 NFG50,nfg-cir51-overdue-%D%H,Y,,Y,,,,00,01,Y,N,O,4,
W1 05:50:00 Y CPS50 p_cir_51 CPS50,cps-cir51-billhs-%D%H,Y,,Y,,CPSHS,,00,00,Y,N,L,2,
W1 05:50:00 Y LEA50 p_cir_51 LEA50,lea-cir51-billlst-%D%H,Y,,Y,,,,00,00,Y,N,L,2,

The conflict *seemed* to occur with the nfg50 and und50 runs. This should not be a problem. We could either wait and see if the problem occurs again or you could stagger all of these to run at different times.

In regard to this question: "Please let us know ... if we will have to back out the transactions or if they will just be picked up in tomorrow's run."

The p_cir_51 database-updating step occurs after the notice-generating step, so if you didn't get any notices, the database was not updated and these overdues will be picked up in tomorrow's run.

Let us know if this happens again.

Article last edited: 10/8/2013