Enterprise Manager Generic (MOSC)

MOSC Banner

Discover ASM Instance manual discovery also fails

edited Jan 11, 2017 4:01AM in Enterprise Manager Generic (MOSC) 3 commentsAnswered

EM 12.1.0.4.0 target +ASM instance is 11.2.0.3.

EMGC discovers the target as shown by excerpt from emoms.trc on OMS server:

oracledb.pl: Fri Dec 30 14:09:30 2016: INFO:  DB_LISTENER_DISCOVERY:  found dynamic sid="+ASM" service =+ASM port = 1521 host =SERVERNAME home=/u01/app/grid/product/11.2.0.3  oracledb.pl: Fri Dec 30 14:09:47 2016: INFO:  DB_LISTENER_DISCOVERY:  processing sid="+ASM"

oracledb.pl: Fri Dec 30 14:09:51 2016: INFO:  DB_LISTENER_DISCOVERY:  osm_instance target "+ASM_SERVERNAME" discovered. Details: [+ASM_SERVERNAME,+ASM,SERVERNAME,/u01/app/grid/product/11.2.0.3,1521]

Agent, however, doesn't recognize the target

2016-12-30 13:30:38,207 [412681:C3390A37:HTTP Listener-412681 - /emd/main/ (~Task-free~ OMS.console@22993@OMS.SERVERNAME=>[148312262480001])] INFO - >>> Dispatching request: GetTargetsRequest (osm_instance.+ASM_SERVERNAME INCLUDE BROKEN) <<<

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center