My Oracle Support Banner

EM13.5: Metric Extension On The PDB Target is Showing Metric Collection Error ORA-12514, TNS:listener does not currently know of service requested in connect descriptor (Doc ID 3044160.1)

Last updated on AUGUST 30, 2024

Applies to:

Enterprise Manager for Oracle Database - Version 13.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ME was created /tested and deployed successfully . However when check the ME on the Target PDB page it shows Metric Collection Error .

This is the message shown on the Metric Collection Error page of the PDB.

Message Failed to connect: java.sql.SQLRecoverableException: Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
Last Comment Failed to connect: java.sql.SQLRecoverableException: Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor: on Aug 2, 2024 10:25:17 PM PDT
Internal Event Name ME$MY_TEST_ME
Event Type Metric Evaluation Error
Category Error



PDB target showing UP in the Console. All the metrics are working fine. Test Connection on the Monitoring Configuration page is successful.

The scan was working fine , however when running the ME on the target PDB it builds the connect string based on the properties ( ie Listener Machine/Port/Service etc )


gcagent.log


{SQLINPARAM3=%app_signatures2%, MachineName=MYHOSTvip, SQLINPARAM2=%app_signatures1%, SQLINPARAM1=%discovery_id%, UserName=***, Port=1521, Protocol=TCP, ServiceName=MYPDB.xyz.com Role=***, password=***, STATEMENT=select ............

2024-08-16 13:41:34,262 [260:8BAD85C1] DEBUG - Execution error:

oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: Failed to connect: java.sql.SQLRecoverableException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor

at oracle.sysman.gcagent.addon.fetchlet.sqlfetchlet.SqlFetchlet.getMetric(SqlFetchlet.java:1082)
at oracle.sysman.gcagent.target.interaction.execution.FetchletFactory.getMetric(FetchletFactory.java:466)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.executeQueryDescriptor(ExecuteTask.java:1358)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.runTask(ExecuteTask.java:3354)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.call(ExecuteTask.java:4706)
at oracle.sysman.gcagent.metadata.impl.collection.MetricColl$1.call(MetricColl.java:602)

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.