[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | Oracle Rdb - Still a strategic database for DEC on Alpha AXP! |
| Notice: | RDB_60 is archived, please use RDB_70 .. |
| Moderator: | NOVA::SMITHI SON |
|
| Created: | Fri Mar 18 1994 |
| Last Modified: | Fri May 30 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5118 |
| Total number of notes: | 28246 |
4988.0. "MON$DBR_READY + 78 bugcheck" by M5::DDAYBERR () Fri Jan 31 1997 11:42
A customer reported the following behavior Wednesday morning.
I didn't find much information on a MON$DBR_READY bugcheck, or
tincan buffer errors. The customer is running RDB 6.1-01 so
I've sent eco 4 since it addresses a tincan_buffer bugcheck.
Does the tincan_buffer bugcheck 'fixes' have anything to
do with the following scenario?
Debbie
- error freeing tincan buffer: 0031D524
- "%COSI-F-CANTASSMBX, error assigning a channel to a mailbox"
- secondary error message on buffer free:
- "%SYSTEM-W-NOSUCHDEV, no such device available"
------------------------------------------------------------------------------
30-JAN-1997 00:41:18.77 - received user image termination from
21802BD1:2
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for active users to terminate
30-JAN-1997 00:41:18.77 - received user image termination from
21802BD1:1
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for active users to terminate
30-JAN-1997 00:41:18.78 - received user image termination from
21802506:1
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for active users to terminate
30-JAN-1997 00:41:18.79 - received user image termination from
21800861:1
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for active users to terminate
30-JAN-1997 00:41:18.81 - received user image termination from
21803428:1
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for active users to terminate
30-JAN-1997 00:41:18.81 - received user image termination from
21801684:2
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for active users to terminate
30-JAN-1997 00:41:18.81 - received user image termination from
21801684:1
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for active users to terminate
30-JAN-1997 00:41:18.82 - received user image termination from
2180245C:2
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for active users to terminate
30-JAN-1997 00:41:18.82 - received user image termination from
2180245C:1
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for active users to terminate
30-JAN-1997 00:41:18.83 - received user image termination from
21802511:1
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for active users to terminate
30-JAN-1997 00:41:18.83 - received user image termination from
21803403:1
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for active users to terminate
30-JAN-1997 00:41:18.84 - received user image termination from
218031FF:1
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- sending process deletion to process 2180477A
- sending process deletion to process 2180417B
- sending process deletion to process 2180357C
- sending process deletion to process 21804D8F
- sending process deletion to process 21804D90
- sending process deletion to process 21804D9E
- sending process deletion to process 218049A1
- sending process deletion to process 21804FB2
- database shutdown waiting for recovery to terminate
30-JAN-1997 00:42:35.43 - received recovery ready from 21804D8F:1
- process name RDM_RB_5, user SYSTEM
- error freeing tincan buffer: 0031D524
- "%COSI-F-CANTASSMBX, error assigning a channel to a mailbox"
- secondary error message on buffer free:
- "%SYSTEM-W-NOSUCHDEV, no such device available"
30-JAN-1997 00:42:35.48 - received recovery ready from 2180477A:1
- process name RDM_RB_2, user SYSTEM
- error freeing tincan buffer: 0031CB98
- "%COSI-F-CANTASSMBX, error assigning a channel to a mailbox"
- secondary error message on buffer free:
- "%SYSTEM-W-NOSUCHDEV, no such device available"
30-JAN-1997 00:42:35.50 - received recovery process termination
from 21804D90:1
- recovery failed
- continuing shutdown of database
"_DSA516:[PRODUCTION.RDB]DATA_CARE.RDB;1"
- database shutdown waiting for recovery to terminate
30-JAN-1997 00:42:35.50 - received recovery ready from 21804FB2:1
- process name RDM_RB_9, user SYSTEM
- error freeing tincan buffer: 0031D524
- "%COSI-F-CANTASSMBX, error assigning a channel to a mailbox"
- secondary error message on buffer free:
- "%SYSTEM-W-NOSUCHDEV, no such device available"
30-JAN-1997 00:42:35.50 - received recovery ready from 2180417B:1
- process name RDM_RB_3, user SYSTEM
- error freeing tincan buffer: 0031CB98
- "%COSI-F-CANTASSMBX, error assigning a channel to a mailbox"
- secondary error message on buffer free:
- "%SYSTEM-W-NOSUCHDEV, no such device available"
30-JAN-1997 00:42:35.52 - received recovery ready from 21804D9E:1
- process name RDM_RB_7, user SYSTEM
- error freeing tincan buffer: 0031CAC8
- "%COSI-F-CANTASSMBX, error assigning a channel to a mailbox"
- secondary error message on buffer free:
- "%SYSTEM-W-NOSUCHDEV, no such device available"
30-JAN-1997 00:42:35.54 - received recovery ready from 21804D90:1
- process name RDM_RB_6, user SYSTEM
30-JAN-1997 00:42:35.54 - released communication with process
21804D90:1
%RDMS-I-BUGCHKDMP, generating bugcheck dump file in current output
file
Saved PC = 00130EC8 : STD$DUMP_ALPHA_VMS_STACK + 00000088
Saved PC = 001301F4 : KOD$BUGCHECK_DUMP + 00001014
Saved PC = 00069914 : KOD$BUGCHECK_AND_EXIT_HNDLR + 000000A4
Saved PC = 80495D44 : S0 address
Saved PC = F35E42BC : S1 address
***** Exception at 0005C668 : MON$DBR_READY + 00000078
%COSI-F-BUGCHECK, internal consistency failure
Saved PC = 0005918C : MON$UMAIL + 000004F4
Saved PC = 0005898C : MONITOR + 00000D6C
Saved PC = 00046C8C : BLI$CALLG + 000000BC
Saved PC = 000400AC : MON$MAIN + 000000AC
Saved PC = F3611C44 : S1 address
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4988.1 | | NOVA::R_ANDERSON | Oracle Corporation (603) 881-1935 | Fri Jan 31 1997 14:29 | 18 |
| > - error freeing tincan buffer: 0031D524
> - "%COSI-F-CANTASSMBX, error assigning a channel to a mailbox"
> - secondary error message on buffer free:
> - "%SYSTEM-W-NOSUCHDEV, no such device available"
This problem is caused by a process sending mail to the monitor which requires a
response. However, the sending process dies (is terminated?) before the monitor
got around to sending the reply, so when the monitor eventually *does* send the
reply the corresponding mailbox doesn't exist...
This happens for a variety of reasons (i.e. a process trying to attach the
database while is is being shutdown, etc). Typically occurs when the monitor is
bogged down doing "other" things.
I'm not sure you actually have a problem here, and I don't know of any specific
tincan fixes that address this scenario.
Rick
|