Error in executing job captured ?

hi ,
if i have an oracle job and it executes with an error , is the error captured anywhere ?
if not how shld i capture the job's error ?
pls advise
rgds

This might help you
Oracle 10g JOB and output parameters
i think you can capture the errors.
Thanks,
Ganesh.

Similar Messages

  • Error when executing job from BW

    Hi,
    We have created a job that transfers a set of data to BW PSA.
    When executing from data services designer or from the management console the job works fine.
    When executing the job from BW administration workbench, the job is executed and does not report failures (we can consult the log in the management console).
    But nothing arrives in the PSA, and on the workbench we get the following errors:
    Error in a data conversion in record
    data record      1 of the fragmented entry is too long.
    Error in a data conversion in record
    Please advice what to check next.
    Best regards
    Thomas

    Hi,
    Thank you for your help.
    I tried changing the BW datastore to UTF-8 but am still not able to load these data when it is trigged from BW.
    After changing the datastore to UTF-8 I get some additional information in the log but no errors
    Additional information in the log:
    The specified locale  and datastore codepage
    Br
    Søren Ejlersen

  • Solution Manager - Error when executing Job SM:EXEC SERVICES

    Hi,
    I am trying to get the data from the earlywatch alert report and when i start the job SM:EXEC SERVICES.
    The jobs starts but i get an error during is execucion:
    Runtime errors         SYNTAX_ERROR                                          
           Occurred on     17.01.2008 at   14:06:28                                                                               
    Syntax error in program "RDSVASAEW_DBMSS____________052 ".                                                                               
    What happened?                                                                               
    The following syntax error occurred in the program                           
    RDSVASAEW_DBMSS____________052 :                                            
    "INCLUDE report "/1CAGTF/IF_LOGFUNC_000208" not found."                      
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because one of
    the                                                                         
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.   
    I tried to generate all the function modules and i get this error:
    Logical function:  MSQ_TEMPDB_DOWNLOAD            :                    
    Error      1  during generation of  /1CAGTF/IF_LOGFUNC_000208          
    Syntax error.
    Can you help me on this error?
    Best regards,
    Nuno Silva

    Hi Pedro,
    I insert my answer from a similar thread.
    As a pitty, that's a well known error.
    Please check [SAP Note 727998|http://service.sap.com/sap/support/notes/727998]
    Basically, these three steps needs to be performed:
    1) BDL_DELETE_ALL_TABLES
    2) SDCCN - Refresh Service Definitions
    3) Generate Logfuncs
    SE37: /BDL/_GENERATE_LOGFUNCINCLUDES
    OPTION: ALL
    It's also described in the Implementation Guide (IMG), transaction SPRO in the SAP Solution Manager system:
    SAP Solution Manager -> Configuration -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> Service Data Control Center
    -> Activate the Service Data Control Center in the Solution Manager
    -> Generate Includes for Service Data Contol Center
    With the next ST-PI Support Package. The steps can be triggered via the menu of transaction SDCCN.
    Best regards,
    Ruediger Stoecker

  • Error while executing Job

    Hi All,
    I am facing an error while trying to run a job for IDOC data posting in to SAP ECC 6.0.
      XML source in data flow <Query> could not process the XML data .Notify Customer Support
    Anyone has got this scenario. Please suggest any inputs.
    Thanks
    Phaneendranadh K

    Hi,
    If  CI & DB are on different host this error normally occures.SAP return codes 236 means no connection to gateway, can you check it?
    Also check whether TCP/IP RFC connection SAPXPG_DBDEST_*  is working fine or not.If it is not working fine then please check whether you have mentioned below details
    Program              sapxpg
    Target Host          DB Host name
    Gateway Host    DB host/gateway host
    Gateway service sapgw##
    Also refer SAP Note  108777 - CCMS: Message 'SAPXPG failed for BRTOOLS' & Note 446172 - SXPG_COMMAND_EXECUTE (program_start_error) in DB13
    Hope this helps.
    Thanks,
    Sushil

  • Error running executable job

    Every job I'm trying to run an OS command (even a simple dir command) failes:
    ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
    Please help

    I am trying to run rman from DBMS_SCHEDULER to no avail. The command I try runs at the command line but the scheduler does not like it. Any ideas?
    Here is my code and I am setting the job up as user sys:
    begin
    dbms_scheduler.create_job (
    job_name => 'RMAN_TEST'
    ,job_type => 'EXECUTABLE'
    ,job_action => 'c:\oracle\product\10.1.0\db_1\bin\rman target sys/mdlt cmdfile C:\CDNMDLT\cdn_mdlt\Software_Engineering\Database\scripts\delete_logs2.txt log c:\temp\DBMS_SCHEDULER.LOG'
    ,start_date => '23-MAY-06 11.12.00 AM'
    ,repeat_interval => 'FREQ=DAILY'
    ,enabled => TRUE
    ,comments => 'RMAN Test');
    end;
    If you would, please contact me at [email protected] as the email associated with this user is no longer valid. Thanks.
    Message was edited by:
    aolinc38

  • Short dump while executing job SM:EXEC SERVICES for EWA alert generation

    Hello All,
    I'm getting short dump error while executing job SM:EXEC SERVICES for EWA alert generation.I'm using EHP1@SP22 of Sol Man.
    Please find the logs
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "RDSVASCABAP_TRANS__________073
    " in include "RDSVASIABAP_TRANS__________073 " in
    line 1782:
    "Field "STATEMENT_SUMMARY001019" is unknown. It is neither in one of th"
    "e specified tables nor defined by a "DATA" statement. "DATA" statement"
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    If anyone came across such kind of dump, please reply asap, due to this, i could not generate EWA report for R/3 system 6.04.
    Thanks,
    Anand.

    >
    Anand Tigadikar wrote:
    > Thx Paul, but i already did checked this note and its not solving my issue
    Dear Anand,
    Did you perform a complete service definition replacement for SDCC/SDCCN as described in the note?
    These are manual steps you need to perform on the system and are not code corrections.
    I would suggest you perform it, if you have not, and check the SDCCN logs to review the process ran cleanly.
    Note: Please make sure SDCC_OSS is functioning and a connection to SAP can be made before
    deleting the service definitions.
    If you have already replaced the service defintions on the Solution Manager system, then no point doing it again. However checking a note and applying it are not the same thing. So I am uncertain if you replaced the service definitions or not. The dump you are getting in SM:EXEC SERVICES suggests its due to a problem with the service definitons. The recommendation is to replace them according to the process described in SAP Note 727998. If you have not done so please do so.
    If you have successfully replaced the service definitions are you still getting the same dump, or has it possibly changed?
    Regards,
    Paul

  • Error when scheduling job (JOB_SUBMIT) when execute PC in WAD

    Dear BIers,
      I execute a Process Chain in commond button of WAD, however, I got the error message:
      Job BI_PROCESS_DTP_LOAD could not be scheduled. Termination with returncode 8
      Returncode '8' means ' Error when scheduling job (JOB_SUBMIT).
    Any suggestions are appreciated.
    B.R
    Gerald

    Dear Raju,
    Have you checked SM21? Maybe you have a problem with your TemSe object. If this is the case a basis guy should know how to handle it.
    Greetings,
    Stefan

  • Error while executing the Job for Objects :null  Batch Risk Analysis

    Hi All,
    We've recently upgraded Virsa to version  5.3_14 .  I'm encountering a problem when executing the Batch Risk Analysis job for users, roles and profiles.  The job does not complete for some objects and it seems to be sporadic and shows this error: -
    Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null                                                                               
    I've attached the log for your review.
    Thanks in advance for your help.                                                                               
    Linda Lewis                                                                               
    Feb 9, 2011 1:47:53 PM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
    FINEST: ObjAuthMatcher constructed: 4ms, #singles=2141, #ranges=0, #super=0
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
    WARNING:  Job ID:395 : Failed to run Risk Analysis
    java.lang.StringIndexOutOfBoundsException at java.lang.String.substring(String.java:1019)
    at com.virsa.cc.xsys.util.RuleLoader.getPermRule(RuleLoader.java:573)
    at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1609)
    at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:321)
    at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1166)
    at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1464)
    at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:560)
    at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:363)
    at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)
    at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)
    at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
    at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
    at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(AccessController.java:207)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
    FINEST: Lock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
    FINEST: Unlock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
    WARNING: Error: while executing BatchRiskAnalysis for JobId=395 and object(s):ABROWN: Skipping error to continue with next object: null Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
    FINEST: --- @@@@@@@@@@@ Updating the Job History -
    2@@Msg is Error while executing the Job for Object(s) :ABROWN:null
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
    INFO: -
    Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
    FINEST: Lock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
    FINEST: Unlock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
    INFO: --- BKG User Permission Analysis (System: P20:020) completed ---  elapsed time: 4522 ms
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
    Edited by: Linda Lewis on Feb 9, 2011 9:08 PM

    Hi,
    Was a solution found for this error?
    Thanks,
    Glen

  • Error while executing the Job:Cannot assign NULL to host variable 1

    Hello!
    I have the following issue:
    Error while executing the Job:Cannot assign NULL to host variable 1. setNull() can only be used if the corresponding column is nullable. The statement is "INSERT INTO "VIRSA_... (see log for details)
    Note 1362138 - Rule generation - null pointer exception virsa_cc_rtmap  doesn't me. After uploading files of ZCC_DOWNLOAD_SAPOBJ and ZCC_DOWNLOAD_DESC I got the same problem during job running...
    How can I find out where is the problem?

    Hi
    That looks like your fields are disabled but they could still be causing the problem edited ( nah - talking rubbish as you've put dummy " " in there) edited - the 'null' error caused many background jobs to fail but, once we had the evidence to show the space (somebody had pressed enter instead of delete/backspace to clear the entry) it stopped the problem - just a bit of learning on the job which we all go through for the GRC chaps in KL.
    A " " would be valid but a    (I know you can't see it but it's there wouldn't be      )
    edited.When you did an edit/replace did it say it had replaced anything please?edited
    The word doc option does sound good!
    Cheers
    David
    Edited by: David Berry on Nov 4, 2010 7:33 PM

  • Error while executing Batch Risk Analysis job in full sync mode

    Hi Gurus,
    I am getting following error while executing Batch Risk Analysis job in full sync mode for the first time, please help me out.
    May 12, 2011 3:57:26 AM com.virsa.cc.multi.node.dao.NodeDAO deleteMTGenObjTable
    INFO: In deleteMTGenObjTable() deleting from VIRSA_CC_MTGENOBJ for jobid = 100
    May 12, 2011 3:59:53 AM com.virsa.cc.multi.node.dao.NodeDAO deleteMTGenObjTable
    INFO: In deleteMTGenObjTable() deleting from VIRSA_CC_MTGENOBJ for jobid = 100
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchSyncAndAnalysis
    INFO: --- Batch Sync/Analysis/Mgmt Report completed ---  elapsed time: 104907817 ms
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BgJob setStatus
    INFO: Job ID: 100 Status: Error
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
    FINEST: --- @@@@@@@@@@@ Updating the Job History -
    2@@Msg is Error Job not completed
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
    INFO: -
    Background Job History: job id=100, status=2, message=Error Job not completed
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
    INFO: -
    Complted Job =>100----
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
    INFO: Daemon idle time longer than RFC time out, terminating daemon [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start
    INFO: Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 terminiated
    May 12, 2011 4:00:35 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/.&threadId=0&daemonType=BG
    May 12, 2011 4:01:36 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/.&threadId=0&daemonType=BG
    May 12, 2011 4:02:37 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/.&threadId=0&daemonType=BG
    May 12, 2011 4:02:37 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start
    INFO: Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 started
    May 12, 2011 4:02:38 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start
    FINEST: Another Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 is already running

    Hi,
    May be it worked in your case How the job names going to affect the execution of the job. The issue is purely because of RFC timeout (As per the logs). I recommend to change the parameter in the configuration tab as recommended by Sunny in the previous thread.
    Regards,
    Raghu

  • From Time to Time error while executing RMAN Job

    Hi everybody,
    i have a strange problem. From time to time i recieve following error when executing a Job from Grid Control (Enterprise Manager).
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-04004: Fehler aus Recovery-Katalog-Datenbank: ORA-12170: TNS: Connect Timeout aufgetreten
    After that error the Job uses the Control File of the Database so the job runs. The strange thing for me is, that sometimes the jobs runs without problems and sometimes it gaves the error shown above.
    For clarifying. Grid Control runs on a Unix (Sun Solaris) Machine and the target Database runs on a Windows Server in a DMZ. I tried to find out what the problem is but neither on the windows server nor on the firewall side there are any problems.
    So can anybody help me finding out what the problem is?
    Any help would be appreciated.
    Greetings

    Hi sunny,
    i have tried the tnsping several times. There is no problem with this. The tnsping works without problems and in an appropriate time.
    When i issue the command on our unix machine it shows the following:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = srvxyz)(PORT = 1521))) (CONNECT_DATA = (SID = db1) (SERVICE_NAME = db1)))
    OK (10 msec)
    And when issue it on the Windows Server the follwoing output is shown:
    TNS Ping Utility for 64-bit Windows: Version 10.2.0.4.0 - Production on 26-APR-2011 10:35:45
    Copyright (c) 1997, 2007, Oracle. All rights reserved.
    Parameterdateien benutzt:
    O:\ORACLE\product\10.2.0\network\admin\sqlnet.ora
    Adapter TNSNAMES zur Auflösung des Alias benutzt
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = tcp.world)(PROTOCOL = TCP)(Host = SRVXYZ)(Port = 1521))) (CONNECT_DATA = (SID = db1)))
    OK (0 ms)
    So any other ideas??

  • Code in before report getting executed but "Job error is: BIP job failed."

    Customer is executing a BIP job that fires a pl/sql procedure via before report trigger. Procedure is completing successfully. But the BIP report is not getting generated. ESS process ends in error with the following error:
    oracle.as.scheduler.ExecutionErrorException: ESS-07033 Job logic indicated a system error occurred while executing an asynchronous java job for request 604103. Job error is: BIP job failed.
         at oracle.as.scheduler.rp.AsyncFinalizeProcessor.processFinalizeRequest(AsyncFinalizeProcessor.java:131)
         at oracle.as.scheduler.rp.AsyncJavaSysExecWrapper.finalizeExecution(AsyncJavaSysExecWrapper.java:250)
         at oracle.as.scheduler.rp.EndpointProcessor.finalizeExecute(EndpointProcessor.java:1018)
         at oracle.as.scheduler.rp.EndpointProcessor.finalizeExecuteWrapper(EndpointProcessor.java:980)
         at oracle.as.scheduler.adapter.EndpointImpl.finalizeExecute(EndpointImpl.java:561)
         at oracle.as.scheduler.ejb.EssAppEndpointBean.finalizeExecute(EssAppEndpointBean.java:162)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy197.finalizeExecute(Unknown Source)
         at oracle.as.scheduler.ejb.ESSAppEndpoint_t596cy_MDOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.MDOMethodInvoker.invoke(MDOMethodInvoker.java:35)
         at oracle.as.scheduler.ejb.ESSAppEndpoint_t596cy_MDOImpl.finalizeExecute(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.invokeFinalizeExecute(RequestProcessor.java:8133)
         at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.execStage_Finalize(RequestProcessor.java:7331)
         at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.process_execute(RequestProcessor.java:4813)
         at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.dispatchHandler(RequestProcessor.java:2833)
         at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.processExecuteEvent(RequestProcessor.java:696)
         at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.processUpdateEvent(RequestProcessor.java:1345)
         at oracle.as.scheduler.adapter.ra.WorkUnitWorkerBase.processWork(WorkUnitWorkerBase.java:199)
         at oracle.as.scheduler.adapter.ra.WAWorker.run(WAWorke...
    Any tips/pointers on possible issues? Could this be a template corruption?

    Any reply for the above error please.I do have the same issue.
    Please suggest.

  • Error executing job

    I encountered the following error when running a job with transformation:
    'The job to calculate usage dependencies cannot be executed because the job contains obsolete connection information. Please notify Customer Support'
    What might be the cause?
    Thanks

    Background : in every repository there are some hidden jobs that calculate the usage dependencies needed to show impact and lineage information in the management console. These jobs use a (hidden) datastore with the connection to your repository. When you change the repository password at the database level, the connection information in this hidden datastore will not be valid anymore. I'm assuming this is what happend in your case.
    In order to solve this :
    1) Start Designer and go to Tools / Options / Job Server / General
    2) Add the following attribute values to unhide the hidden objects in the repository :
    Section : STRING
    Key : DisplayDIInternalJob
    Value : TRUE
    3) Click OK to close the options window.
    4) Now restart Designer to enforce the new options.
    5) You will see a new datastore with the name CD_DS_d0cafae2. Edit the datastore with the correct connection parameters for your repository.
    6) To hide the datastore again, repeat steps 1-4 but use FALSE as the value.
    Hope this helps. If you search the documentation for "Display DI Internal Job" you will get some more detail (Designer Guide / Executing jobs).

  • F150 Dunning selection executed, job deleted

    Hi ,
    Pl let me know that from tcode F150 i am getting error like "Dunning selection executed, job deleted".
    after defining Parameter & scheduling the job, it is deleting. Whereas It should come "selection scheduled for 28.08.05   at 00:00:00".
    Thanks,
    Chandra Prakash

    Did you try to debug it? Put a break-point inside the 'JOB PREAPARATION' routine in the include LF150F01 and check whether the Job is created?
    good luck,
    Suresh Datti

  • Error in Backup job scheduling in DB13

    Hi All
    Backup job scheduled in DB13 kicks error ,I am using Oracle as database and ERP6.0
    database and application are on diffrent servers.Before it was working fine,I didn't changed any password
    I can run backupjob sucessfully directly from BRtools on database server.Please provide any hint
    Job started
    Step 001 started (program RSDBAJOB, variant &0000000000060, user )
    No application server found on database host - rsh/gateway will be used
    Execute logical command BRBACKUP On host DLcSapOraG08
    Parameters:-u / -jid INLOG20090120204230 -c force -t online -m incr -p initerd.sap -w use_dbv -a -c force -p in
    iterd.sap -cds -w use_rmv
    BR0051I BRBACKUP 7.00 (31)
    BR0128I Option 'use_dbv' ignored for 'incr'
    BR0055I Start of database backup: bdztcorv.ind 2009-01-20 20.42.31
    BR0484I BRBACKUP log file: D:\oracle\ERD\sapbackup\bdztcorv.ind
    BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
    BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
    'CONNECT /'
    ORA-01017: invalid username/password; logon denied
    BR0310E Connect to database instance ERD failed
    BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
    BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
    'CONNECT /'
    ORA-01017: invalid username/password; logon denied
    BR0310E Connect to database instance ERD failed
    BR0056I End of database backup: bdztcorv.ind 2009-01-20 20.42.32
    BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
    BR0054I BRBACKUP terminated with errors
    BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
    BR0291I BRARCHIVE will be started with options '-U -jid INLOG20090120204230 -d disk -c force -p initerd.sap -cds -w use_rmv'
    BR0002I BRARCHIVE 7.00 (31)
    BR0181E Option '-cds' not supported for 'disk'
    BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
    BR0301W SQL error -1017 at location BrDbConnect-2, SQL statement:
    'CONNECT /'
    ORA-01017: invalid username/password; logon denied
    BR0310W Connect to database instance ERD failed
    BR0007I End of offline redo log processing: adztcorw.log 2009-01-20 20.42.32
    BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
    BR0005I BRARCHIVE terminated with errors
    BR0280I BRBACKUP time stamp: 2009-01-20 20.42.33
    BR0292I Execution of BRARCHIVE finished with return code 3
    External program terminated with exit code 3
    BRBACKUP returned error status E
    Job finished

    Hi,
    not sure if the recommendations given will address this issue.
    You are getting this error:
    BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
    'CONNECT /'
    ORA-01017: invalid username/password; logon denied
    the log file indicates:
    > No application server found on database host - rsh/gateway will be used
    This indicated that the user that is connecting from the AS to the DB server is not properly configured to perform the DB tasks on it.
    So, first question would be to know if you have configured a gateway on the DB server and how, or if you are using remote shell.
    Second question, you can do backups on the DB server.
    > I can run backupjob sucessfully directly from BRtools on database server
    How did you run exactly the backup job (what is the exact command line, what is the exact OS user that executed it)?
    What is the OS of the DB server?
    I have reread your post, your OS is windows therefore you fall in the "typical" error in Windows.
    You have executed your backup as <sid>ADM and it works. Unfortunatelly, in windows, SAP is exectuted by SAPSERVICE<sid>, and this is the user who should be connecting to your DB server, and this is the user who cannot execute the backup.
    The fact that you can run the backup with <sid>ADM in Windows does not means that you have SAPService<sid> properly configured.
    For the error (see before) I think your ops$ user for this user is not properly configured in the DB server. take a look at the note mentioned by KT and pay attention to the SAPSERVICE<sid> configuration
    Edited by: Fidel Vales on Jan 24, 2009 12:45 AM

Maybe you are looking for