OEM : Agent installation ( Agent registration password issue )

 

Intro 

Monitoring plays a major part in mission-critical environments. As the environments are critical IT administrators need to make sure database and application servers are up and running 24X7. OEM (Oracle Enterprise Manager) plays a critical role in monitoring and administration, For the Oracle database this best product for addressing issues proactively. 

Migrating everything to the cloud at once can be a complex and challenging process for many organizations, which is why a hybrid approach is often adopted. This involves integrating on-premises infrastructure with cloud services, allowing for a gradual transition. 

In the case of Database Cloud Service (DBCS), there are typically no restrictions on integrating it with Oracle Cloud Infrastructure (OCI) OEM (Oracle Enterprise Manager) or on-premises OEM. This means that organizations can manage their database instances both in the cloud and on-premises using the same management tool, providing flexibility and ease of management.

Monitoring Oracle Cloud Infrastructure (OCI) Database Cloud Service (DBCS) involves tracking various performance metrics, identifying potential issues, and ensuring the overall health and efficiency of your database. Here are some key aspects and tools you can use for monitoring OCI DBCS:

• Oracle Cloud Infrastructure Console:DB System Details Page: 

Access the OCI console and navigate to your DBCS instance. The DB System Details page provides a summary of your database system, including performance metrics, status, and alerts.

• Oracle Cloud Infrastructure Metrics:

OCI provides a set of performance metrics that you can monitor. These include CPU utilization, memory utilization, disk I/O, network I/O, and more. You can view these metrics in the OCI console or use the OCI Monitoring service.

• OCI Monitoring Service:

Utilize the OCI Monitoring service to set up custom alarms based on specific metrics. Alarms can notify you when certain thresholds are breached, allowing you to proactively address potential issues.


Oracle Enterprise Manager (OEM) Cloud Control:

OEM Cloud Control is a comprehensive management tool for Oracle databases. It provides in-depth monitoring, administration, and diagnostics. You can configure and receive alerts, view performance metrics, and perform various administrative tasks.

In this article, I will elaborate on the issues faced during agent installation. 

Installation

Installing OEM agent manually is easy, highly high-risk systems do not allow port 22 from the OMS server for the installation. In those scenarios, we need to install an agent manually. 

First, Check the status of the OMS server and open the required ports. To get a clear understanding of the port https://docs.oracle.com/cd/E24628_01/install.121/e24089/firewalls.htm.

About ports: EM 13c, EM 12c: The Default Ports Used in Enterprise Manager Cloud Control OMS Configuration and their Directionality (Doc ID 2362242.1)

                                  Figure 1: OEM ports need to be enabled through the firewall.

[oracle@oracle-oms]$ ./emctl status oms -details
Oracle Enterprise Manager Cloud Control 13c Release 5
Copyright (c) 1996, 2021 Oracle Corporation.  All rights reserved.
Console Server Host        : oracle12c.cepeo.local
HTTP Console Port          : 7788
HTTPS Console Port         : 7802
HTTP Upload Port           : 4889
HTTPS Upload Port          : 4903
EM Instance Home           : /u01/app/oracle/gc_inst1/em/EMGC_OMS1
OMS Log Directory Location : /u01/app/oracle/gc_inst1/em/EMGC_OMS1/sysman/log
OMS is not configured with SLB or virtual hostname
Agent Upload is locked.
OMS Console is locked.
Active CA ID: 2
Console URL: https://oracle12c.cepeo.local:7802/em
Upload URL: https://oracle12c.cepeo.local:4903/empbs/upload

WLS Domain Information
Domain Name            : GCDomain
Admin Server Host      : oracle12c.cepeo.local
Admin Server HTTPS Port: 7102
Admin Server is RUNNING

Oracle Management Server Information
Managed Server Instance Name: EMGC_OMS1
Oracle Management Server Instance Host: oracle12c.cepeo.local
WebTier is Up
Oracle Management Server is Up
JVMD Engine is Up

Secondly, Get the supported agent version from the OEM. 

[oracle@oracle-oms]$ export MW_HOME=/u01/app/oracle/Middleware13.5/
[oracle@oracle-oms]$ $MW_HOME/bin/emcli login -username=sysman
Enter password
Login successful
[oracle@oracle-oms]$ $MW_HOME/bin/emcli sync
Synchronized successfully
[oracle@oracle-oms]$ $MW_HOME/bin/emcli get_supported_platforms
-----------------------------------------------
Version = 13.5.0.0.0
 Platform = Linux x86-64
-----------------------------------------------
Version = 13.4.0.0.0
 Platform = Linux x86-64
-----------------------------------------------
Version = 13.3.0.0.0
 Platform = Linux x86-64
-----------------------------------------------
Platforms list displayed successfully.
[oracle@oracle12c Middleware13.5]$

Download the agent software

You can download the software using 

emcli get_agentimage -destination=/stage/OEM_AGNET_PATCH -platform="Linux x86-64" -version="13.5.0.0.0".

[oracle@oracle-om]$ $MW_HOME/bin/emcli get_agentimage -destination=/stage/OEM_AGNET_PATCH -platform="Linux x86-64" -version="13.5.0.0.0"
 === Partition Detail ===
Space free : 119 GB
Space required : 1 GB
Check the logs at /u01/app/oracle/gc_inst1/em/EMGC_OMS1/sysman/emcli/setup/.emcli/get_agentimage_2023-12-21_10-24-41-AM.log
Downloading /stage/OEM_AGNET_PATCH/13.5.0.0.0_AgentCore_226.zip
File saved as /stage/OEM_AGNET_PATCH/13.5.0.0.0_AgentCore_226.zip
Downloading /stage/OEM_AGNET_PATCH/13.5.0.0.0_Plugins_226.zip
File saved as /stage/OEM_AGNET_PATCH/13.5.0.0.0_Plugins_226.zip
Downloading /stage/OEM_AGNET_PATCH/unzip
File saved as /stage/OEM_AGNET_PATCH/unzip
Executing command: /stage/OEM_AGNET_PATCH/unzip /stage/OEM_AGNET_PATCH/13.5.0.0.0_Plugins_226.zip -d /stage/OEM_AGNET_PATCH
Archieving agentImage and plugins.
Exit status is:0
Agent Image Download completed successfully.
[oracle@oracle-oms]$

Installation

Once you download the agent installation binary copy it to the database server and install using below mentioned commands.

/u01/app/oracle/Software_Agent/agentDeploy.sh AGENT_BASE_DIR=/u01/app/oracle/product/agent13c \
-force \
-ignorePrereqs \
-invPtrLoc /etc/oraInst.loc  \
AGENT_PORT=3872 \
EM_UPLOAD_PORT=4903 \
OMS_HOST=oracle-oms.example.com \
ORACLE_HOSTNAME=test-db.privatesubnetce.test.oraclevcn.com \
AGENT_INSTANCE_HOME=/u01/app/oracle/product/agent13c/agent_inst \
AGENT_REGISTRATION_PASSWORD=Welcome1 \
SCRATCHPATH=/tmp

Error

Installation failed with trying to secure the connection with OMS. Please find the error below.

Validated the oms host and port :- oracle12c.cepeo.local----4903
Getting Inet Addresses for host test-cepeo-1.privatesubnetce.test.oraclevcn.com
** Agent Port Check completed successfully.**
Validated the agent port :- ----3872
shared agent value is :false
chain install is :false
SEVERE:emctl secure agent command has failed with status=1
SEVERE:emctl secure agent command has failed with status=1
SEVERE:emctl secure agent command has failed with status=1
Agent configuration has failed
/u01/app/oracle/product/agent13c/agent_13.5.0.0.0/cfgtoollogs/agentDeploy/agentDeploy_2024-01-16_13-58-04-PM.log

Solution

This happens because the registration password is not stored in the OMS, you need to add this password for the agent registration. 

Settings > Security > Registration password > Create registration password.

How to add a registration password.

Figure 2 shows how to navigate to register a password page.

                                                 Figure 2: Navigate to registration password

Figure 3 shows how you can add the registration password.

                                           Figure 3:  Create agent registration password.

Conclusion

By integrating DBCS with OEM, organizations can gain centralized management capabilities, monitoring, and performance tuning across their entire database environment, whether it's in the cloud or on-premises. This hybrid approach allows organizations to leverage the benefits of cloud services while still maintaining control over their on-premises infrastructure.