Time Out - ODS to ODS

Question

Hi Experts,
I am loading data from one ODs C1 to another ODs C2 with routines written in between these 2. loading of data works fine in dev but gives a dump : time out in quality ....
Runtime Errors         TIME_OUT
Date and Time          08.04.2008 09:41:12
Short text
     Time limit exceeded.
What happened?
     The program "GP4993111HUC1PPLV19LJVF0F7O" has exceeded the maximum permitted
      runtime without
     interruption and has therefore been terminated.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
    After a specific time, the program is terminated to make the work area
    available to other users who may be waiting.
    This is to prevent a work area being blocked unnecessarily long by, for
    example:
    - Endless loops (DO, WHILE, ...),
    - Database accesses with a large result set
    - Database accesses without a suitable index (full table scan)
    The maximum runtime of a program is limited by the system profile
    parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this
     time limit is
    exceeded, the system attempts to cancel any running SQL statement or
    signals the ABAP processor to stop the running program. Then the system
    waits another 60 seconds maximum. If the program is then still active,
    the work process is restarted.
How to correct the error
    Programs with long runtime should generally be started as background
    jobs. If this is not possible, you can increase the system profile
    parameter "rdisp/max_wprun_time".
    Depending on the cause of the error, you may have to take one of the
    following measures:
    - Endless loop: Correct program;
    - Dataset resulting from database access is too large:
      Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
      (for example);
    - Database has unsuitable index: Check index generation.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "TIME_OUT" " "
    "GP4993111HUC1PPLV19LJVF0F7O" or "GP4993111HUC1PPLV19LJVF0F7O"
    "R0011_A_CLINVDT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
     Display the system log by calling transaction SM21.
     Restrict the time interval to 10 minutes before and five minutes
  after the short dump. Then choose "System->List->Save->Local File
  (Unconverted)".
  3. If the problem occurs in a problem of your own or a modified SAP
  program: The source code of the program
     In the editor, choose "Utilities->More
  Utilities->Upload/Download->Download".
  4. Details about the conditions under which the error occurred or which
  actions and input led to the error.
How to solve this error???
Regards,
Vaishnavi

Answer 1

Hi Vaishnavi,
The error itself provided u the required solutions to retify it.
How to correct the error
Programs with long runtime should generally be started as background
jobs. If this is not possible, you can increase the system profile
parameter "rdisp/max_wprun_time".
Depending on the cause of the error, you may have to take one of the
following measures:
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
*Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table*
(for example);
- Database has unsuitable index: Check index generation.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"TIME_OUT" " "
"GP4993111HUC1PPLV19LJVF0F7O" or "GP4993111HUC1PPLV19LJVF0F7O"
"R0011_A_CLINVDT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
you can try any of these methods.
Regards,
Rajkandula