Kbase P155935: Activating an index online using proutil dbname -C idxactive terminates abnormally after 20 mins.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/03/2010 |
|
Status: Unverified
SYMPTOM(s):
Activating an index online using proutil dbname -C idxactive terminates abnormally after 20 mins.
Index Activate: BEGIN activation of <indexname>. (13258)
Index Activate: recs value: <recordnumber> refresh rate: <refreshrate>. (13259)
Enabling table locks. (14636)
Disconnecting dead user <number>. (2527)
Begin transaction backout. (2252)
Transaction backout completed. (2253)
Disabling table locks. (14637)
A 0 length protrace file is being created.
The last message you see to standard out is (12811) and then returns the user with the PROENV prompt where the command was initiated.
Activating Index <indexname> at Database timestamp <timestamp>. (12811)
The same problem with idxactivate occurs even if the database is shut down / offline.
FACT(s) (Environment):
The idxactivate command is able to run successfully against a schema only copy of the database.
The problem does not occur with 10.2B.
Windows
OpenEdge 10.2A
OpenEdge 10.2A01 32-bit Service Pack
OpenEdge 10.2A02 32-bit Service Pack
CHANGE:
Added a new deactivated index to the database by loading a .df
CAUSE:
Bug# OE00194702
CAUSE:
Index activation used the wrong size for fetching records.
FIX:
Upgrade to 10.2A03 or 10.2B or later.
If upgrading to 10.2B is not possible then a workaround for this issue is to make use of idxbuild or idxfix offline to activate the index.