Skip to main content

OEM 13c-12c: Container Database Target in Enterprise Manager Cloud Control shows DOWN Status when using OCI

OEM 13c-12c: Container Database Target in Enterprise Manager Cloud Control shows DOWN Status when using OCI


Error:

EM 13c / 12c Cloud Control shows a container database target (CDB) with DOWN status and this corresponding message:

The <OMS_HOME>/em/EMGC_OMS1/sysman/log/emoms.log will show the below exception:

 

ERROR conf.Task logp.251 - Caught Exception in thread pool-2308-thread-1
java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor


I was using OCI DBCS where listener was running from Grid Home

USE_SID_AS_SERVICE_LISTENER=ON was set in the listener.ora file for the database listener.
USE_SID_AS_SERVICE_LISTENER converts the SID connection string to service name and the EM Agent is connecting using the SID designation, hence the agent connection fails.

It will only be an issue if the database SID value is different from its SERVICE_NAME value.



Solution:


Create a second listener (without USE_SID_AS_SERVICE_LISTENER=ON being set) for use by the EM Agent for target monitoring. 

1. Archive and edit $ORACLE_HOME/network/admin/listener.ora and add the following lines:

LISTENER_EM =
 (DESCRIPTION_LIST =
   (DESCRIPTION =
     (ADDRESS = (PROTOCOL = TCP)(HOST = <host_name>)(PORT = <new_port>))
   )
 )


The listener may be created from a database Oracle Home or a Grid Infrastructure Oracle Home.


2. Start the new listener: $ORACLE_HOME/bin/lsnrctl start LISTENER_EM


3. Log in to the SQL*Plus of the CDB and run this command:

SQL> alter system set LOCAL_LISTENER="(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=<host_name>)(PORT=<original_listener_port>))(ADDRESS=(PROTOCOL=tcp)(HOST=<host_name>)(PORT=<new_port>)))" scope=BOTH;

SQL> alter system register;


4. Make sure that the CDB and any PDBs are registered to both listeners:

a) lsnrctl status <original_listener_name>
b) lsnrctl status LISTENER_EM


5. From OEM, edit the monitoring configuration of the CDB:

a) Navigate: Targets > All Targets > right click listener target] > Target Setup > Monitoring Configuration
b) Modify the listener port to be the <new_port>, Select OK to save
c) Test the connection


With this listener arrangement, the regular listener will be used with USE_SID_AS_SERVICE_<name>=ON set, and the EM Agent will use another dedicated listener without USE_SID_AS_SERVICE_<name>=ON set.







If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...