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

And have you looked at this Doc ID? 2264625.1

> On Aug 24, 2017, at 10:40 AM, Mark W. Farnham <mwf_at_rsiz.com> wrote:
>
> Where do you keep the full tree manual backup of lsinventory you do before each patch?
>
> Do you happen to have an environment you did not patch? Perhaps you can play a shell game.
>
> Sorry I don’t have a solution in hand.
>
> mwf
>
> From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of De DBA
> Sent: Thursday, August 24, 2017 12:27 PM
> To: mark.powell2_at_dxc.com; oracle-l_at_freelists.org
> Subject: Re: ORA-600 after July PSU apply -- production down.
>
> hmm that does not seem to apply here. opatch did not have any errors...
>
> I wonder if this is related to the 12c patch bundle recall that Seth Miller shared sometime ago.. although this is 11g...
>
> Cheers,
> Tony
>
> On 25/08/17 01:53, Powell, Mark wrote:
> 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> <oracle-l-bounce_at_freelists.org> <mailto:oracle-l-bounce_at_freelists.org> on behalf of De DBA <dedba_at_tpg.com.au> <mailto: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