Kbase P13476: PROSERVER job consumes most of CPU during incremental load.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Verified
FACT(s) (Environment):
IBM AS/400 (RISC)
Progress/400 DataServer
Progress 9.1x
SYMPTOM(s):
PROSERVER job consumes most of CPU during incremental load.
When loading the incremental df file the process gets into standstill during the change of the primary index.
The PROSERVER job is ACTIVE but there's no visible activity and it takes up to 98% of CPU.
Very few I/Os can be noticed during this time (1-2 per hour).
The incremental load loops when it attempts to modify the primary index of a table.
The call stack is as follows:
_C_pcp
main
server_main
nsaloop
nsadorm
as4rmmak
processQCMD
ServerCommand
dbaDltObj
RemoveEntries
fndinxen
CAUSE:
Bug# 20021111-005
CAUSE:
The problem was found in our code. The initial key for the find of the user index entries was never being updated after the first pass of the loop. Therefore the same 512 entries were being read over and over again causing the hang.
FIX:
The fix is in the Progress/400 DataServer patch 9.1C07