Hi,
Due to a brief power outage while i was in Mumps prompt (M>), I'm now getting this error when i try to access/write to my global ....
%GTM-E-REQRUNDOWN, Error accessing database /root/gtm/mumps.dat. Must be rundown on cluster node localhost
Can anyone tell me what happened and how i should recover from this ?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-10-24
This is the full error from the above problem:
%GTM-E-REQRUNDOWN, Error accessing database /root/gtm/mumps.dat. Must be rundown on cluster node localhost.
%GTM-I-RTSLOC, At M source location DISABLE+10^%SerenjD
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Setup your GT.M environment (environment variables $gtmgbldir, $gtmroutines, etc.). Then execute
mupip rundown -region "*"
If there was a power failure while a database was open, there may be database integrity errors and you should also run an integ on it:
mupip integ -region "*"
If there are errors reported by mupip integ, the chapter on DSE in the Admin & Ops Guide will tell you how to repair them. If you want a database that can be automatically recovered after a power failure, you will need to use before image journaling, which is discussed in the journaling chapter of the A&O.
-- Bhaskar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Due to a brief power outage while i was in Mumps prompt (M>), I'm now getting this error when i try to access/write to my global ....
%GTM-E-REQRUNDOWN, Error accessing database /root/gtm/mumps.dat. Must be rundown on cluster node localhost
Can anyone tell me what happened and how i should recover from this ?
Thanks.
This is the full error from the above problem:
%GTM-E-REQRUNDOWN, Error accessing database /root/gtm/mumps.dat. Must be rundown on cluster node localhost.
%GTM-I-RTSLOC, At M source location DISABLE+10^%SerenjD
Setup your GT.M environment (environment variables $gtmgbldir, $gtmroutines, etc.). Then execute
mupip rundown -region "*"
If there was a power failure while a database was open, there may be database integrity errors and you should also run an integ on it:
mupip integ -region "*"
If there are errors reported by mupip integ, the chapter on DSE in the Admin & Ops Guide will tell you how to repair them. If you want a database that can be automatically recovered after a power failure, you will need to use before image journaling, which is discussed in the journaling chapter of the A&O.
-- Bhaskar