| > So presumably it is fixed in V6.1-04 and 6.1-1 ?
Not sure why you would presume this. it looks to me as though
the release notes that you are reading are not the ECO 1 final release
notes but instead the Rdb 7.0 release notes (what does the first page
of the release notes say)?
The particular release note indicates that the problem is
fixed in 6.0B, 6.1A and 7.0. you can read about it in the release
notes (this is from 6.1-04 and it appears to have been fixed in ECO 2
for V6.1):
2.2.21 Monitor "hangs" after certain period of activity
It is possible for the database monitor process to suddenly
stop processing user attaches and appear to be "hung". The
monitor process must be manually killed and re-started to
get the system back operational.
This situation can be determined by analyzing the system
using the VMS SDA utility and examining the open channels
(using the SHOW PROC/CHANNEL command). The mailbox channels
(typically 2 of them, starting with MBAn) should both have
a status of "busy". If the mailboxes do NOT have a status
of busy, then you have encountered this problem.
There is no work-around to this problem. Issuing a RMU/OPEN
command when the database is already open, or a RMU/MON
REOPEN_LOG command makes the situation more likely to
occur.
This problem has been corrected in Oracle Rdb Version V6.1
ECO2.
|