1.7 Behavior of Oracle ORAchk or Oracle EXAchk Daemon

AHF 23.9 includes a new command option reset to change the behavior of Oracle ORAchk or Oracle EXAchk daemon during autostart, autostop, and upgrade.

Command	Description
exachk -autostart reset orachk -autostart reset ahfctl compliance -autostart reset	Starts and loads the default schedulers.
exachk -autostop unset orachk -autostop unset ahfctl compliance -autostop unset	Removes all default unmodified schedulers.

Daemon behavior until AHF 23.8

The behavior of exachk -autostart, orachk -autostart, ahfctl compliance -autostart, and ahfctl upgrade are the same. The table below illustrates different scenarios of schedulers and their behavior before and after autostart and upgrade.

Before autostart/upgrade	After autostart/upgrade
Default schedulers	Default schedulers
User-defined + default schedulers	User-defined
Only user-defined	Only user-defined
User-defined + modified default schedulers	User-defined + modified default schedulers
2 default schedulers: One modified default and the other is not	Only modified default scheduler
Only one default scheduler out of 2 default schedulers	Both default schedulers
No schedulers	No schedulers

The table below illustrates different scenarios of schedulers and their behavior before and after exachk -autostart, orachk -autostart, and ahfctl compliance -autostart.

Before autostop	After autostop
Default schedulers	No schedulers
User-defined + default schedulers	User-defined schedulers only
Only user-defined	Only user-defined
User-defined + modified default schedulers	User-defined + modified default schedulers
2 default schedulers: One modified default and the other is not	Only modified default scheduler
Only one default scheduler out of 2 default schedulers	No scheduler
No scheduler	No scheduler

Daemon behavioral changes in AHF 23.9

The behavior of exachk -autostart, orachk -autostart, ahfctl compliance -autostart, and ahfctl upgrade remains the same as in AHF 23.8. There will be no changes to the scheduler entries be it default schedulers or user-defined schedulers.

Before autostart/upgrade or autostop and then autostart	After autostart/upgrade or autostop and then autostart
Default schedulers	Default schedulers
User-defined + default schedulers	User-defined + default schedulers
Only user-defined	Only user-defined
User-defined + modified default schedulers	User-defined + modified default schedulers
2 default schedulers: One modified default and the other is not	2 default schedulers: One modified default and the other is not
Only one default scheduler out of 2 default schedulers	Only one default scheduler out of 2 default schedulers
No schedulers	No schedulers

The table below illustrates the behavior after autostart reset.

Before -autostart reset	After -autostart reset
Default schedulers	Default schedulers
User-defined + default schedulers	Default schedulers
Only user-defined	Default schedulers
User-defined + modified default schedulers	Default schedulers
2 default schedulers: One modified default and the other is not	Default schedulers
Only one default scheduler out of 2 default schedulers	Default schedulers
No schedulers	Default schedulers

The table below illustrates the behavior when autostop unset is run and then autostart.

Before -autostop unset and then autostart	After -autostop unset and then autostart
Default schedulers	No schedulers
User-defined + default schedulers	User-defined
Only user-defined	Only user-defined
User-defined + modified default schedulers	User-defined + modified default schedulers
2 default schedulers: One modified default and the other is not	Only modified default scheduler
Only one default scheduler out of 2 default schedulers	No schedulers
No schedulers	No schedulers

Use Cases

Use case	Outcome
-autostop and then -autostart	autostop will only deconfigure the compliance and autostart will start the compliance and load all the schedulers that were present before autostop.
-autostop unset and then -autostart	autostop unset will deconfigure the compliance and remove all the default unmodified schedulers and autostart will start the compliance and load the user-defined schedulers and modified default schedulers if they exist.
-autostop and then -autostart reset	autostop will only deconfigure the compliance and autostart reset will start the compliance and only load the default schedulers.
-autostop unset and then -autostart reset	autostop unset will deconfigure the compliance and remove all the default unmodified schedulers and autostart reset will start the compliance and only load the default schedulers.

Example 1-1 exachk -autostop unset, exachk -autostart reset, and exachk -get all

# exachk -autostop unset
Removing exachk cache discovery....
Successfully completed exachk cache discovery removal.
Successfully copied Daemon Store to Remote Nodes
 
# exachk -autostart reset
Successfully copied Daemon Store to Remote Nodes
exachk is using TFA Scheduler. TFA PID: 113253
Daemon log file location is : /opt/oracle.ahf/data/test-server/exachk/user_root/output/exachk_daemon.log
 
# exachk -get all
------------------------------------------------------------
Scheduled runs:
------------------------------------------------------------
ID: exachk.autostart_client_exatier1
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -profile exatier1 -dball -showpass -tag autostart_client_exatier1 -readenvconfig
AUTORUN_SCHEDULE  =  3 2 * * 1,2,3,4,5,6
COLLECTION_RETENTION  =  7
------------------------------------------------------------
------------------------------------------------------------
ID: exachk.autostart_client
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -tag autostart_client -readenvconfig
AUTORUN_SCHEDULE  =  3 3 * * 0
COLLECTION_RETENTION  =  14
------------------------------------------------------------

Example 1-2 exachk -autostop unset and exachk -get all

# exachk -autostop unset
Removing exachk cache discovery....
Successfully completed exachk cache discovery removal.
Successfully copied Daemon Store to Remote Nodes
 
# exachk -get all
No scheduler for any ID

Example 1-3 exachk -autostart reset and exachk -get all

# exachk -autostart reset
Successfully copied Daemon Store to Remote Nodes
exachk is using TFA Scheduler. TFA PID: 113253
Daemon log file location is : /opt/oracle.ahf/data/test-server/exachk/user_root/output/exachk_daemon.log
 
# exachk -get all
------------------------------------------------------------
Scheduled runs:
------------------------------------------------------------
ID: exachk.autostart_client_exatier1
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -profile exatier1 -dball -showpass -tag autostart_client_exatier1 -readenvconfig
AUTORUN_SCHEDULE  =  3 2 * * 1,2,3,4,5,6
COLLECTION_RETENTION  =  7
------------------------------------------------------------
------------------------------------------------------------
ID: exachk.autostart_client
------------------------------------------------------------
AUTORUN_FLAGS  =  -usediscovery -tag autostart_client -readenvconfig
AUTORUN_SCHEDULE  =  3 3 * * 0
COLLECTION_RETENTION  =  14
------------------------------------------------------------