Kbase P121733: idxactivate cores when the index is not specified
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/07/2008 |
|
Status: Verified
SYMPTOM(s):
Activating indexes aborts with system error 49
proutil -C idxactivate cores
SYSTEM ERROR: Memory violation. (49)
Creating protrace file <pathname>/<filename> (13638)
Stack trace from _proutil on Solaris reads:
drExitOnTerm()
sigaction()
_getfp()
_fork()
upIdxParseArgs()
upIdxActivate()
dbusIndexActivate()
OpenEdge 10.1A02
FACT(s) (Environment):
OpenEdge 10.1A
Linux Intel
Linux x86 64-bit
Sun Solaris SPARC
CAUSE:
proutil idxactivate cores on supported Linux and Solaris platforms if there is a syntax error in the cmd line, eg the index is not specified
CAUSE:
Bug# OE00128076
FIX:
The error messages are correctly returned in OpenEdge 10.1B when the syntax is incorrect:
Index name must be fully qualified as Table.Index. (10036)
upIdxParseArgs: failed to parse index name to be activated ret -1 (12801)
Ensure that the correct syntax is used when activating indexes:
$ proutil db-name -C idxactivate [owner-name.]table-name.index-name [useindex index-name] [recs n] [refresh t]
NOTE: the "useindex" cannot be a word index and the table-name qualifer must not be used here, or the build will fail.
For further information, please consult the online OpenEdge database administration available at: www.progress.com/support Documentation.