Symptom
- 1. Extraction of data using the CO delta DataSources takes a very long time.
An SQL trace tells you that this is caused by select statements on the COVP table containing a lot of conditions joined with 'OR'.As a result, the optimal COEP indexes 1 (for a full updated) or 4 (for a delta init update or delta update) are not used.
- 2. It may also be useful to implement the correction for this note if the extraction frequently terminates with ORA-01555 short dumps when you access table COVP (see also Note 7634).
Other Terms
Performance, BW-BCT-COOM,
CO delta DataSources
0CO_OM_CCA_9, 0CO_OM_OPA_6, 0CO_OM_ABC_7, 0CO_OM_WBS_6, 0CO_OM_NAE_2, 0CO_OM_NTW_2, 0OC_OM_NWA_2, extractor, BWOMD, delta, BWOMR, ORA155.
Reason and Prerequisites
- Database index 1 or 4 for the table COEP is not active.
- The database system optimizer does not tolerate SELECT-statements with several intervals linked by 'OR' for a field and therefore selects the wrong index.
Solution
- 1. Make sure that indexes 1 and 4 delivered by SAP on the database for the table COEP are active in the form delivered in the standard system. In the standard system, index 4 is not delivered as active and must be manually activated by the customer when using the CO Delta DataSources (see documentation on the InfoSource in the BW content).
- 2. Make sure that indexes defined by the customer do not interfere with the selection. The customer is responsible for these indices. Analysis and elimination of performance problems caused by these indexes is subject to a fee.
- 3. When you use the Oracle Cost-Based Optimizers:
Check whether current and precise statistics exist for tables COEP and COBK. It may be possible to solve the problem by refreshing the statistics.
- 4. If you are already using PI 2001.1 or higher, you can skip implementing the program corrections in the next two steps.
- 5. Implement the corrections in note 409990.
- 6. Implement the attached program corrections. Bear in mind that you first have to implement note 374228!
- 7. By using the maintenance of table BWOM_SETTINGS, you can now set whether several selects without the 'OR' links are transmitted instead of a few conditions linked by 'OR' for the 'OBJNR' field.
-
a) To do this, create an entry (if not already present) in the BWOM_SETTINGS table.
OLTPSOURCE = ' '
PARAM_NAME = 'OBJSELSIZE'
As an alternative, you can use transaction RSA3 to run any of the affected extractors with any of the selection criteria.
-
b) Use transaction SE16 to change the value in the 'PARAM_VALUE' column for the above-mentioned entry of the 'BWOM_SETTING' table to 'X'. This means:
PARAM_VALUE = ' ' as few selects as possible (default)
PARAM_VALUE = 'X' no 'OR' links for 'OBJNR'
Other Attributes
|
Header Data
| Released On | 2002.04.10 22:08:37 |
| Release Status | Released for Customer |
| Component | BW-BCT-CO-OM Overhead Cost Controlling |
| Priority | Recommendations / Additional Info |
| Category | Special development |
Validity
|
Correction Instructions
| Correction Instructions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Support Packages & Patches
| Support Packages | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
References
This document refers to:
SAP NotesThis document is referenced by:
SAP Notes (10)
7460
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
