EXAchk now provides limited beta testing support for Oracle Private Cloud Appliance.
New checks can be seen in the EXAchk Health Check Catalog under the Engineered systems of Private Cloud Appliance and Private Cloud Appliance Plane.
Oracle Trace File Analyzer root installations on Linux or Solaris on non-engineered systems will automatically setup and run the ORAchk daemon.
The daemon will be restarted at 1am every morning, in order to discover any environment changes. A full local ORAchk run will be performed at 2am every morning and a partial run of the most impactful checks will be run every 2 hours via the oratier1 profile.
Any collections older than 2 weeks will automatically be purged.
If ORAchk is installed in stand-alone mode Auto start can also be used for quick setup by running orachk -autostart, again only when run as root on Linux or Solaris on a non-engineered system.
Once auto start is enabled the daemon settings can be changed as per normal and auto start can be removed any time by using orachk -autostop or tfactl run orachk -autostop
ORAchk and EXAchk can now be run against specific individual PDBs.
To run against specific PDBs use -pdbnames {pdb_name1,pdb_name2}
User defined checks can now have custom check names, pass and fail messages, all declared dynamically at run time.
The dynamic values can be set like this
---CHECK STARTS---
{existing_check_code}
echo "CUSTOM_CHECK_NAME={customized_check_name}" >> CUSTOMIZE_CHECK_PARAMS
echo "CUSTOM_PASS_MSG={customized_pass_message}" >> CUSTOMIZE_CHECK_PARAMS
echo "CUSTOM_FAIL_MSG={customized_fail_message}" >> CUSTOMIZE_CHECK_PARAMS
---CHECK ENDS---
Additionally user defined checks that are on hold will no longer be exported by default. You can still choose to export on hold checks by selecting the relevant tick box.
The summary section of report output now shows the role of each database (Primary or Standby)
In the "DB Home - Version - Names" section click the number of databases to expand details and see the role of each database
As of the 18.3.0 release the ORAchk and EXAchk EBS checks feature has been deprecated.
This means the running of health checks against EBS is no longer being enhanced, but is still supported until the ORAchk and EXAchk 19.3.0 release (approximately one year).
In the ORAchk and EXAchk 19.3.0 release the EBS checks feature will be desupported, meaning Oracle will no longer fix bugs in ORAchk or EXAchk related to EBS checks and the EBS checking feature will be removed altogether.
All EBS health checks can be performed using the EBS Analyzers available at note: 1545562.1.
This release includes integration with DBSAT 2.0.2.
DBSAT is provided at no additional cost and enables customers to quickly find:
As always this release of ORAchk and EXAchk contain many new Oracle Stack Health Checks including all Exadata Critical Issues.
For full details of the new checks see:
The Health Check Catalog is also contained within the download.