OCI Observability & Management (O&M) Platform consists of a several cloud services that we can enable to monitor, analyze, and manage applications and infrastructure environments with full-stack visibility, prebuilt analytics, and automation capabilities.
For Kerberos authentication, first we need to configure Kerberos in the Oracle database that will be integrated with Microsoft Active Directory.
CMU-Active Directory only supports the Microsoft Active Directory Kerberos server. Other non-Active Directory Kerberos servers are not supported with CMU-Active Directory.
Oracle Database can authenticate and authorize Microsoft Active Directory users with the database directly without intermediate directories or Oracle Enterprise User Security.
We were using the Oracle Database backup on a managed disk directly connected to the VM, then copy over to other storage, but to keep even a backup for a month is expensive on managed disk.
Recently we upgraded AHF to latest version and I found the new ahfctl command line is very helpful and easy to upgrade AHF.
AHFCTL command line utility starts from version 21.1 version.
Here are the steps:
1. Download latest patch to patch location.
[root@oda-base0 stage]# pwd
/u01/stage
[root@oda-base0 stage]# ls -lrt
total 402584
-rw-r--r-- 1 root root 411834022 Dec 15 19:44 AHF-LINUX_v21.3.4.zip
[root@oda-base0 stage]#
2. Check the current version of AHF using below command: ahfctl statusahf
[root@oda-base0 stage]# ahfctl statusahf
.------------------------------------------------------------------------------------------------.
| Host | Status of TFA | PID | Port | Version | Build ID | Inventory Status |
+----------+---------------+-------+------+------------+----------------------+------------------+
|oda-base0 | RUNNING | 18822 | 5000 | 21.3.3.0.0 | 21330020211213022521 | COMPLETE |
'----------+---------------+-------+------+------------+----------------------+------------------'
------------------------------------------------------------
Master node = oda-base0
orachk daemon version = 21.3.0
Install location = /opt/oracle/dcs/oracle.ahf/orachk
Started at = Fri Nov 19 10:40:14 EST 2021
Scheduler type = TFA Scheduler
Scheduler PID: 18822
------------------------------------------------------------
ID: orachk.autostart_client_oratier1
------------------------------------------------------------
AUTORUN_FLAGS = -usediscovery -profile oratier1 -dball -showpass -tag autostart_client_oratier1 -readenvconfig
COLLECTION_RETENTION = 7
AUTORUN_SCHEDULE = 3 2 * * 1,2,3,4,5,6
------------------------------------------------------------
------------------------------------------------------------
ID: orachk.autostart_client
------------------------------------------------------------
AUTORUN_FLAGS = -usediscovery -tag autostart_client -readenvconfig
COLLECTION_RETENTION = 14
AUTORUN_SCHEDULE = 3 3 * * 0
------------------------------------------------------------
Next auto run starts on Dec 16, 2021 02:03:00
ID:orachk.AUTOSTART_CLIENT_ORATIER1
3. Set Software stage location: ahfctl setupgrade -swstage <patch location>
[root@oda-base0 stage]# ahfctl setupgrade -swstage /u01/stage/
AHF autoupgrade parameters successfully updated
Successfully synced AHF configuration
refreshConfig() completed successfully.
NOTE: you don't need to unzip the file4. Upgrade AHF using ahfctl upgrade command:
[root@oda-base0 stage]# ahfctl upgrade
/u01/stage/AHF-LINUX_v21.3.4.zip successfully extracted at /u01/stage/
AHF software signature has been validated successfully
AHF Installer for Platform Linux Architecture x86_64
AHF Installation Log : /tmp/ahf_install_213400_77222_2021_12_16-15_05_05.log
Starting Autonomous Health Framework (AHF) Installation
AHF Version: 21.3.4 Build Date: 202112151432
AHF is already installed at /opt/oracle.ahf
Installed AHF Version: 21.3.3 Build Date: 202112130225
Upgrading /opt/oracle.ahf
Shutting down AHF Services
Stopped OSWatcher
Nothing to do !
Shutting down TFA
oracle-tfa stop/waiting
Killing TFA running with pid 52188 gracefully
. . . . .
Killing TFA running with pid 52188
. . .
Successfully shutdown TFA..
Starting AHF Services
Starting TFA..
oracle-tfa start/running, process 83660
Waiting up to 100 seconds for TFA to be started..
. . . . .
Successfully started TFA Process..
. . . . .
TFA Started and listening for commands
No new directories were added to TFA
Directory /u01/app/grid/crsdata/oda-base0/trace/chad was already added to TFA Directories.
INFO: Starting orachk scheduler in background. Details for the process can be found at /opt/oracle.ahf/data/oda-base0/diag/orachk/compliance_start_161221_150721.log
AHF is successfully upgraded to latest version
.-----------------------------------------------------------------.
| Host | TFA Version | TFA Build ID | Upgrade Status |
+-----------+-------------+----------------------+----------------+
| oda-base0 | 21.3.4.0.0 | 21340020211215143236 | UPGRADED |
|-----------+-------------+----------------------+----------------'
Moving /tmp/ahf_install_213400_77222_2021_12_16-15_05_05.log to /opt/oracle.ahf/data/oda-base0/diag/ahf/
[root@oda-base0 stage]# tfactl status
.-------------------------------------------------------------------------------------------------.
| Host | Status of TFA | PID | Port | Version | Build ID | Inventory Status |
+-----------+---------------+-------+------+------------+----------------------+------------------+
| oda-base0 | RUNNING | 83922 | 5000 | 21.3.4.0.0 | 21340020211215143236 | COMPLETE |
|-----------+---------------+-------+------+------------+----------------------+------------------'1. Oracle recommends that you back up the Middleware Home, the Management Repository, Central inventory, Software library, Management Agent.
2. The minimum version supported for upgrading to EM 13.5 is 13.3. If the OMS is at 12.1.0.x, 13.1 or 13.2, it is mandatory that it is first upgraded to 13.3.0.0.0 or 13.4.0.0.0.
In this blog post I will show you how to disable Automatic database backups on ExaCC using dbaascli.
