ALE: Intensive SQL accesses when reading change pointers
[ALE] [capital intensive] [intensive] [intensive care] [intensive reading]
Related:
- FAQ: I/O-intensive database operationsSymptom 1. What does the term “I/O-intensive database operations” refer...
Symptom
You create change pointers for your master data from which IDocs are then created at a later stage. During a database analysis, you discover that, when you access BDCPV, SQL statements occur that require intensive processing.
Other terms
ALE, RBDMIDOC, CHANGE_POINTERS_READ
Reason and Prerequisites
The performance of the system when reading change pointers depends directly
on the size of the BDCP and BDCPS tables. The accesses were
configured in an optimum manner and independent of the database. However, it was shown that further optimization at database level can increase the performance of individual databases. This note only applies for Oracle databases. Read Note 515886 for information about the DB2 OS/390 database.
Solution
Also refer to Note 328355 for information in connection with Oracle databases. The general aim should be to keep the BDCP and BDCPS tables as small as possible. Useful information about this is contained in Note 513454. To optimize at database level, you must implement the attached correction.
You must also create histograms for the BDCP and BDCPS tables. Create an entry with the “EH” method in the control table for statistics for BDCP and BDCPS (Note 106047).
Execute the BRCONNECT program with the following parameters in order to create the statistics:
brconnect -u / -c -f stats -t BDCP -f collect
brconnect -u / -c -f stats -t BDCPS -f collect