Re: [Info-ingres] How to stop ingres safely?

#1

Hi Frank,

Quote:

Hi all,
There are some error messages in errlog.log
[II_RCP , 40279700]: Sun Mar 20 23:22:09 2005 E_DMA469_PROC
ESS_HAS_DIED Process (0000198D) has died. A process attached to the
logging and locking system has exited without going through normal
cleanup processing. The system will now perform cleanup processing on
behalf of the failed process

I guess some unfinished transactions didn't clear transaction
log .

Shall I stop ingres as the following steps ?

May not be necessary. Check to see what exactly failed - that
should be the next line in the errlog. I may just be a single component
that can be restarted. eg a NET server, ingstart -iigcc

Connect to the servers- do they respond? Check the status of
user connections in those servers. Are you seeing MUTEX sessions?

Note also that the system does indicate that clean-up processes
have started for the failed process.

Quote:

Remove active sessions
ingsstop
if some ingres processes still runing , then kill them
It never hurts to do at least a ps -uingres -f > ps.log

You never know when you want to look at this again
afterwards. Have a good hard look at the processes. Is something
looping?

Dont just jump in with kill -KILL. Try a few other signals first:
kill -HUP, kill -QUIT, kill -INT, kill -TERM

Quote:

if some ingres processes still runing , ingstop -force

I cant imagine what would be running after you reach kill -KILL.
If there is anything running that a kill -KILL cant kill, then kill the
machine to clear the zombies.

Quote:

$II_SYSTEM/ingres/utility/ipcclean
rm $II_SYSTEM/ingres/files/memory/*
ingstart

BTW, I am confused about ingstop -kill , ingstop -force and
ingstop -immediate.
Not surprising, the manual is not very clear on the differences

between these options.

Quote:

As for ingstop -force , will transaction recovery be required when
the installation is restarted ? In other words, some unfinished
transactions will lost , right ? As a result , the database will be
marked as inconsistent, right? Anyway , which parameter do you
recommend to stop ingres if ingstop cannot stop it? Thanks.

It doesn't follow that an incomplete transaction will force the
database inconsistent. The recovery - which is automatic on the restart
- will normally be able to flush out of the log the incomplete transaction,
and bring the database to a consistent state.

BTW. By being prepared to kill the processes anyway, I
suspect you aremimicing the action of ingstop -kill.

Martin Bowes

--
Random Farscape Quote #21:
Jools - Everything I have seen is despicable.
John - Welcome to the Federation Starship SS.Buttcrack!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: [Info-ingres] How to stop ingres safely?

comp.databases.ingres comp.databases.ingres

Re: [Info-ingres] How to stop ingres safely? - 03-21-2005 , 08:38 AM