Long running job in BW source system - Urgent

Hello,
While loading BW data delta load for data source 0CO_OM_CCA_9 the
corresponding R/3 job is taking the long time to complete approximately
3 days.
When we checked the Job log in the Source sytem we found the following
entry
"2 LUWs confirmed and 2 LUWs to be deleted with function module
RSC2_QOUT_CONFIRM_DATA"
and job is taking too much time to complete this task.
Can you please help me out to resolve this issue at earliest?
Best Regards

Hi Venkata,
When you check indexes in SE11 -> COEP -> Index 4
You may see the status as "Active", but did u check the line below ?
it should read
"Index COEP~4 exists in database system"
If it reads
"Index does not exist in database system" , then the INDEX 4 is not active and not used.
Cheers,
Praveen.

Similar Messages

  • Job terminated in source system -- Request set to red,SAPSQL_SQLS_INVALID_

    Hi All,
    can any one help on this issue.
    I run the BI statistics in production and found out the error while triggering the delta's
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System Response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Extractor .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
    Error msg :  Job terminated in source system --> Request set to red
    Message no. RSM078
    Job started
    Step 001 started (program SBIE0001, variant &0000000000756, user ID
    Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
    DATASOURCE = 0TCT_DSA1
    RLOGSYS = BCLNT300
    REQUNR = REQU_D4GZHNLA3PSQ7XRNGL0EMV6AP
    UPDMODE = D
    LANGUAGES = *
    Current Values for Selected Profile Parameters *
    abap/heap_area_nondia......... 0 *
    abap/heap_area_total.......... 2147483648 *
    abap/heaplimit................ 40894464 *
    zcsa/installed_languages...... ED *
    zcsa/system_language.......... E *
    ztta/max_memreq_MB............ 2047 *
    ztta/roll_area................ 3000320 *
    ztta/roll_extension........... 2000683008 *
    ABAP/4 processor: SAPSQL_SQLS_INVALID_CURSOR
    Job cancelled
    But delta laoding for same is working in DEV...but not in prod...
    Please suggest
    Regards
    Shweta

    Swetha
    finally found out the notes.
    Please look into them and ask you basis to implemnt,
    1161940
    1106569
    1145041
    1146851
    Please have a look and ask for implemtation in your system which are suitable for you
    We also faced the same issue job termination in source system for BI Statistics
    Regards#
    Srini

  • Job Termination in source system-Dataload failure

    Hello Forum,
    We are on BW 3.1 and our source is SAP R/3 Enterprise.
    We have been facing a recurring problem for a dataload, that is JOB TERMINATION IN SOURCE SYSTEM.
    Details of the load:
    Target:Master Data
    Full load
    Processing:      PSA and InfoObject table in se

    Sorry, it got posted before I completed it.
    Please find the full details here:
    Hello Forum,
    We are on BW 3.1 and our source is SAP R/3 Enterprise.
    We have been facing a recurring problem for a dataload, that is JOB TERMINATION IN SOURCE SYSTEM.
    Details of the load:
    Target:Master Data
    Update Mode: Full load
    Processing: PSA and InfoObject table in series
    Selections: None
    Records Check:Terminate if errors occur; Aggregation    permitted
    Character Check: Switched off
    This has been delaying the loads for a long long time.
    Could you please suggest us the ways to fix this problem?
    Thanks is advance,
    Raj

  • Trigger Alert for Long Running Jobs in CPS

    Hello,
    I am currently trying to make a trigger so that I can monitor the long running jobs in the underlying ERP. Can you help me on the APIs to use?
    Im trying to modify my previous alert - Chekcing of failed jobs
      // only check error jobs
      if (jcsPostRunningContext.getNewStatus().equals(JobStatus.Error)) {
        String alertList = "email address ";
        String [] group = alertList.split(",");
        for (int i = 0; i < group.length; i++) {
          JobDefinition jobDefinition = jcsSession.getJobDefinitionByName("System_Mail_Send");
          Job aJob = jobDefinition.prepare();
          aJob.getJobParameterByName("To").setInValueString(group<i>);
          aJob.getJobParameterByName("Subject").setInValueString("Job " + jcsJob.getJobId() + " failed");
          aJob.getJobParameterByName("Text").setInValueString(jcsJob.getDescription());
    Im trying to look for the API so I can subtract the system time and the start time of the job and compare it to 8 hours?
    if (jcsPostRunningContext.getNewStatus().equals(JobStatus.Error)) {    <--  Can I have it as ( ( Start Run Time - System Time ) > 8 Hours )
    Or is there an easier way? Can somebody advise me on how to go about this one?

    Hi,
    You can do it using the api:
    if ((jcsJob,getRunEnd().getUTCMilliSecs() - jcsJob.getRunStart().getUTCMilliSecs()) > (8*24*60*1000))
    This has the drawback that you will only be notified when the job finally ends (maybe more then 8 hours!).
    The more easier and integrated method is using the Runtime Limits tab on your Job Definition or Job Chain. This method can raise an event when the Runtime Limit is reached. The event can trigger your notification method.
    Regards Gerben

  • Re:How to determine the long running jobs in a patch

    Hi ,
    How to determine the long running jobs in a patch .
    Regards

    Hi,
    Check the below MY ORACLE SUPPORT note:
    Note.252422.1 .... Check Completed Long Running Jobs In Oracle Apps.
    Best regards,
    Rafi

  • Job termination in source system

    Dear All,
         I am trying to load payroll data using Datasource ZHR_PY_1 . I am doing init data for the first time using infopackage for this datasource. I have tried to pull a couple of years, 2 months, even 1 day of data, but all give me the same error.
    The error is
    1.The request turns red after a couple of hrs pulling zero records.
    2. Error Message says Job terminated in source system.
    3.Step by step analysis says
    red - data selection successfully started
    red - data selection successfully finished
    red - processing error in source system.
    Error says "error occured in data selection"
    If I go to RSA7 in R/3, datasource ZHR_PY_1 has yellow status.
    RSA6 shows everything active.
    Can anybody make out what may be the reasons why BI system is not able to connect to pull R/3 data.
    Regards,
    Jack

    Hi,
    Some times the source system needs a lot of time to "prepare" the output records and will got through a lot of tables before getiing any result how small it may be.
    But also try the options as given by the others consultants (as RSA3, checking the system connection, replicate and activae data source again.)
    Your can also use tx SMQ2 u2013 qRFC-monitor in R/3 to see what happened.
    Success,
    Udo

  • Prgess indicator on long running jobs

    I have an FX application that is directly linked to my database. The program allows all DML operations as well as user defined actions (action commands and various other methods). I have the same application running in Swing, SWT, Canoo ULC and al works just fine. In each of the other front end types, the application automatically displays a busy indicator when a long running job is executed. Now I need this in FX.
    My application is basically a Rich Client framework which allows the same business logic and forms to have different front ends depending on customer requirements. The application is built by customers in a 4GL style development tool. The application is actually built at run time and the data is provided by the user through various services. Because I am building an FX program for a framework, I don't know when the user may execute a long running job when, for example, a button is pressed. I have full control over the retrieval and modification of data but not user interaction. I am therefore looking for a busy indicator that comes automatically when the main thread is waiting.
    Any help would be great!

    Hi guys and thanks for your answers
    I may have stretched the mark with "long running jobs" by these I mean a database query, a price calculation, order process etc. These are standard jobs that are issued on a Rich Client application. Basically I have a screen which will execute a query, and I want to give the user feedback when the query is executing so that he doesn't think that the application has hung. In Swing I have done this by creating my own event queue with a delay timer:
    public class WaitCursorEventQueue extends EventQueue implements DelayTimerCallback
        private final CursorManager cursorManager;
        private final DelayTimer    waitTimer;
        public WaitCursorEventQueue(int delay)
            this.waitTimer = new DelayTimer(this, delay);
            this.cursorManager = new CursorManager(waitTimer);
        public void close()
            waitTimer.quit();
            pop();
        protected void dispatchEvent(AWTEvent event)
            cursorManager.push(event.getSource());
            waitTimer.startTimer();
            try
                super.dispatchEvent(event);
            finally
                waitTimer.stopTimer();
                cursorManager.pop();
        public AWTEvent getNextEvent() throws InterruptedException
            waitTimer.stopTimer(); // started by pop(), this catches modal dialogs
            // closing that do work afterwards
            return super.getNextEvent();
        public void trigger()
            cursorManager.setCursor();
    }I then implemented this into my application like this:
    _eventQueue = new WaitCursorEventQueue(TIMEOUT);
    Toolkit.getDefaultToolkit().getSystemEventQueue().push(_eventQueue);Now each time the application waits for a specific time, the cursor will become a wait timer. This give s the user a visual feedback so that he knows that the application is working and not just hung. By doing this, I do not need to wrap each user callout in a timer. Much easier like this!
    I would like to implement the same in FX.
    Edited by: EntireJ on Dec 15, 2011 12:34 AM

  • Reg: job termination in source system

    hi experts
    can anyone tell me solution for this problem after loading infopackage, status of the infopackage is showing is like this "job termination in source system", but i checked with ss it showing job gets cancelled. but i am not assigned any to the data source, so how can eliminate this problem.
    regards
    harikrishna.N

    HI
    This can happen when request IDOC is sent source system, but the source system for some reason is not available.     
    Ensure that source system is available. Change technical status of request to red and delete request from datatarget. Trigger Infopackage again to get data from source system.
    Cheers,
    Raj

  • Long Running Jobs based on average time of last 5 run

    Hi Experts,
    I need a query to find out the Long Running Jobs, based on average time of last 5 run.
    Could you please help me.
    Thanks in advance. 
    --------------------------------- Devender Bijania

    SELECT 
        [sJOB].[name] AS [JobName]
        , CASE 
            WHEN [sJOBH].[run_date] IS NULL OR [sJOBH].[run_time] IS NULL THEN NULL
            ELSE CAST(
                    CAST([sJOBH].[run_date] AS CHAR(8))
                    + ' ' 
                    + STUFF(
                        STUFF(RIGHT('000000' + CAST([sJOBH].[run_time] AS VARCHAR(6)),  6)
                            , 3, 0, ':')
                        , 6, 0, ':')
                    AS DATETIME)
          END AS [LastRunDateTime]
        , CASE [sJOBH].[run_status]
            WHEN 0 THEN 'Failed'
            WHEN 1 THEN 'Succeeded'
            WHEN 2 THEN 'Retry'
            WHEN 3 THEN 'Canceled'
            WHEN 4 THEN 'Running' -- In Progress
          END AS [LastRunStatus]
        , STUFF(
                STUFF(RIGHT('000000' + CAST([sJOBH].[run_duration] AS VARCHAR(6)),  6)
                    , 3, 0, ':')
                , 6, 0, ':') 
            AS [LastRunDuration (HH:MM:SS)]
          , CASE [sJOBSCH].[NextRunDate]
            WHEN 0 THEN NULL
            ELSE CAST(
                    CAST([sJOBSCH].[NextRunDate] AS CHAR(8))
                    + ' ' 
                    + STUFF(
                        STUFF(RIGHT('000000' + CAST([sJOBSCH].[NextRunTime] AS VARCHAR(6)),  6)
                            , 3, 0, ':')
                        , 6, 0, ':')
                    AS DATETIME)
          END AS [NextRunDateTime]
    FROM 
        [msdb].[dbo].[sysjobs] AS [sJOB]
        LEFT JOIN (
                    SELECT
                        [job_id]
                        , MIN([next_run_date]) AS [NextRunDate]
                        , MIN([next_run_time]) AS [NextRunTime]
                    FROM [msdb].[dbo].[sysjobschedules]
                    GROUP BY [job_id]
                ) AS [sJOBSCH]
            ON [sJOB].[job_id] = [sJOBSCH].[job_id]
        LEFT JOIN (
                    SELECT 
                        [job_id]
                        , [run_date]
                        , [run_time]
                        , [run_status]
                        , [run_duration]
                        , [message]
                        , ROW_NUMBER() OVER (
                                                PARTITION BY [job_id] 
                                                ORDER BY [run_date] DESC, [run_time] DESC
                          ) AS RowNumber
                    FROM [msdb].[dbo].[sysjobhistory]
                    WHERE [step_id] = 0
                ) AS [sJOBH]
            ON [sJOB].[job_id] = [sJOBH].[job_id]
            AND [sJOBH].[RowNumber] = 1
    ORDER BY [LastRunDateTime] desc,
             [LastRunDuration (HH:MM:SS)] DESC
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • How to research a long running job from 3 days ago

    Re: How to research a long running job from 3 days ago
    Client called to say that a job that normally runs for 6 hours ran for 18 hours on 11/01. 11/01 was a Saturday, and end of month. The long running job writes to a log and I can from the log that that the problem started right around 10:43am. Every step
    before 10:43 was taking the normal amount of time. Then at 10:43 a step that takes seconds hung for 12 hours. After 12 hours the step finished and the job completed successfully.
    I looked at the SQL Log, Event Log, Job History (for all jobs). What else can I look at to try and resolve an issue that happened on 11/01/2014?

    It does execute an SSIS package.
    Personally I feel this as kind of bug in SSIS package but I am not expert in SSIS so I would move it to SSIS forum. Please update your question giving complete information what SSIS package does.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • This is urgent please help!  long running job in sm37 but not in sm66

    Hi,
    Can someone please help for an explanation as to why if you call sm37, you can see that the job is long running (example about 70,000 sec), but when you look at the PID where the job is running in sm66 it does not show 70,000 sec but only around 6,000 sec.
    Can someone please explain why?  Thank you very much

    For background processes, additional information is available for the background job that is currently running. You can only display this information, if you are logged onto the instance where the job is running, or if you choose Settings and deselect Display only abbreviated information, avoid RFC. In any case, the job must still be running.
    Regards
    Anilsai

  • Job terminated in source system -- Request set to red

    Hi Developers and supporters can you any one help me.
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System Response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Extractor .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the
    Date        Time      Message
    13.10.2010  16:48:01  Job started
    13.10.2010  16:48:01  Step 001 started (program SBIE0001, variant &0000000024579, user ID RFCUSR)
    13.10.2010  16:48:01  DATASOURCE = 0ACTIVITY_ATTR
    13.10.2010  16:48:01  *************************************************************************
    13.10.2010  16:48:01  *          Current Values for Selected Profile Parameters               *
    13.10.2010  16:48:01  *************************************************************************
    13.10.2010  16:48:01  * abap/heap_area_nondia......... 2000683008                              *
    13.10.2010  16:48:01  * abap/heap_area_total.......... 2000683008                              *
    13.10.2010  16:48:01  * abap/heaplimit................ 40894464                                *
    13.10.2010  16:48:01  * zcsa/installed_languages...... 6EDGIJL                                 *
    13.10.2010  16:48:01  * zcsa/system_language.......... E                                       *
    13.10.2010  16:48:01  * ztta/max_memreq_MB............ 256                                     *
    13.10.2010  16:48:01  * ztta/roll_area................ 6500352                                 *
    13.10.2010  16:48:01  * ztta/roll_extension........... 2000683008                              *
    13.10.2010  16:48:01  *************************************************************************
    13.10.2010  17:57:09  ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
    13.10.2010  17:57:09  Job cancelled

    Hi SUSUSU,
    The dump is related to temp table space issue.check the space for PSATEMP table.
    Use tcode DB02 to check the table spaces, in the tree diaplayed on you left. try to see the % used for your ODS & FACT tablespaces. Incase the % are too high like 99% etc, get in touch with you BASIS team.
    Request your basis team to increase the PSATEMP table space.
    Or
    Decrease the data packet size and run the info package.
    to decreae the packet size -- in the IP screen menu --> schedular -->Datasource setting for sending data --> there change the parameter Maximum size of a data packet in kByte.
    down you can find the area to enter the data packet size .
    for ex if it is 20000 decrease it to 10000 and run the info package

  • RE:JOB TERMINATED IN SOURCE SYSTEM.

    Hi Gurus,
                  In production environment while we are trying to load data we recived follwing error message.
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System Response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Extractor .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
    We tried RFC checks, repliacted Data source and activation in BI and all other checks.It seems all OK in BI.When we tried to activate the Data Source in CRM(back end) transation RSA5 its prompting for Work Bench request.my question is are we allowed to create work bench request in production environment? This happens to us even in BI when we try to run an Info package manually I.Can you please advise me what could be othr reasons for the job failure.

    Hi
    We tried RFC checks, repliacted Data source and activation in BI and all other checks.It seems all OK in BI.When we tried to activate the Data Source in CRM(back end) transation RSA5 its prompting for Work Bench request.my question is are we allowed to create work bench request in production environment? This happens to us even in BI when we try to run an Info package manually I.Can you please advise me what could be othr reasons for the job failure.
    Hope you have checked RFC at Source system side SM58/59/66 and IDOCs BD87,WE05 also.
    Yes some times it will prompt the Work Bench Request at Source system side too. But do not create any new request for this. Try to see for the Request locks -- Check back with BASIS team for this-- Happens if the 2 or more process/jobs trying to hit at same point this will happen.
    Better to cancel/delete the present request and Repeat Delta.
    Hope it helps

  • Job termination in source system /Asynchronous transmission of info IDoc 2

    Hi All,
    We have certain loads that we do every 2 hours, which will run for 20 to 30 minutes to load current year BCS data into a Basic Cube. So, In total we schedule 12 times in a day. This is needed as we have users around the globe.
    We have totally 10 BGD processes and 10 Dialog processes.
    These loads are scheduled through a process chain and we submit three parallel jobs at a time based on the version and in total we have 15 loads, 5 per each parallel job.
    We went live with this process yesterday and the jobs ran all well until today afternoon, when they started giving the following message and when I checked the log of the process chain, one of the InfoPackage did fail with job termination in the source system.
    The job log is as follows:
    Date       Time     Message text                                                                 Message class Message no. Message type                                                                               
    06/20/2007 13:55:47 Job started                                                                       00           516          S       
    06/20/2007 13:55:47 Step 001 started (program SBIE0001, variant &0000000014146, user ID RFCUSER)      00           550          S       
    06/20/2007 13:55:47 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)          R3           413          S       
    06/20/2007 13:55:47 DATASOURCE = 80BCS_VC10                                                           R3           299          S       
    06/20/2007 13:55:47 *************************************************************************         R8           048          S       
    06/20/2007 13:55:47 *          Current Values for Selected Profile Parameters               *         R8           049          S       
    06/20/2007 13:55:47 *************************************************************************         R8           048          S       
    06/20/2007 13:55:47 * abap/heap_area_nondia......... 2000683008                              *        R8           050          S       
    06/20/2007 13:55:47 * abap/heap_area_total.......... 2000683008                              *        R8           050          S       
    06/20/2007 13:55:47 * abap/heaplimit................ 40894464                                *        R8           050          S       
    06/20/2007 13:55:47 * zcsa/installed_languages...... EFD                                     *        R8           050          S       
    06/20/2007 13:55:47 * zcsa/system_language.......... E                                       *        R8           050          S       
    06/20/2007 13:55:47 * ztta/max_memreq_MB............ 2047                                    *        R8           050          S       
    06/20/2007 13:55:47 * ztta/roll_area................ 3000320                                 *        R8           050          S       
    06/20/2007 13:55:47 * ztta/roll_extension........... 2000683008                              *        R8           050          S       
    06/20/2007 13:55:47 *************************************************************************         R8           048          S       
    06/20/2007 13:58:04 NONE                                                                             UGBW          001          E       
    06/20/2007 13:58:04 Job cancelled after system exception ERROR_MESSAGE                                00           564          A                                                                               
    I do not have acceess in BWP to get you the Data Transfer Parameters within BW system.
    Any suggestions would be greatly appreciated.
    Thanks & Best Regards,
    - Shashi

    Hi Shashi,
    Check in st22 for any dumps, do you have any pointer there?
    Also check sm21 to identify possible cause of errors.
    Regards.

  • Job terminated in source system  SAPSQL_SQLS_INVALID_CURSOR

    Hi all,
    can any one help on this issue.
    I run the BI statistics and found out the error while triggering the delta's
    Job started
    Step 001 started (program SBIE0001, variant &0000000000756, user ID
    Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
    DATASOURCE = 0TCT_DSA1
    RLOGSYS    = BCLNT300
    REQUNR     = REQU_D4GZHNLA3PSQ7XRNGL0EMV6AP
    UPDMODE    = D
    LANGUAGES  = *
             Current Values for Selected Profile Parameters               *
    abap/heap_area_nondia......... 0                                       *
    abap/heap_area_total.......... 2147483648                              *
    abap/heaplimit................ 40894464                                *
    zcsa/installed_languages...... ED                                      *
    zcsa/system_language.......... E                                       *
    ztta/max_memreq_MB............ 2047                                    *
    ztta/roll_area................ 3000320                                 *
    ztta/roll_extension........... 2000683008                              *
    ABAP/4 processor: SAPSQL_SQLS_INVALID_CURSOR
    Job cancelled
    Edited by: BW User on Nov 10, 2008 11:41 AM

    Hi Arun,
    Source system is also BW itself..No idocs have been archived.
    For other BI statistics its running fine only for this one,,,,it is getting error.
    If i didi INIT W/O data tarnsfer and running the delta,,,delta is failing
    If i did INIT With data then 20000 records are comming after trying to run the delta again the same error is ocmming
    Regards

Maybe you are looking for