# #------------------------------------------------------------------------- # BUNDLE Patch for Base Bug 26925644 #------------------------------------------------------------------------- # # DATE: 6:35:58 Oct 5 2017 # ------------------------------- # Platform Patch for : Linux x86-64 (226) # Product Version # : 12.2.0.1.0 # Product Patched : CRS/RDBMS # #------------------------------------------------------------------------- # # WARNING: Failure to carefully read and understand these requirements may # result in your applying a patch that can cause your Oracle Server to # malfunction, including interruption of service and/or loss of data. # # If you do not meet all of the following requirements, please log an # iTAR, so that an Oracle Support Analyst may review your situation. The # Oracle analyst will help you determine if this patch is suitable for you # to apply to your system. We recommend that you avoid applying any # temporary patch unless directed by an Oracle Support Analyst who has # reviewed your system and determined that it is applicable. # # Requirements: # # - You must have located this patch via a Bug Database entry # and have the exact symptoms described in the bug entry. # # - Your system configuration (Oracle Server version and patch # level, OS Version) must exactly match those in the bug # database entry - You must have NO OTHER PATCHES installed on # your Oracle Server since the latest patch set (or base release # x.y.z if you have no patch sets installed). # # Refer to the following link for details on Perl and OPatch: # http://metalink.oracle.com/metalink/plsql/ # ml2_documents.showDocument?p_database_id=NOT&p_id=189489.1 # # If you do NOT meet these requirements, or are not certain that you meet # these requirements, please log an iTAR requesting assistance with this # patch and Support will make a determination about whether you should # apply this patch. # # Bugs fixed by this bundle # ========================= # # CRS HOME # ======== # #26144044 12.2.0.1.170620DBBP INSTALLATION FAILED, PATCHES HAVE CONFLICTS #25541343 RHP DID NOT RELOCATE RAC ONE DATABASE DURING PATCHING #25715179 RHPCTL MOVE GIHOME FAIL WITH PRGO-1373 #25493588 LNX64-12C-UD:CVU-PRECHECK COMPLAINED PRVG-12938 WHEN CHECKING ASM PARAMETER #24932026 CRSCTL START RESOURCE IS FAILING IN SOME AGENT LRGS #24801915 GPNP LOG FILES ARE FLOODING ON ODA SYSTEM AFTER UPGRADING TO 12.1.2.8.0 #25832375 RHPCTL IMPORT IMAGE FAILS WITH HASCONTEXT INTERNAL ERROR #25728787 SRVCTL CONFIG MGMTDB IS REPORTING WRONG STATE ON MEMBER CLUSTER #25825732 RHPCTL ADD WORKINGCOPY FAILED WITH OPATCH ERROR CODE 15 #24578464 CRS : MASTER NODE CRSD LEAK IN OCRSCRUBTIMERHANDLER #25832312 LNX64-12.2-CHM-FCF: NODE IS STILL EVICTED WHEN ONLY DELAY PRIVATE NIC 18S #25742471 'RHP MOVE DB' DID NOT MERGE ALL TNS*ORA FILES IN DB HOME #25790699 WHILE IMPORT OF AN IMAGE WHICH IS PRESENT IN A REMOTE NODE USING SUDO IT IS FAIL #25655495 LNX64-12.2-CHA: FAIL TO MONITOR ONE DB INST DUE TO PROJECT STORE WRITE TIMEOUT #25307145 FLEX: SEVERE: CLSCH-1004 : OCHAD ABORTED MONITORING OF HOST #25485737 WORKINGCOPY OSOPER GROUP BECOMES NULL IF NOT SPECIFIED DURING ADD WORKINGCOPY #25505841 MOVE DATABASE SHOULD FAIL IF DATAPATCH FAILS #25697364 RHPCTL UPGRADE DATABASE FAIL WITH PRGO-1716:THE SITE VERSION 11.2.0.4.0 IS LOWER #24663993 LNX64-12.2-GH:AFTER 11204GI PATCHING, INVENTORY.XML HAVE NOT BEEN UPDATED #25026470 LNX64-12.2-GH:REMOTE IMPORT DB IMAGE FROM 12.2 RHP CLIENT FAILS #25591658 FIX FOR BUG 25591658 #25537905 DB STARTUP ISSUES AFTER SUCCESSFUL GI UPGRADE PRCD-1027 PRCD-1035 #24451580 SERVICE RESOURE BECOMES UNKNOWN WHEN DATABASE BECOMES STUCK ARCHIVE #25409838 DBCA FAILS ON SCAN VIP CHECK IN IPV6 ENVIRONMENT #25371632 CLUVFY PICKS WRONG LIMITS.CONF FILE #25569634 CHCLDX0142 : GI UPGRADE FIALUE DUE TO LISTENER CRASH ISSUE #25245759 LNX64-12.2-CHM: TWO OLOGGERD PROCESSES RUNNING AFTER MGMTDB SWITCHED #24665035 CLSRSC-180: AN ERROR OCCURRED WHILE EXECUTING THE COMMAND 'SRVCTL CONFIG ASM' #25646592 CRSCTL STAT RESOURCE IS FAILED - FIXED BY RTI 20128761 #25025157 AIX-12.2-UD:DROPPING GIMR FAILED,UD 12101 TO 122 #24732650 GAPS IN OCLUMON OUTPUT, 10 TO 20SEC ON AIX RUNNING LOW LOAD #24664849 HPI_122_UP:CRSD ORAAGENT CORE DUMPED WHEN RUNNING ROOTUPGRADE.SH ON 4TH NODE #24584419 12.2AIX:CREATION OF MANIFEST FILE FAILS WHEN USING MEMBER_TYPE AS APPLICATION #24423011 HPI-122:MESSAGE ERROR WHEN GETTING NODE ROLE #24831158 GIPCD TO REDUCE THE IB SM QUERY AND ENABLE THE TRACE LOG CALLBACK #25037836 EXAPASS: ISHAINSTALLED API BROKEN WITH 12.2 GRID AND 11204 DB #25556203 ROOTUPGRADE.SH DOING ALTER DISKGROUP DGNAME CHECK NOREPAIR TAKES AGES #24464953 OCR MUST REGISTER CRS_VERSION GROUP WITH NO_NOTIFY FLAG TO AVOID NOTIFICATIONS #24657753 LNX64-12.2-CRS:STARTING SERVICES IN PARALLEL,SOME OF THE SERVICES START FAILED #25197670 LNX64-12.1-UD:AGENT CORE DUMP FILE GENERATED DURING THE UPGRADE #24796183 THE NODE DOESN'T GET CRASHED BY KILLING OCSSD AFTER CRASHDUMP ENABLED #20559126 NODE1 CANNOT JOIN CLUSTER BECAUSE OF ADDRESS ALREADY IN USE (98) ON CSSD #25197395 LNX64-12.1-UD:UPGRADE HANG AT 'CRSCTL STARTUPGRADE' #24808260 TRACKING INT DIF IN SRGDBCONF: BLOWOUT.DIF PCWSTART FAILED. EVMD FAILED #26546632 FIX FOR BUG 26546632 #24792446 CLSNCRSAGENT.CPP COMPILE ERROR FOR HAS_MAIN_AIX.PPC64 #25774482 UPDATE WLM CONFIGURATION TO RUN ON TOMCAT 8.0.43 #26529142 LNX64-12.2-GH: INVENTORY NOT GETTING UPDATED AFTER DELETING S W ONLY GI WC #26379711 RHP SERVER FAILS TO MOVE GI HOME ON REMOTE 12.2 CLIENT #26248428 'QUERY IMAGE' NOT SHOWING PATCH INFO. WHEN GI IMAGE WAS CREATED WITH 'ADD IMAGE' #25865563 RHPCTL ADD WORKINGCOPY FAILS WITH PRCT-1014 #25408895 RHP: BEFORE SWITCH DB GI HOME FROM AN UNMANAGED HOME, CHECK FOR CONFLICTS #25667162 FLEX: OSYSMOND COREDUMP AT GIPCMODPACKETCREATE #26301456 LNX64-12.2-GH: 12201 TO 12202 GI UPGRADE FAILS WITH PRKC-1137 #26238801 LNX64-121-CMT: CVU CHECK HIT WARNING THAT THE THP IS ENABLED #25801922 PROGRESS MESSAGES NOT DISPLAYED ON RHP SERVER WHEN TARGETS HAVE NO CONNECT BACK #25216003 LNX64-12.2-GH:PATCH 21626377 NOT REQUIRE W CORRECT COMPATIBLE.ASM IN CMP ENV #25825755 12.2.0.1 OUI PREREQ CHECK FAILS WHEN ASM OF NFS IS CHOSEN ALONG WITH NFS V4 #25233797 LNX64-12.2-GIPC: GIPCD OFTEN CONSUMES HIGH CPU( =25%) #25164540 THE NODE DOESN'T GET CRASHED AFTER KILLING OCSSD ON GI VCS VENDOR CLUSTER #25049033 RDS IB communication causes node eviction #24824518 FAILED UPGRADE DUE TO FAILURE TO IMPORT OCR FROM EXPORT FILE #24509984 ORACLE RESTART: PRCR-1097 : RESOURCE ATTRIBUTE NOT FOUND: PWFILE #24462646 AFTER UPG GI FROM 11.2, AGENT NOT SET REMOTE_REGISTRATION_ADDRESS TO SCAN LSNR #24422155 LNX64-12.2-CRS: MEMORY USAGE OF EVMD.BIN INCREASED ABOUT 40M BOUNCING DATABASE #23762756 CLUSTERWARE DOESN'T ALWAYS RESTART A DB INSTANCE WHEN WE KILL -9 PMON #25851874 SCLS_IDDB_IS_A_PRIVGRP_MEMBER_BY_ID UNLOCKS AN UNLOCKED MUTEX G_MUTEX #25518447 12.2 GI UPGRADE FAILS WHEN THERE ARE ACFS REPLICATION RESOURCES BEFORE UPGRADE #24953946 AIX-12.2-UD:FAILED TO PERFORM ACFS REGISTRY UPGRADE FROM 11203 TO 12201 #13250991 NEED DYNAMIC GIPC TRACING #22999793 ORA-07445 [__STRSTR_SSE42()+10] - SIMILAR TO BUG 17230892 THAT CT IS HITTING #24670214 ALTER SYSTEM REGISTER IS EXECUTED BY AGENT EVERY MINUTE ON SIHA #24583356 ORAROOTAGENT CHANGES FOR 22234338 AND 23232923 #22986384 THREADS 7, 8, AND 13 OF OCSSD.BIN ARE USING LARGE AMOUNT OF CPU #25784424 PRVG-0802 : STORAGE TYPE FOR PATH COULD NOT BE DETERMINED ON NODE #25301463 ROOTCRS.SH DOWNGRADE: MISSING OR INVALID VERSION NUMBER #25448476 ROOTUPGRADE.SH: CLSRSC-537: THE ROOT SCRIPT FAILED TO COPY THE OCR BACKUP FILE F #24403376 LNX64-12.2-GH:UPGRADE 11204- 122 CVU PRECHECK HIT PRVG-12945&PRVG-4568 #23722215 LNX64-12.2-RAC:CLUUTIL FAILS WHEN ORACLE BASE IS SHARED #23340259 OCR_PERF: MAKE OCR LOCKS MORE GRANULAR TO ACHEIVE FASTER RESPONSES #25564644 GI 12.2: FAIL TO DOWNGRADE THE THIRD NODE TO 12.1 DUE TO ORA.CSSDMONITOR FAILED #26198627 CRSCTL REPLACE VOTEDISK FAILS WITH CRS-8503 [MEMCPY()+347] [SIGNAL EXCEPTION: 11 #25785073 OCCSD HUNG WHILE DIAGSNAP TAKING PSTACK - CAUSES NODE REBOOT #24445255 LNX64-12.2-CHM: DIAGSNAP.PL LEFT RUNNING FOR A FEW MINUTES AFTER GI STACK STOP #26088770 PROVISIONING WITH CREDNAME OPTION IS NOT USING THE PROVIDED CREDENTIALS # # # RDBMS_HOME # ========== # # 13852018 DB12; NEED TEST PATCH FOR DB12 FROM SE FOR EVERY CANDIDATE DB LABEL # # # NOTE: A non-clustered RDBMs HOME runing the CSSD and ASM may also benefit # from a number of the CRS HOME patches. # # # Known Issues: # ============= # N/A # # Patch Installation Instructions: # -------------------------------- # Make sure all instances running under the ORACLE_HOME being patched # are cleanly shutdown before installing this patch. Also ensure that # the tool used to terminate the instance(s) has exited cleanly. # # Ensure that the directory containing the opatch script appears in # your $PATH. Execute "which opatch" to confirm. # # CRS_HOME = the full path to the crs home. # RDBMS_HOME = the full path to the server home. # # If the owner of these homes are different ensure you execute the # following steps as the correct owner in the correct environment. # # Configuration A: With a shared CRS Home, a full cluster outage must # be planned. The patch will update the shared copy of the binaries, # and no daemons can be online while the binaries are modified. # # Configuration B: When each node of the cluster has its own CRS Home, # the patch should be applied as a rolling upgrade. All of the following # steps should be followed for each node. Do not patch two nodes at once. # ########################################################################### # # 1. Verify that the Oracle Inventory is properly configured. # # % opatch lsinventory -detail -oh <CRS_HOME> # % opatch lsinventory -detail -oh <RDBMS_HOME> # # This should list the components the list of nodes. # # If the Oracle inventory is not setup correctly this utility will # fail. # # ########################################################################### # # 2. Unzip the PSE container file # # % unzip p26925644_12201_LINUX.X64.zip # ########################################################################### # # 3.1 In configuration A, shut down the CRS managed resources running from DB # home # on all nodes before shutting down the CRS daemons on # all nodes. Note that these steps must be run in the order specified. # # 3.1.1 Stop the CRS managed resources running from DB homes using # # % <RDBMS_HOME>/bin/srvctl stop home -o <RDBMS_HOME> -s <status file # location> -n <node_name># # note the status file is created by the process # # 3.2 In configuration B, shut down the CRS managed resources running from DB # home # followed by CRS daemons on the local node. # # 3.2.1 Stop the CRS managed resources running from DB homes using # # % <RDBMS_HOME>/bin/srvctl stop home -o <RDBMS_HOME> -s <status file # location> -n <node_name># # note the status file is created by the process # ########################################################################### # # 4. Prior to applying this part of the fix, you must invoke this script # as root to unlock protected files. # # # <CRS_HOME>/crs/install/rootcrs.pl -unlock # # Note: In configuration A, invoke this only on one node. # # ########################################################################### # # 5. Save the RDBMS home configuration settings # # ( Please review section 6.2 first ) As the RDBMS software owner; # % custom/server/26925644/custom/scripts/prepatch.sh -dbhome <RDBMS_HOME> # ########################################################################### # # 6. Patch the Files # # 6.1 Patch the CRS home files # # After unlocking any protected files and saving configuration settings # you are now ready to run opatch using the following command. # # As the Oracle Clusterware (CRS) software owner, # from the directory where the patch was unzipped; # # % opatch napply -local -oh <CRS_HOME> -id 26925644 # # Note: In configuration A, invoke this only on one node. # # # 6.2 Patch the RDBMS home files. # # Note: The RDBMS portion can only be applied to an RDBMS home that # has been upgraded to *11.2.0.1.0*. # # For additional information please read Note.363254.1; # Applying one-off Oracle Clusterware patches in a mixed version home # environment # # As the RDBMS software owner, # from the directory where the patch was unzipped; # # % opatch napply custom/server/ -local -oh <RDBMS_HOME> -id 26925644 # # Note: In configuration A, invoke this only on one node. # ########################################################################### # # 7. Configure the HOME # # 7.1 Configure the RDBMS HOME # # After opatch completes, some configuration settings need to be applied # to the patched files. As the RDBMS software owner execute the following; # # % custom/server/26925644/custom/scripts/postpatch.sh -dbhome <RDBMS_HOME> # # Note: In configuration A, invoke this only on one node. # ########################################################################### # # 8. Now security settings need to be restored on the CRS Home. This script # will also restart the CRS daemons. Invoke this script as root. # # # <CRS_HOME>/crs/install/rootcrs.pl -patch # # # <DB_HOME>/bin/srvctl start home -o <DB_HOME> -s <status file location> -n # <node name> # # Note: This script should only be invoked as part of the patch process. # # Note: In configuration A, invoke this on each node. Do not invoke this # in parallel on two nodes. ########################################################################### # # 9. On success you can determine whether the patch has been installed by # using the following command; # # % opatch lsinventory -detail -oh <CRS_HOME> # % opatch lsinventory -detail -oh <RDBMS_HOME> # ########################################################################### # # Additional Special Notes: # ------------------------- # If there are multiple Server Homes in your configuration, then # in step 5.2, 6.2, 7.1 run the commmands for each home before continuing. # # If you later install an additional Server home, or if you skip a # server home, then applying the patch to additional homes is easier. # 1. Shut down all instances using that Server home # 2. Apply the patch to that Server home as described in step 5.2, 6.2, 7.1 # 3. Restart the instances in that Server home # This can be done while CRS is active. # # ########################################################################### # # Special Instruction for AIX # --------------------------- # # During the application of this patch should you see any errors with regards # to files being locked or opatch being unable to copy files then this # # could be as result of a process which requires termination or an additional # # file needing to be unloaded from the system cache. # # # To try and identify the likely cause please execute the following commands # # and provide the output to your support representative, who will be able to # # identify the corrective steps. # # # genld -l | grep <CRS_HOME> # # genkld | grep <CRS_HOME> ( full or partial path will do ) # # # Simple Case Resolution: # # If genld returns data then a currently executing process has something open # in # the <CRS_HOME> directory, please terminate the process as # required/recommended. # # # If genkld return data then please remove the enteries from the # OS system cache by using the slibclean command as root; # # # slibclean # ########################################################################### # # Patch Deinstallation Instructions: # ---------------------------------- # # To roll back the patch, follow all of the above steps 1-5. In step 6, # invoke the following opatch commands to roll back the patch in all homes. # # % opatch rollback -id 26925644 -local -oh <CRS_HOME> # # % opatch rollback -id 26925644 -local -oh <RDBMS_HOME> # # Afterwards, continue with steps 7-9 to complete the procedure. # ########################################################################### # # If you have any problems installing this PSE or are not sure # about inventory setup please call Oracle support. # ###########################################################################