Activating data in an ODS takes a very long time.

[Former Member]

Bad performance (4/5 hours) during activation of an ODS with 2/3 millions of records in BW 3.0b SuppPack24.

Does someone know how to reduce the activation time????

[Former Member · Accepted solution]

Hi Piergiorgio,

Parallel ODS Object Data Activation (BW 3.x) can improve activation time significantly.

1)Data Activation can be processed in parallel and distributed to server groups in the BW customizing (transaction RSCUSTA2) in BW 3.x. There are parameters for the maximum number of parallel activation dialog processes, minimum number of records per package, maximum wait time in seconds for ODS activation (if there is no response of the scheduled parallel activation processes within this time, the overall status is red) and a server group for the RFC calls when activating ODS data.

2)Do not set the “BEx Reporting” flag if you do not plan to Report on ODS objects in BEx or in Web. If your reporting requirements on ODS objects are very restricted (e.g., display only very few, selective records), use InfoSets on top of ODS objects and disable the “BEx Reporting” flag.

In BW 3.x, the SIDs are determined during activation, in BW 2.x during data load. ,hence increasing the Activation time

Hope this Helps

-Doodle

[Former Member · Accepted solution]

If you are activating multiple requests at a time which has total no of records as 2/3 million then have a look at OSS Note 790249

[edwin_harpino]

hi,

transaction RSCUSTA2,

oss note 120253 565725 670208

and remove 'bex reporting' setting in ods if that ods not used for reporting.

hope this helps.

565725

Symptom

This note contains recommendations for improving the load performance of ODS objects in Business Information Warehouse Release 3.0B and 3.1 Content.

Other terms

Business Information Warehouse, ODS object, BW, RSCUSTA2, RSADMINA

Solution

To obtain a good load performance for ODS objects, we recommend that you note the following:

1. Activating data in the ODS object

<b> In the Implementation Guide in the BW Customizing, you can implement different settings under Business Information Warehouse -> General BW settings -> Settings for the ODS object that will improve performance when you activate data in the ODS object.</b>

1. Creating SIDs

The creation of SIDs is time-consuming and may be avoided in the following cases:

a) You should not set the indicator for BEx Reporting if you are only using the ODS object as a data store.Otherwise, SIDs are created for all new characteristic values by setting this indicator.

b) If you are using line items (for example, document number, time stamp and so on) as characteristics in the ODS object, you should mark these as 'Attribute only' in the characteristics maintenance.

SIDs are created at the same time if parallel activation is activated (see above).They are then created using the same number of parallel processes as those set for the activation. However:if you specify a server group or a special server in the Customizing, these specifications only apply to activation and not the creation of SIDs.The creation of SIDs runs on the application server on which the batch job is also running.

1. DB partitioning on the table for active data (technical name:

The process of deleting data from the ODS object may be accelerated by partitioning on the database level.Select the characteristic after which you want deletion to occur as a partitioning criterion.For more details on partitioning database tables, see the database documentation (DBMS CD).Partitioning is supported with the following databases:Oracle, DB2/390, Informix.

1. Indexing

Selection criteria should be used for queries on ODS objects.The existing primary index is used if the key fields are specified.As a result, the characteristic that is accessed more frequently should be left justified.If the key fields are only partially specified in the selection criteria (recognizable in the SQL trace), the query runtime may be optimized by creating additional indexes.You can create these secondary indexes in the ODS object maintenance.

1. Loading unique data records

If you only load unique data records (that is, data records with a one-time key combination) into the ODS object, the load performance will improve if you set the 'Unique data record' indicator in the ODS object maintenance.

[former_member184494]

piergiorgio ,

Also try :

1. Uncheck activate subsequent data providers and do the same using a proces chain

2. uncheck activate data automatically and do the same using process chain.

hope this helps,

Arun