Beruflich Dokumente
Kultur Dokumente
HTML XML
Results Results
Email JSON
Notification Results
3) Act on recommendations
-d start
AUTORUN_SCHEDULE = ? ? ? ?
Hour (0 23) Month (1 12)
example: -set 'AUTORUN_SCHEDULE=8,20 * * 2,5' will schedule runs on Tuesday and Friday at 08:00 & 20:00
Health score
Summary of run
Table of content
Controls for report features
Findings
Recommendations
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
doesnt change the report but optionally hides
findings on a check by check basis
Display a printable view
Check status
Type of Check
Check Message
Where the check was run
Link to expand details
Diff overview
Summary of this run vs previous
o Post Upgrade
Run after upgrade
-u o post
AUTORUN_SCHEDULE AUTORUN_FLAGS
Schedule when orachk will be run Command line options to be passed through to orachk run
Hour, day of month, month of year & day of week
Comma separate multiple values for same timeframe set AUTORUN_FLAGS=-profile dba tag dba
* Wildcard
Day of month (1 31) Day of week (0 6)
(0 to 6 are Sunday to Saturday)
? ? ? ?
Hour (0 23) Month (1 12)
NOTIFICATION_EMAIL
set AUTORUN_SCHEDULE=2 * * 1,3,5
Comma separated list of emails to send daemon notifications to
set NOTIFICATION_EMAIL=some.person@acompany.com,another.person@acompany.com
COLLECTION_RETENTION
Number of days to keep files created by scheduled run, files older than this will be deleted
set COLLECTION_RETENTION=30
PASSWORD_CHECK_INTERVAL
Frequency in hours of password validation
When found invalid daemon stops & notifies via log & email
set PASSWORD_CHECK_INTERVAL=48
d stop_client d stop
initsetup
If the Exadata storage cells are unable to send email use usecompute, which will
send the email from the database server instead:
-testemail "NOTIFICATION_EMAIL=some.person@acompany.com" -usecompute
or
-sendemail "NOTIFICATION_EMAIL=some.person@acompany.com" -usecompute
Automatically discovers all databases and prompts for which should be checked
o Do not prompt but run all checks on all discovered database: dball
o Do not prompt and skip all database related checks: dbnone
o Only run checks against a subset of databases: dbnames <db_1>,<db_2>
If using sudo access to root from a lower privileged user id, temporary directory must be
reflected in /etc/sudoers file
<user> ALL=(root) NOPASSWD:<TEMPDIR>/.[orachk|exachk]/root_[orachk|exachk].sh
Merge multiple reports into one with merge and list of collection directories or zip
files: merge <collection_1>,<collection_2>
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
Health
Score Warning count
Ignore count
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
Can be excluded:
-excludeprofile user_defined_checks
APEX version:
Will determine the APEX version you
APEX 4.2: CollectionManager_App.sql
have and install the latest applicable
APEX 5.x: Apex5_CollectionManager_App.sql
Collection Manager app
3. Follow Health Check Collection Manager
If the Collection Manager schema
installation in the User Guide
changes in the future then ORAchk will
4. Login to Collection Manager Application prompt for auto upgrade
via a URL like the following:
http://hostname:port/apex/f?p=ApplicationID Note: APEX 4.2 version of CM app exists for backwards compatibility.
http://hostname:port/pls/apex/f?p=ApplicationID New features will only go into the APEX 5 Collection Manager app
-setdbupload RAT_UPLOAD_TABLE,RAT_PATCH_UPLOAD_TABLE
Debug output:
-javahome JDK8dirname RAT_JAVA_HOME Point to the JAVA_HOME directory for a JDK8 installation
-appjar dirname RAT_AC_JARDIR Point to the parent directory name for the code. Will analyze .class files, and recursively .jar files
and directories.
To enable for all session run: alter system set event='trace[progint_appcont_rdbms]' scope = spfile;
2. Run through the application functions. To report on an application function, it needs to have executed. The more application
functions run, the better the information that the coverage analysis provides.
3. Use ORAchk to analyze the collected database traces and report the level of protection, and where not protected, report why
Command-Line Argument Shell Environment Usage
Variable
asmhome jarfilename RAT_AC_ASMJAR Point to a version of asm-all-5.0.3.jar that you download from http://asm.ow2.org/
-javahome JDK8dirname RAT_JAVA_HOME Point to the JAVA_HOME directory for a JDK8 installation
-apptrc dirname RAT_AC_TRCDIR Directory name containing one or more database server trace files. The trace directory is
generally: $ORACLE_BASE/diag/rdbms/{DB_UNIQUE_NAME}/$ORACLE_SID/trace
2. Run : ./orachk
If the oraInst.loc file is not in the default directory then specify the 3. If database is running on a remote server, then extract
oraInventory directory using the RAC_INV_LOCAL environment variable.
For example: orachk_IAM.zip there
export RAT_INV_LOC=/scratch/shared/oracle/oraInventory
4. Run : ./orachk -idmdbruntime
or
-sendemail "NOTIFICATION_EMAIL=some.person@acompany.com" -usecompute
Copyright 2017, Oracle and/or its affiliates. All rights reserved. | 100
Virtualization
1. Run from dom0 on first compute to cover all dom0s, cells and switches
o Install EXAchk into the management domain (DOM0) & run as root
o Will discover all compute nodes, storage servers and InfiniBand switches in the entire InfiniBand fabric
and run EXAchk on all
o If a single machine has been separated into multiple management domains
Use -clusternodes, -cells, -ibswitches to detail the components of the separate management domains
clusternodes <node_1>, <node_2> cells <cell_1>,<cell_2> ibswitches <switch_1>,<switch_2>
Copyright 2017, Oracle and/or its affiliates. All rights reserved. | 101
Agenda
1 Features Common to both ORAchk & EXAchk
2 ORAchk Specific
3 EXAchk on Exadata
4 EXAchk on Exalogic
5 EXAchk on SuperCluster / MiniCluster
6 EXAchk on Exalytics
7 EXAchk on Big Data
Copyright 2017, Oracle and/or its affiliates. All rights reserved. | 102
Agenda
1 Features Common to both ORAchk & EXAchk
2 ORAchk Specific
3 EXAchk on Exadata
4 EXAchk on Exalogic
5 EXAchk on SuperCluster / MiniCluster
6 EXAchk on Exalytics
7 EXAchk on Big Data
Copyright 2017, Oracle and/or its affiliates. All rights reserved. | 103
Agenda
1 Features Common to both ORAchk & EXAchk
2 ORAchk Specific
3 EXAchk on Exadata
4 EXAchk on Exalogic
5 EXAchk on SuperCluster / MiniCluster
6 EXAchk on Exalytics
7 EXAchk on Big Data
Copyright 2017, Oracle and/or its affiliates. All rights reserved. | 104
Agenda
1 Features Common to both ORAchk & EXAchk
2 ORAchk Specific
3 EXAchk on Exadata
4 EXAchk on Exalogic
5 EXAchk on SuperCluster / MiniCluster
6 EXAchk on Exalytics
7 EXAchk on Big Data
Copyright 2017, Oracle and/or its affiliates. All rights reserved. | 105
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 Oracles products remains at the sole discretion of Oracle.
Copyright 2017, Oracle and/or its affiliates. All rights reserved. | 106
Copyright 2017, Oracle and/or its affiliates. All rights reserved. | 107