What does the error %GTM-E-REQRUNDOWN mean ?

From VistApedia
Revision as of 16:19, 19 August 2009 by DavidWhitten (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

When I try

GTM>D Q^DI 

i get this:

GTM>D Q^DI
%GTM-E-REQRUNDOWN, Error accessing database /home/vista/EHR/g/mumps.dat.  Must be rundown on cluster node poohbah.
At M source location Q^DI

I know that poohbah is the name of my pc, and I know that I have VistA globals stored in /home/vista/EHR/g/mumps.dat but I don't know what to do. It seems that surely the database is broken.


This error usually occurs because a GT.M system has been stopped before it had a chance to save all the work in memory onto the Host File System (hard disk) file where the MUMPS data is stored.


K.S. Bhaskar suggests that you set up before image journaling and perform a mupip journal recover on the database when you boot up your computer.

Related questions are: How do I know if I am running journaling? How do I set up VistA ? and How do I set up GT.M ?


To fix the %GTM-E-REQRUNDOWN error, you should run a Linux program named mupip which is part of GT.M, with the sub-command "rundown"

there are two variants of this:

The first variant will probably fix your immediate problem of the error, but if you don't perform a journal recovery, you will probably loose data.

$ $gtm_dist/mupip rundown -r "*"

This calls the mupip command in the directory named by the environment variable named "gtm_dist", and tells the rundown sub-command that all regions should be rundown.

The second variant is useful if you run out of semaphores in memory.

$ $gtm_dist/mupip rundown
This calls the mupip command in the directory named by the environment variable named "gtm_dist", and tells the rundown sub-command that memory semaphores that are not being used should be cleaned up.