13/04/2016 OracleDatabasePatch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.

160119(Jan2016)
Gotoprimarycontent

OracleDatabase
Patch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)
Platform:Linuxx8664,SolarisAMD,SolarisSparc64,IBMAIX,HPUXItanium,IBM:LinuxonSystemz

Released:January19,2016

InthisdocumentOracleDatabaseHomereferstoEnterpriseEdition.StandardEditionDatabasesoftwareinstallsshouldinstallDatabasePSU.

TheDatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)includesupdatesforboththeClusterwarehomeandDatabasehomethatcanbe
appliedinarollingfashion.

ThispatchisDataGuardStandbyFirstInstallableSeeSection2.5,"InstallingDatabasePSUinStandbyFirstMode"formoreinformation.

ThispatchincludesJSONfunctionality.Ifyouintendtousethisfunctionality,therearesomeprerequisitesthatneedtobepresentbeforeinstallingthispatch.SeeMyOracle
SupportNote1992767.1JSONDatabasePatchBundleDetails.

ThispatchcanbeappliedusingOracleEnterpriseManagerCloudControl12cversion.OracleEnterpriseManagerprovidescompleteautomationtopatchtheclusterinzero
downtimebothinInplaceandOutofPlacemodes(OutofPlaceiscurrentlyavailableforExadatainstallationsonly.Formoreinformation,seeMyOracleSupportNote
1265998.1PatchOracleExadataDatabaseMachineviaOracleEnterpriseManager.)

ThispatchissupportedbyOPlan.OPlanisautilitythatfacilitatesthepatchinstallationprocessbyprovidingyouwithstepbysteppatchinginstructionsspecifictoyour
environment.Theinstructionscoverbothpatchapplicationandpatchrollbacksteps.TheinstructionsalsocovermultiplepatchingoptionsacrossInplaceandOutofPlace
methodologies.ImportantNote:12.1.0.1GIandRACOutofPlacepatchinghaveafewknownissues.SeeMyOracleSupportNote1306814.1OracleSoftwarePatchingwith
OPLANformoredetailedinformation.

Thisdocumentisaccurateatthetimeofrelease.ForanychangesandadditionalinformationregardingDatabasePatchforEngineeredSystemsandDBInMemory
12.1.0.2.160119(Jan2016),seetheserelateddocumentsthatareavailableatMyOracleSupport(http://support.oracle.com/):

Document2076305.1DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)KnownIssues

Thisdocumentincludesthefollowingsections:

Section1,"PatchInformation"

Section2,"PatchInstallationandDeinstallation"

Section3,"KnownIssues"

Section4,"References"

Section5,"ManualStepsforApply/RollbackPatch"

Section6,"BugsFixedbyThisPatch"

Section7,"DocumentationAccessibility"

1PatchInformation
FromCPUJan2016onwards,the5thdigitoftheversionnumberwillbechangedtoreflectthereleasedateintheformatYYMMDD.SeeMyOracleSupportDocument2061926.1
formoreinformation.

TheDatabasePatchforEngineeredSystemsandDBInMemorypatchesarecumulativeandincludetheDatabasePSUandassociatedCPUprogramsecuritycontent.

Table1describesinstallationtypesandsecuritycontent.Foreachinstallationtype,itindicatesthemostrecentpatches,whichincludesnewsecurityfixesthatarepertinentto
thatinstallationtype.Iftherearenosecurityfixestobeappliedtoaninstallationtype,then"None"isindicated.Ifaspecificpatchislisted,thenapplythatoranylaterpatchto
becurrentwithsecurityfixes.

Table1InstallationTypesandSecurityContent

InstallationType LatestDatabasePatchwithSecurityFixes

Serverhomes DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)

GridInfrastructurehome DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)

ClientOnlyInstallations None

InstantClientInstallations None

(TheInstantClientinstallationisnotthesameastheclientonlyInstallation.ForadditionalinformationaboutInstantClientinstallations,
seeOracleCallInterfaceProgrammer'sGuide.)

Table2liststhevariousconfigurationsandtheapplicableDatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)Patchthatshouldbeusedto
patchthatconfiguration.

Table2ConfigurationandDatabasePatchMapping

OPatch
Configuration GIVersion DatabaseVersions Patch CommandFoot1 Comments

GIHomeinconjunctionwithRAC, 12.1.0.2 12.1.0.2 DatabasePatchfor opatchauto GIHomeandalltheDatabaseHomes

RACOne,orSingleInstancehome EngineeredSystems willbepatched
andDBInMemory
12.1.0.2.160119
(Jan2016)

GIHomeinconjunctionwithRAC, 12.1.0.2 12.1.0.2andprior DatabasePatchfor opatchauto GIHomeandDatabaseHomeat

https://updates.oracle.com/Orion/Services/download?type=readme&aru=19644511 1/10
13/04/2016 OracleDatabasePatch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)
RACOne,orSingleInstancehome versions EngineeredSystems 12.1.0.2versionwillbepatched.
andDBInMemory
12.1.0.2.160119 ForDatabasehomewithversionother
(Jan2016) than12.1.0.2,applytheappropriate
DatabasePSUforthatversion.For
example,apply12.1.0.2.xPSUto
Databaseversion12.1.0.2.0.

GIHomeinconjunctionwithRAC, 12.1.0.2 Versionspriorto DatabasePatchfor opatchauto GIHomealoneispatched.

RACOne,orSingleInstancehome 12.1.0.2 EngineeredSystems
andDBInMemory ForDatabasehome,applythe
12.1.0.2.160119 appropriateDatabasePSUforthat
(Jan2016) version.Forexample,apply12.1.0.2.x
PSUtoDatabaseversion12.1.0.2.0.

OracleRestartHome 12.1.0.2 12.1.0.2 DatabasePatchfor opatchauto GIHomeandalltheDatabaseHomes

EngineeredSystems willbepatched.
andDBInMemory
12.1.0.2.160119
(Jan2016)

DatabaseSingleInstancehome NA 12.1.0.2 DatabasePatchfor opatchapply None

EngineeredSystems
andDBInMemory
12.1.0.2.160119
(Jan2016)

DatabaseClienthome NA 12.1.0.2 DatabasePatchfor opatchapply None

EngineeredSystems
andDBInMemory
12.1.0.2.160119
(Jan2016)

Footnote1OpatchautodoesnotsupportpatchinginDataGuardenvironments.SeeSection2.5,"InstallingDatabasePSUinStandbyFirstMode"formoreinformation.

Table3liststhevariouspatchesbypatchnumbergettinginstalledaspartofthisBundlepatch.

Table3PatchNumbersGettingInstalledasPartofthisBundlePatch

PatchNumber Description ApplicableHomes

21949015 DBBP12.1.0.2.160119 OnlyDBHomefornonOracleRACsetup.BothDBHomesandGridHomeforOracle

RACsetup.

22329617 OCWPSU12.1.0.2.160119 BothDBHomesandGridHome

21948341 ACFSPSU12.1.0.2.160119 OnlyGridHome

21436941 DBWLMPSU12.1.0.2.5 OnlyGridHome

2PatchInstallationandDeinstallation
Thissectionincludesthefollowingsections:

Section2.1,"PatchInstallationPrerequisites"

Section2.2,"OneoffPatchConflictDetectionandResolution"

Section2.3,"opatchauto"

Section2.4,"PatchInstallation"

Section2.5,"InstallingDatabasePSUinStandbyFirstMode"

Section2.6,"PatchPostInstallationInstructions"

Section2.7,"PatchPostInstallationInstructionsforDatabasesCreatedorUpgradedafterInstallationofPatchintheOracleHome"

Section2.8,"PatchDeinstallation"

Section2.9,"PatchPostDeinstallationInstructions"

2.1PatchInstallationPrerequisites

Youmustsatisfytheconditionsinthefollowingsectionsbeforeapplyingthepatch:

OPatchUtilityInformation

OCMConfiguration

ValidationofOracleInventory

https://updates.oracle.com/Orion/Services/download?type=readme&aru=19644511 2/10
13/04/2016 OracleDatabasePatch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)
DownloadandUnzipthePatch

RunOPatchConflictCheck

RunOPatchSystemSpaceCheck

2.1.1OPatchUtilityInformation

YoumustusetheOPatchutilityversion12.1.0.1.7orlatertoapplythispatchforallplatformsexceptHPUXItanium.FortheHPUXItaniumplatform,youmustusetheOPatch
utilityversion12.1.0.1.7orlatertoapplythispatch.OraclerecommendsthatyouusethelatestreleasedOPatchversionfor12.1releases,whichisavailablefordownloadfrom
MyOracleSupportpatch6880880byselectingARUlinkforthe12.1.0.1.0release.ItisrecommendedthatyoudownloadtheOpatchutilityandthepatchinasharedlocationto
beabletoaccessthemfromanynodeintheclusterforthepatchapplicationoneachnode.

WhenpatchingtheGIHome,asharedlocationonACFSonlyneedstobeunmountedonthenodewheretheGIHomeisbeingpatched.

ThenewopatchutilityshouldbeupdatedinalltheOracleRACdatabasehomesandtheGIhomethatarebeingpatched.

ToupdateOpatch,usethefollowinginstructions:

1.DownloadtheOPatchutilitytoatemporarydirectory.

2.ForeachOracleRACdatabasehomeandtheGIhomethatarebeingpatched,runthefollowingcommandsasthehomeownertoextracttheOPatchutility.

$unzip<OPATCHZIP>d<ORACLE_HOME>
$<ORACLE_HOME>/OPatch/opatchversion

Theversionoutputofthepreviouscommandshouldbe12.1.0.1.7orlater.

ForinformationaboutOPatchdocumentation,includinganyknownissues,seeMyOracleSupportDocument293369.1OPatchdocumentationlist.

2.1.2OCMConfiguration

TheOPatchutilitywillpromptforyourOCM(OracleConfigurationManager)responsefilewhenitisrun.YoushouldenteracompletepathofOCMresponsefileifyoualready
havecreatedthisinyourenvironment.OCMresponsefileisrequiredandisnotoptional.

IfyoudonothavetheOCMresponsefile(ocm.rsp),seethefollowingMyOracleSupportDocument966023.1HowToCreateAnOCMResponseFileForOpatchSilent
Installation.

2.1.3ValidationofOracleInventory

Beforebeginningpatchapplication,checktheconsistencyofinventoryinformationforGIhomeandeachdatabasehometobepatched.Runthefollowingcommandas
respectiveOraclehomeownertochecktheconsistency.

$<ORACLE_HOME>/OPatch/opatchlsinventorydetailoh<ORACLE_HOME>

Ifthiscommandsucceeds,itliststheOraclecomponentsthatareinstalledinthehome.Savetheoutputsoyouhavethestatuspriortothepatchapply.

Ifthiscommandfails,contactOracleSupportServicesforassistance.

2.1.4DownloadandUnzipthePatch

Toapplythepatch,itmustbeaccessiblefromallnodesintheOraclecluster.Downloadthepatchandunzipittoasharedlocation,thisiscalledthe
<UNZIPPED_PATCH_LOCATION>.Thisdirectorymustbeemptyandnotbe/tmp.Additionally,thedirectoryshouldhavereadpermissionfortheORA_INSTALLgroup.

$cd<UNZIPPED_PATCH_LOCATION>

Checkthatthedirectoryisempty.

$ls

Unzipthepatchasgridhomeownerexceptforinstallationsthatdonothaveanygridhomes.ForinstallationswherethispatchwillbeappliedtotheDatabasehomeonly,the
patchneedstobeunzippedasthedatabasehomeowner.

$unzipp22243551_121020_<platform>.zip

2.1.5RunOPatchConflictCheck

DeterminewhetheranycurrentlyinstalledoneoffpatchesconflictwiththeDatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)22243551as
follows:

ForGridInfrastructureHome,ashomeuser:

%$ORACLE_HOME/OPatch/opatchprereqCheckConflictAgainstOHWithDetailphBaseDir<UNZIPPED_PATCH_LOCATION>/22243551/21949015
%$ORACLE_HOME/OPatch/opatchprereqCheckConflictAgainstOHWithDetailphBaseDir<UNZIPPED_PATCH_LOCATION>/22243551/22329617
%$ORACLE_HOME/OPatch/opatchprereqCheckConflictAgainstOHWithDetailphBaseDir<UNZIPPED_PATCH_LOCATION>/22243551/21948341
%$ORACLE_HOME/OPatch/opatchprereqCheckConflictAgainstOHWithDetailphBaseDir<UNZIPPED_PATCH_LOCATION>/22243551/21436941

ForDatabasehome,ashomeuser:

%$ORACLE_HOME/OPatch/opatchprereqCheckConflictAgainstOHWithDetailphBaseDir<UNZIPPED_PATCH_LOCATION>/22243551/21949015
%$ORACLE_HOME/OPatch/opatchprereqCheckConflictAgainstOHWithDetailphBaseDir<UNZIPPED_PATCH_LOCATION>/22243551/22329617

ThereportwillindicatethepatchesthatconflictwiththeDatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)22243551andthepatchesfor
whichtheDatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)22243551isasuperset.

Note:

WhenOPatchstarts,itvalidatesthepatchandensuresthattherearenoconflictswiththesoftwarealreadyinstalledintheORACLE_HOME.
OPatchcategorizesconflictsintothefollowingtypes:

ConflictswithapatchalreadyappliedtotheORACLE_HOME.Inthiscase,stopthepatchinstallationandcontactOracleSupport
Services.
ConflictswithsubsetpatchalreadyappliedtotheORACLE_HOME.Inthiscase,continuewiththepatchinstallationbecauseasthe
newpatchcontainsallthefixesfromtheexistingpatchintheORACLE_HOME.And,inanycase,thesubsetpatchwillautomatically
berolledbackpriortotheinstallationofthenewpatch.

https://updates.oracle.com/Orion/Services/download?type=readme&aru=19644511 3/10
13/04/2016 OracleDatabasePatch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)

2.1.6RunOPatchSystemSpaceCheck

CheckifenoughfreespaceisavailableontheORACLE_HOMEfilesystemforthepatchestobeappliedasgivenbelow:

ForGridInfrastructureHome,ashomeuser:

1.Createfile/tmp/patch_list_gihome.txtwiththefollowingcontent:

%cat/tmp/patch_list_gihome.txt
<UNZIPPED_PATCH_LOCATION>/22243551/21436941
<UNZIPPED_PATCH_LOCATION>/22243551/21948341
<UNZIPPED_PATCH_LOCATION>/22243551/22329617
<UNZIPPED_PATCH_LOCATION>/22243551/21949015

2.RuntheopatchcommandtocheckifenoughfreespaceisavailableintheGridInfrastructureHome:

%$ORACLE_HOME/OPatch/opatchprereqCheckSystemSpacephBaseFile/tmp/patch_list_gihome.txt

ForDatabasehome,ashomeuser:

1.Createfile/tmp/patch_list_dbhome.txtwiththefollowingcontent:

%cat/tmp/patch_list_dbhome.txt
<UNZIPPED_PATCH_LOCATION>/22243551/22329617
<UNZIPPED_PATCH_LOCATION>/22243551/21949015

2.RunopatchcommandtocheckifenoughfreespaceisavailableintheDatabaseHome:

%$ORACLE_HOME/OPatch/opatchprereqCheckSystemSpacephBaseFile/tmp/patch_list_dbhome.txt

Thecommandoutputreportspassandfailmessagesasperthesystemspaceavailability:

IfOPatchreportsPrereq"checkSystemSpace"failed.,thencleanupthesystemspaceastherequiredamountofspaceisnotavailable.

IfOPatchreportsPrereq"checkSystemSpace"passed.,thennoactionisneeded.Proceedwithpatchinstallation.

2.2OneoffPatchConflictDetectionandResolution

ThefastestandeasiestwaytodeterminewhetheryouhaveoneoffpatchesintheOraclehomethatconflictwiththepatch,andtogetthenecessaryconflictresolutionpatches,
istousethePatchRecommendationsandPatchPlansfeaturesonthePatches&UpdatestabinMyOracleSupport.ThesefeaturesworkinconjunctionwiththeMyOracle
SupportConfigurationManager.RecordedtrainingsessionsonthesefeaturescanbefoundinDocument603505.1.

However,ifyouarenotusingMyOracleSupportPatchPlans,theMyOracleSupportConflictCheckertoolenablesyoutouploadanOPatchinventoryandcheckthepatches
thatyouwanttoapplytoyourenvironmentforconflicts.

Ifnoconflictsarefound,youcandownloadthepatches.Ifconflictsarefound,thetoolfindsanexistingresolutiontodownload.Ifnoresolutionisfound,itwillautomatically
requestaresolution,whichyoucanmonitorinthePlansandPatchRequestsregionofthePatches&Updatestab.

Formoreinformation,seeKnowledgeDocument1091294.1,HowtousetheMyOracleSupportConflictCheckerTool.

Or,manuallydeterminewhetheranycurrentlyinstalledoneoffpatchesconflictwiththePSUpatchasfollows:

IntheunzippeddirectoryasdescribedinSection2.1.4,"DownloadandUnzipthePatch".

Thefollowingcommandscheckforconflictsinboththe12.1GIhomeandthe12.1DBhomes.

Incaseyouareapplyingthepatch,runthiscommand:

#GRID_HOME/OPatch/opatchautoapply<UNZIPPED_PATCH_LOCATION>/22243551analyze

Incaseyouarerollingbackthepatch,runthiscommand:

#GRID_HOME/OPatch/opatchautorollback<UNZIPPED_PATCH_LOCATION>/22243551analyze

NotethatOracleproactivelyprovidesPSUoneoffpatchesforcommonconflicts.

SeeMyOracleSupportDocument1061295.1PatchSetUpdatesOneoffPatchConflictResolutiontodetermine,foreachconflictingpatch,whetheraconflictresolutionpatch
isalreadyavailable,andifyouneedtorequestanewconflictresolutionpatchoriftheconflictmaybeignored.

2.3opatchauto

TheOpatchutilityhasautomatedthepatchapplicationfortheOracleGridInfrastructure(GI)homeandtheOracleRACdatabasehomes.Itoperatesbyqueryingexisting
configurationsandautomatingthestepsrequiredforpatchingeachOracleRACdatabasehomeofsameversionandtheGIhome.

Theutilitymustbeexecutedbyanoperatingsystem(OS)userwithrootprivileges,anditmustbeexecutedoneachnodeintheclusteriftheGIhomeorOracleRAC
databasehomeisinnonsharedstorage.Theutilityshouldnotberuninparallelontheclusternodes.

Dependingoncommandlineoptionsspecified,oneinvocationofopatchautocanpatchtheGIhome,OracleRACdatabasehomes,orbothGIandOracleRACdatabasehomes
ofthesameOraclereleaseversionasthepatch.Youcanalsorollbackthepatchwiththesameselectivity.

Addthedirectorycontainingtheopatchautotothe$PATHenvironmentvariable.Forexample:

$exportPATH=$PATH:<GI_HOME>/OPatch

TopatchtheGIhomeandallOracleRACdatabasehomesofthesameversion:

#opatchautoapply<UNZIPPED_PATCH_LOCATION>/22243551ocmrf<ocmresponsefile>

TopatchonlytheGIhome:

#opatchautoapply<UNZIPPED_PATCH_LOCATION>/22243551oh<GI_HOME>ocmrf<ocmresponsefile>

TopatchoneormoreOracleRACdatabasehomes:

#opatchautoapply<UNZIPPED_PATCH_LOCATION>/22243551oh<oracle_home1_path>,<oracle_home2_path>ocmrf<ocmresponsefile>

TorollbackthepatchfromtheGIhomeandeachOracleRACdatabasehome:

#opatchautorollback<UNZIPPED_PATCH_LOCATION>/22243551

https://updates.oracle.com/Orion/Services/download?type=readme&aru=19644511 4/10
13/04/2016 OracleDatabasePatch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)
TorollbackthepatchfromtheGIhome:

#opatchautorollback<UNZIPPED_PATCH_LOCATION>/22243551oh<pathtoGIhome>

TorollbackthepatchfromtheOracleRACdatabasehome:

#opatchautorollback<UNZIPPED_PATCH_LOCATION>/22243551oh<oracle_home1_path>,<oracle_home2_path>

Formoreinformationaboutopatchauto,seeOracleOPatchUser'sGuide.

Fordetailedpatchinstallationinstructions,seeSection2.4,"PatchInstallation".

2.4PatchInstallation

Note:

EnsuretoreviewtheIssue2mentionedundertheSection3,"KnownIssues"beforeperformingthepatchinstallation.

InanExadataOVMdeployment,reviewIssue6inSection3,"KnownIssues"beforeperformingthepatchinstallation.

ThepatchinstructionswilldifferbasedontheconfigurationoftheGridinfrastructureandtheOracleRACdatabasehomes.PatchinginstructionsforOracleRACDatabase
HomesandGItogetherarelistedbelow.

Themostcommonconfigurationsarelistedasfollows:

Case1:GIHomeandtheDatabaseHomesthatarenotsharedandACFSfilesystemisnotconfigured.

Case2:GIHomeisnotshared,DatabaseHomeisshared,ACFSmaybeused.

Case3:NonOracleRACDatabasehomes.

Forotherconfigurationslistedbelow,seeMyOracleSupportDocument1591616.1:

GIHomeisnotshared,theDatabaseHomeisnotshared,ACFSmaybeused.

PatchingOracleRACDatabaseHomes.

PatchingGIHomealone.

PatchingOracleRestartHome.

PatchingasoftwareonlyGIHomeinstallationorbeforetheGIHomeisconfigured.

PatchingOracleRACDatabaseHomesandGITogether

Case1:GIHomeandtheDatabaseHomesthatarenotsharedandACFSfilesystemisnotconfigured.

Asrootuser,executethefollowingcommandoneachnodeofthecluster:

#<GI_HOME>/OPatch/opatchautoapply<UNZIPPED_PATCH_LOCATION>/22243551ocmrf<ocmresponsefile>

Case2:GIHomeisnotshared,DatabaseHomeisshared,ACFSmaybeused.

Patchinginstructions:

1.FromtheOracledatabasehome,makesuretostoptheOracleRACdatabasesrunningonallnodes.Asthedatabasehomeownerexecute:

$<ORACLE_HOME>/bin/srvctlstopdatabased<dbuniquename>

2.Onthe1stnode,unmounttheACFSfilesystems.SeeMyOracleSupportDocument1494652.1forunmountingACFSfilesystems.

3.Onthe1stnode,applythepatchtotheGIHomeusingtheopatchautocommand.Asrootuser,executethefollowingcommand:

#<GI_HOME>/OPatch/opatchautoapply<UNZIPPED_PATCH_LOCATION>/22243551oh<GI_HOME>ocmrf<ocmresponsefile>

4.Ifthemessage,"AsystemrebootisrecommendedbeforeusingACFSisshown,thenarebootmustbeissuedbeforecontinuing.Failuretodosowillresultin
runningwithanunpatchedACFS\ADVM\OKSdriver.

5.Onthe1stnode,remountACFSfilesystems.SeeMyOracleSupportDocument1494652.1formountingACFSfilesystems.

6.Onthe1stnode,applythepatchtotheDatabasehomeusingtheopatchautocommand.SincetheDatabasehomeisshared,thisoperationwillpatchthe
Databasehomeacrossthecluster.NotethataUSMonlypatchcannotbeappliedtoadatabasehome.Asrootuser,executethefollowingcommand:

#<GI_HOME>/OPatch/opatchautoapply<UNZIPPED_PATCH_LOCATION>/22243551oh<ORACLE_HOME>ocmrf<ocmresponsefile>

7.Onthe1stnodeonly,restarttheOracleinstance,whichyouhavepreviouslystoppedinStep1.Asthedatabasehomeownerexecute:

$<ORACLE_HOME>/bin/srvctlstartinstanced<dbuniquename>n<nodename>

8.Onthe2nd(next)node,unmounttheACFSfilesystems.SeeMyOracleSupportDocument1494652.1forunmountingACFSfilesystems.

9.Onthe2ndnode,applythepatchtoGIHomeusingtheopatchautocommand.Asrootuser,executethefollowingcommand:

#<GI_HOME>/OPatch/opatchautoapply<UNZIPPED_PATCH_LOCATION>/22243551oh<GI_HOME>ocmrf<ocmresponsefile>

10.Ifthemessage,"AsystemrebootisrecommendedbeforeusingACFSisshown,thenarebootmustbeissuedbeforecontinuing.Failuretodosowillresultin
runningwithanunpatchedACFS\ADVM\OKSdriver.

11.Onthe2ndnode,runningtheopatchautocommandinStep9willrestartthestack.

12.Onthe2ndnode,remountACFSfilesystems.SeeMyOracleSupportDocument1494652.1formountingACFSfilesystems.

13.Onthe2ndnodeonly,restarttheOracleinstance,whichyouhavepreviouslystoppedinStep1.Asthedatabasehomeownerexecute:

$<ORACLE_HOME>/bin/srvctlstartinstanced<dbuniquename>n<nodename>

14.RepeatSteps8through13forallremainingnodesofthecluster.

Case3:NonOracleRACDatabasehomes.

https://updates.oracle.com/Orion/Services/download?type=readme&aru=19644511 5/10
13/04/2016 OracleDatabasePatch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)
Followthesesteps:

1.IfyouareusingaDataGuardPhysicalStandbydatabase,youmustinstallthispatchonboththeprimarydatabaseandthephysicalstandbydatabase,as
describedbyMyOracleSupportDocument278641.1.

2.IfthisisaRACenvironment,installthePSUpatchusingtheOPatchrolling(nodowntime)installationmethodasthePSUpatchisrollingRACinstallable.Referto
MyOracleSupportDocument244241.1RollingPatchOPatchSupportforRAC.

3.IfthisisnotaRACenvironment,shutdownallinstancesandlistenersassociatedwiththeOraclehomethatyouareupdating.Formoreinformation,seeOracle
DatabaseAdministrator'sGuide.

4.SetyourcurrentdirectorytothedirectorywherethepatchislocatedandthenruntheOPatchutilitybyenteringthefollowingcommands:

cd<UNZIPPED_PATCH_LOCATION>/22243551/21949015
opatchapply

5.Ifthereareerrors,refertoSection3,"KnownIssues".

2.5InstallingDatabasePSUinStandbyFirstMode

ForDataGuardStandbyFirstpatching,seeMyOracleSupportDocument1265700.1.ForStandbyFirstpatchingforOracleDatabasePSU12.1andhigher,thefollowingpoints
needtobeconsidered:

1.TheDatabasesubpatch(21949015)mustbeappliedtotheDataGuardstandbyusingOpatch.

2.DatapatchmustnotbeinvokedontheDataGuardstandbyenvironmenttoapplypostpatchSQLactionsfortheDatabasePSU.Ifdatapatchisrunonastandby,itwill
errorwhiletryingtocalltheSYS.DBMS_QOPATCHinterface.Formoredetailsaboutthiserror,seeMyOracleSupportDocument1599479.1.

3.Datapatchmustbeinvokedontheprimarydatabaseafterallthedatabases,thatisprimaryandDataGuard,arepatchedandpatchdeploymentoftheDatabasePSUis
completeforthesetup.

2.6PatchPostInstallationInstructions

Afterinstallingthepatch,performthefollowingactions:

1.ApplyconflictresolutionpatchesasexplainedinSection2.6.1.

2.Ifyouarenotusingopatchauto,thenloadmodifiedSQLfilesintothedatabase,asexplainedinSection2.6.2.

3.UpgradetheOracleRecoveryManagerCataloginSection2.6.3

2.6.1ApplyingConflictResolutionPatches

ApplythepatchconflictresolutiononeoffpatchesthatweredeterminedtobeneededwhenyouperformedthestepsinSection2.2,"OneoffPatchConflictDetectionand
Resolution".

2.6.2LoadingModifiedSQLFilesintotheDatabase

ThefollowingstepsloadmodifiedSQLfilesintothedatabase.ForaRACenvironment,performthesestepsononlyonenode.

DatapatchisruntocompletethepostinstallSQLdeploymentforthePSU.ForfurtherdetailsaboutDatapatch,includingKnownIssuesandworkaroundstocommonproblems,
see:Database12cPostPatchSQLAutomation(DocID1585822.1).

1.ForeachseparatedatabaserunningonthesamesharedOraclehomebeingpatched,runthedatapatchutilityasdescribedinTable4.

Table4StepstoRuntheDatapatchUtilityforStandaloneDBVersusSingle/Multitenant(CDB/PDB)DB

Steps StandaloneDB Steps Single/Multitenant(CDB/PDB)DB

1 %sqlplus/nolog 1 %sqlplus/nolog

2 SQL>Connect/assysdba 2 SQL>Connect/assysdba

3 SQL>startup 3 SQL>startup

4 SQL>quit 4 SQL>alterpluggabledatabaseallopenFoot1

5 %cd$ORACLE_HOME/OPatch 5 SQL>quit

6 %./datapatchverbose 6 %cd$ORACLE_HOME/OPatch

7 %./datapatchverbose

Footnote1ItisrecommendedthePostInstallstepberunonallpluggabledatabaseshowever,thefollowingcommand(SQL>alterpluggabledatabase
PDB_NAMEopen)couldbesubstitutedtoonlyopencertainPDBsinthesingle/multitenantdatabase.DoingsowillresultinthePostInstallsteponlybeingrunonthe
CDBandopenedPDB's.Toupdateapluggabledatabaseatalaterdate(skippedornewlypluggedin),openthedatabaseusingthealterpluggabledatabase
commandmentionedpreviouslyandrerunthedatapatchutility.SeeMyOracleSupportDocument1935365.1MultitenantUnplug/PlugBestPracticesformoreinformation
abouttheprocedureforunplugging/pluggingwithdifferentpatchreleases(inbothdirections).

ThedatapatchutilitywillthenrunthenecessaryapplyscriptstoloadthemodifiedSQLfilesintothedatabase.Anentrywillbeaddedtothe
dba_registry_sqlpatchviewreflectingthepatchapplication.Inthedba_registry_sqlpatchview,verifytheStatusfortheAPPLYis"SUCCESS".Forany
otherstatus,refertothefollowingMyOracleSupportnoteforadditionalinformationandactions:Document1609718.1DatapatchKnownIssues.

2.Checkthefollowinglogfilesin$ORACLE_BASE/cfgtoollogs/sqlpatch/21949015/<uniquepatchID>forerrors:

21949015_apply_<databaseSID>_<CDBname>_<timestamp>.log

wheredatabaseSIDisthedatabaseSID,CDBnameisthenameofthemultitenantcontainerdatabase,andtimestampisoftheformYYYYMMMDD_HH_MM_SS.

https://updates.oracle.com/Orion/Services/download?type=readme&aru=19644511 6/10
13/04/2016 OracleDatabasePatch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)
3.IftheOJVMPSUisalsoinstalled,youmayseeinvalidobjectsafterexecutionofdatapatchinthepreviousstep.Ifthisisthecase,runutlrp.sqltorevalidatethese
objects.

cd$ORACLE_HOME/rdbms/admin
sqlplus/nolog
SQL>CONNECT/ASSYSDBA
SQL>@utlrp.sql

2.6.3UpgradeOracleRecoveryManagerCatalog

IfyouareusingtheOracleRecoveryManager,thecatalogneedstobeupgraded.Enterthefollowingcommandtoupgradeit:

$rmancatalogusername/password@alias
RMAN>UPGRADECATALOG
RMAN>UPGRADECATALOG

2.7PatchPostInstallationInstructionsforDatabasesCreatedorUpgradedafterInstallationofPatchintheOracleHome

YoumustexecutethestepsinSection2.6.2,"LoadingModifiedSQLFilesintotheDatabase"foranyneworupgradeddatabase.

2.8PatchDeinstallation

DatapatchisruntocompletethepostdeinstallSQLdeploymentfortheDatabasesubpatch.ForfurtherdetailsaboutDatapatch,includingKnownIssuesandworkaroundsto
commonproblems,see:Database12cPostPatchSQLAutomation(DocID1585822.1).

InaMultitenentenvironment,afterrollingbackDatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016),theseeddatabasePDB$SEEDmaybe
leftinamountedstate.SeeKnownIssue1fortheresolution.

ThepatchrollbackinstructionswilldifferbasedontheconfigurationoftheGridinfrastructureandtheOracleRACdatabasehomes.RollBackinstructionsforOracleRAC
DatabaseHomesandGIarelistedbelow.

Themostcommonconfigurationsarelistedasfollows:

Case1:GIHomeandtheDatabaseHomesthatarenotsharedandACFSfilesystemisnotconfigured.

Case2:GIHomeisnotshared,DatabaseHomeisshared,ACFSmaybeused.

Case3:NonOracleRACDatabasehomes.

Forotherconfigurationslistedbelow,seeMyOracleSupportDocument1591616.1:

GIHomeisnotshared,theDatabaseHomeisnotshared,ACFSmaybeused.

RollingbackfromOracleRACDatabaseHomes.

RollingbackfromGIHomealone.

RollingbackthepatchfromOracleRestartHome.

RollingbackthepatchfromasoftwareonlyGIHomeinstallationorbeforetheGIHomeisconfigured.

RollBacktheOracleRACDatabaseHomesandGITogether

Case1:GIHomeandDatabaseHomesthatarenotsharedandACFSfilesystemisnotconfigured.

Asrootuser,executethefollowingcommandoneachnodeofthecluster.

#<GI_HOME>/OPatch/opatchautorollback<UNZIPPED_PATCH_LOCATION>/22243551

Ifthemessage,"AsystemrebootisrecommendedbeforeusingACFS"isshown,thenarebootmustbeissuedbeforecontinuing.Failuretodosowillresultinrunning
withanunpatchedACFS\ADVM\OKSdriver.

Case2:GIHomeisnotshared,DatabaseHomeissharedandACFSmaybeused.

1.FromtheOracledatabasehome,makesuretostoptheOracleRACdatabasesrunningonallnodes.Asthedatabasehomeownerexecute:

$<ORACLE_HOME>/bin/srvctlstopdatabased<dbuniquename>

2.Onthe1stnode,unmounttheACFSfilesystems.SeeMyOracleSupportDocument1494652.1forunmountingACFSfilesystems.

3.Onthe1stnode,rollbackthepatchfromtheGIHomeusingtheopatchautocommand.Asrootuser,executethefollowingcommand:

#<GI_HOME>/OPatch/opatchautorollback<UNZIPPED_PATCH_LOCATION>/22243551oh<GI_HOME>

4.Ifthemessage,"AsystemrebootisrecommendedbeforeusingACFSisshown,thenarebootmustbeissuedbeforecontinuing.Failuretodosowillresultin
runningwithanunpatchedACFS\ADVM\OKSdriver.

5.Onthe1stnode,remountACFSfilesystems.SeeMyOracleSupportDocument1494652.1formountingACFSfilesystems.

6.Onthe1stnode,rollbackthepatchtotheDatabasehomeusingtheopatchautocommand.ThisoperationwillrollbackthepatchtotheDatabasehomeacross
theclustergiventhatitisasharedACFShome.NotethataUSMonlypatchcannotbeappliedtoaDatabasehome.Asrootuser,executethefollowing
command:

#<GI_HOME>/OPatch/opatchautorollback<UNZIPPED_PATCH_LOCATION>/22243551

7.Onthe1stnodeonly,restarttheOracleinstance,whichyouhavepreviouslystoppedinStep1.Asthedatabasehomeownerexecute:

$<ORACLE_HOME>/bin/srvctlstartinstanced<dbuniquename>n<nodename>

8.Onthe2nd(next)node,unmounttheACFSfilesystems.SeeMyOracleSupportDocument1494652.1forunmountingACFSfilesystems.

9.Onthe2ndnode,rollbackthepatchtoGIHomeusingtheopatchautocommand.Asrootuser,executethefollowingcommand:

#<GI_HOME>/OPatch/opatchautorollback<UNZIPPED_PATCH_LOCATION>/22243551

10.Ifthemessage,"AsystemrebootisrecommendedbeforeusingACFSisshown,thenarebootmustbeissuedbeforecontinuing.Failuretodosowillresultin
runningwithanunpatchedACFS\ADVM\OKSdriver.

11.Onthe2ndnode,runningtheopatchautocommandinStep9willrestartthestack.

12.Onthe2ndnode,remountACFSfilesystems.SeeMyOracleSupportDocument1494652.1formountingACFSfilesystems.

https://updates.oracle.com/Orion/Services/download?type=readme&aru=19644511 7/10
13/04/2016 OracleDatabasePatch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)
13.Onthe2ndnodeonly,restarttheOracleinstance,whichyouhavepreviouslystoppedinStep1.Asthedatabasehomeownerexecute:

$<ORACLE_HOME>/bin/srvctlstartinstanced<dbuniquename>n<nodename>

14.RepeatSteps8through13forallremainingnodesofthecluster.

Case3:NonOracleRACDatabasehomes.

Followthesesteps:

1.ShutdownallinstancesandlistenersassociatedwiththeOraclehomethatyouareupdating.Formoreinformation,seeOracleDatabaseAdministrator'sGuide.

2.RuntheOPatchutilityspecifyingtherollbackargumentasfollows.

opatchrollbackid21949015

3.Ifthereareerrors,refertoSection3,"KnownIssues".

2.9PatchPostDeinstallationInstructions

Afterdeinstallingthepatch,performthefollowingactions:

Section2.9.1,"RunthedatapatchUtility"

Section2.9.2,"UpgradeOracleRecoveryManagerCatalog"

2.9.1RunthedatapatchUtility

Performthefollowingsteps:

1.ForeachseparatedatabaserunningontheOraclehomebeingpatched,runthedatapatchutilityasdescribedinTable5.IfthisisOracleRAC,rundatapatchononly
oneinstance.

Table5StepstoRunthedatapatchUtilityforStandaloneDBVersusSingle/Multitenant(CDB/PDB)DB

Steps StandaloneDB Steps Single/Multitenant(CDB/PDB)DB

1 %sqlplus/nolog 1 %sqlplus/nolog

2 SQL>Connect/assysdba 2 SQL>Connect/assysdba

3 SQL>startup 3 SQL>startup

4 SQL>quit 4 SQL>alterpluggabledatabaseallopenFoot1

5 %cd$ORACLE_HOME/OPatch 5 SQL>quit

6 %./datapatchverbose 6 %cd$ORACLE_HOME/OPatch

7 %./datapatchverbose

Footnote1ItisrecommendedthePostInstallstepberunonallpluggabledatabaseshowever,thefollowingcommand(SQL>alterpluggabledatabase
PDB_NAMEopen)couldbesubstitutedtoonlyopencertainPDBsinthesingle/multitenantdatabase.DoingsowillresultinthePostInstallsteponlybeingrunonthe
CDBandopenedPDB's.Toupdateapluggabledatabaseatalaterdate(skippedornewlypluggedin),openthedatabaseusingthealterpluggabledatabase
commandmentionedpreviouslyandrerunthedatapatchutility.SeeMyOracleSupportDocument1935365.1MultitenantUnplug/PlugBestPracticesformoreinformation
abouttheprocedureforunplugging/pluggingwithdifferentpatchreleases(inbothdirections).

ThedatapatchutilitywillthenrunthenecessaryapplyscriptstoloadthemodifiedSQLfilesintothedatabase.Anentrywillbeaddedtothe
dba_registry_sqlpatchviewreflectingthepatchapplication.Inthedba_registry_sqlpatchview,verifytheStatusfortheAPPLYis"SUCCESS".Forany
otherstatus,refertothefollowingMyOracleSupportnoteforadditionalinformationandactions:Document1609718.1DatapatchKnownIssues.

2.Checkthefollowinglogfilesin$ORACLE_HOME/sqlpatch/21949015/forerrors:

21949015_rollback_<databaseSID>_<CDBname>_<timestamp>.log

wheredatabaseSIDisthedatabaseSID,CDBnameisthenameofthemultitenantcontainerdatabase,andtimestampisoftheformYYYYMMMDD_HH_MM_SS.

3.IftheOJVMPSUisalsoinstalled,youmayseeinvalidobjectsafterexecutionofdatapatchinthepreviousstep.Ifthisisthecase,runutlrp.sqltorevalidatethese
objects.

cd$ORACLE_HOME/rdbms/admin
sqlplus/nolog
SQL>CONNECT/ASSYSDBA
SQL>@utlrp.sql

2.9.2UpgradeOracleRecoveryManagerCatalog

IfyouareusingtheOracleRecoveryManager,thecatalogneedstobeupgraded.Enterthefollowingcommandtoupgradeit:

$rmancatalogusername/password@alias
RMAN>UPGRADECATALOG
RMAN>UPGRADECATALOG

3KnownIssues
ForissuesdocumentedafterthereleaseofthisDatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016),seeMyOracleSupportDocument
2076305.1DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)KnownIssues.

Issue1

https://updates.oracle.com/Orion/Services/download?type=readme&aru=19644511 8/10
13/04/2016 OracleDatabasePatch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)
ForallOpatchautoknownissues,seeMyOracleSupportMasterNoteforOPatch(DocumentID293369.1).Formoreinformationaboutopatchautoandknownissues
whilepatching,seeOracleOPatchUser'sGuideRelease12.1forWindowsandUNIX.

Issue2

Problem:

Duetobug20157569,customersupgradingfromthefollowingscenarios,willhitaconflictbetweentheOCWsubpatch19392604andtheDBsubpatch21949015:

121021DBBPto121023DBBP(andhigherDBBPversions)

121022DBBPto121023DBBP(andhigherDBBPversions)

Solution:

RollbacktheOCWsubpatch19392604beforeapplyingthe121023DBBP(orhigherDBBPversion)ontopofthe121021DBBPorontopofthe121022DBBP.

Youcaneitherrollbackthe121021DBBPor121022DBBPusingopatchautorollbackandthenapplythehigherDBBPversion,oryoucanfollowthemanual
instructionlistedinSection5,"ManualStepsforApply/RollbackPatch"torollbacktheOCWsubpatch19392604aloneoneachnodeoftheclusterandthenproceedwith
thehigherDBBPversioninstallationusingopatchauto.

SeeDocument2076305.1DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)KnownIssuesformoreinformation.

Issue3

Runningdatapatchmaycausethefollowingerror:CATCONINITFAILED,whenapplyingapatchinamultidatabaseenvironment.

Symptom:

Datapatchmayfailwiththefollowingerror:

/scratch/racusr/app/racusr/product/12.1.0/dbhome_1/OPatch/datapatch'
SQLPatchingtoolversion12.2.0.0.0onThuSep1111:34:222014
Copyright(c)2014,Oracle.Allrightsreserved.

Connectingtodatabase...OK
Note:DatapatchwillonlyapplyorrollbackSQLfixesforPDBs
thatareinanopenstate,nopatcheswillbeappliedtoclosedPDBs.
PleaserefertoNote:Datapatch:Database12cPostPatchSQLAutomation
(DocID1585822.1)
catcon:ALLcatconrelatedoutputwillbewrittento
/tmp/sqlpatch_catcon__catcon_22173.lst
catcon:See/tmp/sqlpatch_catcon_*.logfilesforoutputgeneratedbyscripts
catcon:See/tmp/sqlpatch_catcon__*.lstfilesforspoolfiles,ifany
start_processes:failedtoopenSTDOUT(1)

catconInitfailed,exiting

SeeMyOracleSupportDocument1609718.1forinformationonhowtoresolvethiserror.

Cause:

Bug19603117121021gipsu:hit"catconinitfailed"whenapplydbbpindifferentuserenv

Workaround:

ThisproblemhappensbecauseofmultipleOSusershavingownershipofmultipledatabasesintheenvironment.TheseOSusersdonothavewriteprivilegesoneach
other'sfilesandasaresult,datapatchfailswhiletryingtoopencatconlogfiles.Theworkaroundistodeletefilesunder:/tmp/sqlpatch_*andrerundatapatchfor
theaffecteddatabase.

Issue4

Symptom:IncreasingtheNPROClimitusingthefixforbug19680763isnoteffective.

Cause:BUG19680763INCREASEDEFAULTFORCRS_LIMIT_NPROCINS_CRSCONFIG_<NODENAME>_ENV.TXT

WorkaroundorFix:Itisnotsupportedtomodifythisfileduringpatchingsincetheusercanmodifythisfilewiththeirownsettingsandpatchingisnotexpectedto
overridethem.Oraclesuppliesdefaultsduringinstallandupgrade.

Issue5

RapidHomeProvisioning(RHP)imagesimportmayfail.

Symptom:RHPImportimagefailedinSolarisfor11204and11203version

Cause:Bug19609388RHPIMPORT11203/11204IMAGEFAILED

Fix:Applythepatchforbug19609388

Issue6

Problem:ExadataOVMdeploymentonlyduetobug21210985,OracleClusterwarefailstostartonthesecondnodeafterapplying12.1.0.2.10DBBP.

Solution:Applypatch21210985beforeinstalling12.1.0.2.10DBBP.

Issue7

ItispossibleforpriorversionsofdatapatchtonotfullyinstalltheSQLportionofthebundlepatchwhenruninamultinodeOracleRACenvironmentusingOpatchauto.
SeeMyOracleSupportDocument2069046.1DatapatchmayskiptheapplicationofSQLpayloadforcertainpatchesincludedinagivenbundleinaRACenvironment,
formoredetailsincludingavalidationSQLscripttocheckifthisissuehasoccurredonagivensystemandremediationsteps.Thisissueisfixedfromthisbundlepatch
versiononwards.

Issue8

OntheAIXplatform,youmaygetanerrorwhilerunningtheunzipcommand.

Symptom:Unzip:cannotfind<patch>.zip,<patch>.zip.zipor<patch>.zip.ZIP.

Cause:Youmaybeusinganolderunziputilitythatdoesnotsupportlargefiles.

Solution:UsethelatestunziputilityoronepresentunderORACLE_HOME/bin.

https://updates.oracle.com/Orion/Services/download?type=readme&aru=19644511 9/10
13/04/2016 OracleDatabasePatch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)
4References
Thefollowingdocumentsarereferencesforthispatch.

Document1591616.1PatchInstallationandDeinstallationfor12.1.0.1.xGIPSU

Document1494652.1InstructionsforMounting/UnmountingACFSFileSystems

Document1585822.1Database12cPostPatchSQLAutomation

Document360870.1ImpactofJavaSecurityVulnerabilitiesonOracleProducts

Document340978.1Genclntsh:CouldNotLocate$ORACLE_HOME/network/admin/shrept.lst

Document468959.1EnterpriseManagerGridControlKnownIssues

Document2076305.1DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)KnownIssues

OracleOPatchUser'sGuide

5ManualStepsforApply/RollbackPatch
SeeMyOracleSupportDocument1591616.1forcaseswhereopatchautocannotbeused.

6BugsFixedbyThisPatch
SeeMyOracleSupportDocument1937782.1

7DocumentationAccessibility
ForinformationaboutOracle'scommitmenttoaccessibility,visittheOracleAccessibilityProgramwebsiteathttp://www.oracle.com/us/corporate/accessibility/index.html.

AccesstoOracleSupport

OraclecustomershaveaccesstoelectronicsupportthroughMyOracleSupport.Forinformation,visithttp://www.oracle.com/support/contact.htmlorvisit
http://www.oracle.com/us/corporate/accessibility/support/index.htmlifyouarehearingimpaired.

Patch22243551DatabasePatchforEngineeredSystemsandDBInMemory12.1.0.2.160119(Jan2016)forUNIX

Copyright2006,2016,Oracleand/oritsaffiliates.Allrightsreserved.

Thissoftwareandrelateddocumentationareprovidedunderalicenseagreementcontainingrestrictionsonuseanddisclosureandareprotectedbyintellectualpropertylaws.
Exceptasexpresslypermittedinyourlicenseagreementorallowedbylaw,youmaynotuse,copy,reproduce,translate,broadcast,modify,license,transmit,distribute,exhibit,
perform,publish,ordisplayanypart,inanyform,orbyanymeans.Reverseengineering,disassembly,ordecompilationofthissoftware,unlessrequiredbylawfor
interoperability,isprohibited.

Theinformationcontainedhereinissubjecttochangewithoutnoticeandisnotwarrantedtobeerrorfree.Ifyoufindanyerrors,pleasereportthemtousinwriting.

IfthisissoftwareorrelateddocumentationthatisdeliveredtotheU.S.GovernmentoranyonelicensingitonbehalfoftheU.S.Government,thefollowingnoticeisapplicable:

U.S.GOVERNMENTRIGHTSPrograms,software,databases,andrelateddocumentationandtechnicaldatadeliveredtoU.S.Governmentcustomersare"commercial
computersoftware"or"commercialtechnicaldata"pursuanttotheapplicableFederalAcquisitionRegulationandagencyspecificsupplementalregulations.Assuch,theuse,
duplication,disclosure,modification,andadaptationshallbesubjecttotherestrictionsandlicensetermssetforthintheapplicableGovernmentcontract,and,totheextent
applicablebythetermsoftheGovernmentcontract,theadditionalrightssetforthinFAR52.22719,CommercialComputerSoftwareLicense(December2007).OracleAmerica,
Inc.,500OracleParkway,RedwoodCity,CA94065.

Thissoftwareorhardwareisdevelopedforgeneraluseinavarietyofinformationmanagementapplications.Itisnotdevelopedorintendedforuseinanyinherentlydangerous
applications,includingapplicationsthatmaycreateariskofpersonalinjury.Ifyouusethissoftwareorhardwareindangerousapplications,thenyoushallberesponsibletotake
allappropriatefailsafe,backup,redundancy,andothermeasurestoensureitssafeuse.OracleCorporationanditsaffiliatesdisclaimanyliabilityforanydamagescausedby
useofthissoftwareorhardwareindangerousapplications.

OracleandJavaareregisteredtrademarksofOracleand/oritsaffiliates.Othernamesmaybetrademarksoftheirrespectiveowners.

IntelandIntelXeonaretrademarksorregisteredtrademarksofIntelCorporation.AllSPARCtrademarksareusedunderlicenseandaretrademarksorregisteredtrademarksof
SPARCInternational,Inc.AMD,Opteron,theAMDlogo,andtheAMDOpteronlogoaretrademarksorregisteredtrademarksofAdvancedMicroDevices.UNIXisaregistered
trademarklicensedthroughX/OpenCompany,Ltd.

Thissoftwareorhardwareanddocumentationmayprovideaccesstoorinformationoncontent,products,andservicesfromthirdparties.OracleCorporationanditsaffiliatesare
notresponsibleforandexpresslydisclaimallwarrantiesofanykindwithrespecttothirdpartycontent,products,andservices.OracleCorporationanditsaffiliateswillnotbe
responsibleforanyloss,costs,ordamagesincurredduetoyouraccesstooruseofthirdpartycontent,products,orservices.

Copyright2006,2016,Oracleand/oritsaffiliates.Allrightsreserved.

https://updates.oracle.com/Orion/Services/download?type=readme&aru=19644511 10/10