Installing Oracle Autonomous Health Framework

2.5.1.1 Prerequisites for Configuring Oracle Autonomous Health Framework

Review the prerequisites to configure Oracle Autonomous Health Framework.

Minimum disk storage space for AHF Software directory: at least 3 GB
AHF Software directory is ahf_loc (ahf_home) flag value where AHF software is placed, for example, /opt/oracle.ahf.
Minimum disk storage space for AHF Data directory: at least 5 GB
However, it is advisable to set based on the customer environment and requirements. For example, when a cluster has many nodes or many databases running or if the customers want to keep reports/collections for longer period.

AHF Data directory is data_dir (ahf_data) flag value where AHF data and collections are generated, for example, /u01/oracle/grid/oracle.ahf/data or /opt/oracle.ahf/data
Minimum disk storage space for /tmp location: at least 2 GB

Parent topic: Installing Oracle Autonomous Health Framework

2.5.1.2 Installing Oracle Autonomous Health Framework on Linux

Install Oracle Autonomous Health Framework as root to obtain the fullest capabilities. Oracle Autonomous Health Framework has reduced capabilities when you install it as a non-root user.

(Recommended) Installing on Linux or Unix as root User in Daemon Mode
To obtain the fullest capabilities of Oracle Autonomous Health Framework, install it as root.
Installing on Linux or UNIX as Non-root User in Non-Daemon Mode
If you are unable to install as root, then install Oracle Autonomous Health Framework as the Oracle home owner.
Running AHF on SELinux Enabled Systems
To run AHF on SELinux enabled systems, use this procedure.

Parent topic: Installing Oracle Autonomous Health Framework

2.5.1.2.1 (Recommended) Installing on Linux or Unix as root User in Daemon Mode

To obtain the fullest capabilities of Oracle Autonomous Health Framework, install it as root.

Note:

Perl version 5.10 or later is required to install Oracle Autonomous Health Framework.

Oracle Autonomous Health Framework maintains Access Control Lists (ACLs) to determine which users are allowed access. By default, the GRID_HOME owner and ORACLE_HOME owners have access to their respective diagnostics. No other users can perform diagnostic collections.

If Oracle Autonomous Health Framework is already installed, then reinstalling performs an upgrade to the existing location.

To install as root:

Download the Oracle Autonomous Health Framework zipped file, copy the downloaded file to the required machine, and then unzip the file.
To ensure that the environment has been set correctly, enter the following commands:
```
umask
env | more
```
Verify that the umask command displays a value of 22, 022, or 0022.
Run the ahf_setup command:
```
ahf_setup
```
If you plan to run only Oracle Orachk or Oracle Exachk and do not want to run any Oracle Trace File Analyzer processes, then use the install option of -extract -notfasetup.

The installation prompts you to do a local or cluster installation.

Cluster installation requires passwordless SSH user equivalency for root to all cluster nodes. If you have not already configured passwordless SSH user equivalency, then the installation optionally sets up passwordless SSH user equivalency and then removes at the end.

If you do not wish to use passwordless SSH, then you install Oracle Autonomous Health Framework on each host using a local installation. Run the tfactl syncnodes command to generate and deploy relevant SSL certificates.

Oracle Clusterware does not manage Oracle Autonomous Health Framework because Oracle Autonomous Health Framework must be available if Oracle Clusterware stops working.

The installation configures Oracle Autonomous Health Framework for auto-start. The implementation of auto-start is platform-dependent. Linux usesinit, or an init replacement, such as upstart or systemd and Microsoft Windows uses a Windows service.

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

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.

To remove auto start:

orachk -autostop
exachk -autostop

To remove all default unmodified schedulers:

orachk -autostop unset
exachk -autostop unset

To auto start, run:

orachk -autostart
orachk -autostart

The installer prompts you to specify one or more email addresses of the recipients who can receive diagnostic notifications. Oracle Autonomous Health Framework notifies the recipients with the results of Oracle Orachk and Oracle Exachk compliance checking, or when Oracle Autonomous Health Framework detects significant faults.

To start and load the default schedulers:

orachk -autostart reset
exachk -autostart reset

2.5.1.2.2 Installing on Linux or UNIX as Non-root User in Non-Daemon Mode

If you are unable to install as root, then install Oracle Autonomous Health Framework as the Oracle home owner.

Note:

Perl version 5.10 or later is required to install Oracle Autonomous Health Framework.
You cannot perform cluster-wide installation as a non-root user.

Oracle Autonomous Health Framework has reduced capabilities when you install it as the non-root user in non-daemon mode. Therefore, you cannot complete the following tasks:

Automate diagnostic collections
Collect diagnostics from remote hosts
Collect files that are not readable by the Oracle home owner, for example, /var/log/messages, or certain Oracle Grid Infrastructure logs

To install as the Oracle home owner, use the –ahf_loc option, and optionally specify the -notfasetup option to prevent the running of any Oracle Trace File Analyzer processes.

ahf_setup -ahf_loc install_dir [-notfasetup]

For more information, run ahf_setup -h.

Parent topic: Installing Oracle Autonomous Health Framework on Linux

2.5.1.2.3 Running AHF on SELinux Enabled Systems

To run AHF on SELinux enabled systems, use this procedure.

SELinux Modes

Disabled: SElinux is disabled.
Permissive: SELinux prints warnings instead of enforcing.
Enforcing: SELinux security policy is enforced.

You can enable or disable SELinux. When enabled, SELinux can run in either enforcing or permissive modes. To check the status of SELinux, run the getenforce or sestatus commands. The getenforce command returns Enforcing, Permissive, or Disabled.

/usr/sbin/getenforce
Permissive

The sestatus command returns the SELinux status and the SELinux policy being used:

/usr/sbin/sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: permissive
Mode from config file: permissive
Policy MLS status: enabled
Policy deny_unknown status: allowed
Memory protection checking: actual (secure)
Max kernel policy version: 31

Installing AHF in Permissive or Enforcing Mode

AHF installer loads the policy and sets relevant contexts.

Installing AHF in Disabled Mode

AHF is installed successfully. However, later if you switch the mode to Permissive or Enforcing, then SELinux starts blocking the AHF processes.

To run AHF, load the SELinux policy:

ahfctl loadpolicy
Checking if policy exists 
Please wait while the policy is being loaded, it might take couple of minutes.
Successfully loaded SELinux policy
Restarting TFA...

To check if the policy is loaded successfully, run the following command:

/usr/sbin/semodule -l | grep inittfa-policy

To unload the SELinux policy:

ahfctl unloadpolicy
Please wait while the policy is being removed, it might take couple of minutes.
Successfully removed Contexts and Policy

Parent topic: Installing Oracle Autonomous Health Framework on Linux

2.5.1.3 Installing AHF on Microsoft Windows

Install Oracle Trace File Analyzer as a Microsoft Windows service. Run the AHF compliance framework (Oracle Orachk/Oracle Exachk) on-demand.

Note:

You cannot install Oracle Autonomous Health Framework into a directory if there is a space in the name of the directory, for example, Program Files.

Strawberry Perl for Windows version 5.30 or later (OR) Perl 5 version 28 binaries located in Grid home, and .NET Framework version 4.0.30319 or later

Note:

AHF Notification Email and MOS functionalities are not supported on Microsoft Windows systems. AHF will not prompt you with the following messages while installing on Windows systems.

Do you want to add AHF Notification Email IDs ? [Y]|N :
Do you want AHF to store your My Oracle Support Credentials for Automatic
Upload ? Y|[N] :

Copy the downloaded zip file to a temporary location on a required machine, and then unzip it.
Open a command prompt as administrator, and then run the installer script by specifying a Perl home and the location where you want to install Oracle Autonomous Health Framework, for example:
```
installahf.bat -perlhome D:\oracle\product\12.2.0\dbhome_1\perl -ahf_loc c:\AHF
```
You can also run installahf.bat -perlhome D:\oracle\product\12.2.0\dbhome_1\perl and provide AHF location during installation when the installer prompts.
To install AHF on Oracle Grid Infrastructure:
```
installahf.bat -crshome crshome_path
```

For clusterwide AHF setup, perform a local installation on each host, and then run the tfactl syncnodes command to generate and deploy relevant SSL certificates.

Related Topics

Determine which .NET Framework versions are installed

Parent topic: Installing Oracle Autonomous Health Framework

2.5.1.4 Installing AHF on Oracle Big Data Appliance

Run the ahf_setup command to run Oracle Autonomous Health Framework on the Oracle Big Data Appliance.

Download the Oracle Autonomous Health Framework zipped file to a directory on the Oracle Big Data Appliance, as root user.
Run the ahf_setup command and you can optionally specify the –extract option.
```
ahf_setup -ahf_loc install_dir
```
For more information, run ahf_setup -help.

Parent topic: Installing Oracle Autonomous Health Framework

2.5.1.5 Installing AHF on Oracle Exadata Dom0

To run AHF scheduler on Oracle Exadata dom0, follow these steps:

Standalone: Extracts only the AHF bits.
Typical: Performs full install including configuring scheduling for important features like compliance checking.

AHF in Standalone (default) Mode on Exadata dom0

To install AHF in standalone (default) mode on dom0:

# ./ahf_setup

AHF Installer for Platform Linux Architecture x86_64

AHF Installation Log : /tmp/ahf_install_242000_45942_2024_02_27-22_19_10.log

Starting Autonomous Health Framework (AHF) Installation

AHF Version: 24.2.0 Build Date: 202402262228

Default AHF Location : /opt/oracle.ahf

Do you want to install AHF at [/opt/oracle.ahf] ? [Y]|N :

AHF Location : /opt/oracle.ahf

AHF Data Directory : /EXAVMIMAGES/oracle.ahf/data

Extracting AHF to /opt/oracle.ahf

Setting up AHF CLI and SDK

AHF is deployed at /opt/oracle.ahf

EXAchk is available at /opt/oracle.ahf/bin/exachk

AHF binaries are available in /opt/oracle.ahf/bin

Do you want to start TFA and EXAchk schedulers Y|[N] :

AHF is successfully Installed

Moving /tmp/ahf_install_242000_45942_2024_02_27-22_19_10.log to /EXAVMIMAGES/oracle.ahf/data/scam02db01/diag/ahf/

Convert AHF Standalone (default) Installation to Typical Installation

To convert AHF Standalone (default) installation to Typical installation:

# ./ahf_setup -upgradetotypical -silent

AHF Installer for Platform Linux Architecture x86_64

AHF Installation Log : /tmp/ahf_install_242000_123646_2024_02_27-22_50_39.log

Starting Autonomous Health Framework (AHF) Installation

AHF Version: 24.2.0 Build Date: 202402262228

AHF Location : /opt/oracle.ahf

Installed AHF Version: 24.1.1 Build Date: 202402210742

AHF Data Directory : /EXAVMIMAGES/oracle.ahf/data

Extracting AHF to /opt/oracle.ahf

Setting up AHF CLI and SDK

AHF is deployed at /opt/oracle.ahf

EXAchk is available at /opt/oracle.ahf/bin/exachk

AHF binaries are available in /opt/oracle.ahf/bin

Configuring TFA Services

Discovering Nodes and Oracle Resources

Successfully generated certificates.

Starting TFA Services
Created symlink from /etc/systemd/system/multi-user.target.wants/oracle-tfa.service to /etc/systemd/system/oracle-tfa.service.
Created symlink from /etc/systemd/system/graphical.target.wants/oracle-tfa.service to /etc/systemd/system/oracle-tfa.service.

.---------------------------------------------------------------------------------.
| Host       | Status of TFA | PID    | Port | Version    | Build ID              |
+------------+---------------+--------+------+------------+-----------------------+
| scam02db01 | RUNNING       | 143538 | 5000 | 24.2.0.0.0 | 240200020240226222853 |
'------------+---------------+--------+------+------------+-----------------------'

Running TFA Inventory...

Adding default users to TFA Access list...

.----------------------------------------------------------------.
|                  Summary of AHF Configuration                  |
+-----------------+----------------------------------------------+
| Parameter       | Value                                        |
+-----------------+----------------------------------------------+
| AHF Location    | /opt/oracle.ahf                              |
| TFA Location    | /opt/oracle.ahf/tfa                          |
| Exachk Location | /opt/oracle.ahf/exachk                       |
| Data Directory  | /EXAVMIMAGES/oracle.ahf/data                 |
| Repository      | /EXAVMIMAGES/oracle.ahf/data/repository      |
| Diag Directory  | /EXAVMIMAGES/oracle.ahf/data/scam02db01/diag |
'-----------------+----------------------------------------------'

Starting EXAchk Scheduler from AHF

AHF is successfully Installed

Moving /tmp/ahf_install_242000_123646_2024_02_27-22_50_39.log to /EXAVMIMAGES/oracle.ahf/data/scam02db01/diag/ahf/

The -silent option is used to avoid user prompt.

AHF is upgraded from Standalone to Typical and the Standalone data directory /opt is moved to /EXAVMIMAGES.

AHF Scheduler on Local Exadata dom0 - Install Locally and Synchronize at the End

To run AHF scheduler on Exadata dom0:

# ./ahf_setup -scheduler

AHF Installer for Platform Linux Architecture x86_64

AHF Installation Log : /tmp/ahf_install_242000_240604_2024_02_27-22_32_31.log

Starting Autonomous Health Framework (AHF) Installation

AHF Version: 24.2.0 Build Date: 202402262228

AHF Location : /opt/oracle.ahf

AHF Data Directory : /EXAVMIMAGES/oracle.ahf/data

Do you want to add AHF Notification Email IDs ? [Y]|N : N

Extracting AHF to /opt/oracle.ahf

Setting up AHF CLI and SDK

Configuring TFA Services

Discovering Nodes and Oracle Resources

Successfully generated certificates.

Starting TFA Services

.---------------------------------------------------------------------------------.
| Host       | Status of TFA | PID    | Port | Version    | Build ID              |
+------------+---------------+--------+------+------------+-----------------------+
| scam02db01 | RUNNING       | 254226 | 5000 | 24.2.0.0.0 | 240200020240226222853 |
'------------+---------------+--------+------+------------+-----------------------'

Running TFA Inventory...

Adding default users to TFA Access list...

.----------------------------------------------------------------.
|                  Summary of AHF Configuration                  |
+-----------------+----------------------------------------------+
| Parameter       | Value                                        |
+-----------------+----------------------------------------------+
| AHF Location    | /opt/oracle.ahf                              |
| TFA Location    | /opt/oracle.ahf/tfa                          |
| Exachk Location | /opt/oracle.ahf/exachk                       |
| Data Directory  | /EXAVMIMAGES/oracle.ahf/data                 |
| Repository      | /EXAVMIMAGES/oracle.ahf/data/repository      |
| Diag Directory  | /EXAVMIMAGES/oracle.ahf/data/scam02db01/diag |
'-----------------+----------------------------------------------'

Starting EXAchk Scheduler from AHF

AHF binaries are available in /opt/oracle.ahf/bin

AHF is successfully Installed

Do you want AHF to store your My Oracle Support Credentials for Automatic Upload ? Y|[N] :

Moving /tmp/ahf_install_242000_240604_2024_02_27-22_32_31.log to /EXAVMIMAGES/oracle.ahf/data/scam02db01/diag/ahf/

This will install AHF scheduler only on local dom0. After installing, synchronize Oracle Trace File Analyzer. There are two ways to synchronize Oracle Trace File Analyzer.

Using SSH password:

After installing AHF scheduler on all the dom0s, run the tfactl syncnodes command on any one of the nodes to synchronize Oracle Trace File Analyzer. When prompted provide a comma-delimited list of remote nodes.

# tfactl syncnodes

Please Enter all the remote nodes you want to sync...

Enter Remote Node List (separated by space) : node2

Node List to sync TFA Certificates :
     1  node2

Syncing TFA Certificates on node2 :

TFA_HOME on node2 : /opt/oracle.ahf/tfa
DATA_DIR on node2 : /opt/oracle.ahf/data/node2/tfa
Shutting down TFA on node2...
Copying TFA Certificates to node2...
Copying SSL Properties to node2...
Sleeping for 5 seconds...
Starting TFA on node2...

Trying to add node2 to TFA...
.------------------------------------------------------------------------------------------------------.
| Host          | Status of TFA | PID    | Port | Version    | Build ID             | Inventory Status |
+---------------+---------------+--------+------+------------+----------------------+------------------+
| node1         | RUNNING       | 148216 | 5000 | 22.1.0.0.0 | 22100020220411155753 | COMPLETE         |
| node2         | RUNNING       |  95897 | 5000 | 22.1.0.0.0 | 22100020220405120331 | COMPLETE         |
'---------------+---------------+--------+------+------------+----------------------+------------------'

Using sockets:

After installing AHF scheduler on all the dom0s, run the tfactl syncnodes -nodes comma-delimited-list-of-all-dom0s command on all the dom0 nodes to synchronize Oracle Trace File Analyzer.

# tfactl syncnodes -nodes node1,node2

Exadata Dom0 Node List : node1,node2

Please wait for 3 to 5 minutes for sync to complete.

.----------------------------------------------------------------------------------------------------.
| Host       | Status of TFA | PID   | Port | Version     | Build ID             | Inventory Status |
+------------+---------------+-------+------+-------------+-----------------------+------------------+
| node1      | RUNNING       |   581 | 5000 | 23.10.0.0.0 |231000020231013114958 | COMPLETE         |
| node2      | RUNNING       | 52602 | 5000 | 23.10.0.0.0 |231000020231013114958 | COMPLETE         |
'------------+---------------+-------+------+-------------+-----------------------+------------------'

SYNC MESSAGE : TFA Synced on all Cluster Nodes
.--------------------------.
| Node       | Sync Status |
+------------+-------------+
| node1      | SYNCED      |
| node2      | SYNCED      |
'------------+-------------'

AHF Scheduler on all Exadata dom0 - Recommended

To run AHF scheduler on all Exadata dom0 and synchronize the nodes: ahf_setup -scheduler -nodes comma-delimited-list-of-remote-dom0s.

# ahf_setup -scheduler -nodes node2
AHF Installer for Platform Linux Architecture x86_64
AHF Installation Log : /tmp/ahf_install_221000_239748_2022_04_05-05_08_14.log
Starting Autonomous Health Framework (AHF) Installation
AHF Version: 22.1.0 Build Date: 202204051203
Default AHF Location : /opt/oracle.ahf
Do you want to install AHF at [/opt/oracle.ahf] ? [Y]|N :
AHF Location : /opt/oracle.ahf
AHF Data Directory stores diagnostic collections and metadata.
AHF Data Directory requires at least 5GB (Recommended 10GB) of free space.
Please Enter AHF Data Directory : /opt/oracle.ahf
AHF Data Directory : /opt/oracle.ahf/data
Do you want to add AHF Notification Email IDs ? [Y]|N : n
AHF will also be installed/upgraded on these Cluster Nodes :
1. node2
The AHF Location and AHF Data Directory must exist on the above nodes
AHF Location : /opt/oracle.ahf
AHF Data Directory : /opt/oracle.ahf/data
Extracting AHF to /opt/oracle.ahf
Configuring TFA Services
Discovering Nodes and Oracle Resources
Successfully generated certificates.
Starting TFA Services
Created symlink from /etc/systemd/system/multi-user.target.wants/oracle-tfa.service to /etc/systemd/system/oracle-tfa.service.
Created symlink from /etc/systemd/system/graphical.target.wants/oracle-tfa.service to /etc/systemd/system/oracle-tfa.service.

.-----------------------------------------------------------------------------------.
| Host          | Status of TFA | PID    | Port | Version    | Build ID             |
+---------------+---------------+--------+------+------------+----------------------+
| node1         | RUNNING       | 261388 | 5000 | 22.1.0.0.0 | 22100020220405120331 |
'---------------+---------------+--------+------+------------+----------------------'

Running TFA Inventory...
Adding default users to TFA Access list...

.-----------------------------------------------------------.
|                Summary of AHF Configuration               |
+-----------------+-----------------------------------------+
| Parameter       | Value                                   |
+-----------------+-----------------------------------------+
| AHF Location    | /opt/oracle.ahf                         |
| TFA Location    | /opt/oracle.ahf/tfa                     |
| Exachk Location | /opt/oracle.ahf/exachk                  |
| Data Directory  | /opt/oracle.ahf/data                    |
| Repository      | /opt/oracle.ahf/data/repository         |
| Diag Directory  | /opt/oracle.ahf/data/node1/diag	|	
'-----------------+-----------------------------------------'

Starting exachk scheduler from AHF ...
AHF install completed on node1
Installing AHF on Remote Nodes :
AHF will be installed on node2, Please wait.
Installing AHF on node2 :
[node2] Copying AHF Installer
[node1] Running AHF Installer
[node2] Syncing TFA Certificates
[node2] Restarting TFA

.------------------------------------------------------------------------------------------------------.
| Host          | Status of TFA | PID    | Port | Version    | Build ID             | Inventory Status |
+---------------+---------------+--------+------+------------+----------------------+------------------+
| node1         | RUNNING       | 261388 | 5000 | 22.1.0.0.0 | 22100020220405120331 | COMPLETE         |
| node2         | RUNNING       | 113878 | 5000 | 22.1.0.0.0 | 22100020220405120331 | COMPLETE         |
'---------------+---------------+--------+------+------------+----------------------+------------------'

AHF binaries are available in /opt/oracle.ahf/bin
AHF is successfully installed
Do you want AHF to store your My Oracle Support Credentials for Automatic Upload ? Y|[N] : n
Moving /tmp/ahf_install_221000_239748_2022_04_05-05_08_14.log to /opt/oracle.ahf/data/node1/diag/ahf/

For more information about managing CPU and memory resources on dom0, see Running AHFCTL Commands to Limit CPU and Memory Usage.

Related Topics

Running AHFCTL Commands to Limit CPU and Memory Usage

Parent topic: Installing Oracle Autonomous Health Framework

2.5.1.6 Group Permissions for Oracle Exachk Results Directories and Files

Note:

Not applicable to Microsoft Windows.

During AHF installation, the installer runs the $ORACLE_HOME/bin/osdbagrp command to get the default operating system group and grants 750 permission to the default operating system group till the user_root directory.
```
# cat install.properties | grep EXACHK_DATA_DIR
EXACHK_DATA_DIR=/opt/oracle.ahf/data/adcs/exachk
```
```
# ls -l /opt/oracle.ahf/data/adcs/exachk | grep user_root
drwxr-x--t 4 root dba  4096 May 18 14:34 user_root
```
Each time either orachk or exachk is run,
- The default operating system group is set with permission 750 on the output directory and the directories within it.
```
# ls -l /opt/oracle.ahf/data/adcs/exachk/user_root | grep output
drwxr-x--t 5 root dba  4096 May 22 08:27 output
```
- The default operating system group is set with permission 750 on the upload directory.
```
# ls -lrt /opt/oracle.ahf/data/adcs/exachk/user_root/output/<collection_dir> | grep upload
drwxr-x--- 2 root dba  4096 May 23 06:32 upload
```
- The default operating system group is set with permission 640 on all of the JSON files within the upload direcoty.
```
# ls -lrt /opt/oracle.ahf/data/adcs/exachk/user_root/output/exachk_adcs_rac19c_052322_063119/upload | grep .*.json
-rw-r----- 1 root dba  3068 May 23 06:32 exachk_summary.json
-rw-r----- 1 root dba  2463 May 23 06:32 adcs_exachk_valid_results.json
-rw-r----- 1 root dba  5675 May 23 06:32 check_env.json
```
Use the ahfctl setosgroup command to change the default operating system group any time you want. This group change will reflect on the user_root directory. Similarly, the respective runs will have the new group.
```
ahfctl setosgroup [-h] [-group GROUP]
```
For example, to set the default operating system group to dba, run the ahfctl setosgroup -group dba command.
Use the ahfctl getosgroup command to get the default operating system group configured.
```
$ ahfctl getosgroup
os_group: dba
```

Parent topic: Installing Oracle Autonomous Health Framework

2.5.1.7 Configure MOS Upload While Installing or Upgrading AHF

Use the -setupmos or -nosetupmos command options to configure MOS upload while installing or upgrading AHF.

Note:

If you have already configured MOS upload on the cluster nodes, then you will not be prompted to enter MOS upload configuration details.

Installing AHF without using the -setupmos or -nosetupmos command options:

Local: ./ahf_setup –local

Cluster-wide: ./ahf_setup

You will be prompted to confirm if you want to configure MOS upload. If you enter Y to confirm configuration, then you will be prompted to enter MOS configuration details, name, user, password, and URL. After successful AHF installation, run the ahfctl getupload command to validate MOS upload configuration.

If you install AHF cluster-wide and configure MOS upload, then the MOS upload configuration will automatically be synchronized to other nodes in the cluster.

Installing AHF using the -setupmos command option:

Local: ./ahf_setup –local -setupmos

Cluster-wide: ./ahf_setup -setupmos

You will be prompted to enter MOS configuration details, name, user, password, and URL. After successful AHF installation, run the ahfctl getupload command to validate MOS upload configuration.

If you install AHF cluster-wide and configure MOS upload, then the MOS upload configuration will automatically be synchronized to other nodes in the cluster.

Installing AHF using the -nosetupmos command option:

Local: ./ahf_setup –local -nosetupmos

Cluster-wide: ../ahf_setup -nosetupmos

You will not be prompted to enter MOS upload configuration details.

Upgrading AHF without using the -setupmos or -nosetupmos command options:

Local: ./ahf_setup –local

Cluster-wide: ./ahf_setup

You will be prompted to confirm if you want to configure MOS upload. If you enter Y to confirm configuration, then you will be prompted to enter MOS configuration details, name, user, password, and URL. After successful AHF installation, run the ahfctl getupload command to validate MOS upload configuration.

If you upgrade AHF cluster-wide and configure MOS upload, then the MOS upload configuration will automatically be synchronized to other nodes in the cluster.

Parent topic: Installing Oracle Autonomous Health Framework