Opatch 11.2.0.3 gives error when the opatch version higher than Grid Infrastructure 11.2.0.2 || applying patch set updates on GI_HOME

Hello,

While working to autopatch newly installed Standalone grid infrastructure the below error appeared.

Error:

root@svprtldbdev1:/app/11.2.0/grid/patchsetupdate# opatch auto .
Executing /app/grid/perl/bin/perl /app/grid/OPatch/crs/patch11203.pl -patchdir . -patchn . -paramfile /app/grid/crs/install/crsconfig_params
Bareword "ValidateCRSCTL" not allowed while "strict subs" in use at /app/grid/crs/install/crspatch.pm line 101.
Bareword "ValidateCRSCTL" not allowed while "strict subs" in use at /app/grid/crs/install/crspatch.pm line 112.
Compilation failed in require at /app/grid/OPatch/crs/patch11203.pl line 415.
BEGIN failed--compilation aborted at /app/grid/OPatch/crs/patch11203.pl line 415.

Note:
I was applying patch set update for 11.2.0.2 database and the patch number is p17272753_112020_SOLARIS64.zip.

workaround:

·       Grid Infrastructure Home:

$GRID_HOME/OPatch/opatch auto <UNZIPPED_PATCH_LOCATION> -oh <<Grid Home>> -olderver

·      The database Home:

 Please run below without olderver clause:

$GRID_HOME/OPatch/opatch auto <UNZIPPED_PATCH_LOCATION> -oh <<RDBMS Home>

The finding was that sometimes the higher version Opatch may cause the above error with higher version grid infrastructure.

Regards

Mohamed

Single Client Access Name "SCAN" for Oracle Real application cluster 11g

I will discuss today a new feature that came up with Oracle 11g R 1.this new feature is known as single client access name(SCAN).prior to oracle 11g real application cluster the client connection will use each node virtual IP. When you add any new node or remove a node then the client tnsnames.ora needs to be updated with the new IP addition or removal.
Oracle 11G introduced the SCAN to handle this problem.The SCAN provide a single  name from clients  to access the database running in the cluster.
This is also very beneficial for client connecting using JDBC thin URLs and EZCONNECT to cluster with single hostname.

The components of the SCAN a cluster :
1-SCAN Name.
2-SCAN IP,Oracle recommends 3 IP addresses for SCAN for cluster.
3-SCAN Listener.

The SCAN Name is the cluster representative in the network .The SCAN Name has to be registered in the DNS and resolved using round-robin  algorithm.
To test the round-robin algorithm configuration just nslookup on the SCAN Name.The DNS server should return those 3 set of IP  addresses in different order each time.