on 12-10-2011 6:06 PM
Hi guru's, I have a problem with a BW system. I see in SM66 that accessing the table RSBATCHDATA takes a very long time and involves sequential reads. With transaction SM50 I can see that the table is queried with the following command:
SELECT
"BATCH_ID" , "TIMESTA
FROM
"RSBATCHDATA"
WHERE
"RELID" = :A0#
The funny thing is that this table has the following key:
RELID
BATCH_ID
BATCH_PROCESS
METHOD
TIMESTAMP
SRTF2
Therefore I would expect that access to this table should be very fast. Nevertheless, the system that I work with shows me 1205 seconds (and still counting while I write this) and "Sequential read".
Can someone explain this to me? Furthermore: is there a whitepaper about the detailed screen that you see when you double-click a line in SM50.
Jans,
I am not sure but this might be worth a try...
Check the size of the table and see if it can be archived - an index scan on a 1 GB ( for example ) table will still take time...!!!!
Check if there is any archiving that can be done for this table
Check the number of entries in this table - if the table is too large - then you might have to archive this
Also this table is related to data load monitor tables - see if you can implement request archiving if you are on BW7.0 and above
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.