Oracle ORAchk - An Overview Guide to Oracle Stack Health Checks

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Oracle ORAchk
Oracle Stack Health Checks
Version 12.2.0.1.2

Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
2

Agenda
1
2
Why Oracle ORAchk?
Recommended Usage Overview
Report Structure
Detailed Usage Options
Oracle Health Check Collection Manager
Integration With Other Tools
Troubleshooting
3
4
5
6
7
3

Agenda
1
2
Why Oracle ORAchk?
Report Structure
Troubleshooting
3
4
5
6
7
4

–Automated risk identification and proactive notification
before business is impacted
–Health Checks based on most impactful reoccurring
problems across Oracle customer base
–Runs in your environment – no need to send anything to
Oracle
–Scheduled email Health Check reports
–Findings can be integrated into other tools of choice
Why Oracle ORAchk
Engineered
Systems
Non Engineered
Systems
Oracle
EXAchk
Oracle
ORAchk
Common Framework
Lightweight & non intrusive Oracle Stack Health Checks
5
Note: Oracle Database Appliance is the only Oracle Engineered System, which uses ORAchk. For all other Engineered Systems use EXAchk

Oracle Stack Coverage
• Oracle Engineered Systems
• Oracle Database Appliance
• Oracle ASR
• Oracle Systems
• Oracle Solaris
• Cross stack checks
• Solaris Cluster
• OVN
• Oracle Database
• Standalone Database
• Grid Infrastructure & RAC
• Maximum Availability Architecture (MAA)
Scorecard
• Upgrade Readiness Validation
• Golden Gate
• Oracle Restart
• Oracle Enterprise Manager Cloud Control
• Repository
• Agent
• OMS
• Oracle Middleware
• Application Continuity
• Oracle Identify and Access Management
Suite (Oracle IAM)
• Oracle E-Business Suite
• Oracle Payables
• Oracle Workflow
• Oracle Purchasing
• Oracle Order Management
• Oracle Process Manufacturing
• Oracle Receivables
• Oracle Fixed Assets
• Oracle HCM
• Oracle CRM
• Oracle Project Billing
• Oracle Siebel
• Database best practices
• Oracle PeopleSoft
• Database best practices
• Oracle SAP
• EXAdata best practices
6

Agenda
1
2
Why Oracle ORAchk?
Report Structure
Troubleshooting
3
4
5
6
7
7

Recommended Usage – Automated Risk Notification
1) Schedule ORAchk to run in daemon mode weekly or
daily and email report
2) Identify actions easily by viewing automated
comparison of previous runs
3) Act on recommendations
8

Schedule ORAchk
?
Hour (0 – 23)
? ? ?
Day of month (1 – 31)
Month (1 – 12)
Day of week (0 – 6)
(0 to 6 are Sunday to Saturday)
example: orachk -set 'AUTORUN_SCHEDULE=8,20 * * 2,5' will schedule runs on Tuesday and Friday at 08:00 & 20:00
AUTORUN_SCHEDULE =
99

• First email will contain the HTML report
Email Notification
10

View ORAchk Report
• Health score
• Summary of ORAchk run
• Table of content
• Controls for report features
• Findings
• Recommendations
11

View ORAchk Report
• Table of content
• Controls for report features
• Checks which passed are not shown by default
• Quickly show or hide checks based on their
status
• Show or hide major sections of the report
• Collapse or expand check findings
• Show check Ids
• Remove the findings from the report – This
doesn’t change the report but optionally hides
findings on a check by check basis
• Display a printable view
12

View ORAchk Findings
• Check status
• Type of Check
• Check Message
• Where the check was run
• Link to expand details
13

• What to do to solve the problem
• Links to relevant Knowledge docs
• Where recommendation applies
• Where problem doesn’t apply
• Example of data the
recommendation is based on
View Recommendations
14

Subsequent emails compare results to
previous run
• Easily see if something has changed
• Email attachment has:
o Latest report
o Previous report
o Diff Report
Email Notification
15

Diff overview
• Summary of this run vs previous
Diff Output
16

Differences between each run
Diff Output
17

• Upgrade or Patching
o Detects all databases registered in the
clusterware automatically
o Presents list of databases to check
o Pre Upgrade
 Run during upgrade planning phase
 Asks which version you plan to upgrade to
o Post Upgrade
 Run after upgrade
• Other typical times to run ORAchk
o Machine moves
o Hardware failure / repair
o Problem troubleshooting
o In addition to go-live testing
Other Recommended Usage
./orachk -u –o pre
./orachk -u –o post
18

Agenda
1
2
Why Oracle ORAchk?
Report Structure
Troubleshooting
3
4
5
6
7
19

Report Demo
20
Example ORAchk HTML Report

Agenda
1
2
Why Oracle ORAchk?
Report Structure
Troubleshooting
3
4
5
6
7
21

Supported Environments
22
Operating System Versions Supported
Linux / zLinux Oracle Linux/RedHat 4, 5, 6, 7
SuSE 9,10, 11, 12
Oracle Solaris SPARC / x86-64 9, 10, 11
AIX 5.2, 5.3, 6.1, 7.1, 7.2
HPUX Itanium / PA-RISC 11.23, 11.31
Microsoft Windows (with cygwin) 2008, 2012

1. Included in Database
and Grid infrastructure
install
2. Download latest version
from My Oracle Support
(install < 1 min)
3. Auto update when later
version available
Roll Out & Maintain
23

1. Download the
orachk.zip to your local
machine from MOS
Note 1268927.2
2. Transfer to a directory
on the target System
3. Unzip orack.zip
o As owner of oracle
database or grid home
Installation
24

• Run as root (recommended)
o ORAchk will su to lower privileged owners of
RDBMS or grid homes
• Run as RDBMS or GRID Home Owner
o User must be able to switch to root for root level
checks – several options:
1. Provide the root userid password at prompts
or
2. Set up sudo
or
3. Pre-configure passwordless SSH connectivity
Which User to Run ORAchk as
25

Option 1 With internet connection
o When ORAchk is older than 120 days it will prompt
you to let it automatically download newer version
from My Oracle Support
o Can also be specifically triggered with:
Option 2 No internet connection
a) Download the latest orachk.zip to a shared
network staging location
b) Set environment variable RAT_UPGRADE_LOC:
c) Next time orachk is started it will prompt to allow
it to upgrade itself
Maintaining ORAchk
./orachk -download
export RAT_UPGRADE_LOC=<staging dir>
26

Maintaining ORAchk
• Option 3 Applied with PSU
o Each database PSU contains the latest ORAchk version available at time of creation
oWhen a database PSU is applied the ORAchk zip version contained will be staged in
$ORACLE_HOME/suptools
oThe next run of ORAchk it will prompt you to upgrade if the version copied by the PSU
is newer than installed – Just like option 2
27

Automated Usage with the Daemon
28

Set Daemon Options, When, What & Who to Tell
./orachk –set “<option_1>=<option_1_value>;<option_2>=<option_2_value>;<option_n>=<option_n_value>”
AUTORUN_SCHEDULE
• Schedule when orachk will be run
• Hour, day of month, month of year & day of week
• Comma separate multiple values for same timeframe
• * Wildcard
?
Hour (0 – 23)
? ? ?
Day of month (1 – 31)
Month (1 – 12)
Day of week (0 – 6)
(0 to 6 are Sunday to Saturday)
./orachk –set “AUTORUN_SCHEDULE=2 * * 1,3,5”
AUTORUN_FLAGS
• Command line options to be passed through to orachk run
./orachk –set “AUTORUN_FLAGS=-profile dba –tag dba”
NOTIFICATION_EMAIL
• Comma separated list of emails to send daemon notifications to
./orachk –set “NOTIFICATION_EMAIL=some.person@acompany.com,another.person@acompany.com”
29

Set Daemon Options, Maintenance
./orachk –set “<option_1>=<option_1_value>;<option_2>=<option_2_value>;<option_n>=<option_n_value>”
COLLECTION_RETENTION
• Number of days to keep files created by scheduled run, files older than this will be deleted
./orachk –set “COLLECTION_RETENTION=30”
PASSWORD_CHECK_INTERVAL
• Frequency in hours of password validation
• When found invalid daemon stops & notifies via log & email
./orachk –set “PASSWORD_CHECK_INTERVAL=48”
30

Set Daemon Options, Multiple IDs
• Only one Daemon process should be used across a database cluster
o Multiple daemon profiles can be configured using IDs
o Allows for multiple different types of orachk runs
./orachk –id <ID> –set “<option>=<value>”
31

Get Daemon Option
• Find a specific daemon option which has been set
• Use with or without ID
./orachk –id <ID> –get <option>
Get value of particular option for specific id
./orachk –get <option>
Get value of particular option for all IDs
32

Get All Daemon Options
• Find any Daemon options which have been set
• Used with or without ID
./orachk –id <ID> –get all
Get value of all options for specific id
./orachk –get all
Get value of all options for all IDs
33

Start Daemon
./orachk –d start
1. Start the daemon
2. Follow the prompts
34

Daemon Information
./orachk –d status
Check if the daemon is running:
./orachk –d info
Get more detailed information about the daemon
35

Daemon Next Autorun
./orachk –d nextautorun ./orachk –id <id> –d nextautorun
Find when the next auto run will happen: Find when the next auto run will happen for a specific ID
36

Daemon Stopping
./orachk –d stop_client ./orachk –d stop
Stop an orachk run mid-flow: Stop the daemon
37

Auto Restart Daemon
• Restart daemon if
machine restarts
o Uses passwordless ssh
user equivalence to root
./orachk –initsetup
38

Restart status of daemon can be queried: If you want to remove restart settings:
Auto Restart Daemon, Check Status & Remove Auto Restart
./orachk –initcheck ./orachk –initrmsetup
39

With or Without the Daemon
• When daemon is running, if orachk is run in on-demand mode it will
connect to the daemon by default and make use of pre-provided prompt
values
o To avoid connecting to the daemon use –nodaemon:
oTo only run orachk when the daemon is running use –daemon:
./orachk –nodaemon
./orachk –daemon
40

Email Notifications
• Run in ad hoc mode and receive html report via email
• Verify email configuration function
• Use –testemail all to use email addresses stored in daemon configuration
./orachk -sendemail "NOTIFICATION_EMAIL=abc@company.com,xyz@company.com"
./orachk -testemail "NOTIFICATION_EMAIL=abc@company.com,xyz@company.com"
./orachk -testemail all
41

Additional Oracle ORAchk Capabilities & Features
42

Health Check Catalog
• Bundled within .zip download
• ORAchk_Health_Check_Catalog.html
• Contains all published checks
• Filterable & searchable
• Engineered System
• Profiles
• Alert Level
• Release Check Authored
• Platforms
• Privileged User
• Look up check id without running report
43

Database Checks
• ORAchk runs checks against all database nodes in the cluster by default
o To specify only a subset of nodes use:
o Only local node:
• Automatically discovers all databases and prompts for which should be checked
o Do not prompt but run all checks on all discovered database:
o Do not prompt and skip all database related checks:
o Only run checks against a subset of databases:
./orachk –clusternodes <node_1>,<node_2>
./orachk –localonly
./orachk –dball
./orachk –dbnone
./orachk –dbnames <db_1>,<db_2>
44

Output
• ORAchk will output the collection results to the directory it is run from unless run
from $ORACLE_HOME/suptools/orachk then output goes to $ORACLE_BASE/orachk
o Output can be directed to a different directory with –output
• Output will be directory and a zip of the same name
./orachk –output <OUTPUT_DIR>
o log : various log files
o outfiles : collection results checks are based on
o reports : subreports used to build the main report
o scripts : scripts used during collection
o upload : files for upload of collection into database or
integration into other tools
o orachk_*.html : Main HTML report output
45

Temporary Working Directory
• ORAchk will create temporary files during execution
• Default location is $HOME/.orachk of the user ORAchk is running as
• Location can be changed by setting RAT_TMPDIR
• If using sudo access to root from a lower privileged user id, temporary directory must be
reflected in /etc/sudoers file
• Root privilege checks run from root_orachk.sh in the temporary directory
– If you want the root script in a different directory to RAT_TMPDIR use: RAT_ROOT_SH_DIR
export RAT_TMPDIR=<TEMP_DIR>
./orachk
<user> ALL=(root) NOPASSWD:<TEMPDIR>/.orachk/root_orachk.sh
46
oracle ALL=(root) NOPASSWD:/mylocation/root_orachk.sh
oracle ALL=(root) NOPASSWD:/tmp/.orachk/root_orachk.sh
export RAT_ROOT_SH_DIR=/mylocation

Parallel Execution
• Database collections are executed in parallel
• The default number of slave processes used is calculated automatically
• Default can be changed with –dbparallel <# slave processes> or -dbparallelmax
• Parallel execution can be disabled altogether if required with -dbserial
./orachk –dbparallel <# slave processes> ./orachk –dbparallelmax
./orachk –dbserial
47

Tagging, Merging & Comparing Reports
• Collections are typically of the format: orachk_<dbserver>_<database>_<date>_<timestamp>.html
• Tag collections so output contains another word to help differentiate it:
orachk_<dbserver>_<database>_<date>_<timestamp>_<tag_name>.html
• Merge multiple reports into one with –merge and list of collection directories or zip
files:
• Compare collections with –diff:
./orachk –merge <collection_1>,<collection_2>
./orachk –diff <collection_1>,<collection_2>
./orachk –tag <tag_name>
48

• Profiles provide logical grouping of
checks which are about similar topics
• Run only checks in a specific profile
• Run everything except checks in a specific
profile
Profiles
./orachk –profile <profile>
./orachk –excludeprofile <profile>
Profile Description
asm ASM Checks
clusterware Oracle clusterware checks
dba DBA Checks
ebs Oracle E-Business Suite checks
emagent Cloud control agent checks
emoms Cloud Control management server
em Cloud control checks
goldengate Oracle GoldenGate checks
hardware Hardware specific checks for Oracle Engineered systems
oam Oracle Access Manager checks
oim Oracle Identify Manager checks
oud Oracle Unified Directory server checks
ovn Oracle Virtual Networking
peoplesoft Peoplesoft best practices
preinstall Pre-installation checks
prepatch Checks to execute before patching
security Security checks
siebel Siebel Checks
solaris_cluster Solaris Cluster Checks
sysadmin Sysadmin checks
user_defined_checks Run user defined checks from user_defined_checks.xml
49

Run or exclude individual checks
• Granular control to execute or exclude a single check
• Ideal for testing new checks or troubleshooting
• Run only specific check(s):
• Exclude a specific check:
• Find check id either from report or Health Check Catalog
./orachk -check <check_id_1>,<check_id_2>
./orachk –excludecheck <check_id_1>,<check_id_2>
50

• Track changes to the attributes of important files with –fileattr
– Looks at all files & directories within Grid Infrastructure and Database homes by default
– The list of monitored directories and their contents can be configured to your specific requirements
– Use –fileattr start to start the first snapshot
51
Keep Track of Changes to the Attributes of Important Files
$ ./orachk -fileattr start
CRS stack is running and CRS_HOME is not set. Do you want to set CRS_HOME to
/u01/app/11.2.0.4/grid?[y/n][y]
Checking ssh user equivalency settings on all nodes in cluster
Node mysrv22 is configured for ssh user equivalency for oradb user
Node mysrv23 is configured for ssh user equivalency for oradb user
List of directories(recursive) for checking file attributes:
/u01/app/oradb/product/11.2.0/dbhome_11203
/u01/app/oradb/product/11.2.0/dbhome_11204
orachk has taken snapshot of file attributes for above directories at:
/orahome/oradb/orachk/orachk_mysrv21_20160504_041214
./orachk –fileattr start

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 52
• Include other directories with –includedir <directories> using a comma separated list of directories
./orachk –fileattr start includedir “/home/oradb,/etc/oatab”
• Exclude the default discovered directories with –excludediscovery
./orachk –fileattr start includedir “/home/oradb,/etc/oatab” -excludediscovery

Note:
• Use the same arguments with check that you used with start
• Will proceed to perform standard health checks after attribute checking
• File Attribute Changes will also show in HTML report output
• Compare current attributes against first snapshot using –fileattr check
53
$ ./orachk -fileattr check -includedir "/root/myapp/config" -excludediscovery
CRS stack is running and CRS_HOME is not set. Do you want to set CRS_HOME to
/u01/app/12.2.0/grid?[y/n][y]
Checking for prompts on myserver18 for oragrid user...
Checking ssh user equivalency settings on all nodes in cluster
Node myserver17 is configured for ssh user equivalency for root user
List of directories(recursive) for checking file attributes:
/root/myapp/config
Checking file attribute changes...
.
"/root/myapp/config/myappconfig.xml" is different:
Baseline : 0644 oracle root /root/myapp/config/myappconfig.xml
Current : 0644 root root /root/myapp/config/myappconfig.xml
…etc
…etc
./orachk –fileattr check
• Results of snapshot comparison will also
be shown in the HTML report output

• To prevent standard health checking after attribute checking add –fileattronly:
• To use a different snapshot baseline use –baseline:
• To remove all snapshot use –fileattr remove
54
./orachk –fileattr check –fileattronly
./orachk -fileattr check -baseline <snapshot>
./orachk -fileattr remove

Agenda
1
2
Why Oracle ORAchk?
Report Structure
Troubleshooting
3
4
5
6
7
55

Oracle Health Check Collection Manager Dashboard
56

Dashboard Filters
Filter by
Interval
Filter by
configurable
business units Filter by
systems
Click on color coded
area to drill down
57
Filter by
health score

Most Failures & Warnings
Click to see the
recommendation details
58

Most Failures
Click to drill into
failures
59

Most Warnings
Click to drill into
warnings
60

No difference OR No regression
failed in current collection
At least one regression from
Non-WARNING to WARNING OR
Found WARNING regression in
current collection
At least one regression from
Non-FAIL to FAIL OR Found FAIL
regression in current collection
Non clickable green flag -
Preceding collection not found
Recent Collections
Health
Score Warning count
Fail count Info count Pass count
Ignore count
61

View Collection
Collection
Link
62

View Collection
Recommendation
63

User Defined Checks
• Use as a Health Checking Platform
• You write your own business
specific User Defined Checks
• Collection Manager authoring UI
very similar to Oracle’s internal
authoring tool
• OS or SQL logic
• Generates user_defined_checks.xml
sample in install directory
• Utilizes framework features such as
result output, email notification,
CM storage etc
64

User Defined Checks
• Have their own profile:
user_defined_checks
• Can be excluded:
./orachk -excludeprofile user_defined_checks
• Have their own section of the report
./orachk -profile user_defined_checks
• Can be run on their own:
65

1. First time installation done via the APEX
workspace (either APEX 4.2 or 5.x)
2. Use the sql script applicable for your
APEX version:
– APEX 4.2: CollectionManager_App.sql
– APEX 5.x: Apex5_CollectionManager_App.sql
3. Follow Health Check Collection Manager
installation in the User Guide
4. Login to Collection Manager Application
via a URL like the following:
http://hostname:port/apex/f?p=ApplicationID
http://hostname:port/pls/apex/f?p=ApplicationID
• Collection Manager upgrade done from
orachk:
• Will determine the APEX version you
have and install the latest applicable
Collection Manager app
• If the Collection Manager schema
changes in the future then ORAchk will
prompt for auto upgrade
66
Setup
./orachk -cmupgrade
Note: APEX 4.2 version of CM app exists for backwards compatibility.
New features will only go into the APEX 5 Collection Manager app

Collection Storage Table
• Collection zip files are stored in the RCA13_DOCS
table - already created during collection manager
installation
• Provide ORAchk details of where to upload
collection results with –setdbupload all and
complete prompts:
• Get current values with -getdbupload:
• Unset values with –unsetdbupload <parameter>:
./orachk -setdbupload all
./orachk –unsetdbupload RAT_UPLOAD_PASSWORD
./orachk -getdbupload
67

Store DB Upload Variables in Wallet
• Set all with:
• Set specific variables by specifying comma separated list:
• Unset all with
• Check if variables are set correctly:
./orachk -setdbupload all
./orachk -setdbupload RAT_UPLOAD_CONNECT_STRING,RAT_UPLOAD_PASSWORD
./orachk -unsetdbupload all
./orachk -checkdbupload
68
Other Upload Parameters Not Set
by default
Description
RAT_UPLOAD_USER The user to connect as (default is ORACHKCM)
RAT_UPLOAD_TABLE The table name to store non-zipped collection
results
RAT_PATCH_UPLOAD_TABLE The table name to store non-zipped patch results
RAT_UPLOAD_ORACLE_HOME The ORACLE_HOME used during establishing
connection and uploading.
(Uses GI HOME discovered by ORAchk by default)
RAT_UPLOAD_TABLE &
RAT_PATCH_UPLOAD_TABLE
Only needed if you are using your own custom
application to view collection results, rather than
Collection Manager.

Agenda
1
2
Why Oracle ORAchk?
Report Structure
Troubleshooting
3
4
5
6
7
69

Integrating With
Oracle Enterprise Manager Cloud Control 13.1
70

Enterprise Manager Integration
•Check results integrated into EM
compliance framework via plugin
•View results in native EM
compliance dashboards
•Related checks grouped into
compliance standards
•View targets checked, violations &
average score
•Drill down into compliance standard
to see individual check results
•View break down by target
71

Setting Up Enterprise Manager Plugin
• The plugin is already installed by default with Enterprise Manager 13.1
1. Deploy the plugin using the Enterprise Manager Plugin Deployment feature
2. Provision the plugin to setup the ORAchk daemon
72

• Use Enterprise Manager provisioning
feature and select ORAchk/EXAchk
• After selected this will launch the
provisioning wizard, choose the system
type
Provision ORAchk
73

Provision ORAchk
• Provide new or select existing
credentials
• Specify install location
• Select when daemon should be run
74

Provision ORAchk
• Verify CRS Home
• Finally choose Cell & InfiniBand
configuration
75

Drill into applicable standard and view
individual checks & target status
View Results by Compliance Standard
Filter by Exachk%”
Click individual checks for
recommendation details
76

Integrating With 3rd Party Tools
77

• The JSON provides many tags to
allow dashboard filtering based on
facts such as:
• Engineered System type
• Engineered System version
• Hardware type
• Node name
• OS version
• Rack identifier
• Rack type
• Database version
• And more...
• Kibana can be used to view health
check compliance across your data
center
• Results can also be filtered based
on any combination of exposed
system attributes
78
JSON Output to Integrate with Kibana, Elastic Search etc

• ORAchk results are also output in
JSON format in the upload
directory of the collection
• Writing JSON Results With syslog
1. JSON output results can be sent to the
syslogd Daemon with –syslog option e.g.:
2. ORAchk uses the message levels of “crit”,
“err”, “warn” and “info”
3. You can verify syslog configuration by
running the following commands:
4. Then verify in your configured message
location (e.g. /var/adm/messages) that each
test message was written
JSON Result Output
./orachk –set “AUTORUN_FLAGS=-syslog”
79

Integrating With Your Own Application
80

If you don’t use Collection Manager and have your own application which consumes the ORAchk results
1. Create the tables: auditcheck_result, auditcheck_patch_result & RCA13_DOCS
2. Set default parameters:
– This will prompt you for and set the RAT_UPLOAD_CONNECT_STRING & RAT_UPLOAD_PASSWORD
3. Set optional parameters for RAT_UPLOAD_TABLE & RAT_PATCH_UPLOAD_TABLE
81
Configure Details for Upload of Collection Results
./orachk –setdbupload all
./orachk -setdbupload RAT_UPLOAD_TABLE,RAT_PATCH_UPLOAD_TABLE
Other Upload Parameters Not Set by default Description
RAT_UPLOAD_USER The user to connect as (default is ORACHKCM)
RAT_UPLOAD_TABLE The table name to store non-zipped collection results
RAT_PATCH_UPLOAD_TABLE The table name to store non-zipped patch results
RAT_UPLOAD_ORACLE_HOME The ORACLE_HOME used during establishing connection and
uploading.
(Uses GI HOME discovered by ORAchk by default)
RAT_UPLOAD_TABLE &
RAT_PATCH_UPLOAD_TABLE
Only needed if you are using your own custom application to view
collection results, rather than Collection Manager.

Agenda
1
2
Why Oracle ORAchk?
Report Structure
Troubleshooting
3
4
5
6
7
82

• View Component Elapsed Times
o Identify if one particular component is slow
• View top 10 Time Consuming Checks
o If some in particular are slow, show check_id
and run again with:
Troubleshooting Performance
./orachk –excludecheck <check_id>
• Try increasing the number of parallel
slave processes (Note: will increase resource usage)
./orachk –dbparallelmax
83

• If checks are being killed this will be due
to timeout:
• Timeouts can be caused by slow checks or
interactive prompts
• Try increasing default times with applicable
environment variables:
• EBS checks query application data which
can vary hugely in size depending on the
size of your data
oIf you suspect EBS checks try excluding
EBS profile:
oUse RAT_TIMEOUT to increase to a
value where they are no longer killed
Troubleshooting Timeouts
./orachk –excludeprofile ebs
84
Environment Variable Timeout Controlled
Default Value
(seconds)
RAT_TIMEOUT
non-root individual
commands
90
RAT_ROOT_TIMEOUT
root userid command
sets
300
RAT_PASSWORDCHECK_TIMEOUT
ssh login DNS
handshake
1

• Debugging via Daemon • Debugging ondemand ORAchk runs
Collecting Debug
./orachk –d start_debug ./orachk –debug
• Debug output:
85

Safe Harbor Statement
The preceding is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
86

Oracle ORAchk - An Overview Guide to Oracle Stack Health Checks

Oracle ORAchk - An Overview Guide to Oracle Stack Health Checks

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (18)

En vedette

En vedette (19)

Similaire à Oracle ORAchk - An Overview Guide to Oracle Stack Health Checks

Similaire à Oracle ORAchk - An Overview Guide to Oracle Stack Health Checks (20)

Plus de Gareth Chapman

Plus de Gareth Chapman (7)

Dernier

Dernier (20)

Oracle ORAchk - An Overview Guide to Oracle Stack Health Checks