Recover from Ingres crash
From PTAGISWiki
When Ingres terminates unexpectedly, follow this procedure to restore the system to operation.
Contents |
ingstop
Not all Ingres processes may be killed by a crash. First, bring everything to a stop by issuing
ingstop
as the user ingres on blueback. If this does not succeed in shutting down all Ingres processes, it may be necessary to issue "ingstop" on all client machines first (bay and jack).
ingstart
As user ingres, start ingres with
ingstart
FDVL
FDVL uses a lock file and the table fd_control to manage resource contention and these elements will probably be left in an inconsistent state after a crash. They mush be repaired before FDVL will operate properly.
fd_control table
When the system is at rest and ready to process a newly submitted file, it should have these values:
| fdv_command | RUN |
| fdv_state | WAITING |
| fdv_semaphore | |
| fdl_command | RUN |
| fdl_state | WAITING |
As 'ptagdev' on 'blueback' ...
> tv
OK > qbf -mupdate -upittag ptagis3 fd_control -s
- Set 'Fdv State' to 'WAITING'
- Clear out 'Fdv Semaphore'
- Save changes
/home/pittag/etc/FD_LOCK
This lock file should look like this during a state of rest:
PID=NULL Mon Nov 9 14:54:54 PST 2009
Typically, after a crash, FD_LOCK will contain a PID that is no longer running and will thus block any subsequent attempts of FDVL to run. To clear the PID, use this script:
/home/pittag/bin/FDVL/fdc_nullLock.sh
restart TDS heartbeat and monitor
As user pittag issue these commands:
cd /home/pittag/bin/TDS ./TDS_runEventHeartbeat.pl ./TDS_runEventMonitor.pl
submit a test file to FDVL
FDVL is launched by the receipt of a tagging file. This can be submitted via email.
To : pitdata@psmfc.org
Attachment: /home/pittag/data/FDVL/loaded/tagging/ZZX/2000/ZZX00100.DC-L_1
Subject : TAGGING CORRECTIONS
