on 03-30-2017 4:12 PM
We noticed that running costing run (SAPRCK10) with parallel processing dramatically increases the 'Elapsed' time for the DELETE INDX query (Navigation modules) in DB02. During a costing run in first 4 minutes, DELETE query on INDX table took almost 6000 seconds (most of it waiting). This query shows up as most time consuming query in DB02.
I was wondering if this is the cost of using parallel processing and there is no way to really optimize this?
This was happening during the costing run. There is a OSS note that could potentially address this issue. This note requires customer enhancement. We will try implementing this note to see if it makes a difference.
1280119 User exit introduced to alter INDX key formed for Octroi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.