4 Replies Latest reply on Aug 10, 2004 5:25 PM by 365674

    Using OEM Console to Manage OAI Infrastructure

    416900
      For those of you who have not tried to use OEM Console to manage the OAI components, I'd recommend it. It saves having look for the latest log files, and the Tracking Fields functionality is excellent.

      However, my question is "what about adapters that are not placed on the Hub server, but on the target application server instead. Can OEM Console manage those too?"

      My suspicion is that it can't, but can anyone confirm this?

      Cheers
      Ian
        • 1. Re: Using OEM Console to Manage OAI Infrastructure
          388003
          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 ?
          • 2. Re: Using OEM Console to Manage OAI Infrastructure
            424253
            I was trying to install Management infrastructure(server)
            but for post instalation steaps its showing some error
            like

            Class not found: oracle.sysman.vdrRegistry.VdruLoader
            Press any key to continue . . .

            could anybody help me.......

            • 3. Re: Using OEM Console to Manage OAI Infrastructure
              416900
              Rupesh,

              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.
              SET JLIBROOT=D:\\oracle\\ora9ias\\jlib
              should be SET JLIBROOT=D:\oracle\ora9ias\jlib

              Hope this helps.
              Ian
              • 4. Re: Using OEM Console to Manage OAI Infrastructure
                365674
                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.