{"id":641,"date":"2019-11-24T20:01:07","date_gmt":"2019-11-24T23:01:07","guid":{"rendered":"http:\/\/www.fernandosimon.com\/blog\/?p=641"},"modified":"2020-07-19T19:15:01","modified_gmt":"2020-07-19T22:15:01","slug":"tfa-error-after-gi-upgrade-to-19c","status":"publish","type":"post","link":"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/","title":{"rendered":"TFA error after GI upgrade to 19c"},"content":{"rendered":"<p style=\"text-align: justify;\">Recently I made an Exadata stack upgrade\/update to the last 19.2 version (19.2.7.0.0.191012) and I upgraded the GI from 18c to 19c (last 19c version &#8211; 19.5.0.0.191015) and after that, TFA does not work.<\/p>\n<p style=\"text-align: justify;\">Since I don\u2019t want to complete execute a TFA clean and reinstallation I tried to find the error and the solution. Here I want to share with you the workaround (since there is no solution yet) that I discovered and used to fix the error.<\/p>\n<h2 style=\"text-align: justify;\">The environment<\/h2>\n<p style=\"text-align: justify;\">The actual environment is:<\/p>\n<ul style=\"text-align: justify;\">\n<li>Old Grid Infrastructure: Version 18.6.0.0.190416<\/li>\n<li>New Grid Infrastructure: Version 19.5.0.0.191015<\/li>\n<li>Exadata domU: Version 19.2.7.0.0.191012 running kernel 4.1.12-124.30.1.el7uek.x86_64<\/li>\n<\/ul>\n<h2 style=\"text-align: justify;\">TFA error<\/h2>\n<p style=\"text-align: justify;\">After upgrade the GI from 18c to 19c, the TFA does not work. If you try to start it or collect log using it, you can receive errors. In the environment described here, the TFA was running fine with the 18c version, and the <em>rootupgrade<\/em> script from 18c to 19c does not report an error.<\/p>\n<p style=\"text-align: justify;\">And to be more precise, the TFA upgrade from 18c to 19c called by <em>rootupgrade<\/em> was ok (according to the log \u2013 I will show later). But even after that, the error occurs.<\/p>\n<p style=\"text-align: justify;\">The provided solution as usual (by MOS support): download the lastest TFA and reinstall the actual one. Unfortunately, I not like this approach because can lead to an error during GI upgrade for next releases (like 20) and updates (19.6 as an example).<\/p>\n<p style=\"text-align: justify;\"><!--more Click here to read more...--><\/p>\n<p style=\"text-align: justify;\">So, when I tried to collect TFA:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite1c1 ~]# \/u01\/app\/19.0.0.0\/grid\/tfa\/bin\/tfactl diagcollect\r\nWARNING - TFA Software is older than 180 days. Please consider upgrading TFA to the latest version.\r\nTFA-00002 Oracle Trace File Analyzer (TFA) is not running\r\nPlease start TFA before running collections\r\n[root@exsite1c1 ~]#<\/pre>\n<p style=\"text-align: justify;\">So, when checking for running TFA I made <em>ps -ef<\/em> and not saw process running:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite1c1 ~]# ps -ef |grep tfa\r\nroot      10665      1  0 Nov21 ?        00:00:06 \/bin\/sh \/etc\/init.d\/init.tfa run &gt;\/dev\/null 2&gt;&amp;1 &lt;\/dev\/null\r\nroot      40285  37137  0 11:05 pts\/0    00:00:00 grep --color=auto tfa\r\n[root@exsite1c1 ~]#<\/pre>\n<p style=\"text-align: justify;\">And if I try to start TFA (as root), nothing report (error or OK):<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite1c1 ~]# \/etc\/init.d\/init.tfa start\r\nStarting TFA..\r\nWaiting up to 100 seconds for TFA to be started..\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n. . . . .\r\n[root@exsite1c1 ~]# \r\n[root@exsite1c1 ~]# ps -ef |grep tfa\r\nroot      10665      1  0 Nov21 ?        00:00:06 \/bin\/sh \/etc\/init.d\/init.tfa run &gt;\/dev\/null 2&gt;&amp;1 &lt;\/dev\/null\r\nroot      46031  37137  0 11:07 pts\/0    00:00:00 grep --color=auto tfa\r\n[root@exsite1c1 ~]#<\/pre>\n<p style=\"text-align: justify;\">Checking in the MOS I saw related problems with bad Perl version. For this TFA release is needed version 5.10 at lease. But was not the case:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite1c1 ~]# perl -v\r\n\r\nThis is perl 5, version 16, subversion 3 (v5.16.3) built for x86_64-linux-thread-multi\r\n(with 39 registered patches, see perl -V for more detail)\r\n\r\nCopyright 1987-2012, Larry Wall\r\n\r\nPerl may be copied only under the terms of either the Artistic License or the\r\nGNU General Public License, which may be found in the Perl 5 source kit.\r\n\r\nComplete documentation for Perl, including FAQ lists, should be found on\r\nthis system using \"man perl\" or \"perldoc perl\".  If you have access to the\r\nInternet, point your browser at http:\/\/www.perl.org\/, the Perl Home Page.\r\n\r\n[root@exsite1c1 ~]#<\/pre>\n<h2 style=\"text-align: justify;\">Searching the problem<\/h2>\n<p style=\"text-align: justify;\">Digging for the source of the problem I checked the <em>rootupgrade<\/em> but the report was good. The TFA upgrade completed with success:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite1c1 ~]# vi \/u01\/app\/grid\/crsdata\/exsite1c2\/crsconfig\/rootcrs_exsite1c2_2019-11-15_12-12-21AM.log\r\n...\r\n...\r\n2019-11-14 14:18:40: Executing the [UpgradeTFA] step with checkpoint [null] ...\r\n2019-11-14 14:18:40: Executing cmd: \/u01\/app\/19.0.0.0\/grid\/bin\/clsecho -p has -f clsrsc -m 595 '1' '18' 'UpgradeTFA'\r\n2019-11-14 14:18:40: Executing cmd: \/u01\/app\/19.0.0.0\/grid\/bin\/clsecho -p has -f clsrsc -m 595 '1' '18' 'UpgradeTFA'\r\n2019-11-14 14:18:40: Command output:\r\n&gt;  CLSRSC-595: Executing upgrade step 1 of 18: 'UpgradeTFA'.\r\n&gt;End Command output\r\n2019-11-14 14:18:40: CLSRSC-595: Executing upgrade step 1 of 18: 'UpgradeTFA'.\r\n2019-11-14 14:18:40: Executing cmd: \/u01\/app\/19.0.0.0\/grid\/bin\/clsecho -p has -f clsrsc -m 4015\r\n2019-11-14 14:18:40: Executing cmd: \/u01\/app\/19.0.0.0\/grid\/bin\/clsecho -p has -f clsrsc -m 4015\r\n2019-11-14 14:18:40: Command output:\r\n&gt;  CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.\r\n&gt;End Command output\r\n2019-11-14 14:18:40: CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.\r\n2019-11-14 14:18:40: Executing the [ValidateEnv] step with checkpoint [null] ...\r\n2019-11-14 14:18:40: Executing cmd: \/u01\/app\/19.0.0.0\/grid\/crs\/install\/tfa_setup -silent -crshome \/u01\/app\/19.0.0.0\/grid\r\n2019-11-14 14:18:40: Executing cmd: \/u01\/app\/19.0.0.0\/grid\/bin\/clsecho -p has -f clsrsc -m 595 '2' '18' 'ValidateEnv'\r\n2019-11-14 14:18:40: Executing cmd: \/u01\/app\/19.0.0.0\/grid\/bin\/clsecho -p has -f clsrsc -m 595 '2' '18' 'ValidateEnv'\r\n2019-11-14 14:18:40: Command output:\r\n&gt;  CLSRSC-595: Executing upgrade step 2 of 18: 'ValidateEnv'.\r\n...\r\n...\r\n2019-11-14 14:23:45: Command output:\r\n&gt;\r\n&gt;  TFA Installation Log will be written to File : \/tmp\/tfa_install_293046_2019_11_14-14_18_40.log\r\n...\r\n...\r\n2019-11-14 14:23:45: Command output:\r\n&gt;  CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.\r\n&gt;End Command output\r\n<\/pre>\n<p style=\"text-align: justify;\">And other related logs reported complete success:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite1c1 ~]# cat \/tmp\/tfa_install_293046_2019_11_14-14_18_40.log\r\n[2019-11-14 14:18:40] Log File written to : \/tmp\/tfa_install_293046_2019_11_14-14_18_40.log\r\n[2019-11-14 14:18:40]\r\n[2019-11-14 14:18:40] Starting TFA installation\r\n[2019-11-14 14:18:40]\r\n[2019-11-14 14:18:40] TFA Version: 192000 Build Date: 201904260414\r\n[2019-11-14 14:18:40]\r\n[2019-11-14 14:18:40] About to check previous TFA installations ...\r\n[2019-11-14 14:18:40] TFA HOME : \/u01\/app\/18.0.0\/grid\/tfa\/exsite1c1\/tfa_home\r\n[2019-11-14 14:18:40]\r\n[2019-11-14 14:18:40] Installed Build Version: 184100 Build Date: 201902260236\r\n[2019-11-14 14:18:40]\r\n[2019-11-14 14:18:40] INSTALL_TYPE GI\r\n[2019-11-14 14:18:40] Shutting down TFA for Migration...\r\n[2019-11-14 14:20:24]\r\n[2019-11-14 14:20:24] Removing \/etc\/init.d\/init.tfa...\r\n[2019-11-14 14:20:24]\r\n[2019-11-14 14:20:24] Migrating TFA to \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite1c1\/tfa_home...\r\n[2019-11-14 14:20:50]\r\n[2019-11-14 14:20:50] Starting TFA on exsite1c1...\r\n[2019-11-14 14:20:50]\r\n[2019-11-14 14:21:05]\r\n[2019-11-14 14:21:05] TFA_INSTALLER \/u01\/app\/19.0.0.0\/grid\/crs\/install\/tfa_setup\r\n[2019-11-14 14:21:05] TFA is already installed. Upgrading TFA\r\n[2019-11-14 14:21:05]\r\n[2019-11-14 14:21:05] TFA patching CRS or DB from zipfile extracted to \/tmp\/.293046.tfa\r\n[2019-11-14 14:21:06] TFA Upgrade Log : \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite1c1\/tfapatch.log\r\n[2019-11-14 14:23:31] Patch Status : 0\r\n[2019-11-14 14:23:31] Patching OK : Running install_ext\r\n[2019-11-14 14:23:32] Installing oratop extension..\r\n[2019-11-14 14:23:32]\r\n.-----------------------------------------------------------------.\r\n| Host      | TFA Version | TFA Build ID         | Upgrade Status |\r\n+-----------+-------------+----------------------+----------------+\r\n| exsite1c1 |  19.2.0.0.0 | 19200020190426041420 | UPGRADED       |\r\n| exsite1c2 |  18.4.1.0.0 | 18410020190226023629 | NOT UPGRADED   |\r\n'-----------+-------------+----------------------+----------------'\r\n\r\n[2019-11-14 14:23:44] Removing Old TFA \/u01\/app\/18.0.0\/grid\/tfa\/exsite1c1\/tfa_home...\r\n[2019-11-14 14:23:45] Cleanup serializable files\r\n[2019-11-14 14:23:45]\r\n[root@exsite1c1 ~]#\r\n[root@exsite1c1 ~]# cat \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite1c1\/tfapatch.log\r\n\r\nTFA will be upgraded on Node exsite1c1:\r\n\r\n\r\nUpgrading TFA on exsite1c1 :\r\n\r\nStopping TFA Support Tools...\r\n\r\nShutting down TFA for Patching...\r\n\r\nShutting down TFA\r\n. . . . .\r\n. . .\r\nSuccessfully shutdown TFA..\r\n\r\nNo Berkeley DB upgrade required\r\n\r\nCopying TFA Certificates...\r\n\r\n\r\nStarting TFA in exsite1c1...\r\n\r\nStarting TFA..\r\nWaiting up to 100 seconds for TFA to be started..\r\n. . . . .\r\nSuccessfully started TFA Process..\r\n. . . . .\r\nTFA Started and listening for commands\r\n\r\nEnabling Access for Non-root Users on exsite1c1...\r\n\r\n[root@exsite1c1 ~]#<\/pre>\n<p style=\"text-align: justify;\">One know problem occurs when (for some reason) the nodes of the clusters lost the sync for TFA. I tried to do the sync, and this pointed one clue:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite1c1 ~]# \/u01\/app\/19.0.0.0\/grid\/tfa\/bin\/tfactl syncnodes\r\nWARNING - TFA Software is older than 180 days. Please consider upgrading TFA to the latest version.\r\n\r\n\/u01\/app\/19.0.0.0\/grid\/tfa\/exsite1c1\/tfa_home\/bin\/synctfanodes.sh: line 237: \/u01\/app\/18.0.0\/grid\/perl\/bin\/perl: No such file or directory\r\nTFA-00002 Oracle Trace File Analyzer (TFA) is not running\r\n\r\nCurrent Node List in TFA :\r\n1.\r\n\r\nUnable to determine Node List to be synced. Please update manually.\r\n\r\nDo you want to update this node list? [Y|N] [N]: ^C[root@exsite1c1 ~]#\r\n[root@exsite1c1 ~]#<\/pre>\n<p style=\"text-align: justify;\">As you can see, the <em>syncnodes.sh<\/em> made a reference for the old 18c GI home. And inside of the sync script, you can see the reference of that like 237 (my mark below) checked for PERL, and this came from the file<strong> tfa_setup.txt.<\/strong><\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\">[root@exsite1c1 ~]# vi \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite1c1\/tfa_home\/bin\/synctfanodes.sh\r\n...\r\n...\r\n        if [ `$GREP -c '^PERL=' $tfa_home\/tfa_setup.txt` -ge 1 ]    &lt;== TFA CHECK\r\n        then\r\n                PERL=`$GREP '^PERL=' $tfa_home\/tfa_setup.txt | $AWK -F\"=\" '{print $2}'`;\r\n        fi\r\n\r\n        if [ `$GREP -c '^CRS_HOME=' $tfa_home\/tfa_setup.txt` -ge 1 ]\r\n        then\r\n                CRS_HOME=`$GREP '^CRS_HOME=' $tfa_home\/tfa_setup.txt | $AWK -F\"=\" '{print $2}'`;\r\n        fi\r\n\r\n        if [ `$GREP -c '^RUN_MODE=' $tfa_home\/tfa_setup.txt` -ge 1 ]\r\n        then\r\n                RUN_MODE=`$GREP '^RUN_MODE=' $tfa_home\/tfa_setup.txt | $AWK -F\"=\" '{print $2}'`;\r\n        fi\r\nfi\r\n\r\nRUSER=`$RUID | $AWK '{print $1}' | $AWK -F\\( '{print $2}' | $AWK -F\\) '{print $1}'`;\r\n\r\nif [ $RUSER != $DAEMON_OWNER ]\r\nthen\r\n        $ECHO \"User '$RUSER' does not have permissions to run this script.\";\r\n        exit 1;\r\nfi\r\n\r\nSSH_USER=\"$DAEMON_OWNER\";\r\n\r\nHOSTNAME=`hostname | $CUT -d. -f1 | $PERL -ne 'print lc'`;    &lt;===== LINE 237\r\n...\r\n...<\/pre>\n<h3 style=\"text-align: justify;\">Checking tfa_setup.txt<\/h3>\n<p style=\"text-align: justify;\">Checking the file we can see the error:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite1c1 ~]# cat \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite1c1\/tfa_home\/tfa_setup.txt\r\nCRS_HOME=\/u01\/app\/18.0.0\/grid\r\nexsite1c1%CRS_INSTALLED=1\r\nNODE_NAMES=exsite1c1\r\nORACLE_BASE=\/u01\/app\/grid\r\nJAVA_HOME=\/u01\/app\/18.0.0\/grid\/jdk\/jre\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/OPatch\/crs\/log\r\nexsite1c1%CFGTOOLS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/cfgtoollogs\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/crf\/db\/exsite1c1\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/crs\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/cv\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/evm\/admin\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/evm\/admin\/logger\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/evm\/log\r\nexsite1c1%INSTALL%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/install\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/network\/log\r\nexsite1c1%DBWLM%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/oc4j\/j2ee\/home\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/opmn\/logs\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/racg\/log\r\nexsite1c1%ASM%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/rdbms\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/scheduler\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/12.1.0.2\/grid\/srvm\/log\r\nexsite1c1%ACFS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/acfs\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/core\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/crsconfig\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/crsdiag\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/cvu\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/evm\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/output\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/trace\r\nexsite1c1%INSTALL%DIAGDEST=\/u01\/app\/oraInventory\/ContentsXML\r\nexsite1c1%INSTALL%DIAGDEST=\/u01\/app\/oraInventory\/logs\r\nTRACE_LEVEL=1\r\nINSTALL_TYPE=GI\r\nPERL=\/u01\/app\/18.0.0\/grid\/perl\/bin\/perl\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_1||\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1||\r\nRDBMS_ORACLE_HOME=\/u01\/app\/12.2.0.1\/grid||\r\nTZ=Europe\/Luxembourg\r\nRDBMS_ORACLE_HOME=\/u01\/app\/18.0.0\/grid||\r\nlocalnode%ADRBASE=\/u01\/app\/grid\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/product\/18.0.0\/dbhome_1||\r\nlocalnode%ADRBASE=\/u01\/app\/oracle\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/product\/11.2.0.4\/financ||\r\nlocalnode%ADRBASE=\/u01\/app\/oracle\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/product\/12.1.0.2\/financ||\r\nlocalnode%ADRBASE=\/u01\/app\/oracle\r\nDAEMON_OWNER=root\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/agent\/13.2.0\/agent_13.2.0.0.0||\r\nRDBMS_ORACLE_HOME=\/u01\/app\/12.1.0.2\/grid||\r\nRDBMS_ORACLE_HOME=\/u01\/app\/19.0.0.0\/grid||\r\nlocalnode%ADRBASE=\/u01\/app\/grid\r\nCRS_ACTIVE_VERSION=\r\n[root@exsite1c1 ~]#<\/pre>\n<p style=\"text-align: justify;\">As you can see above, the CRS_HOME, JAVA_HOME, PERL, and ORACLE_HOME parameters are pointing to the old GI folder. <strong>As a workaround I edited the tfa_setup.txt in both nodes and fixed the GI folder from 18.0 to 19.0<\/strong>:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite1c1 ~]# vi \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite1c1\/tfa_home\/tfa_setup.txt\r\n[root@exsite1c1 ~]#\r\n[root@exsite1c1 ~]#\r\n[root@exsite1c1 ~]#\r\n[root@exsite1c1 ~]# cat \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite1c1\/tfa_home\/tfa_setup.txt\r\nCRS_HOME=\/u01\/app\/19.0.0.0\/grid\r\nexsite1c1%CRS_INSTALLED=1\r\nNODE_NAMES=exsite1c1\r\nORACLE_BASE=\/u01\/app\/grid\r\nJAVA_HOME=\/u01\/app\/19.0.0.0\/grid\/jdk\/jre\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/OPatch\/crs\/log\r\nexsite1c1%CFGTOOLS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/cfgtoollogs\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/crf\/db\/exsite1c1\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/crs\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/cv\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/evm\/admin\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/evm\/admin\/logger\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/evm\/log\r\nexsite1c1%INSTALL%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/install\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/network\/log\r\nexsite1c1%DBWLM%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/oc4j\/j2ee\/home\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/opmn\/logs\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/racg\/log\r\nexsite1c1%ASM%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/rdbms\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/scheduler\/log\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/19.0.0.0\/grid\/srvm\/log\r\nexsite1c1%ACFS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/acfs\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/core\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/crsconfig\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/crsdiag\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/cvu\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/evm\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/output\r\nexsite1c1%CRS%DIAGDEST=\/u01\/app\/grid\/crsdata\/exsite1c1\/trace\r\nexsite1c1%INSTALL%DIAGDEST=\/u01\/app\/oraInventory\/ContentsXML\r\nexsite1c1%INSTALL%DIAGDEST=\/u01\/app\/oraInventory\/logs\r\nTRACE_LEVEL=1\r\nINSTALL_TYPE=GI\r\nPERL=\/u01\/app\/19.0.0.0\/grid\/perl\/bin\/perl\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_1||\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1||\r\nTZ=Europe\/Luxembourg\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/product\/18.0.0\/dbhome_1||\r\nlocalnode%ADRBASE=\/u01\/app\/oracle\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/product\/11.2.0.4\/financ||\r\nlocalnode%ADRBASE=\/u01\/app\/oracle\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/product\/12.1.0.2\/financ||\r\nlocalnode%ADRBASE=\/u01\/app\/oracle\r\nDAEMON_OWNER=root\r\nRDBMS_ORACLE_HOME=\/u01\/app\/oracle\/agent\/13.2.0\/agent_13.2.0.0.0||\r\nRDBMS_ORACLE_HOME=\/u01\/app\/19.0.0.0\/grid||\r\nlocalnode%ADRBASE=\/u01\/app\/grid\r\nCRS_ACTIVE_VERSION=19.0.0.0\r\n[root@exsite1c1 ~]#<\/pre>\n<p style=\"text-align: justify;\">And after the edit was possible to start TAF correctly:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite1c1 ~]# \/etc\/init.d\/init.tfa start\r\nStarting TFA..\r\nWaiting up to 100 seconds for TFA to be started..\r\n. . . . .\r\nSuccessfully started TFA Process..\r\n. . . . .\r\nWARNING - TFA Software is older than 180 days. Please consider upgrading TFA to the latest version.\r\nTFA Started and listening for commands\r\n[root@exsite1c1 ~]#\r\n[root@exsite1c1 ~]#\r\n[root@exsite1c1 ~]# ps -ef |grep tfa\r\nroot     113905      1  0 11:31 ?        00:00:00 \/bin\/sh \/etc\/init.d\/init.tfa run &gt;\/dev\/null 2&gt;&amp;1 &lt;\/dev\/null\r\nroot     115917      1 99 11:31 ?        00:00:24 \/u01\/app\/19.0.0.0\/grid\/jdk\/jre\/bin\/java -server -Xms256m -Xmx512m -Djava.awt.headless=true -Ddisable.checkForUpdate=true -XX:ParallelGCThreads=5 oracle.rat.tfa.TFAMain \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite1c1\/tfa_home\r\nroot     117853  37137  0 11:31 pts\/0    00:00:00 grep --color=auto tfa\r\n[root@exsite1c1 ~]#<\/pre>\n<p style=\"text-align: justify;\">And execute the diagcollect:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite1c1 ~]# \/u01\/app\/19.0.0.0\/grid\/tfa\/bin\/tfactl diagcollect\r\nWARNING - TFA Software is older than 180 days. Please consider upgrading TFA to the latest version.\r\n\r\nBy default TFA will collect diagnostics for the last 12 hours. This can result in large collections\r\nFor more targeted collections enter the time of the incident, otherwise hit &lt;RETURN&gt; to collect for the last 12 hours\r\n[YYYY-MM-DD HH24:MI:SS,&lt;RETURN&gt;=Collect for last 12 hours] :\r\n\r\nCollecting data for the last 12 hours for all components...\r\nCollecting data for all nodes\r\n\r\nCollection Id : 20191122124148exsite1c1\r\n\r\nDetailed Logging at : \/u01\/app\/grid\/tfa\/repository\/collection_Fri_Nov_22_12_41_49_CET_2019_node_all\/diagcollect_20191122124148_exsite1c1.log\r\n2019\/11\/22 12:41:53 CET : NOTE : Any file or directory name containing the string .com will be renamed to replace .com with dotcom\r\n2019\/11\/22 12:41:53 CET : Collection Name : tfa_Fri_Nov_22_12_41_49_CET_2019.zip\r\n2019\/11\/22 12:41:54 CET : Collecting diagnostics from hosts : [exsite1c1, exsite1c2]\r\n2019\/11\/22 12:41:54 CET : Scanning of files for Collection in progress...\r\n2019\/11\/22 12:41:54 CET : Collecting additional diagnostic information...\r\n2019\/11\/22 12:44:13 CET : Completed collection of additional diagnostic information...\r\n2019\/11\/22 13:15:39 CET : Getting list of files satisfying time range [11\/22\/2019 00:41:53 CET, 11\/22\/2019 13:15:39 CET]\r\n2019\/11\/22 13:40:42 CET : Collecting ADR incident files...\r\n2019\/11\/22 13:40:48 CET : Completed Local Collection\r\n2019\/11\/22 13:40:48 CET : Remote Collection in Progress...\r\n.---------------------------------------.\r\n|           Collection Summary          |\r\n+-----------+-----------+-------+-------+\r\n| Host      | Status    | Size  | Time  |\r\n+-----------+-----------+-------+-------+\r\n| exsite1c2 | Completed | 412MB |  318s |\r\n| exsite1c1 | Completed | 284MB | 3534s |\r\n'-----------+-----------+-------+-------'\r\n\r\nLogs are being collected to: \/u01\/app\/grid\/tfa\/repository\/collection_Fri_Nov_22_12_41_49_CET_2019_node_all\r\n\/u01\/app\/grid\/tfa\/repository\/collection_Fri_Nov_22_12_41_49_CET_2019_node_all\/exsite1c1.tfa_Fri_Nov_22_12_41_49_CET_2019.zip\r\n\/u01\/app\/grid\/tfa\/repository\/collection_Fri_Nov_22_12_41_49_CET_2019_node_all\/exsite1c2.tfa_Fri_Nov_22_12_41_49_CET_2019.zip\r\n[root@exsite1c1 ~]#\r\n[root@exsite1c1 ~]# \/u01\/app\/19.0.0.0\/grid\/tfa\/bin\/tfactl diagcollect -since 1h\r\nWARNING - TFA Software is older than 180 days. Please consider upgrading TFA to the latest version.\r\nCollecting data for all nodes\r\n\r\nCollection Id : 20191122134319exsite1c1\r\n\r\nDetailed Logging at : \/u01\/app\/grid\/tfa\/repository\/collection_Fri_Nov_22_13_43_20_CET_2019_node_all\/diagcollect_20191122134319_exsite1c1.log\r\n2019\/11\/22 13:43:24 CET : NOTE : Any file or directory name containing the string .com will be renamed to replace .com with dotcom\r\n2019\/11\/22 13:43:24 CET : Collection Name : tfa_Fri_Nov_22_13_43_20_CET_2019.zip\r\n2019\/11\/22 13:43:24 CET : Collecting diagnostics from hosts : [exsite1c1, exsite1c2]\r\n2019\/11\/22 13:43:24 CET : Scanning of files for Collection in progress...\r\n2019\/11\/22 13:43:24 CET : Collecting additional diagnostic information...\r\n2019\/11\/22 13:44:49 CET : Getting list of files satisfying time range [11\/22\/2019 12:43:24 CET, 11\/22\/2019 13:44:49 CET]\r\n2019\/11\/22 13:45:50 CET : Completed collection of additional diagnostic information...\r\n2019\/11\/22 13:59:19 CET : Collecting ADR incident files...\r\n2019\/11\/22 13:59:19 CET : Completed Local Collection\r\n2019\/11\/22 13:59:19 CET : Remote Collection in Progress...\r\n.--------------------------------------.\r\n|          Collection Summary          |\r\n+-----------+-----------+-------+------+\r\n| Host      | Status    | Size  | Time |\r\n+-----------+-----------+-------+------+\r\n| exsite1c2 | Completed | 230MB | 295s |\r\n| exsite1c1 | Completed | 105MB | 955s |\r\n'-----------+-----------+-------+------'\r\n\r\nLogs are being collected to: \/u01\/app\/grid\/tfa\/repository\/collection_Fri_Nov_22_13_43_20_CET_2019_node_all\r\n\/u01\/app\/grid\/tfa\/repository\/collection_Fri_Nov_22_13_43_20_CET_2019_node_all\/exsite1c2.tfa_Fri_Nov_22_13_43_20_CET_2019.zip\r\n\/u01\/app\/grid\/tfa\/repository\/collection_Fri_Nov_22_13_43_20_CET_2019_node_all\/exsite1c1.tfa_Fri_Nov_22_13_43_20_CET_2019.zip\r\n[root@exsite1c1 ~]#<\/pre>\n<h2 style=\"text-align: justify;\"><strong>TFA error #2<\/strong><\/h2>\n<p style=\"text-align: justify;\">Another error that I got in another cluster that passed for the same update\/upgrade process was related with <em>*ser<\/em> files in tfa home. If I try to use TFA (with diagcolect as an example) I receive this error:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite2c1 ~]# \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite2c1\/tfa_home\/bin\/tfactl diagcollect\r\nWARNING - TFA Software is older than 180 days. Please consider upgrading TFA to the latest version.\r\nStorable binary image v2.10 contains data of type 101. This Storable is v2.9 and can only handle data types up to 30 at \/usr\/lib64\/perl5\/vendor_perl\/Storable.pm line 381, at \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite2c1\/tfa_home\/bin\/common\/tfactlshare.pm line 25611.\r\n[root@exsite2c1 ~]#<\/pre>\n<p style=\"text-align: justify;\">If you look in the MOS, will point to PERL version. But it is not the case here, the perl it is more than 5.10 version for this version of Exadata. <strong>The solution was more *.ser files to another folder (remove from TFA home), or delete it<\/strong>. After that, no more \u201cStorage binary error\u201d (but the error about with tfa_setup.txt continues):<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"no-highlight\">[root@exsite2c1 ~]# mv \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite2c1\/tfa_home\/internal\/*ser \/tmp\r\n[root@exsite2c1 ~]# ls -l \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite2c1\/tfa_home\/internal\/*ser\r\nls: cannot access \/u01\/app\/19.0.0.0\/grid\/tfa\/exsite2c1\/tfa_home\/internal\/*ser: No such file or directory\r\n[root@exsite2c1 ~]#<\/pre>\n<h2 style=\"text-align: justify;\">Problem and Solution<\/h2>\n<p style=\"text-align: justify;\">It is not clear the source of the problem in this case. As you saw above, the logs of upgrade\/update of GI from 18c to 19c reported success, even for TFA. But it is clear that tfa_setup.txt was left with wrong parameters inside. And if you look closely you can see that exists reference to the new GI home in the first version.<\/p>\n<p style=\"text-align: justify;\">But unfortunately, the needed parameters were left with the wrong values. The workaround was just to change the tfa_setup.txt and fix the wrong folders for parameters. Was not tested to execute the <em>$GI_HOME\/grid\/crs\/install\/tfa_setup -silent -crshome $GI_HOME<\/em> to fix the filed, but you can try. The idea was trying to identify the issue instead of just remove TFA and reinstall it.<\/p>\n<p style=\"text-align: justify;\">Again, this is a workaround tested in my environment and worked. You need to verify logs and other files to see if you hit the same issues. If yes, at least, you can try.<\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify;\"><strong>Disclaimer<\/strong>: <em>\u201cThe postings on this site are my own and don\u2019t necessarily represent my actual employer positions, strategies or opinions. The information here was edited to be useful for general purpose, specific data and identifications were removed to allow reach the generic audience and to be useful for the community. Post protected by copyright.\u201d<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Recently I made an Exadata stack upgrade\/update to the last 19.2 version (19.2.7.0.0.191012) and I upgraded the GI from 18c to 19c (last 19c version &#8211; 19.5.0.0.191015) and after that, TFA does not work. Since I don\u2019t want to complete execute a TFA clean and reinstallation I tried to find the error and the solution. [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[64,71,29,77,6,56,5,119],"tags":[99,72,100,117,69,65,120],"class_list":["post-641","post","type-post","status-publish","format-standard","hentry","category-18c","category-19c","category-database","category-engineeredsystems","category-exadata","category-grid-infrastructure","category-oracle","category-tfa","tag-18c","tag-19c","tag-engineered-systems","tag-error","tag-exadata","tag-oracle","tag-tfa"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>TFA error after GI upgrade to 19c - Fernando Simon<\/title>\n<meta name=\"description\" content=\"Check the workaround for TFA error that does not start after upgrade GI from 18c to 19c running over Exadata database server running OEL7.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"TFA error after GI upgrade to 19c - Fernando Simon\" \/>\n<meta property=\"og:description\" content=\"Check the workaround for TFA error that does not start after upgrade GI from 18c to 19c running over Exadata database server running OEL7.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/\" \/>\n<meta property=\"og:site_name\" content=\"Fernando Simon\" \/>\n<meta property=\"article:published_time\" content=\"2019-11-24T23:01:07+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-07-19T22:15:01+00:00\" \/>\n<meta name=\"author\" content=\"Simon\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Simon\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"17 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/\"},\"author\":{\"name\":\"Simon\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9\"},\"headline\":\"TFA error after GI upgrade to 19c\",\"datePublished\":\"2019-11-24T23:01:07+00:00\",\"dateModified\":\"2020-07-19T22:15:01+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/\"},\"wordCount\":804,\"commentCount\":0,\"keywords\":[\"18c\",\"19c\",\"Engineered Systems\",\"error\",\"Exadata\",\"Oracle\",\"tfa\"],\"articleSection\":[\"18c\",\"19c\",\"Database\",\"Engineered Systems\",\"Exadata\",\"Grid Infrastructure\",\"Oracle\",\"TFA\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/\",\"url\":\"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/\",\"name\":\"TFA error after GI upgrade to 19c - Fernando Simon\",\"isPartOf\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#website\"},\"datePublished\":\"2019-11-24T23:01:07+00:00\",\"dateModified\":\"2020-07-19T22:15:01+00:00\",\"author\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9\"},\"description\":\"Check the workaround for TFA error that does not start after upgrade GI from 18c to 19c running over Exadata database server running OEL7.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.fernandosimon.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"TFA error after GI upgrade to 19c\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#website\",\"url\":\"https:\/\/www.fernandosimon.com\/blog\/\",\"name\":\"Fernando Simon\",\"description\":\"Have you hugged your backup today?\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.fernandosimon.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9\",\"name\":\"Simon\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g\",\"caption\":\"Simon\"},\"sameAs\":[\"http:\/\/www.fernandosimon.com\"],\"url\":\"https:\/\/www.fernandosimon.com\/blog\/author\/simon\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"TFA error after GI upgrade to 19c - Fernando Simon","description":"Check the workaround for TFA error that does not start after upgrade GI from 18c to 19c running over Exadata database server running OEL7.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/","og_locale":"en_US","og_type":"article","og_title":"TFA error after GI upgrade to 19c - Fernando Simon","og_description":"Check the workaround for TFA error that does not start after upgrade GI from 18c to 19c running over Exadata database server running OEL7.","og_url":"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/","og_site_name":"Fernando Simon","article_published_time":"2019-11-24T23:01:07+00:00","article_modified_time":"2020-07-19T22:15:01+00:00","author":"Simon","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Simon","Est. reading time":"17 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/#article","isPartOf":{"@id":"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/"},"author":{"name":"Simon","@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9"},"headline":"TFA error after GI upgrade to 19c","datePublished":"2019-11-24T23:01:07+00:00","dateModified":"2020-07-19T22:15:01+00:00","mainEntityOfPage":{"@id":"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/"},"wordCount":804,"commentCount":0,"keywords":["18c","19c","Engineered Systems","error","Exadata","Oracle","tfa"],"articleSection":["18c","19c","Database","Engineered Systems","Exadata","Grid Infrastructure","Oracle","TFA"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/","url":"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/","name":"TFA error after GI upgrade to 19c - Fernando Simon","isPartOf":{"@id":"https:\/\/www.fernandosimon.com\/blog\/#website"},"datePublished":"2019-11-24T23:01:07+00:00","dateModified":"2020-07-19T22:15:01+00:00","author":{"@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9"},"description":"Check the workaround for TFA error that does not start after upgrade GI from 18c to 19c running over Exadata database server running OEL7.","breadcrumb":{"@id":"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.fernandosimon.com\/blog\/tfa-error-after-gi-upgrade-to-19c\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.fernandosimon.com\/blog\/"},{"@type":"ListItem","position":2,"name":"TFA error after GI upgrade to 19c"}]},{"@type":"WebSite","@id":"https:\/\/www.fernandosimon.com\/blog\/#website","url":"https:\/\/www.fernandosimon.com\/blog\/","name":"Fernando Simon","description":"Have you hugged your backup today?","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.fernandosimon.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9","name":"Simon","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g","caption":"Simon"},"sameAs":["http:\/\/www.fernandosimon.com"],"url":"https:\/\/www.fernandosimon.com\/blog\/author\/simon\/"}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p5ofTp-al","_links":{"self":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/posts\/641","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/comments?post=641"}],"version-history":[{"count":0,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/posts\/641\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/media?parent=641"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/categories?post=641"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/tags?post=641"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}