Running EXAchk in an EXADATA Server

In this post we'll see about EXAchk utility, command-line options and how to run it on an EXADATA Server.

     1. What is EXAchk? 

      ·         Automates risk identification and proactive notification before your                        business is  impacted. 

·         Runs health checks based on critical and reoccurring problems

·         Presents high-level reports about your system health risks and vulnerabilities to   known issues

·         Enables you to drill-down specific problems and understand their resolutions

·         Enables you to schedule recurring health checks at regular intervals

·         Sends email notifications and diff reports while running in daemon mode

·         Integrates the findings into Oracle Health Check Collections Manager and other   tools of your choice

       ·         Runs in your environment with no need to send anything to Oracle    

You have access to Oracle EXAchk as a value add-on to your existing support contract. There is no additional fee or license required to run Oracle EXAchk. 

Use Oracle EXAchk for Oracle Engineered Systems for Oracle Database Appliance. 

Run health check for Oracle products using the command-line options.

     2. Command-Line Options

• List of general Oracle EXAchk commands

• List of commands to control the scope of checks. 

     3. How to run EXAchk?

• Check the version of exachk utility available in your EXADATA server.

• Check the metalink note 1070954.1 for the recent version of exachk utility. It is always advisable to run the latest version of exachk utility to get accurate results on the health of the server and MAA results.

• If the existing version of the utility is lower than the one available from oracle support, download the same and install the latest version of the utility as done below.

• Check the exachk utility version again to check it is the latest one or not.

• Run the exachk against the desired database.

• Go-through the location where the output file is generated, transfer the .zip file to your local machine and go through the .html file for the detailed report on the database, server and MAA results.

• The result is self-explanatory and provide details and recommendation for all the results.

• Base on the recommendations, we can work and make the server more stable in terms of health check.

Ref : Oracle Exadata Database Machine EXAchk or HealthCheck (Doc ID 1070954.1)

                          ****************************நன்றி****************************

PLS-00302: component 'PURGE_BUSINESS_EXCEPTIONS' must be declared

In my environment we are using R12.2.5. Recently after a fresh clone of the application tier, before releasing the instance, performed the post clone activity and sanity works. As a part of this tasks, ran the concurrent program 'Purge Debug Log and System Alerts' to remove the log files.

After submission, the program has completed with error.

From the log file observed the below error:

"Cause: FDPSTP failed due to ORA-06550: line 1, column 20:

PLS-00302: component 'PURGE_BUSINESS_EXCEPTIONS' must be declared

ORA-06550: line 1, column 7:

PL/SQL: Statement ignored"

"Purge Debug Log and System Alerts" is the name of the old purge program that was used in Oracle Application Release 11i, "Purge Logs and Closed System Alerts" is name of new one introduced in Release 12. Both of them do basically same thing, that is purge logs and alerts. "Purge Diagnostic and Log Messages" is no longer used in R12. If someone runs concurrent program "Purge Diagnostic and Log Messages" then it will error out with below error message in concurrent program logfile :  

Error:
ORACLE error 6550 in FDPSTP

Cause: FDPSTP failed due to ORA-06550: line 1, column 20:
PLS-00302: component 'PURGE_BUSINESS_EXCEPTIONS' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored 

To overcome the above error "Purge Logs and Closed System Alerts [FNDLGPRG]" should be run instead of "Purge Debug Log and System Alerts" in Release 12.

To disable Concurrent program "Purge Diagnostic and Log Message" in Release 12 do the following:

Query for the concurrent program 'Purge Diagnostic and Log Messages'

Uncheck the 'Enabled' checkbox and save the program.

Now run the program 'Purge Logs and Closed System Alerts' to purge the messages.

Ref : How to Purge/Troubleshoot the FND_LOG_MESSAGES table (Doc ID 735138.1)

****************************நன்றி****************************