You are about to read the second part of this mini-series on TFA and Oracle 12.2. In the previous article I wrote about TFA and Oracle 12.2 single instance. In this short article I am going to have a look at TFA in a 12.2 Oracle Restart environment before rounding it up with an investigation into a full-blown RAC installation in part 3.
Summarising the first part I can only say that I am very happy that we now get TFA as part of the standard installation. Running it in daemon mode provides some great insights, and even if you did not upgrade the installation to “MOS-TFA”, you have a very fine tool for Oracle troubleshooting at your disposal.
Summary of the environment
My environment is largely the same as last time, except the machine name changed to server4 and I have additional storage for use with ASM.
- It’s still Oracle Linux 7.4 with UEK4
- Oracle 184.108.40.206.0 Grid Infrastructure was installed first
- Followed by an installation of the Oracle 220.127.116.11.0 RDBMS EE software
- After having created a database in ASM I applied the January 2018 GI RU
- Finally I upgraded TFA to the current version (as downloaded from My Oracle Support DOC ID 1513912.1)
Not all of these steps are relevant for this article though.
Now where would you find TFA?
The question I had when creating this environment was essentially this: where would I find TFA? Would it be part of the Grid Home, or rather the RDBMS installation?
After having installed the binaries for Grid Infrastructure, I didn’t find a reference to roottfa.sh in the Grid Home’s root.sh script.
[oracle@server4 ~]$ cat /u01/app/oracle/product/18.104.22.168/grid/root.sh #!/bin/sh unset WAS_ROOTMACRO_CALL_MADE . /u01/app/oracle/product/22.214.171.124/grid/install/utl/rootmacro.sh "$@" . /u01/app/oracle/product/126.96.36.199/grid/install/utl/rootinstall.sh # # Root Actions related to network # /u01/app/oracle/product/188.8.131.52/grid/network/install/sqlnet/setowner.sh # # Invoke standalone rootadd_rdbms.sh # /u01/app/oracle/product/184.108.40.206/grid/rdbms/install/rootadd_rdbms.sh /u01/app/oracle/product/220.127.116.11/grid/rdbms/install/rootadd_filemap.sh /u01/app/oracle/product/18.104.22.168/grid/crs/config/rootconfig.sh $@ EXITCODE=$? if [ $EXITCODE -ne 0 ]; then exit $EXITCODE fi [oracle@server4 ~]$
I checked whether TFA has been configured in a different place, but there wasn’t any TFA-related process running nor was there a systemd unit file with *tfa* in its name. So it looks like you don’t get the option to install TFA automatically as part of the Grid Infrastructure installation.
Not finding TFA configured to run out of Grid Infrastructure surprised me, especially since Oracle states in the Autonomous Health Framework documentation chapter 4.2.2 that TFA is automatically configured as part of the GI configuration, upon invoking root.sh or rootupgrade.sh. According to my testing, this is true for RAC, but not Oracle Restart.
Which kind-of makes sense if you consider that most users will install the database software anyway in an Oracle Restart setup.
It doesn’t really matter, read on ;)
Installing the RDBMS software
If TFA isn’t configured automatically with Grid Infrastructure in an Oracle Restart configuration it should come as no surprise that TFA is once more installed and configured from the RDBMS home. Just as with the single instance installation I wrote about previously, you find a reference to roottfa.sh in the RDBMS home’s root.sh:
[oracle@server4 tfa]$ cat /u01/app/oracle/product/22.214.171.124/dbhome_1/root.sh #!/bin/sh unset WAS_ROOTMACRO_CALL_MADE . /u01/app/oracle/product/126.96.36.199/dbhome_1/install/utl/rootmacro.sh "$@" . /u01/app/oracle/product/188.8.131.52/dbhome_1/install/utl/rootinstall.sh /u01/app/oracle/product/184.108.40.206/dbhome_1/suptools/tfa/release/tfa_home/install/roottfa.sh /u01/app/oracle/product/220.127.116.11/dbhome_1/install/root_schagent.sh # # Root Actions related to network # /u01/app/oracle/product/18.104.22.168/dbhome_1/network/install/sqlnet/setowner.sh # # Invoke standalone rootadd_rdbms.sh # /u01/app/oracle/product/22.214.171.124/dbhome_1/rdbms/install/rootadd_rdbms.sh /u01/app/oracle/product/126.96.36.199/dbhome_1/rdbms/install/rootadd_filemap.sh [oracle@server4 tfa]$
The procedure appears to be almost exactly the same as with single instance Oracle. I have again opted to use TFA in daemon mode, just as I did before in my post about Oracle single instance.
TFA thankfully discovers and adds both RDBMS as well as Grid Infrastructure directories (and quite a few Linux related directories, too!). You can see for yourself when running tfactl print directories.
As the final step you might want to consider upgrading TFA to the MOS version. That’s it-happy troubleshooting!