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@xxxxxxxxxxx> Dimensional.dba@xxxxxxxxxxx
<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@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Powell, Mark
Sent: Thursday, August 24, 2017 8:54 AM
To: oracle-l@xxxxxxxxxxxxx
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@xxxxxxxxxx <mailto:dedba@xxxxxxxxxx> >
Sent: Thursday, August 24, 2017 11:32:35 AM
To: Powell, Mark; oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx>
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 <<