Search
BWFreak - Journey to the center of Business Intelligence

It’s ideal if all processes in BW process chains can be executed one after another, but sometimes, it’s not possible.

Usually, there’s only certain time frame in a day can be used for BW loading. I need to avoid the maintenance window, the critical hours for users, the inconvenient hours for monitoring and load fixing, etc, etc. Parallel processing is unavoidable.

When running several process chains or several branches in the same process at the same time, extra attention is needed to avoid locking. Here’s a list of BW locks I got.

1. Attribute Change Run lock.

2. Master data lock. infoPackages to the same master data can only be scheduled one at a time.

3. ODS activation lock. infoPackages to the same ODS can be scheduled parallel, but before activating ODS.

4. CUBE/Aggregates related lock.

5. User lock.

To check if the lock is released, use t-code SM12.

To fix the process chain errors caused by locks, use a “repeat” on the red chain step if no infoPackage involved. Otherwise, fix the infoPackage first.

Something to say?

You must be logged in to post a comment.