My Oracle Support Banner

EM 12c : Unable to Discover Database Plugin Targets After applying Discovery Patch 24610055 (Doc ID 2203250.1)

Last updated on DECEMBER 13, 2019

Applies to:

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


Using agent with Database Plugin.
Attempting to discover new databases on the target server using the below methods do not list any targets:

1. Auto discovery method.
2. Add target manually via guided process

- The agent-side Discovery <Patch 24610055> has been applied recently to the Database Plugin home at this agent.

- With DEBUG level logging, the <AGENT_INST>/sysman/log/gcagent.log shows the below entries:

2016-10-11 14:58:34,018 [1033:FD98A2F4] DEBUG - pluginId=oracle.sysman.db,scriptName=discover/
2016-10-11 14:58:34,018 [1033:FD98A2F4] DEBUG - OSChannel:
/<AGENT_BASE>/core/ agenthost.domain] STDIN={}
2016-10-11 14:58:34,018 [1033:FD98A2F4] DEBUG - OSChannel executing id=Unknown@1476161914018_269: Command(/<AGENT_BASE>/core/

The script is getting called at 2016-10-11 14:58:34. However, the emagent_perl.trc shows no entries for the script when the Database discovery is run, even when the DEBUG level tracing is enabled for PERL modules. 

-  Attempting to execute the <AGENT_BASE_DIR>/plugins/oracle.sysman.db.discovery.plugin_12. script manually fails with:

$ perl '<HOSTNAME>'
Global symbol "$hostMatchFound" requires explicit package name at
line 1500.
Execution of aborted due to compilation errors.


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

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