Odi agent logs

Hi All,
I am running a scheduler agent in unix platform. Can you please tell me how to store the Odi Agent logs in a separate file so that I can use that log for my help ?
Thanks,
AC

Yes, from what I know, load plan logs get purged implicitly even though no purging process is scheduled.
By default, they get purged after 7 days - this is specified in "Keep Log History" attribute of generated load plan.
To avoid this, after creating the load plan and before executing it: Go to Load Plan and scenarios -> Open the generated load plan -> In Definition tab set Keep Log History (days) and change the value to any higher value, say 30 days and ODI will retain these logs for 30 days.
Hope that helps.

Similar Messages

ODI Agent 11g Exception in Linux

Hi,
I set up an agent agent_test in topology and used the correct parameters in odiParams.sh ( with encoded password)
When i try to run using ./agent.sh -NAME=agent_test Port=8080
I'm getting following strange exception
2011-08-03 11:34:52.797 NOTIFICATION ODI-1128 Agent agent64 is starting. Application Server: STANDALONE. Agent Version: 11.1.1.3.0 - 23/06/2010. Port: 8080. JMX Port: 9080
2011-08-03 11:35:04.982 WARNING unavailable
oracle.odi.agent.logging.logFramework.OdiAgentException.getLocalizedMessage(OdiAgentException.java:68)
oracle.odi.agent.logging.logFramework.OdiAgentException.toString(OdiAgentException.java:162)
java.lang.Throwable.<init>(Throwable.java:242)
java.lang.Exception.<init>(Exception.java:77)
java.lang.RuntimeException.<init>(RuntimeException.java:77)
oracle.odi.core.exception.OdiRuntimeException.<init>(OdiRuntimeException.java:56)
oracle.odi.agent.logging.logFramework.OdiAgentException.<init>(OdiAgentException.java:57)
oracle.odi.runtime.agent.processor.impl.CleanStaleSessionsUtils.cleanStaleSessionsAllWorkRepositories(CleanStaleSessionsUtils.java:218)
oracle.odi.runtime.agent.servlet.AgentServlet.cleanStaleSessions(AgentServlet.java:371)
oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:332)
oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:226)
javax.servlet.GenericServlet.init(GenericServlet.java:241)
org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431)
org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:676)
org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1239)
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:466)
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
org.mortbay.jetty.Server.doStart(Server.java:224)
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
oracle.odi.Agent.startAgent(Agent.java:200)
oracle.odi.Agent.main(Agent.java:493)
I have ran and scheduled agents before but this strange exception to me. please help.
Thanks
John

Did you try a different port number.
8080 is commonly used as an alternative to the HTTP port 80
Also, do you have a 64 bit linux ? If thats the case, then you have to install ODI using 32 bit version of Java on 64 bit linux

ODI Agent error: java.sql.SQLException: Invalid column name

When running a scenairo on a standalone ODI agent, it hangs on "Wait" state. The ODI agent's log is logging the following errors over and over again.
We are in Fusion Application Development and are using Middleware D8B4A RC5.
[2011-01-07T14:35:16.381-08:00] [odi] [WARNING] [] [oracle.odi.agent] [tid: 4215] [ecid: 0000IpYbCrKE8TQRyaJ7D01D8^zE00009o,0] /oraclediagent/invoke.do[[
oracle.odi.core.security.SecurityManager.doODIInternalAuthentication(SecurityManager.java:356)
oracle.odi.core.security.SecurityManager.createAuthentication(SecurityManager.java:331)
oracle.odi.runtime.agent.servlet.AgentServlet.doPost(AgentServlet.java:418)
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:503)
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
org.mortbay.jetty.Server.handle(Server.java:326)
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:749)
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:219)
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)
[2011-01-07T14:35:18.341-08:00] [] [ERROR] [ODI-1131] [] [tid: 4214] [ecid: 0000IpYaiZCE8TQRyaJ7D01D8^zE00009n,0] [arg: OracleDiAgent] [arg: java.sql.SQLException: Invalid column name] Agent OracleDiAgent encountered an error: java.sql.SQLException: Invalid column name

Are you sure the datasources point to the right master/work configuration, and that your repository is correctly up-to-date? This looks like the agent trying to connect a repository, but the repository is not updated correctly, or misses some columns. The whole stack (and the name of the missing column) would help of course.

ODI Agent error

Hi John,
I am using my ODI agent as a windows service. It was working fine.
But now it is not running fine and when i have seen the log for it the following error is given
Starting Oracle Data Integrator Agent...
Version : 10.1.3.5 - 10/11/2008
com.sunopsis.tools.core.exception.SnpsRuntimeException: java.sql.SQLException: Io exception: Invalid connection string format, a valid format is: "host:port:sid"
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)
When i trie to launch the agent from the batch file the command prompt is opening and shutting down immediately.
Please let me know the solution

If it is not working from batch then you need to check the odiparams.bat file, it is more than likely some of the information is not correct in it.
Cheers
John
http://john-goodwin.blogspot.com/

ODI Agent - when do i need to use?

can anybody explain me the perpose of ODI Agent? and when do i need to use Agent?
Edited by: knidhi on Oct 5, 2009 3:31 PM
Edited by: knidhi on Oct 5, 2009 4:07 PM

If I could finesse your answer slightly, hopefully to help (or confuse):
There are multiple agent types:
- the Local (No agent): this opens additional threads in the current GUI process. The agent will just run as additional threads in your current process, using the same settings as your GUI environment.
- a standalone agent: if you start an agent from the commandline using the agent.sh/bat. This will start a "listener agent". It starts up and passively listens for execution requests. When a request is passed to the agent, it includes all the necessary information to connect to the repository etc. All this information is there in the invocation package. (for more information on what is passed look at the documentation for the invocation API or at the ODIInvoke webservice)
- a scheduler agent: when you start a scheduler agent from the commandline with the agentscheduler.bat/sh file, it will read from the odiparams.sh/bat file the connectivity paramaters for the repository, where it will "look itself up" based on the agent name passed, to find out what scenarios it should be scheduling. This agent may also take requests, just like the standalone agent described above.
- a task may also be invoved at the opertaing system command level using startscen.bat/sh. This will start a standlone agent for the duration of this execution only, which not listen for other requests, it reads its parameters from the command line (for which sceenario, version and context) and from the odiparams file for the repository connectivity parameters as to where to find the requested scenario and where the execution will be logged.

ODI Agent keeps stopping

*HP-UX B.11.31 ia64
Database 11.2.0.1.0
ODI 10.1.3.6.2*
We have two separate installations of the database and odi on two separate dev instances on two separate servers.
Today we are experiencing the same problem where the ODI agent will start using start_odi_agent.sh and will create 2 UNIX processes, the agentscheduler and a JAVA process as normal but then after about 5 seconds the processes will stop.
This is the entry in the ODI_AGENT.log and is exactly the same on both servers apart from the URL.
Starting Oracle Data Integrator Agent...
Version : 10.1.3.6.2 - 19/04/2010
10/10/2011 01:12:24 PM(main): DwgCmd: getUniqueThreadIdentifier : :Before : mThreadIDIncrementCounter : 0
10/10/2011 01:12:24 PM(main): DwgCmd: getUniqueThreadIdentifier : :After : mThreadIDIncrementCounter : 1 : Unique ID : 0
com.sunopsis.sql.l: Oracle Data Integrator Timeout: connection with URL jdbc:oracle:thin:@************************:6062:****DB4 and user odi_master_dev4.
     at com.sunopsis.sql.SnpsConnection.a(SnpsConnection.java)
     at com.sunopsis.sql.SnpsConnection.connect(SnpsConnection.java)
     at com.sunopsis.dwg.cmd.e.j(e.java)
     at com.sunopsis.dwg.cmd.n.a(n.java)
     at com.sunopsis.l.f.run(f.java)
     at com.sunopsis.dwg.cmd.i.A(i.java)
     at com.sunopsis.dwg.cmd.i.run(i.java)
     at java.lang.Thread.run(Thread.java:619)
It stops very abruptly!
Can anyone shed any light on this problem? I am a DBA and am fairly new to ODI and this one has me struggling.
Thanks.

Can you make sure that windows account have the this privilege?
The Windows account under which the agent runs is used when it makes connections to the Distributor. This account must:
At minimum, be a member of the db_owner fixed database role in the distribution database.
Have read, write, and modify permissions on the snapshot share.
The account that is used to connect to the Publisher must at minimum be a member of the db_owner fixed database role in the publication database.
http://msdn.microsoft.com/en-us/library/ms151868.aspx
--Prashanth

Linux server - ODI agent

Hi guys,
I can start the ODI agent fine but I keep logging in to find the agent has stopped/crashed when using the ODI console. This isn't going to be very good when the monthly schedules run....Is the easiest method to avoid this to schedule a shell script to run the agent before the schedules are do to run? Any ideas as to why my agent keeps stopping? I'm quite new to linux so go easy on me if I have missed something obvious :)
Many thanks,
Russell

I had a quick look in the logs and I cannot find anything suspicous really. The only thing I can see occuring before I notice this issue is this:
[2013-04-17T05:00:27.771+01:00] [] [NOTIFICATION] [ODI-1148] [] [tid: 79] [ecid: 0000JsM9dPvApID5zB^AyW1HPy5G00000Z,0] Agent ODI_Agent executing load plan log purge for work repository WORKREP at Apr 17, 2013 5:00:27 AM.
but this appears to be a normal occurrence?!
I will update again as soon as I experience the issue
Would scheduling a shell script to start the agent cause any issues if it was already started? I would like a failsafe before the monthly builds run to ensure the agent is running.
Many thanks,
Russell

ODI agent status shown prepared in Weblogic

hi,
I have installed FDMEE 11.1.2.4. When i start services everything is ok except ODI Java EE agent. I haven't configured it ( i think it was preconfigured).
I have tried starting ODI agent from enterprise manager but i am getting an error; will paste below.
I have seen that in weblogic server under erpi integrator server my odi console status is active and odi agent status is prepared. I don't know how to start JAVA EE agent.
Any help?
Error:
Invoking Start Up operation for application oraclediagent on target ErpIntegrator0.
[Deployer:149193]Operation 'start' on application 'oraclediagent' has failed on 'ErpIntegrator0'
[Deployer:149034]An exception occurred for task [Deployer:149026]start application oraclediagent on ErpIntegrator0.: [HTTP:101216]Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent".
com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=MasterMemberSet(
    ThisMember=null
    OldestMember=null
    ActualMemberSet=MemberSet(Size=0
    MemberId|ServiceVersion|ServiceJoined|MemberState
    RecycleMillis=1200000
    RecycleSet=MemberSet(Size=0
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:58)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:427)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInternal(DefaultConfigurableCacheFactory.java:968)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(DefaultConfigurableCacheFactory.java:937)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:919)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1296)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:297)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:204)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:181)
at oracle.odi.runtime.agent.coherence.OdiAgentCoherenceCache.<init>(OdiAgentCoherenceCache.java:52)
at oracle.odi.runtime.agent.servlet.AgentServlet.initCoherence(AgentServlet.java:812)
at oracle.odi.runtime.agent.servlet.AgentServlet.initializeClusterCache(AgentServlet.java:762)
at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:437)
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:250)
at javax.servlet.GenericServlet.init(GenericServlet.java:242)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:672)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
:com.tangosol.net.RequestTimeoutException:Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
MemberSet=MasterMemberSet(
    ThisMember=null
    OldestMember=null
    ActualMemberSet=MemberSet(Size=0
    MemberId|ServiceVersion|ServiceJoined|MemberState
    RecycleMillis=1200000
    RecycleSet=MemberSet(Size=0
Operation Start Up on target oraclediagent Failed. Please see error logs for details.
Regards

Hi JanGLi,
The ODI Agent is completely failing to start here from the error that you initially pasted so agent tests are not going to work wherever you try them. Port 6550 should have something listening on it as that's the port that the FDMEE managed server listens on so that would only prove that the FDMEE managed server is up. I can't see the connection closed error having anything to do with running out of connections in the connection pool either as it's simply a message saying that a connection was closed (not that the connection pool is exhausted).
On the plus side though I have seen the 'Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent"' error in the past (I get a lot of the really nice issues coming my way). Which operating system are you using here? I've seen this happen on Windows when there are multiple network interfaces and an incorrect interface has been put to the top of the bind order (e.g. an interface that has fallen back to a link local address in the 169.254.0.0/16 range as DHCP has failed).
Regards
Craig

Agent logs not being generated

On a recent installation of 2 x Exchange Server 2013 Cumulative Update 2 (CU2-v2), neither server appears to be generating Agent Logs. The default path for such logs (C:\Program Files\Microsoft\Exchange Server\v15\TransportRoles\logs\Hub)
does not even appear to contain an "AgentLog" folder.
The Get-TransportService cmdlet returns:
AgentLogMaxAge           : 7.00:00:00
AgentLogMaxDirectorySize : 250 MB (262,144,000 bytes)
AgentLogMaxFileSize      : 10 MB (10,485,760 bytes)
AgentLogPath             : C:\Program Files\Microsoft\Exchange Server\v15\TransportRoles\logs\Hub\AgentLog
AgentLogEnabled          : True
I have tried modifying these settings, changing the path, manually creating the "AgentLog" folder, restarting the transport service, and nothing seems to make any difference.
If anyone can offer any suggestions / provide any pointers, I would be extremely grateful. We regularly use agent logs when querying mail flow.
Many thanks in advance,
Simon.

Hi,
As Martina mentioned,you should install Anti-Spam Agents first.
By default, anti-spam features aren't enabled in the Transport service on a Mailbox server. Typically, you only enable the anti-spam features on a Mailbox server if your Exchange organization doesn't do any prior anti-spam filtering before accepting incoming
messages.
In addition,if you want to configure Spam Agent Logging,plesae refer to the fowllowing article:
Configure Anti-Spam Agent Logging
Thanks.
Niko Cheng
TechNet Community Support

I would Like to print Exceptions to an agent Log not a console

I purposely set this error so my agent would produce the error. The error listed below prints to the Java Console in Lotus Notes. I would like it to print to an agent.log I know this can be done through the use of a StringWriter and e.printStackTrace(StringWriter). But I need some documentation. Can anybody help??
Below is a snippet of the agent and the error follows.
} catch(Exception n) {
System.out.println("Error Caught");
System.out.println("Error Message" + " " + n ); //+ " " + el + " " + n.getMessage());
n.printStackTrace();
[FATAL ERROR] notes:///__86256D7B000B5CD1.nsf/0/CA2EA717D0E3594686256DAD005B7E7D(XMLBody) Line:16 Column:36: "</connectduration>" expected.
Error Caught
Error Message "</connectduration>" expected.
"</connectduration>" expected.
     at com.ibm.xml.framework.XMLParser.handleError(XMLParser.java:413)
     at com.ibm.xml.framework.XMLParser.error1(XMLParser.java:485)
     at com.ibm.xml.internal.DefaultScanner.emitError(DefaultScanner.java:312)
     at com.ibm.xml.internal.DefaultScanner.scanContent(DefaultScanner.java:1195)
     at com.ibm.xml.internal.DefaultScanner.scanDocument(DefaultScanner.java:419)
     at com.ibm.xml.framework.XMLParser.parse(XMLParser.java:329)
     at com.ibm.xml.parsers.NonValidatingDOMParser.parse(NonValidatingDOMParser.java:1069)
     at lotus.domino.Parser.parse(Parser.java:49)
     at lotus.domino.local.Item.parseXML(Item.java:571)
     at ParseEvents.NotesMain(ParseEvents.java:41)
     at lotus.domino.AgentBase.runNotes(AgentBase.java:161)
     at lotus.domino.NotesThread.run(NotesThread.java:203)

If you have a log file created and want to log the stacktrace in it you can get the stacktrace as a String & write it to the log file:
    public static final String getStackTrace(Exception e)
        if (e == null)
            return null;
        StringWriter sWriter = new StringWriter();
        PrintWriter pWriter = new PrintWriter(sWriter);
        e.printStackTrace(pWriter);
        //String stackTrace = new String(sWriter.getBuffer());
        String stackTrace = sWriter.toString();
        pWriter.close();
        try {
            sWriter.close();
        catch (IOException ie) {
        return stackTrace;
    }

ODI agent creation issue

Hi,
I am trying to create ODI agent in Windows. I have followed the steps in ODI set up document. It has launched the server. Now I am trying to create that as a windows service. But I am getting following error message.
I ran the followiing the command line
<ODI_HOME>\bin\agentservice -i -s Sched_Agent 20910
The error I am getting is
"FATAL | wrapper | The argument 'Files\Java\jdk1.5.0_12\bin\java.exe' is not a valid property name-value pair."
I have 10.1.3.5.5
My ODI_JAVA_HOME is pointing to C:\Program Files\Java\jdk1.5.0_12. Is this the issue for the error
Anyone knows why its happening.
-app
Edited by: user6401072 on Jul 28, 2010 11:35 AM

The reason is becuase you JDK path is some thing like this c:\program files\Java\jdk1.5.0_12\bin\java.exe'
so what is the happening becuase of space between program and files its not picking up the correct JDK path .
Either change the path of JDK installation or
go to your odiparam path and go to this line
if "%ODI_JAVA_HOME%" == "" set ODI_JAVA_HOME="c:\program files\Java\jdk1.5.0_12"
or
if "%ODI_JAVA_HOME%" == "" set ODI_JAVA_HOME='c:\program files\Java\jdk1.5.0_12'
i dont remember exactly whether single or double quotes but try and let me know if that helps you

ODI agent may not running

dear all,
odi agent test successfully, update the scheduling successfully but when pressing the scheduling information it give error
"ODI agent may not running"
kindly solve the issue
regards
Naseer

Hi Ratish,
Following are the things i did and things which are happening .. :)
created a scenario and scheduled it.
And from Topology Man.. Agent Window... clicked on "Update Scheduling"... Output is "Planning Update is Completed" and when i click on Schedule Information" it is throwing warning saying... "Unable to retrieve Agents Schedule"... and my scheduled job is also not executed at scheduled time.
Any idea what could be the problem?
Thanks in advance.
Regards,
Amar

Agent Logs under agent names shows no information in CSD

I have 1 supervisor and that supervisor needs to see the agent logs under each individual agent name but for some reason there is nothing being reported there. If an agent takes a call or makes a call, inbound or outbound will appear under the agent name with data but logs just will not show anything. Is there a setting somewhere i'm missing?

You may have already checked this and apologize if you did, but have you verified that the supervisor is configured to see the columns under the Logs?
In Supervisor, go to View - Preferences. In the window that appears, go to Team - Agent - Logs and click on "Configure" on the right side, in the "Columns" field. Make sure that the columns have a check mark next to them.
If that is ok, have you tried running Supervisor from a different machine to see if that works?

Agent Logs out and Logs in back several times

Hi,
Agent Logs out and Logs in back several times without his intervention. this was observed with one agent. Any idea what would be causing? We use a custom CTIOS client and we observe that only one agent had this problem

Hi,
Do you have access to the client desktop and the CTIOS server logs ? Look for the network related errors, sometimes the process in ICM might be giving up..
regards,
Shravan

Agent log rotation

Agent - Sunone Agent 2.1
Webserver - IIS
Policy Server - IS 6.0 SP1.
How do you get the agent log to rotate on size/time? Is there a parameter?
Currently we have to manually delete it.

Log rotation feature available in 2.2 web agents. You need to find other ways to do it.
-Subba

Odi agent logs

Similar Messages

Maybe you are looking for