For a newly created cluster, there are many Event ID 1257 cluster events shown on Failover Cluster Manager.
Cluster network name resource failed registration of one or more associated
DNS name(s) because the access to update the secure DNS zone was denied.
cluster Network name: 'Cluster Name'
DNS Zone: 'DNS Zone'
Ensure that cluster name object (CNO) is granted permissions to Secure
DNS Zone.
Subscribe to get access
Read more of this content when you subscribe today.
Run opatch command to check if enough free space is available in the Database Home:
[oracle@racnode1 ~]$ $ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_dbhome.txt
Oracle Interim Patch Installer version 12.2.0.1.18
Copyright (c) 2020, Oracle Corporation. All rights reserved.
PREREQ session
Oracle Home : /u01/app/oracle/product/12.2.0/dbhome_1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/12.2.0/dbhome_1/oraInst.loc
OPatch version : 12.2.0.1.18
OUI version : 12.2.0.1.4
Log file location : /u01/app/oracle/product/12.2.0/dbhome_1/cfgtoollogs/opatch/opatch2020-02-27_21-37-53PM_1.log
Invoking prereq "checksystemspace"
Prereq "checkSystemSpace" passed.
OPatch succeeded.
[oracle@racnode1 ~]$
4) Check for conflicts in both the 12.2.0.1 GI home and the 12.2.0.1 DB homes.
In case you are applying the patch, run this command:
[root@racnode1 ~]# /u01/app/12.2.0.1/grid/OPatch/opatchauto apply /media/sf_Software/12201-190115/28828733 -analyze
OPatchauto session is initiated at Thu Feb 27 21:41:27 2020
System initialization log file is /u01/app/12.2.0.1/grid/cfgtoollogs/opatchautodb/systemconfig2020-02-27_09-41-30PM.log.
Session log file is /u01/app/12.2.0.1/grid/cfgtoollogs/opatchauto/opatchauto2020-02-27_09-42-17PM.log
The id for this session is GKR6
Executing OPatch prereq operations to verify patch applicability on home /u01/app/12.2.0.1/grid
Executing OPatch prereq operations to verify patch applicability on home /u01/app/oracle/product/12.2.0/dbhome_1
Patch applicability verified successfully on home /u01/app/oracle/product/12.2.0/dbhome_1
Patch applicability verified successfully on home /u01/app/12.2.0.1/grid
Verifying SQL patch applicability on home /u01/app/oracle/product/12.2.0/dbhome_1
Following step failed during analysis:
/bin/sh -c 'cd /u01/app/oracle/product/12.2.0/dbhome_1; ORACLE_HOME=/u01/app/oracle/product/12.2.0/dbhome_1 ORACLE_SID=RACTESTB1 /u01/app/oracle/product/12.2.0/dbhome_1/OPatch/datapatch -prereq -verbose'
SQL patch applicability verified successfully on home /u01/app/oracle/product/12.2.0/dbhome_1
OPatchAuto successful.
--------------------------------Summary--------------------------------
Analysis for applying patches has completed successfully:
Host:racnode1
RAC Home:/u01/app/oracle/product/12.2.0/dbhome_1
Version:12.2.0.1.0
==Following patches were SKIPPED:
Patch: /media/sf_Software/12201-190115/28828733/28864846
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /media/sf_Software/12201-190115/28828733/26839277
Reason: This patch is not applicable to this specified target type - "rac_database"
Patch: /media/sf_Software/12201-190115/28828733/28566910
Reason: This patch is not applicable to this specified target type - "rac_database"
==Following patches were SUCCESSFULLY analyzed to be applied:
Patch: /media/sf_Software/12201-190115/28828733/28870605
Log: /u01/app/oracle/product/12.2.0/dbhome_1/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-27_21-42-30PM_1.log
Patch: /media/sf_Software/12201-190115/28828733/28822515
Log: /u01/app/oracle/product/12.2.0/dbhome_1/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-27_21-42-30PM_1.log
Host:racnode1
CRS Home:/u01/app/12.2.0.1/grid
Version:12.2.0.1.0
==Following patches were SUCCESSFULLY analyzed to be applied:
Patch: /media/sf_Software/12201-190115/28828733/28870605
Log: /u01/app/12.2.0.1/grid/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-27_21-42-30PM_1.log
Patch: /media/sf_Software/12201-190115/28828733/28864846
Log: /u01/app/12.2.0.1/grid/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-27_21-42-30PM_1.log
Patch: /media/sf_Software/12201-190115/28828733/26839277
Log: /u01/app/12.2.0.1/grid/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-27_21-42-30PM_1.log
Patch: /media/sf_Software/12201-190115/28828733/28566910
Log: /u01/app/12.2.0.1/grid/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-27_21-42-30PM_1.log
Patch: /media/sf_Software/12201-190115/28828733/28822515
Log: /u01/app/12.2.0.1/grid/cfgtoollogs/opatchauto/core/opatch/opatch2020-02-27_21-42-30PM_1.log
Following homes are skipped during patching as patches are not applicable:
/u01/app/oracle/product/12.1.0/dbhome_1
OPatchauto session completed at Thu Feb 27 21:42:41 2020
Time taken to complete the session 1 minute, 14 seconds
[root@racnode1 ~]#
In case you are rolling back the patch, run this command:
One of the two RAC nodes failed to startup CRS with following messages in alert log:
2020-02-27 20:17:50.802 [OCSSD(14861)]CRS-1714: Unable to discover
any voting files, retrying discovery in 15 seconds; Details at
(:CSSNM00070:)in /u01/app/grid/diag/crs/racnode1/crs/trace/ocssd.trc
ocssd.trc:
2020-02-27 20:17:50.801 : CSSD:3324163840: clssnmReadDiscoveryProfile: voting file discovery string(/dev/oracleasm/disks)
2020-02-27 20:17:50.801 : CSSD:3324163840: clssnmvDDiscThread: using discovery string /dev/oracleasm/disks for initial discovery
2020-02-27 20:17:50.801 : SKGFD:3324163840: Discovery with str:/dev/oracleasm/disks:
2020-02-27 20:17:50.801 : SKGFD:3324163840: UFS discovery with :/dev/oracleasm/disks:
2020-02-27 20:17:50.801 : SKGFD:3324163840: Execute glob on the string /dev/oracleasm/disks
2020-02-27 20:17:50.801 : SKGFD:3324163840: OSS discovery with :/dev/oracleasm/disks:
2020-02-27 20:17:50.802 : SKGFD:3324163840: Discovery skipping bad asmlib :ASM::
2020-02-27 20:17:50.802 : CSSD:3324163840: clssnmvDiskVerify: Successful discovery of 0 disks
2020-02-27 20:17:50.802 : CSSD:3324163840: clssnmCompleteInitVFDiscovery: Completing initial voting file discovery
2020-02-27 20:17:50.802 : CSSD:3324163840: clssnmvFindInitialConfigs: No voting files found
2020-02-27 20:17:50.802 : CSSD:3324163840: (:CSSNM00070:)clssnmCompleteInitVFDiscovery: Voting file not found. Retrying discovery in 15 seconds
2020-02-27 20:17:51.687 : CSSD:3558553344: clsssc_CLSFAInit_CB: System not ready for CLSFA initialization
2020-02-27 20:17:52.687 : CSSD:3558553344: clsssc_CLSFAInit_CB: System not ready for CLSFA initialization
2020-02-27 20:17:53.687 : CSSD:3558553344: clsssc_CLSFAInit_CB: System not ready for CLSFA initialization
2020-02-27 20:17:54.687 : CSSD:3558553344: clsssc_CLSFAInit_CB: System not ready for CLSFA initialization
2020-02-27 20:17:55.688 : CSSD:3558553344: clsssc_CLSFAInit_CB: System not ready for CLSFA initialization
2020-02-27 20:17:56.688 : CSSD:3558553344: clsssc_CLSFAInit_CB: System not ready for CLSFA initialization
2020-02-27 20:17:57.688 : CSSD:3558553344: clsssc_CLSFAInit_CB: System not ready for CLSFA initialization
Subscribe to get access
Read more of this content when you subscribe today.
From release 12.2.0.1, “Release Update” ( RU) and ” Release Update Revision” ( RUR) are released, which replace the legacy PSUs and Proactive Bundle ( PB ) Patches.
From release 18 onwards, the terms ‘Update‘ and ‘Revision‘ are used instead of “Release Update” ( RU ) and ” Release Update Revision”( RUR ) in 12.2.0.1.
Oracle release pattern of Updates and Releases
Oracle release pattern of Updates and Releases
Updates and Revisions Patching Path
Updates and Revisions Patching Path
The patching path is either :
Vertically upward
Progressive diagonal
Progressive straight.
From an Update, the patching direction should be to either its 2 Revisions, released in consecutive quarters, OR the next quarter’s Update. There is no moving backward or vertical down.
If database is at Update 18.3.0 at the moment, the possible patching path could be :
Update 18.3.0 -> Revisions 18.3.1 , 18.3.2, 18.4.1 and so on
or
Update 18.3.0 -> Updates 18.4.0 , 18.5.0 and so on
Below patching path is NOT supported, because backward patching is non-cumulative. There is no moving back to earlier Release’s Updates and Revisions.
Update 18.3.0 -> Revisions 18.2.1 or 18.2.2 OR to Update 18.2.0
If database is at Revision 18.2.2 at the moment, the possible patching path could be :
Revision 18.2.2 -> Revisions 18.3.1 , 18.3.2, 18.4.1 and so on
or
Revision 18.2.2 -> Updates 18.4.0 , 18.5.0 and so on.
Below patching path is NOT supported, Because Update 18.3.0 is non-cumulative to 18.2.2.
Revision 18.2.2 -> Revision 18.2.1 or to Update 18.3.0