Skip to Content
author's profile photo Former Member
Former Member

Very slow when reading data from archived files

Hi,

We have archived data from SAP R3 (FI module) to IBM CommonStore server.

The archiving objects are FI_DOCUMNT & FI_SL_DATA.

While reading the data after archiving, for object FI_DOCUMNT, through transaction FBL3N, it is taking too much time and then throwing memory dump TSV_TNEW_PAGE_ALLOC_FAILED for e.g. around half an hour to read one months data.

Kindly suggest what should be done.

ALso, when we try to access the data using tcode SARI it is very fast, however problem is that all fields are not shown on the first selection screen. Due to which this is not of much use.

Thanks & Regards,

Kunal Patel.

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Best Answer
    Posted on Nov 13, 2008 at 02:51 AM

    Hi Kunal Patel,

    If you have more application servers try to log into the server on which memory usage is low (you can check this with ST02 T code execute this on the log in server Roll area, Paging area and Extended Memory), are else try to execute your transaction FBL3N when there is less memory usage on the server. If either is not worked need to tune memory parameters.

    Regards,

    S.Manu.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 14, 2008 at 03:10 AM

    Hi Kunal

    Let me explain to you how this works

    When you archive the data, it moves out of the database into a flat file which is latter stored on optical disk/hard disk etc depending upon your archiving solution

    When archving is done, it also creates an index ( depending upon how your have configured the object) This index is of few common fields of the archived objects . This is than stored within SAP. When you call SARI you seen this indexed data from SAP and hence the response is quick. At this point it does not get the data from your archives

    When you call it through the transaction FBL.. , it needs all the fields ( which are not avl in the indexed data ) and hence SAP has to go to the archives to fetch it

    This results in slowing it down.

    Now how slow will it be is a difficult question for us to answer as a lot denpends upon your archiving solution and how much data are you trying to fetch

    As far as memory problem is concerned you need to analsye the dump as to where ( on what buffer parameter is it failing) Depending upon that you will have to either increase memory parmeters OR reduce the amount of data your a fetching

    Thanks

    Naushad

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2009 at 04:50 AM

    solved by creating new infostructure & field catalog and retreiving data through sari after filling infostructures...

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 06, 2011 at 08:29 AM

    Hi Kunal,

    Iam also facing the same problem.Could you explain me how to extract from sari.I have done this.do we need BI for this?

    Pls help me.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 06, 2011 at 08:30 AM

    Sorry for the last post.Instead of "I have not done" I have written " I have done".

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.