This content has been marked as final. Show 5 replies
Looks like there might be some issue with the agent. You need to unblock the agent for the plug-in to work. Also, can you try this against a different agent?
Hi,1 person found this helpful
Provide the outputs of following commands:
<AGENT_HOME>/bin> ./emctl listplugins agent
Here is the confirmatiopn tha the MSSQL plugin is installed on the agent and server:
C:\oracle\product\agent12c\core\220.127.116.11.0\bin>emctl listplugins agent Oracle Enterprise Manager Cloud Control 12c Release 2 Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved. --------------------------------------------------------------- oracle.em.smss 18.104.22.168.0 C:\oracle\product\agent12c\plugins\oracle.em.smss .agent.plugin_22.214.171.124.0
Thanks for your assistance.
[oracle@srv-db-dev03 emcli]$ ./emcli list_plugins_on_server OMS name is EMGC_OMS1 Plug-in Name Version [revision] Oracle Database 126.96.36.199.0 Oracle Exadata 188.8.131.52.0 Oracle Fusion Middleware 184.108.40.206.0 Oracle MOS (My Oracle Support) 220.127.116.11.0 Oracle Virtualization 18.104.22.168.0 Microsoft SQLServer Database 22.214.171.124.0 Oracle Chargeback and Capacity Planning 126.96.36.199.0 Oracle Cloud Application 188.8.131.52.0 Oracle Fusion Applications 184.108.40.206.0
Seems the plugins on agent side were not properly deployed.
I request you to log a Service Request, we can further troubleshoot checking the pluginca logs where it went wrong and which tables were not updated correctly.
Provide the SR#
I've updated an SR I had opened with this issue and the workaround does not work either. (All my tests are on 64bits windows 2008R2). The agent gets blocked if I try to resync the agent. The I have no clue as to how to unlbock it except to deletethe the target.
Known bug - at least for 2008, but it applies to 2005 as well.
SR 3-6438484081 : Cloud 12c - Error when testing connectioon on MSSQL target Deployment
you may be running into this new bug: Bug 14680497 - "TEST CONNECTION" FAILS WITH [_WINAUTHDLLTOLOADDYNAMICPROP;DB CREDENTIALS ARE FO The workaround is: Ignore the "Test Connection" error. Click on OK to Add the Microsoft SQL Server target. This will give a "Metric Collection Error" status. Target Not Configured - Dynamic Category property error, Get dynamic property error. Once added, click on the Microsoft SQL Server drop-down menu > Target Setup > Monitoring Configuration The Monitoring Configuration screen matches the previous version "Add Microsoft SQL Server" screen.
Edited by: jstem1177 on Dec 13, 2012 1:38 PM