Quantcast
Channel: SCN: Message List - Business Content and Extractors
Viewing all articles
Browse latest Browse all 5631

BW statistics load issue

$
0
0

Hi All,

 

I am extracting data into BW statistics cube. I know that data is going to be huge so I am running manually one by one. I started extracting the data into cube 0TCT_C21. After running for few hours it ended in short dump saying "Time limit exceed". It extracted almost 800,000 records and ended with error. I checked TRFC and its in red "with time limit exceeded"
Following is the dump message"

Runtime Errors         TIME_OUT
Date and Time          08.08.2013 11:43:13

 

Short text
     Time limit exceeded.

 

What happened?
     The program "GPD8QJ09M0B7LLIU0X8SFATN28K" 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
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 3600 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.

 

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.

How do I load huge amount of data in one go. I am using 3,x data flow to load the data.

 

Thanks
SK


Viewing all articles
Browse latest Browse all 5631

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>