What happend?
During the last month I updated manually the TFA Software.
I do this update while the TFA release installed via the Patchset is an older Version. This happens while Oracle Support adds the TFA release which is available while they create the Patchset.
Last weekend I start Patching GI Software 12.2 to RU Oct 2018 on a 4 Node Exadata Cluster
As best practice I do the installation manually and not via opatchauto.
First activity is:
/u01/app/12.2.0.1/grid/crs/install/rootcrs.sh -prepatch
This ends with the following error message:
2019/03/09 13:36:12 CLSRSC-46: Error: ‚/u01/app/12.2.0.1/grid/suptools/tfa/release/tfa_home/jlib/jdev-rt.jar‘ does not exist
2019/03/09 13:36:12 CLSRSC-152: Could not set ownership on ‚/u01/app/12.2.0.1/grid/suptools/tfa/release/tfa_home/jlib/jdev-rt.jar‘
Died at /u01/app/12.2.0.1/grid/crs/install/crsutils.pm line 7573.
The command ‚/u01/app/12.2.0.1/grid/perl/bin/perl -I/u01/app/12.2.0.1/grid/perl/lib -I/u01/app/12.2.0.1/grid/crs/install /u01/app/12.2.0.1/grid/crs/install/rootcrs.pl -prepatch‘ execution failed
The following Doc ID 2409411.1 describes how to fix this by modifying two files. I should be fixed in Grid Release 18.
$GRID_HOME/crs/sbs/crsconfig_fileperms.sbs
$GRID_HOME/crs/utl/<node>/crsconfig_fileperms
remove the following two entries.
unix %ORA_CRS_HOME%/suptools/tfa/release/tfa_home/jlib/jdev-rt.jar %HAS_USER% %ORA_DBA_GROUP% 0644
unix %ORA_CRS_HOME%/suptools/tfa/release/tfa_home/jlib/jewt4.jar %HAS_USER% %ORA_DBA_GROUP% 0644
I made the changes but it did not fix the problem. So I can’t go on with the Patching. For me it looks like a problem with the file permissions.
So next research on MOS and I found this important Doc ID 1931142.1:
„How to check and fix file permissions on Grid Infrastructure environment“
Yes, this was the solution :-)
cd /u01/app/12.2.0.1/grid/crs/install/
./rootcrs.sh -init
Using configuration parameter file: /u01/app/12.2.0.1/grid/crs/install/crsconfig_params
As an add on in the note you can check after the „-init“ the complete GI Installation with the following cluvfy command.
cluvfy comp software -n all -verbose
Verifying Software home: /u01/app/12.2.0.1/grid …2894 files verified
Verifying Software home: /u01/app/12.2.0.1/grid …PASSED
Verification of software was successful.
CVU operation performed: software
Date: Mar 11, 2019 10:10:11 AM
CVU home: /u01/app/12.2.0.1/grid/
User: oracle
This is very helpful. Finally I start the GI Patching without any problems
Lesson learned
„It is a good idea to check from time to time the status of the Software via cluvfy.“
