I have previously written a number of posts about OSWatcher integration in Tracefile Analyzer (TFA) w/support tools bundle (available from My Oracle Support Document ID 1513912.1). Thus far I have neglected another useful tool available to administrators in the same package: orachk.
UPDATE
This post covers an old version of the stack. At the time of writing this update TFA has been merged into a new super-tool, named Autonomous Health Framework. This doesn’t change the message though, however you might have to use a different path to access tfactl. The commands remain identical.
Summary of the environment
My lab system used for this post uses Oracle Restart 12.1.0.2 on top of Oracle Linux 7.4. I installed TFA 18.3 to /opt/tfa. If memory serves me right, TFA isn’t automatically deployed with Oracle Restart 12.1 as it now is with 12.2 and later.
[oracle@server1 ~]$ /opt/tfa/bin/tfactl print version TFA Version : 18.3.3.0.0
A quick check using tfactl toolstatus reveals that orachk is indeed present:
[oracle@server1 ~]$ /opt/tfa/bin/tfactl toolstatus .------------------------------------------------------------------. | TOOLS STATUS - HOST : server1 | +----------------------+--------------+--------------+-------------+ | Tool Type | Tool | Version | Status | +----------------------+--------------+--------------+-------------+ | Development Tools | orachk | 12.2.0.1.3 | DEPLOYED | | | oratop | 14.1.2 | DEPLOYED | +----------------------+--------------+--------------+-------------+ | Support Tools Bundle | darda | 2.10.0.R6036 | DEPLOYED | | | oswbb | 8.1.2 | RUNNING | | | prw | 12.1.13.11.4 | NOT RUNNING | +----------------------+--------------+--------------+-------------+ | TFA Utilities | alertsummary | 12.2.1.1.0 | DEPLOYED | | | calog | 12.2.0.1.0 | DEPLOYED | | | dbcheck | 18.3.0.0.0 | DEPLOYED | | | dbglevel | 12.2.1.1.0 | DEPLOYED | | | grep | 12.2.1.1.0 | DEPLOYED | | | history | 12.2.1.1.0 | DEPLOYED | | | ls | 12.2.1.1.0 | DEPLOYED | | | managelogs | 12.2.1.1.0 | DEPLOYED | | | menu | 12.2.1.1.0 | DEPLOYED | | | param | 12.2.1.1.0 | DEPLOYED | | | ps | 12.2.1.1.0 | DEPLOYED | | | pstack | 12.2.1.1.0 | DEPLOYED | | | summary | 12.2.1.1.0 | DEPLOYED | | | tail | 12.2.1.1.0 | DEPLOYED | | | triage | 12.2.1.1.0 | DEPLOYED | | | vi | 12.2.1.1.0 | DEPLOYED | '----------------------+--------------+--------------+-------------' Note :- DEPLOYED : Installed and Available - To be configured or run interactively. NOT RUNNING : Configured and Available - Currently turned off interactively. RUNNING : Configured and Available. [oracle@server1 ~]$
I found it interesting that tfactl toolstatus reports orachk version 12.2 although it actually is 18.3:
[root@server1 ~]# /opt/tfa/bin/tfactl orachk
TFA Orachk : /opt/tfa/server1/tfa_home/ext/orachk/orachk has version 20180808
Suptools Orachk : /u01/app/oracle/product/12.1.0.2/grid/suptools/orachk/orachk has version 20140530
TFA using Orachk : /opt/tfa/server1/tfa_home/ext/orachk/orachk
Running orachk
----------------------------------------------------------
PATH : /opt/tfa/server1/tfa_home/ext/orachk
VERSION : 18.3.0_20180808
COLLECTIONS DATA LOCATION : /opt/tfa/repository/suptools/server1/orachk/root
----------------------------------------------------------
Clusterware stack is running from /u01/app/oracle/product/12.1.0.2/grid. Is this the correct Clusterware Home?
[...]
At the risk of repeating myself: I strongly recommend using TFA with the support tools bundle on every box. It’s deployment can (and probably should) be automated. With these tools it’s like how it is with statspack: if you install at after the incident, it’s too late ;)
Once orachk is deployed, you can even script the execution, as explained in the Autonomous Health Framework, section 2.4.2
Happy troubleshooting!
