2. Run Compliance Checks
  3. Compliance Checking with Oracle Orachk and Oracle Exachk
  4. Running Compliance Checks Automatically

3.1.2 Running Compliance Checks Automatically

Oracle recommends that you use the daemon process to schedule recurring compliance checks at regular intervals.

Note:

Daemon mode is supported only on the Linux and Solaris operating systems.

Configure the daemon to:

  • Schedule recurring compliance checks at regular interval

  • Send email notifications when the compliance check runs complete, clearly showing any differences since the last run

  • Purge collection results after a pre-determined period

  • Check and send email notification about stale passwords

  • Store multiple profiles for automated compliance check runs

  • Restart automatically if the server or node where it is running restarts

Note:

While running, the daemon answers all the prompts required by subsequent on-demand compliance checks.

To run on-demand compliance checks, do not use the daemon process started by others. Run on-demand compliance checks within the same directory where you have started the daemon.

If you change the system configuration such as adding or removing servers or nodes, then restart the daemon.

Related Topics

Parent topic: Compliance Checking with Oracle Orachk and Oracle Exachk

3.1.2.1 Setting and Getting Options for the Daemon

Set the daemon options before you start the daemon. Reset the daemon options anytime after starting the daemon.

To set the daemon options:

Set the daemon options using the –set option.

Set an option as follows:
$ orachk –set "option_1=option_1_value"
$ exachk –set "option_1=option_1_value"
Set multiple options using the name=value format separated by semicolons as follows:
$ orachk –set "option_1=option_1_value;option_2=option_2_value;option_n=option_n_value"
$ exachk –set "option_1=option_1_value;option_2=option_2_value;option_n=option_n_value"
  • AUTORUN_SCHEDULE
    Schedule recurring compliance check runs using the AUTORUN_SCHEDULE daemon option.
  • AUTORUN_FLAGS
    The AUTORUN_FLAGS daemon option determines how compliance checks are run.
  • NOTIFICATION_EMAIL
    Set the NOTIFICATION_EMAIL daemon option to send email notifications to the recipients you specify.
  • collection_retention
    Set the collection_retention daemon option to purge health check collection results that are older than a specified number of days.
  • PASSWORD_CHECK_INTERVAL
    The PASSWORD_CHECK_INTERVAL daemon option defines the frequency, in hours, for the daemon to validate the passwords entered when the daemon was started the first time.
  • Setting Multiple Option Profiles for the Daemon
    Use only one daemon process for each server. Do not start a single daemon on multiple databases in a cluster, or multiple daemons on the same database.
  • Getting Existing Options for the Daemon
    Query the values that you set for the daemon options.

Related Topics

Parent topic: Running Compliance Checks Automatically

3.1.2.1.1 AUTORUN_SCHEDULE

Schedule recurring compliance check runs using the AUTORUN_SCHEDULE daemon option.

To schedule recurring compliance check runs:

Set the AUTORUN_SCHEDULE option, as follows:
AUTORUN_SCHEDULE=minute hour day month day_of_week

Where:

  • minute

    Valid values: 0-59 (Optional. If omitted, then 0 is used)

    Allowed special characters: * , - /

  • hour is 0–23

    Valid values: 0–23

    Allowed special characters: * , - /

  • day

    Valid values: 1–31

    Allowed special characters: * , -

  • month

    Valid values: 1–12 or JAN–DEC

    Allowed special characters: * , -

  • day_of_week

    Valid values: 0–6 or SUN–SAT

    Allowed special characters: * , -

Asterisk (*): Use the asterisk (*) as a wildcard to specify multiple values separated by commas.

Comma (,): Use commas to separate items of a list. For example, using "MON,WED,FRI" in the 5th field (day of week) means Mondays, Wednesdays and Fridays.

Dash (-): Use dash to define ranges.

Slash (/): Use slashes combined with ranges to specify step values. For example, */5 in the minutes field indicates every 5 minutes (see note below about frequencies). It is shorthand for the more verbose form 5,10,15,20,25,30,35,40,45,50,55,00.

Note:

Frequencies, in general, cannot be expressed; only step values, which evenly divide their range express accurate frequencies.
  • For minutes: /2, /3, /4, /5, /6, /10, /12, /15, /20 and /30 because 60 is evenly divisible by those numbers
  • For hours: /2, /3, /4, /6, /8 and /12

Table 3-1 AUTORUN_SCHEDULE

Example Result

"AUTORUN_SCHEDULE=0,15,30,45 * * * *"

Runs every 15 minutes.

"AUTORUN_SCHEDULE=* * * *"

Runs every hour.

"AUTORUN_SCHEDULE=3 * * 0"

Runs at 3 AM every Sunday.

"AUTORUN_SCHEDULE=2 * * 1, 3, 5"

Runs at 2 AM on Monday, Wednesday, and Friday.

"AUTORUN_SCHEDULE=4 1 * *"

Runs at 4 AM on the first day of every month.

"AUTORUN_SCHEDULE=8,20 * * 1, 2, 3, 4, 5"

Runs at 8 AM and 8 PM every Monday, Tuesday, Wednesday, Thursday, and Friday.

"AUTORUN_SCHEDULE=*/5 2-4 * JAN 2"

Runs every 5 minutes at 2,3,4 AM every Tuesday in the month of January.

"AUTORUN_SCHEDULE=*/1 * * * *"

Runs every minute.

"AUTORUN_SCHEDULE=*/5 0-7 * 8 *"

Runs every 5 minutes at 12,1,2,3,4,5,6,7 AM every day in the month of August.

Example 3-2 AUTORUN_SCHEDULE

$ orachk –set "AUTORUN_SCHEDULE=3 * * 0"
$ exachk –set "AUTORUN_SCHEDULE=3 * * 0"

Optionally, you can specify the name of the profile. If you do not specify, then id=DEFAULT.

For example:
$ orachk -id dba -set "AUTORUN_SCHEDULE=3 * * 0"
$ exachk -id dba -set "AUTORUN_SCHEDULE=3 * * 0"

Parent topic: Setting and Getting Options for the Daemon

3.1.2.1.2 AUTORUN_FLAGS

The AUTORUN_FLAGS daemon option determines how compliance checks are run.

To configure how compliance checks should run:

Set the AUTORUN_FLAGS option as follows:
AUTORUN_FLAGS=flags

Where:

  • flags can be any combination of valid command-line flags.

Table 3-2 AUTORUN_FLAGS

Example Result

"AUTORUN_FLAGS=-profile dba"

Runs only the dba profile checks.

"AUTORUN_FLAGS=-profile sysadmin –tag syadmin"

Runs only the dba profile checks and tags the output with the value sysadmin.

-excludeprofile ebs

Runs all checks except the checks in the ebs profile.

Example 3-3 AUTORUN_FLAGS

$ orachk –set "AUTORUN_FLAGS=-profile sysadmin –tag sysadmin"
$ exachk –set "AUTORUN_FLAGS=-profile sysadmin –tag sysadmin"

Parent topic: Setting and Getting Options for the Daemon

3.1.2.1.3 NOTIFICATION_EMAIL

Set the NOTIFICATION_EMAIL daemon option to send email notifications to the recipients you specify.

The daemon notifies the recipients each time a health check run completes or when the daemon experiences a problem.

To configure email notifications:

  1. Specify a comma-delimited list of email addresses, as follows:
    
$ orachk –set "NOTIFICATION_EMAIL=some.person@acompany.com,another.person@acompany.com"
    $ exachk –set "NOTIFICATION_EMAIL=some.person@acompany.com,another.person@acompany.com"

    Optionally, you can specify the name of the profile. If you do not specify, then id=DEFAULT.

    For example:
    $ orachk -id dba -set "NOTIFICATION_EMAIL=some.person@acompany.com,another.person@acompany.com"
    $ exachk -id dba -set "NOTIFICATION_EMAIL=some.person@acompany.com,another.person@acompany.com"
  2. Test the email notification configuration using the –testemail option, as follows:
    $ orachk -testemail all
    $ exachk -testemail all

After the first health check run, the daemon notifies the recipients with report output attached.

For the subsequent health check runs after the first email notification, the daemon emails the summary of differences between the most recent runs to all recipients specified in the NOTIFICATION_EMAIL list.

Related Topics

Parent topic: Setting and Getting Options for the Daemon

3.1.2.1.4 collection_retention

Set the collection_retention daemon option to purge health check collection results that are older than a specified number of days.

To configure collection retention period:

  1. Set the collection_retention option for automatic retention or the user_collection_retention option for on-demand retention, as follows:
    collection_retention=number_of_days
    user_collection_retention=number_of_days

    If you do not set this option, then the daemon does not purge the stale collections.

  2. Set the collection_retention or user_collection_retention option to an appropriate number of days based on:
    • Frequency of your scheduled collections
    • Size of the collection results
    • Available disk space
For example:
$ orachk –set "collection_retention=60"
$ exachk –set "collection_retention=60"
$ orachk –set "user_collection_retention=60"
$ exachk –set "user_collection_retention=60"

Parent topic: Setting and Getting Options for the Daemon

3.1.2.1.4.1 To Control Collection Retention Using Size
Set the size in MB using the environment variable RAT_PURGE_SIZE. When the health check collections consume the size specified, then Oracle Orachk starts purging the old collections, and retains the space specified using RAT_PURGE_SIZE.
For example:
$export RAT_PURGE_SIZE=4096

3.1.2.1.5 PASSWORD_CHECK_INTERVAL

The PASSWORD_CHECK_INTERVAL daemon option defines the frequency, in hours, for the daemon to validate the passwords entered when the daemon was started the first time.

If an invalid password is found due to a password change, then the daemon stops, makes an entry in the daemon log, and then sends an email notification message to the recipients specified in the NOTIFICATION_EMAIL option.

To configure password validation frequency:

  1. Set the PASSWORD_CHECK_INTERVAL option, as follows:
    PASSWORD_CHECK_INTERVAL=number_of_hours

    If you do not set the PASSWORD_CHECK_INTERVAL option, then the daemon cannot actively check password validity and fails the next time the daemon tries to run after a password change. Using the PASSWORD_CHECK_INTERVAL option enables you to take corrective action and restart the daemon with the correct password rather than having failed collections.

  2. Set the PASSWORD_CHECK_INTERVAL option to an appropriate number of hours based on:
    • Frequency of your scheduled collections
    • Password change policies
For example:
$ orachk –set "PASSWORD_CHECK_INTERVAL=1"
$ exachk –set "PASSWORD_CHECK_INTERVAL=1"

Related Topics

Parent topic: Setting and Getting Options for the Daemon

3.1.2.1.6 Setting Multiple Option Profiles for the Daemon

Use only one daemon process for each server. Do not start a single daemon on multiple databases in a cluster, or multiple daemons on the same database.

The daemon does not start, if the daemon detects another Oracle Autonomous Health Framework daemon process running locally.

Define multiple different run profiles using the same daemon. Defining multiple different run profiles enables you to run multiple different compliance checks with different daemon options, such as different schedules, email notifications, and automatic run flags. The daemon manages all profiles.

Define daemon option profiles using the –id id option before the –set option, where id is the name of the profile. 

$ orachk –id id –set "option=value"
$ exachk –id id –set "option=value"

To set multiple option profiles for the daemon:

For example, if the database administrator wants to run checks within the dba profile and the system administrator wants to run checks in the sysadmin profile, then configure the daemon using the profiles option.

  1. Define the database administrator profile as follows:
    $ orachk –id dba –set "NOTIFICATION_EMAIL=dba@example.com;\
   AUTORUN_SCHEDULE=4,8,12,16,20 * * *;AUTORUN_FLAGS=-profile dba –tag dba;\
   collection_retention=30"

Created notification_email for ID[dba]
Created autorun_schedule for ID[dba]
Created autorun_flags for ID[dba]
Created collection_retention for ID[dba]
    $ exachk –id dba –set "NOTIFICATION_EMAIL=dba@example.com;\
   AUTORUN_SCHEDULE=4,8,12,16,20 * * *; AUTORUN_FLAGS=-profile dba –tag dba;\
   collection_retention=30"

Created notification_email for ID[dba]
Created autorun_schedule for ID[dba]
Created autorun_flags for ID[dba]
Created collection_retention for ID[dba]
  2. Define the system administrator profile as follows:
    $ orachk –id sysadmin –set "NOTIFICATION_EMAIL=sysadmin@example.com;\
   AUTORUN_SCHEDULE=3 * * 1,3,5; AUTORUN_FLAGS=-profile sysadmin –tag sysadmin;\
   collection_retention=60"

Created notification_email for ID[sysadmin]
Created autorun_schedule for ID[sysadmin]
Created autorun_flags for ID[sysadmin]
Created collection_retention for ID[sysadmin]
    $ exachk –id sysadmin –set "NOTIFICATION_EMAIL=sysadmin@example.com;\
   AUTORUN_SCHEDULE=3 * * 1,3,5; AUTORUN_FLAGS=-profile sysadmin –tag sysadmin;\
   collection_retention=60"

Created notification_email for ID[sysadmin]
Created autorun_schedule for ID[sysadmin]
Created autorun_flags for ID[sysadmin]
Created collection_retention for ID[sysadmin]

Related Topics

Parent topic: Setting and Getting Options for the Daemon

3.1.2.1.7 Getting Existing Options for the Daemon

Query the values that you set for the daemon options.

To query the values, use [-id ID] -get option | all.

Where:
  • ID is a daemon option profile.
  • option is a specific daemon option you want to retrieve.
  • all returns values of all options.

To get existing options for the daemon:

  1. To get a specific daemon option: –get option
    $ orachk –get NOTIFICATION_EMAIL

ID: orachk.default
------------------------------------------
notification_email = some.body@example.com
    $ exachk –get NOTIFICATION_EMAIL

ID: exachk.default
------------------------------------------
notification_email = some.body@example.com
  2. To query multiple daemon option profiles: –get option:
    $ orachk –get NOTIFICATION_EMAIL

ID: orachk.default
------------------------------------------
notification_email = some.body@example.com

ID: dba
------------------------------------------
notification_email = dba@example.com

ID: sysadmin
------------------------------------------
notification_email = sysadmin@example.com
    $ exachk –get NOTIFICATION_EMAIL

ID: exachk.default
------------------------------------------
notification_email = some.person@example.com

ID: dba
------------------------------------------
notification_email = dba@example.com

ID: sysadmin
------------------------------------------
notification_email = sysadmin@example.com
  3. To limit the request to a specific daemon option profile: –id ID -get option
    To get the NOTIFICATION_EMAIL for a daemon profile called dba:
    $ orachk –id dba –get NOTIFICATION_EMAIL

ID: dba
------------------------------------------
notification_email = dba@example.com
    $ exachk –id dba –get NOTIFICATION_EMAIL

ID: dba
------------------------------------------
notification_email = dba@example.com
  4. To get all options set: –get all 
    $ orachk –get all

ID: orachk.default
------------------------------------------
notification_email = some.body@example.com
autorun_schedule = 3 * * 0
collection_retention = 30
password_check_interval = 1
    $ exachk –get all

ID: exachk.default
------------------------------------------
notification_email = some.body@example.com
autorun_schedule = 3 * * 0
collection_retention = 30
password_check_interval = 1
  5. To query all daemon option profiles: –get all
    $ orachk –get all

ID: orachk.default
------------------------------------------
notification_email = some.body@example.com
autorun_schedule = 3 * * 0
collection_retention = 30
password_check_interval = 12

ID: dba
------------------------------------------
notification_email = dba@example.com
autorun_schedule = 4,8,12,16,20 * * *
autorun_flags = -profile dba –tag dba
collection_retention = 30
password_check_interval = 1

ID: sysadmin
------------------------------------------
notification_email = sysadmin@example.com
autorun_schedule = 3 * * 1,3,5
autorun_flags = -profile sysadmin –tag sysadmin
collection_retension = 60
password_check_interval = 1
    $ exachk –get all

ID: exachk.default
------------------------------------------
notification_email = some.body@example.com
autorun_schedule = 3 * * 0
collection_retention = 30
password_check_interval = 1

ID: dba
------------------------------------------
notification_email = dba@example.com
autorun_schedule = 4,8,12,16,20 * * *
autorun_flags = -profile dba –tag dba
collection_retention = 30
password_check_interval = 1

ID: sysadmin
------------------------------------------
notification_email = sysadmin@example.com
autorun_schedule = 3 * * 1,3,5
autorun_flags = -profile sysadmin –tag sysadmin
collection_retension = 60
password_check_interval = 1
  6. To limit the request to a specific daemon option profile: –id ID -get all

    To get all the options set for a daemon profile called dba: 

    $ orachk –id dba –get all

ID: dba
------------------------------------------
notification_email = dba@example.com
autorun_schedule = 4,8,12,16,20 * * *
autorun_flags = -profile dba –tag dba
collection_retention = 30
password_check_interval = 1
    $ exachk –id dba –get all

ID: dba
------------------------------------------
notification_email = dba@example.com
autorun_schedule = 4,8,12,16,20 * * *
autorun_flags = -profile dba –tag dba
collection_retention = 30
password_check_interval = 1

Parent topic: Setting and Getting Options for the Daemon

3.1.2.2 Starting and Stopping the Daemon

Start and stop the daemon and force the daemon to stop a compliance check run.

To start and stop the daemon:

  1. To start the daemon:
    $ orachk -autostart
    $ orachk -autostart reset
    $ exachk -autostart
    $ exachk -autostart reset

    The tools prompt you to provide required information during startup.

  2. To stop the daemon:
    $ orachk -autostop
    $ orachk -autostop unset
    $ exachk -autostop
    $ exachk -autostop unset

    If a compliance check run is progress when you run the stop command, then the daemon indicates so and continues running.

  3. To force the daemon to stop a compliance check run:
    $ orachk -autostop
    $ orachk -autostop unset
    $ exachk -autostop
    $ exachk -autostop unset

The daemon stops the compliance check run and then confirms when it is done. If necessary, then stop the daemon using the -autostop option.

The window allows to setup a value to randomize the execution hour and minute to be set for each daemon schedule. By default, exachk sets 2:03 AM for exatier profile entry, and 3:03 AM for full run entry.

Regarding the hour, when using the window, if you setup autostart with a window of 5, and considering exachk uses 2 AM as default hour, that means that exachk will pick a value between 2AM +/-5 hours, that is, any hour between 9 PM and 7 AM. If the autostart window is 1, then hour value could be 1 AM, 2 AM, or 3 AM.

Regarding the minute, when using autorun window, the minute will be a randomized value between 0 and 59.

Note that the window applies only to the action of setting up the entry. It is not meant as a window applied for every time the scheduled entry runs. If the entry is setup to run at, let’s say, 4:15 AM, then it will run at that time the days scheduled.

Use cases:

  1. Using the RAT_AUTORUN_WINDOW variable from the environment before installing AHF

    When AHF is installed running the ahf_setup file, if the RAT_AUTORUN_WINDOW is set, then exachk scheduler will pick RAT_AUTORUN_WINDOW value and apply the window to the exachk scheduler entries. 

    # export RAT_AUTORUN_WINDOW=5
#  ./ahf_setup -ahf_loc /opt/oracle.ahf -data_dir /opt/oracle.ahf -silent  
# orachk -get all
------------------------------------------------------------
ID: orachk.autostart_client_oratier1
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -profile oratier1 -dball -showpass -tag autostart_client_oratier1 -readenvconfig
COLLECTION_RETENTION  =  7
AUTORUN_SCHEDULE  =  20 1 * * 1,2,3,4,5,6
------------------------------------------------------------
------------------------------------------------------------
ID: orachk.autostart_client
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -tag autostart_client -readenvconfig
COLLECTION_RETENTION  =  14
AUTORUN_SCHEDULE  =  15 3 * * 0
------------------------------------------------------------
    # export RAT_AUTORUN_WINDOW=5
# ./ahf_setup -ahf_loc /opt/oracle.ahf -data_dir /opt/oracle.ahf -silent    
# exachk -get all
------------------------------------------------------------
ID: exachk.autostart_client_exatier1
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -profile exatier1 -dball -showpass -tag autostart_client_exatier1 -readenvconfig
COLLECTION_RETENTION  =  7
AUTORUN_SCHEDULE  =  20 1 * * 1,2,3,4,5,6
------------------------------------------------------------
------------------------------------------------------------
ID: exachk.autostart_client
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -tag autostart_client -readenvconfig
COLLECTION_RETENTION  =  14
AUTORUN_SCHEDULE  =  15 3 * * 0
------------------------------------------------------------

    As seen above, the hour values belong to the window, and the minute value is a random value between 0 and 59.

  2. Using the -autorun_window <value> option while installing AHF

    The -autorun_window can be specified as an option when running ahf_setup. 

    # ./ahf_setup -ahf_loc /opt/oracle.ahf -data_dir /opt/oracle.ahf -silent -autorun_window 5
# orachk -get all
------------------------------------------------------------
ID: orachk.autostart_client_oratier1
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -profile oratier1 -dball -showpass -tag autostart_client_oratier1 -readenvconfig
COLLECTION_RETENTION  =  7
AUTORUN_SCHEDULE  =  24 6 * * 1,2,3,4,5,6
------------------------------------------------------------
------------------------------------------------------------
ID: orachk.autostart_client
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -tag autostart_client -readenvconfig
COLLECTION_RETENTION  =  14
AUTORUN_SCHEDULE  =  29 6 * * 0
------------------------------------------------------------
    # ./ahf_setup -ahf_loc /opt/oracle.ahf -data_dir /opt/oracle.ahf -silent -autorun_window 5
# exachk -get all
------------------------------------------------------------
ID: exachk.autostart_client_exatier1
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -profile exatier1 -dball -showpass -tag autostart_client_exatier1 -readenvconfig
COLLECTION_RETENTION  =  7
AUTORUN_SCHEDULE  =  24 6 * * 1,2,3,4,5,6
------------------------------------------------------------
------------------------------------------------------------
ID: exachk.autostart_client
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -tag autostart_client -readenvconfig
COLLECTION_RETENTION  =  14
AUTORUN_SCHEDULE  =  29 6 * * 0
------------------------------------------------------------

    Note:

    If RAT_AUTORUN_WINDOW is defined, and -autorun_window is passed, then the -autorun_window command-line option has more priority and the environment variable value will be ignored.

    When the RAT variable is set at install time, it will be stored automatically on the orachk and exachk environment file: 

    # cat `orachk -showenvfile`
RAT_AUTORUN_WINDOW=5

    # cat `exachk -showenvfile`
RAT_AUTORUN_WINDOW=5

    So the subsequent autostop and autostart commands will make use of the existent variable value in the environment file (when defined). Entry can be manually deleted from the file anytime.

  3. Using the existing RAT_AUTORUN_WINDOW value defined in orachk/exachk environment file

    As mentioned above, if the value exists in the environment file, then an autostart command will automatically read the value and apply the window: 

    # orachk -autostart
.
.
Applying execution time window of (+/-) 5 hours
Applying execution time window of (+/-) 5 hours
Successfully copied Daemon Store to Remote Nodes
.  .  .
orachk is using TFA Scheduler. TFA PID: 3964931

# orachk -get all
------------------------------------------------------------
ID: orachk.autostart_client_oratier1
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -profile oratier1 -dball -showpass -tag autostart_client_oratier1 -readenvconfig
COLLECTION_RETENTION  =  7
AUTORUN_SCHEDULE  =  42 23 * * 1,2,3,4,5,6
------------------------------------------------------------
------------------------------------------------------------
ID: orachk.autostart_client
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -tag autostart_client -readenvconfig
COLLECTION_RETENTION  =  14
AUTORUN_SCHEDULE  =  31 0 * * 0
------------------------------------------------------------
    >># exachk -autostart
.
.
Applying execution time window of (+/-) 5 hours
Applying execution time window of (+/-) 5 hours
Successfully copied Daemon Store to Remote Nodes
.  .  .
exachk is using TFA Scheduler. TFA PID: 3964931

# exachk -get all
------------------------------------------------------------
ID: exachk.autostart_client_exatier1
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -profile exatier1 -dball -showpass -tag autostart_client_exatier1 -readenvconfig
COLLECTION_RETENTION  =  7
AUTORUN_SCHEDULE  =  42 23 * * 1,2,3,4,5,6
------------------------------------------------------------
------------------------------------------------------------
ID: exachk.autostart_client
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -tag autostart_client -readenvconfig
COLLECTION_RETENTION  =  14
AUTORUN_SCHEDULE  =  31 0 * * 0
------------------------------------------------------------
  4. Using the -autorun_window option when calling exachk -autostart
    # orachk -autostart -autorun_window 4
.
.
Applying execution time window of (+/-) 4 hours
Applying execution time window of (+/-) 4 hours
Successfully copied Daemon Store to Remote Nodes
.  .  .
orachk is using TFA Scheduler. TFA PID: 3964931

# orachk -get all
------------------------------------------------------------
ID: orachk.autostart_client_oratier1
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -profile oratier1 -dball -showpass -tag autostart_client_oratier1 -readenvconfig
COLLECTION_RETENTION  =  7
AUTORUN_SCHEDULE  =  45 5 * * 1,2,3,4,5,6
------------------------------------------------------------
------------------------------------------------------------
ID: orachk.autostart_client
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -tag autostart_client -readenvconfig
COLLECTION_RETENTION  =  14
AUTORUN_SCHEDULE  =  24 6 * * 0
------------------------------------------------------------
    # exachk -autostart -autorun_window 4
.
.

Applying execution time window of (+/-) 4 hours
Applying execution time window of (+/-) 4 hours
Successfully copied Daemon Store to Remote Nodes

.  .  .
exachk is using TFA Scheduler. TFA PID: 3964931

# exachk -get all
------------------------------------------------------------
ID: exachk.autostart_client_exatier1
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -profile exatier1 -dball -showpass -tag autostart_client_exatier1 -readenvconfig
COLLECTION_RETENTION  =  7
AUTORUN_SCHEDULE  =  45 5 * * 1,2,3,4,5,6
------------------------------------------------------------
------------------------------------------------------------
ID: exachk.autostart_client
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -tag autostart_client -readenvconfig
COLLECTION_RETENTION  =  14
AUTORUN_SCHEDULE  =  24 6 * * 0
------------------------------------------------------------

Note:

Passing a value of 0 to the autorun window option, will disable the window even if the environment variable is set in the environment or in the exachk .env file.

Related Topics

Parent topic: Running Compliance Checks Automatically

3.1.2.3 Querying the Status and Next Planned Daemon Run

Query the status and next automatic run schedule of the running daemon.

To query the status and next planned daemon run:

  1. To check if the daemon is running:
    $ orachk -autostatus
    $ exachk -autostatus

    If the daemon is running, then the daemon confirms and displays the PID.

  2. To query more detailed information about the daemon:
    $ orachk -autostatus
    $ exachk -autostatus

    The daemon responds with the following information:

    • Node on which the daemon is installed
    • Version
    • Install location
    • Time when the daemon was started
  3. To query the next scheduled compliance check run:
    $ orachk -autostatus
    $ exachk -autostatus

    The daemon responds with details of schedule.

    If you have configured multiple daemon option profiles, then the output shows whichever is scheduled to run next.

Related Topics

Parent topic: Running Compliance Checks Automatically

3.1.2.4 Configuring the Daemon for Automatic Start

Installing Oracle Autonomous Health Framework as root on Linux or Solaris automatically sets up and runs the Oracle Orachk or Oracle Exachk daemon.

To configure the daemon to stop or start automatically:

Run these commands as root.

  1. To remove auto start configuration:
    • $ orachk -autostop
    • $ exachk -autostop
    To remove all default unmodified schedulers:
    • orachk -autostop unset
    • exachk -autostop unset
  2. To configure the daemon to start automatically:
    • $ orachk -autostart
    • $ exachk -autostart
    To start and load the default schedulers:
    • orachk -autostart reset
    • exachk -autostart reset

    The daemon runs a full local Oracle Orachk check once every week at 3 AM, and a partial run of the most impactful checks at 2 AM every day through the oratier1 or exatier1 profiles. The daemon automatically purges the oratier1 or exatier1 profile run that runs daily, after a week. The daemon also automatically purges the full local run after 2 weeks. You can change the daemon settings after enabling auto start.

    • $ orachk -autostart -monthly
    • $ exachk -autostart -monthly

    Use the -monthly option to configure the daemon to run a full local Oracle Orachk once every month, and a partial run of the most important checks at 2 AM every day through the oratier1 or exatier1 profiles.

Related Topics

Parent topic: Running Compliance Checks Automatically

3.1.2.5 Configuring the Daemon for Automatic Restart

By default, you must manually restart the daemon if you restart the server or node on which the daemon is running.

However, if you use the automatic restart option, the daemon restarts automatically after the server or node reboot.

Configure the daemons to auto restart as root.

To configure the daemon to restart automatically:

  1. To configure the daemon to restart automatically:
    $ orachk –initsetup
    $ exachk –initsetup

    The tool prompts you to provide the required information during startup.

    Note:

    Stop the daemon before running –initsetup, if the daemon is already running.
  2. To query automatic restart status of the daemon:
    $ orachk –initcheck
    $ exachk –initcheck
  3. To remove automatic restart configuration:
    $ orachk –initrmsetup
    $ exachk –initrmsetup

Related Topics

Parent topic: Running Compliance Checks Automatically