Patch Set Update and Critical Patch Update July 2017 Availability Document
(Doc ID 2261562.1)
Follow link for 11.2.0.4 DB PSU
Patch 25869727: DATABASE PATCH SET UPDATE 1.2.0.4.170718
This Patch has been Superseded.
Reason
Patch 26609445 is a super set of patch 25869727
Note
The most recent replacement for this patch is 26609445.
Replacement Options (Patches or Patchsets known to Include or Supersede this
Patch)
<https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?_afrLoop=4
78871571448389&parent=DOCUMENT&patchId=25869727&sourceId=2261562.1&_afrWindo
wMode=0&_adf.ctrl-state=9xgaapwyj_401> 26609445
DATABASE PATCH SET UPDATE 11.2.0.4.170814
Patch
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 10:00 AM
To: dbakevlar@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx; dedba@xxxxxxxxxx
Subject: Re: ORA-600 after July PSU apply -- production down.
Sorry, check 11.2.0.4 Patch Set - Availability and Known Issues (Doc ID
1562139.1) to see if it contains any notes of interest.
Mark Powell
Database Administration
(313) 592-5148
_____
From: oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx>
<oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx> > on
behalf of De DBA <dedba@xxxxxxxxxx <mailto:dedba@xxxxxxxxxx> >
Sent: Thursday, August 24, 2017 12:53:52 PM
To: dbakevlar@xxxxxxxxx <mailto:dbakevlar@xxxxxxxxx> ;
oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx>
Subject: Re: ORA-600 after July PSU apply -- production down.
Yes, I did - but it talks about the 12.1.0.2.170718 PSU, no mention of the
11.2.0.4.170718 PSU there.. If there is a similar warning about the 11.2
patch, then I've not seen it.
On 25/08/17 02:47, Kellyn Pot'Vin-Gorman wrote:
And have you looked at this Doc ID? 2264625.1
On Aug 24, 2017, at 10:40 AM, Mark W. Farnham <mwf@xxxxxxxx
<mailto:mwf@xxxxxxxx> > 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@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx>
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of De DBA
Sent: Thursday, August 24, 2017 12:27 PM
To: mark.powell2@xxxxxxx <mailto:mark.powell2@xxxxxxx> ;
oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx>
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 <mailto:dedba@xxxxxxxxxx> <dedba@xxxxxxxxxx>
Sent: Thursday, August 24, 2017 11:32:35 AM
To: Powell, Mark; <mailto:oracle-l@xxxxxxxxxxxxx> 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 <<