RE: ORA-600 after July PSU apply -- production down.

Did you use the original DB patch released in July or did you use the super ceded DB Patch released on 8/14/2017?  

p25869727_112040_Linux-x86-64 superceded by

p26609445_112040_Linux-x86-64  

There is a fix in the patch released on 8/14/2017 that includes database will not start scenario. Doesn't affect all databases of course.    

Matthew Parker

Chief Technologist

Dimensional DBA

425-891-7934 (cell)

D&B 047931344

CAGE 7J5S7  <mailto:Dimensional.dba_at_comcast.net> Dimensional.dba_at_comcast.net

 <http://www.linkedin.com/pub/matthew-parker/6/51b/944/> View Matthew Parker's profile on LinkedIn

 <http://www.dimensionaldba.com/> www.dimensionaldba.com    

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Powell, Mark
Sent: Thursday, August 24, 2017 8:54 AM
To: oracle-l_at_freelists.org
Subject: Re: ORA-600 after July PSU apply -- production down.  

I could not find a hit a support for the ORA-00600 but did find this which might or might not be of any help  

JULY PSU 2017 PATCH Fails to apply "Conflict with 19285025" (Doc ID 2291644.1)  

Mark Powell

Database Administration

(313) 592-5148    

From: De DBA <dedba_at_tpg.com.au <mailto:dedba_at_tpg.com.au> > Sent: Thursday, August 24, 2017 11:32:35 AM To: Powell, Mark; oracle-l_at_freelists.org <mailto:oracle-l_at_freelists.org> Subject: Re: ORA-600 after July PSU apply -- production down.  

 Even starting in nomount mode gives ORA-600.  

I just attempted to create a dummy instance with a init.ora file with only 1 line in it (db_name = ORCL) - no ASM, no spfile in play. Starting that also failed with the same ORA-600 [kgfmGetCtx0].  

Cheers,

Tony  

On 25/08/17 01:11, Powell, Mark wrote:

>> ORA-01078: failure in processing system parameters <<
 

Have you in fact verified that your spfile parameters are in fact valid? Startup nomount and full the spfile into a pfile then review it carefully.    

Mark Powell

Database Administration

(313) 592-5148    

From: oracle-l-bounce_at_freelists.org <mailto:oracle-l-bounce_at_freelists.org> <mailto:oracle-l-bounce_at_freelists.org> <oracle-l-bounce_at_freelists.org> on behalf of De DBA <mailto:dedba_at_tpg.com.au> <dedba_at_tpg.com.au> Sent: Thursday, August 24, 2017 10:51:24 AM To: oracle-l_at_freelists.org <mailto:oracle-l_at_freelists.org> Subject: ORA-600 after July PSU apply -- production down.  

HI,

I've tonight applied the July PSU to the last environment - production. All other environments, including DR, went swimmingly, but after applying the patches when I tried to startup upgrade to apply the in-database part, I was regaled with the following fine errors on both nodes:

00:28:52 [25-AUG-17][SYS_at_MyProd]$ startup upgrade ORA-01078: failure in processing system parameters ORA-00600: internal error code, arguments: [kgfmGetCtx0], [kgfm.c], [2840], [ctx], [], [], [], [], [], [], [], []

The parameter files of course do still exist. The MOS lookup tool has no information and my 24/7 db is down. Any clues?

I've already attempted to roll-back the OCW part, but that had no effect. Although now opatch lsinventory no longer lists the original version of that patch (11.2.0.4.5) either.

Environment:

ODA X4-2 RDBMS 11.2.0.4 ASM 12.1.0.2 Database PSU 11.2.0.4.170718

OCW PSU - no longer shown

OVJM PSU 11.2.0.4.170718 Thanks,

Tony  

--
http://www.freelists.org/webpage/oracle-l