How to stop ingres safely? -
03-21-2005
, 06:23 AM
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 ?
Remove active sessions
ingstop
if some ingres processes still runing , then kill them
if some ingres processes still runing , ingstop -force
$II_SYSTEM/ingres/utility/ipcclean
rm $II_SYSTEM/ingres/files/memory/*
ingstart
BTW, I am confused about ingstop -kill , ingstop -force and
ingstop -immediate.
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.
-kill Shuts down the installation without waiting for currently
executing transactions to complete. Transaction recovery
will be required when the installation is restarted. Any Ingres
processes that cannot be shut down by conventional means are terminated.
-force Forces the shut down of active servers in the installation
without waiting for users to disconnect.
-immediate Shuts down the installation immediately. It does not wait
for currently executing transactions to complete.
Transaction recovery will be required when the
installation is restarted.
Thanks |