Database Reference
In-Depth Information
To perform RAC upgrade readiness verification checks, use the following example and response with your inputs
when prompted with questions:
$./raccheck -u -o pre
Following are the supported arguments with the tool:
$ ./raccheck -h
Usage : ./raccheck [-abvhpfmsuSo:c:rt:]
-a All (Perform best practice check and recommended patch check)
-b Best Practice check only. No recommended patch check
-h Show usage
-v Show version
-p Patch check only
-m exclude checks for Maximum Availability Architecture -u Run raccheck to check
pre-upgrade or post-upgrade best
practices.-o pre or -o post is mandatory with -u option like ./raccheck -u -o pre
-f Run Offline.Checks will be performed on data already -o Argument to an option.
if -o is followed by
v,V,Verbose,VERBOSE or Verbose, it will print checks which
passs on the screen
if -o option is not specified,it will print only failures on
screen. for eg: raccheck -a -o v
-r To include High availability best practices also in regular
healthcheck eg ./racchekck -r(not applicable for exachk)
-c Pass specific module or component to check best practice
for.
The assessment report provides a better picture of the RAC environment and includes an overall system health
check rating (out of 100), Oracle Maximum Availability Architecture (MAA) best practices, bug fixes, and patch
recommendations.
■
the tool is available for download only through Mos, which requires additional support licensing. executing the
tool when the systems are heavily loaded is not recommended. it is recommended to test the tool in a non-production
environment first, as it doesn't come by default with oracle software.
Note
Cluster Diagnostic Collection Tool - diagcollection.sh
Every time you run you into a few serious Clusterware issues and confront node eviction, you typically look at various
CRS-level and OS-level logs to gather the required information to comprehend the root cause of the problem. Because
Clusterware manages a huge number of logs and trace files, it will sometimes be cumbersome to review many logs
from each cluster node. The
diagcollection.sh
tool, located under
GRID_HOME/bin
, is capable of gathering the
required diagnostic information referring to various important sources, such as CRS logs, trace and core files, OCR
data, and OS logs.
With the diagnostic collection tool, you have the flexibility to collect diagnostic information at different levels,
such as cluster, Oracle RDBMS home, Oracle base, and Core analysis. The gathered information from various
resources will then be embedded into a few zip files. You therefore need to upload these files to Oracle Support for
further analysis to resolve the problem.
