RDMS_MONITOR abnormal terminated

[RomanceSu]

To everyone~

Do you know what way can debug RDMS_MONITOR ?

[Thomas Ritter]

Try $ rmu/show system
This will list all the current databases.
Do you see 384 databases ?

[RomanceSu]

no~ about 136

[Brad McCusker]

Hi RomanceSu,

There are basically 3 places we look for clues in these situations:

+ The Rdb monitor log files (confirm that we are looking at the right ones)
+ Rdb monitor bugcheck files (could be in various locations)
+ The VMS accounting files.

The name and location of the RDMS monitor log files may be different, depending on the version of Rdb and whether Rdb was installed with the â multiversionâ option or if the monitor log file was redirected when the monitor was started.

First, letâ s confirm that we are looking at the right RDMS_MOITOR log files:

$ SET PROCESS/PRIV=WORLD
$ RMU/SHOW SYSTEM
Oracle Rdb V7.1-401 on node MYNODE 2-JUN-2009 08:40:29.62
- monitor started 19-APR-2009 01:42:57.55 (uptime 44 06:57:32)
- monitor log filename is "SYS$SYSROOT:[SYSEXE]RDMMON71.LOG;51"
- no databases are accessed by this node

In this case, the CURRENT monitor log file is SYS$SYSROOT:[SYSEXE]RDMMON71.LOG;51. You would want to check the prior versions ($SYSROOT:[SYSEXE]RDMMON71.LOG;-1). Please post the â tailâ of this log file:

$ type/tail/out=rdms_mon_tail.log

If the monitor process failed, it may have created a bugcheck file. These will be named RDM*BUG*.DMP and will be located in one of the following locations:

$ DIR/DATE SYS$SYSTEM:RDM*BUG*.DMP
$ DIR/DATE RDM$BUGCHECK_DIR:RDM*BUG*.DMP
$ DIR/DATE SYS$MANAGER:RDM*BUG*.DMP

If the monitor was running under some username other than SYSTEM, you will want to also check the login directory of that username.

Finally, as others have suggested, the VMS accounting file may include information about the process completion status. Unfortunately, unless you know the PID of the monitor process that FAILED, it may be difficult to identify it. However, the following should narrow it down:

First, confirm that you have DETACHED accounting enabled:

$ show accounting
$ Accounting is currently enabled to log the following activities:

PROCESS any process termination
INTERACTIVE interactive job termination
LOGIN_FAILURE login failures
SUBPROCESS subprocess termination
DETACHED detached job termination **** this needs to be enabled ***
BATCH batch job termination
NETWORK network job termination
PRINT all print jobs
MESSAGE user messages

If DETACHED is enabled, then you can issue the following command:

$ ACCOUNTING/FULL/USER=SYSTEM/PROCESS=DETACHED/SINCE=/OUT= RDM_MON_ACC.LOG

$ Search RDM_MON_ACC.LOG â Final statusâ ,â start time:â ,â finish time:â

(the â start timeâ and â finish timeâ are included as a way to â sanity checkâ the information â do the start/finish times match when you think the RDB monitor started/stopped?

If DETACHED accounting is NOT enabled, then you will need to enable it and wait for the next failure:
$ set accounting/enable=detached

For what it is worth, we have also seen the RDB monitor crash while encountering deadlocks with DBR (recovery processes).

Best Regards,

Brad McCusker
Software Concepts International
www.sciinc.com