This content has been marked as final. Show 4 replies
I encountered these problems whith OEM integration :
* start/stop is not managed when the adapter fails or is stopped outside OEM
* I was unable to activate an event error detection on adapters
* Refresh times when you have numerous adapters are awfull
* OEM client console & OEM central console (on the server) did not act same manner
For these reasons we decided to activate a monitoring on the table OAI_AGENT_ERROR
Did someone use OEM in produtioon with interconnect ?
I was trying to install Management infrastructure(server)
but for post instalation steaps its showing some error
Class not found: oracle.sysman.vdrRegistry.VdruLoader
Press any key to continue . . .
could anybody help me.......
Try a search on Metalink for "vdrRegistry.VdruLoader" (without quotes).
I think your problem is that your CLASSPATH should include $ORACLE_HOME\jlib (where the file oembase-9_0_2.jar resides). This jar file contains VdruLoader.
Also check your oemctl.bat file. This is found in $ORACLE_HOME/bin.
I've known Universal Installer (especially when installing OAI 4.1 on a Windows machine) to add extra slashes to the paths. e.g.
should be SET JLIBROOT=D:\oracle\ora9ias\jlib
Hope this helps.
Ggot this error when installed on Solaris. Ian is
right, use metalink to resolve this problem.
For the first question, if the agent is activated in the machine where the adapter is installed it will be possible to manage it.