Re: [PATCH] Re: Shared memory shmat/dt not working well in 2.5.x

Zlatko Calusic
2002-10-02T18:40:37Z

Alessandro Suardi <alessandro.suardi@oracle.com> writes:
> The more complicated bug you're talking about is the exec_mmap
> change introduced in 2.5.19 and fixed a handful of versions
> later, possibly .28, where PMON wouldn't start after 120"...
> I guess :)

Oh, well, if that one is really fixed, then I have another one. ;)

After some time up, few select & few inserts, Oracle decided to die
(2.5.40 + Hugh's patch, SMP, Oracle 9.0.1.4 - works flawlessly on
2.4.19). I have a full coredump, but I don't know what to do with it
(if somebody wants it, just say). It seems benchmarking will
wait... :(

*** 2002-10-02 20:15:27.634
*** SESSION ID:(4.1) 2002-10-02 20:15:27.583
BH (0x0x60fee288) file#: 1 rdba: 0x004000c7 (1/199) class 1 ba: 0x0x60c9a000
set: 3, dbwrid: 0
hash: [53509d88,53509d88], lru: [60fee370,60fee220]
LRU flags:
ckptq: [NULL] fileq: [NULL]
st: XCURRENT, md: NULL, rsop: 0x(nil), tch: 1
L:[0x0.0.0] H:[0x0.0.0] R:[0x0.0.0]
*** 2002-10-02 20:15:27.634
ksedmp: internal or fatal error
ORA-00600: Message 600 not found; No message file for product=RDBMS, facility=ORA; arguments: [kcbkllrba_2]

...

--
Zlatko