6 Replies Latest reply: Aug 27, 2009 7:24 AM by 641721 RSS

    Configuring ODI: Agent

    641721
      Hi,

      I have managed to configure Master repository, Topology and have set up the Work Repository. However when I click Work Repository it give me the following error:

      Unable to connect to remote repository (using Local Agent as I have not yet configured Agent).

      Please note when I press the test connection, it says succeeded. Is this an issue?

      Also I tried configuring the Agent and but I am getting the following error:

      C:\OraHome_1\oracledi\bin>agentscheduler "-port=20300" "-name=odi_demo_agent"
      A JDK is required to execute Web Services with OracleDI. You are currently using
      a JRE.
      OracleDI: Starting Scheduler Agent ...
      Starting Oracle Data Integrator Agent...
      Version : 10.1.3.5 - 10/11/2008
      com.sunopsis.tools.core.exception.SnpsRuntimeException: com.microsoft.sqlserver.
      jdbc.SQLServerException: Invalid object name 'SNP_PLAN_AGENT'.
      at com.sunopsis.dwg.cmd.n.a(n.java)
      at com.sunopsis.a.f.run(f.java)
      at com.sunopsis.dwg.cmd.i.y(i.java)
      at com.sunopsis.dwg.cmd.i.run(i.java)
      at java.lang.Thread.run(Unknown Source)
      Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name
      +'SNP_PLAN_AGENT'.+
      at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError
      +(Unknown Source)+
      at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
      at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.getPrepExecRe
      sponse(Unknown Source)
      at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePrep
      aredStatement(Unknown Source)
      at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PreparedState
      mentExecutionRequest.executeStatement(Unknown Source)
      at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source
      +)+
      at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unkno
      wn Source)
      at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(
      Unknown Source)
      at com.sunopsis.sql.SnpsQuery.executeQuery(SnpsQuery.java)
      at com.sunopsis.dwg.dbobj.generated.GeneratedSnpPlanAgent.getObjectLst(G
      eneratedSnpPlanAgent.java)
      +... 5 more+
      Caused by:
      com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'SNP_PLAN_A
      GENT'.
      at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError
      +(Unknown Source)+
      at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
      at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.getPrepExecRe
      sponse(Unknown Source)
      at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePrep
      aredStatement(Unknown Source)
      at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PreparedState
      mentExecutionRequest.executeStatement(Unknown Source)
      at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source
      +)+
      at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unkno
      wn Source)
      at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(
      Unknown Source)
      at com.sunopsis.sql.SnpsQuery.executeQuery(SnpsQuery.java)
      at com.sunopsis.dwg.dbobj.generated.GeneratedSnpPlanAgent.getObjectLst(G
      eneratedSnpPlanAgent.java)
      at com.sunopsis.dwg.cmd.n.a(n.java)
      at com.sunopsis.a.f.run(f.java)
      at com.sunopsis.dwg.cmd.i.y(i.java)
      at com.sunopsis.dwg.cmd.i.run(i.java)
      at java.lang.Thread.run(Unknown Source)

      Has anyone faced this issue. I am using the following entries to update the odiparam.bat file:

      set ODI_SECU_DRIVER=com.microsoft.sqlserver.jdbc.SQLServerDriver
      set

      ODI_SECU_URL=jdbc:sqlserver://<Servername>;SelectMethod=cursor;responseBuffering=adaptive;databas

      eName=odimaster;integratedSecurity=false;
      set ODI_SECU_USER=<dbname>
      set ODI_SECU_ENCODED_PASS=fFyX1l6MYUKGzrGidfEvh
      set ODI_SECU_WORK_REP=EXECUTION
      set ODI_USER=SUPERVISOR
      set ODI_ENCODED_PASS=LELKIELGLJMDLKMGHEHJDBGBGFDGGH

      Regards,
      Amol
        • 1. Re: Configuring ODI: Agent
          JohnGoodwin
          Hi,

          Something is not right and it may be down to the SQL server side, the SQL user that you are using is it definitely the db_owner, also if you go in sql server management studio, open up the work repository database and then the tables, do they all have dbo. in front the table names?

          Cheers

          John
          http://john-goodwin.blogspot.com/
          • 2. Re: Configuring ODI: Agent
            641721
            Hi John,

            I can't see any tables in the work repository. Please note I have created a odiwork database for repository. Am I missiing something here?

            Regards,

            Amol
            • 3. Re: Configuring ODI: Agent
              JohnGoodwin
              Hi,

              So you have not created the work repository in the topology manager yet?
              Tables will be populated when you create the work repository from inside the topology manager.

              The agent won't operate correctly until you have successfully created the work repository.

              Cheers

              John
              http://john-goodwin.blogspot.com/
              • 4. Re: Configuring ODI: Agent
                641721
                Hi John,

                I did create the work repository after showing test connection succeeded. It looks like it did not create any tables. I am going to create the repository again from scratch.

                Thanks,

                Amol
                • 5. Re: Configuring ODI: Agent
                  641721
                  Hi John,

                  I dropped the Repository db and then recreated it. I also recreated the repository in Topology and now I can see the tables. However I am still getting the exceptions (invalid object name SNP_CONNECT) even though I can see this table in the master repository

                  Regards,

                  Amol
                  • 6. Re: Configuring ODI: Agent
                    641721
                    Hi John,

                    Thanks a lot.

                    This is done. I was using the repository database name in the odiparam.bat instead of the master database and hence the error.
                    (I really must be having a bad day!)

                    Thanks,

                    Amol