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

BWA index creation on Compressed Cube is not finishing


Here is my BWA details .


8 blades of 16 GB each

Rev 52

Global Parameters :


NUMPROC u2013 6

PKTSIZE u2013 100Million

Based on the BWA alert messages we have received from IBM team, decided to drop and reload the cube data from BWA. The cube is fully compressed and it has 126Million records.

This rebuild step use to take anywhere between 4 to 8 Hrs. So we have started this step over week-end by thinking that the job will be completed before Monday morning.

This is the first time we are rebuilding this compressed cube after we applied Rev 52 and the loading process was not as expected.

I see 3 child and one main job in SM37 as soon as I kickoff the BWA index creation step.

1st child process completed after 2 ½ Hrs and loaded 9.5 million records into BWA

2nd child process started sending data after 2 hrs of the actual start time and took 9 hrs to send 41 Million records.

3rd one started after 4 hrs and it was loading only 300,000 records/Hour.

We have created a VeryHigh Priority ticket with SAP but not got much useful info yet.

Any one come across the similar issue and what would be the better way to increase the overall loading process.

Your help is greatly appreciated.



Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Oct 13, 2009 at 04:06 PM

    It is certainly too long. Can your Basis folks check what's going on BWA server side? Seems like this 3rd job has a problem with corresponding service on the accelerator side. if it is indeed the problem on server side, check that all software parameters are the same on that blade comparing to others.



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 15, 2009 at 04:21 PM

    Thank you Sourabh and Vitaliy.

    We have round robin turned ON as part of the BWA implementation.The current status is,

    SAP/IBM looking at it with LEVEL 2 support team and trying to analyze the SQL statements and see why they are behaving differently.

    Will update the message when I see a concrete solution from SAP.

    Thank you every one.


    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.