I'm running GT.M V530002 on Linux (RedHat EL 4.1 32Bit). After a power failure i can't access the database anymore. 'mupip integ' reports no errors.
Any ideas what to do to identify and fix that problem?
Kind regards
Lothar Joeckel
[ljoeckel@localhost gtmjni]$ mupip integ
File or Region: mumps.dat
No errors detected by integ.
Type Blocks Records % Used Adjacent
Directory 2 19 21.484 NA
Index 279 13561 90.070 4
Data 13300 347454 60.429 13274
Free 133219 NA NA NA
Total 146800 361034 NA 13278
[ljoeckel@localhost gtmjni]$ gtm
GTM>d ^%G
Output device: <terminal>:
List ^%C
%GTM-E-REQRUNDOWN, Error accessing database /mydata/workspace_gtm/gtmjni/mumps.dat. Must be rundown on cluster node localhost.localdomain.
List ^
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would like to suggest running before image journaling. Then, just do a mupip journal -recover -backward on power-up (if the system went down cleanly, this does nothing).
Regards
-- Bhaskar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm running GT.M V530002 on Linux (RedHat EL 4.1 32Bit). After a power failure i can't access the database anymore. 'mupip integ' reports no errors.
Any ideas what to do to identify and fix that problem?
Kind regards
Lothar Joeckel
[ljoeckel@localhost gtmjni]$ mupip integ
File or Region: mumps.dat
No errors detected by integ.
Type Blocks Records % Used Adjacent
Directory 2 19 21.484 NA
Index 279 13561 90.070 4
Data 13300 347454 60.429 13274
Free 133219 NA NA NA
Total 146800 361034 NA 13278
[ljoeckel@localhost gtmjni]$ gtm
GTM>d ^%G
Output device: <terminal>:
List ^%C
%GTM-E-REQRUNDOWN, Error accessing database /mydata/workspace_gtm/gtmjni/mumps.dat. Must be rundown on cluster node localhost.localdomain.
List ^
Hello Lothar,
you should perform a rundown of the database:
mupip RU -R DEFAULT
or
mupip RU -F /mydata/workspace_gtm/gtmjni/mumps.dat
Regards
Martin
Thank's. Works perfectly.
I would like to suggest running before image journaling. Then, just do a mupip journal -recover -backward on power-up (if the system went down cleanly, this does nothing).
Regards
-- Bhaskar