:Ĭollecting data for the last 12 hours for all components.ĭetailed Logging at : /u01/app/grid/tfa/repository/collection_Fri_Nov_22_12_41_49_CET_2019_node_all/diagcollect_20191122124148_exsite1c1.logĢ 12:41:53 CET : NOTE : Any file or directory name containing the string. If /dev/null 2>&1 to collect for the last 12 hours 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 ~]# vi /u01/app/19.0.0.0/grid/tfa/exsite1c1/tfa_home/bin/synctfanodes.sh Please update manually.ĭo you want to update this node list? : ~]#Īs you can see, the syncnodes.sh made a reference for the old 18c GI home. Unable to determine Node List to be synced. I tried to do the sync, and this pointed one ~]# /u01/app/19.0.0.0/grid/tfa/bin/tfactl syncnodes One know problem occurs when (for some reason) the nodes of the clusters lost the sync for TFA. Waiting up to 100 seconds for TFA to be started.Įnabling Access for Non-root Users on ~]# Removing Old TFA /u01/app/18.0.0/grid/tfa/exsite1c1/tfa_home. | Host | TFA Version | TFA Build ID | Upgrade Status | ![]() TFA Upgrade Log : /u01/app/19.0.0.0/grid/tfa/exsite1c1/tfapatch.log TFA patching CRS or DB from zipfile extracted to /tmp/.293046.tfa About to check previous TFA installations. > CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.Īnd other related logs reported complete ~]# cat /tmp/tfa_install_293046_2019_11_14-14_18_40.log > CLSRSC-595: Executing upgrade step 2 of 18: 'ValidateEnv'. 14:18:40: Executing the step with checkpoint. 14:18:40: CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector. > CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector. 14:18:40: CLSRSC-595: Executing upgrade step 1 of 18: 'UpgradeTFA'. So, when checking for running TFA I made ps -ef and not saw process ~]# ps -ef |grep tfa TFA-00002 Oracle Trace File Analyzer (TFA) is not running Please consider upgrading TFA to the latest version. WARNING - TFA Software is older than 180 days. ![]() So, when I tried to collect ~]# /u01/app/19.0.0.0/grid/tfa/bin/tfactl diagcollect 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). The provided solution as usual (by MOS support): download the lastest TFA and reinstall the actual one. ![]() And to be more precise, the TFA upgrade from 18c to 19c called by rootupgrade was ok (according to the log – I will show later). In the environment described here, the TFA was running fine with the 18c version, and the rootupgrade script from 18c to 19c does not report an error. If you try to start it or collect log using it, you can receive errors.
0 Comments
Leave a Reply. |