Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: "ORA-27300: OS system dependent operation:GetThreadTimes failed" Causes Instance Crash 10.2.0.2

Re: "ORA-27300: OS system dependent operation:GetThreadTimes failed" Causes Instance Crash 10.2.0.2

From: hpuxrac <johnbhurley_at_sbcglobal.net>
Date: 21 Dec 2006 05:25:47 -0800
Message-ID: <1166707547.788539.285980@79g2000cws.googlegroups.com>

Charles Hooper wrote:
> metatech_at_flashmail.com wrote:
> > Charles Hooper a écrit :
> >
> > > The alert log shows this:
> > > ---------------------------------
> > > Sat Oct 28 00:00:34 2006
> > > Process startup failed, error stack:
> > > Sat Oct 28 00:00:34 2006
> > > Errors in file
> > > d:\oracle\product\10.2.0\admin\DB\bdump\vmfg_psp0_2196.trc:
> > > ORA-27300: OS system dependent operation:GetThreadTimes failed with
> > > status: 6
> > > ORA-27301: OS failure message: The handle is invalid.
> > > ORA-27302: failure occurred at: skgpspawn
> > >
> >
> > See bug fix 5163569
> > RDBMS: There is a timing window at background process spawn time that
> > can cause an ORA-00600 [784].
> > This is fixed in 10.2.0.2.0 Patch 8 (10.2.0.2.8P) 32-Bit Patch 5502226
> > 64-Bit (Itanium) Patch 5500894 64-Bit (x64) Patch 5500921
>
> I installed patch 9 hoping to cure the problem, and now I can crash the
> database sessions every 40 hours if desired. I opened an SR on
> Metalink on 28-NOV-06, and have yet to receive a suggestion from
> Oracle. I came up with a work around 15 days ago.

Do you have a re-creatable test case ( or can you produce one ) so that Oracle can reproduce this at will? If so I would submit that and get it after a week or two consider getting it bumped up to sev 1.

I just got oracle to admit to a bug fix in the 9208 patchset ( second one for this site ) with a service request that's been open since early October. The explanation for the delay was that it was assigned to an analyst who was ( apparently ) looking for another job and that person wasn't motivated to work on it. ( I did have a workaround but still ... maybe I shouldn't have let it sit open at sev 2 for so long ). My problem though wasn't nearly as severe as a bug that brings down the instance. Received on Thu Dec 21 2006 - 07:25:47 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US