Kbase P135639: Multi-threaded binary dump is memory violating when dumping a table on a 32 bit platform
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/10/2008 |
|
Status: Unverified
SYMPTOM(s):
Multi-threaded binary dump is memory violating when dumping a table on a 32 bit platform
SYSTEM ERROR: Memory violation. (49)
Stack trace from _proutil reads:
_sigreturn
free
FACT(s) (Environment):
Database was converted from version 8 to 9 using conv89
Database was converted from version 9 to 10 using conv910
32 bit platform
HP-UX 11.0
HP-UX 11.0 32-bit
OpenEdge 10.1B
CAUSE:
Bug# OE00135661
FIX:
Upgrade to 10.1B01 or later.
If upgrading is not possible at this time, then do not use the -threadnum parameter and set -thread 0 in the binary dump command line.
Command syntax:
proutil db-name -C dump [owner-name.]table-name directory [ -index num ] {[-thread n ] [-threadnum nthreads] [-dumplist dumpfile] }
-thread n
For databases with an Enterprise license, indicate if an online dump is threaded. Specify zero (0) for a single-threaded dump, one (1) for a threaded dump.
-threadnum nthreads
For a threaded dump, specify the maximum number of threads to create. The default value is the number of system CPUs. The actual number of threads created may be less than nthreads. PROUTIL DUMP determines the number of threads to create based on the complexity of the index the DUMP follows.