Runaway log file and RDMMON

[MJ26]

Folks,
I have a Vaxstation 4000-90 with VMS version 5.5-2H4. Anyways, to get to it, I have a system disk that seems to be filling up due to a runaway log file associated with the RDDMMON process. It causes my server to run out of disk space, and ultimately hangs the system from running processes. How do I go about troubleshooting this process? Thanks in advance. I will be activly monitoring this forum, so I will respond asap for the next 4 hours.

[Thomas Ritter]

... run away log file ? My first suggestion is to find out what is being written to the log. If it turns out to be some re-occuring failure deal with that first.

[Steven Schweda · Accepted solution]

As uaual, actual information would be more
helpful than vague descriptions (such as "a
runaway log file associated with the RDDMMON
process").

I know nothing, but if "RDDMMON" was actually
"RDMMON", and if the "runaway log file" was
actually SYS$SYSTEM:RDMMON.LOG, then a quick
Google search suggests that it's an Rdb log
file.

http://www.kuzbass.ru:8083/docs/rdb702/oraclerdb/gdmp7/gdmp_mon.htm

If you don't need the data, perhaps you could
stop the monitor process. You might also
look through the system start-up procedures
to see if you can prevent it from running
in the first place.

If you do need to run the monitor, there
seem to be options ("RMU/MONITOR REOPEN_LOG")
to segment the log file, which could be done
periodically by a batch job, and then purging
the log files would tend to control the
runaway disk space consumption.

Have you looked at what's in the log file to
see if there's some (curable) problem? Are
you using Rdb?

[MJ26]

Thanks for both responses. I have found the log file and also found that there is a connection error to one of the databases that seems to be creating the larger than normal log file. Thanks for the pointers!!

[MJ26]

problem was solved. Found reoccurring issue with a connection problem with one of the databases causing the increased volume in log file size.