Skip to Content
author's profile photo
Former Member

Storage limitations of a LUW

Posted on Apr 29, 2004 at 07:36 AM 8 Views

Hello,

Within one logical unit of work (LUW), about 1.5 million records will be added to the SAP database.

These records are divide over 8 different database tables.

The total amount of record size is about 600 MB (as a result of 160.000 real estate objects).

Which SAP requirements do we have to take into account for this in a sense that a we are not confronted with a Commit of rollback area that becomes to large.

We use the following DBMS : SAP DB, DB/2 on iSeries and Oracle on HP9000 and on Windows servers

regards

Bertil Rebergen

ABAP Development SAP Enterprise Portal
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • author's profile photo
    Former Member
    Posted on Apr 29, 2004 at 07:48 AM

    The problems not with SAP, it's with the DB. Not familar with SAP DB inners, but that should make for some large rollback segments, which may well affect performance for other users as well.

    I'm interested in the scenario. Why is it that these "real estate objects" have to be inserted in a single unit of work?

    What happens if the process dies half way through? You've just wasted a stack of processing time.

    Regards,

    Scott

    Add comment
    10|10000 characters needed characters exceeded