Question:
Hi Guys,
When using import from file on selection option, I was under the impression that 5000 is the upper limit on how many entries you can use in the input file (ABAP-wise). Are you aware of any other parameter that limits the number of records that can be used?
I am using that feature for one of my BW reports to input material from file and experiencing some performance issues when the file has more than 40 entries. This is selecting through a large table (batch characteristics) so at least a million of records.
It is strange behavior: this is not a gradual loss of performance but a complete drop based upon a low threshold (# of records). When I have 40 entries the report runs under a minute but if I have 41 then the report times out (error message is Time limit exceeded - RFC_ERROR_SYSTEM_FAILURE).
We already implemented BW statistics and indexes on this table. Any other suggestions?
Thanks,
Kathy
Answer:
Hi Kathy,
Use the menu option Scheduler-> DataS. Default Data Transfer. There you can see the default settings of the Source system:
Max size of a data packet in rows
Number of data packets per Info-IDoc
and below this the place where you can specify settings for that specific DataSource. If you make any setting greater than the source system default values, the system ignores it and uses the default values.
To increase the settings, go to table RSIDOCPRMS (hope I got it right, else, make a search using RSIDO*). There is an OSS note which wil be of help, but offhand I don't remember the number. It has already been mentioned in this forum. Please search the forum using the term RSIDOCPRMS, or some such!
Hope I read your question right?
_________________
Keep smiling
Answer:
Hi SR
Thank you for your time and response.
Unfortunately you did not read me well, probably I was not clear enough in my question.
This is not an extraction related issue but a query one (using Analyzer). Query is timing out unexpectedly....
Any other thoughts?
Kathy
Answer:
Hi SR
Thank you for your time and response.
Unfortunately you did not read me well, probably I was not clear enough in my question.
This is not an extraction related issue but a query one (using Analyzer). Query is timing out unexpectedly....
Any other thoughts?
Kathy
_________________
Keep smiling
Answer:
Did you try to trace the query?
Matt