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

From: Michael McMullen <>
Date: Fri, 25 Aug 2017 14:01:54 +0000
Message-ID: <>

This same oda server patch also caused my x3-2 to bomb on one node. (on GI)

Still working on getting that back up.

From: <> on behalf of De DBA <> Sent: August 24, 2017 2:57 PM
To:; Subject: Re: ORA-600 after July PSU apply -- production down.

Hi Ian,

Yes, we run ASM in all our environments. They are also all on the same patch versions, so that can be excluded. The only difference is the problem box is an ODA, the others are HP Proliants and ExaData. I tend to blaming ODA - any patching session on the PoS so far has included several sev1 SRs. It's hardly normal...

Next year it will be replaced with another ExaData - can't wait!


On 25/08/17 03:33, MacGregor, Ian A. wrote: I was curious and ran

oracle_at_fermi-oracle02 $ find ./ -name "kgfm* the top directory was $ORACLE_HOME

a typical response was


This on a server with internal disks and not using ASM so there is no GI applied. It seems the problem may lie with ASM. Do the servers which did not fail also use ASM.

Ian MacGregor
SLAC National Accelerator Laboratory

On Aug 24, 2017, at 8:32 AM, De DBA <<>> wrote:

 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].


Received on Fri Aug 25 2017 - 16:01:54 CEST

Original text of this message