Kbase 18796: BI File Size Errors - Sum of all BI extents exceeds 2 Gig
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 6.x
Progress 7.x
Progress 8.x
SYMPTOM(s):
SYSTEM ERROR: Invalid note length <note length> (5111)
SYSTEM ERROR: Invalid note length 0 (5111)
SYSTEM ERROR: rlrdnxt: note prefix and suffix lengths don't match <prefix length> <suffix length> (5112)
rlrdnxt: note prefix and suffix lengths don't match . (7167)
rlrdnxt: note prefix and suffix lengths don't match -207350 . (7167)
CAUSE:
Bug 19990331-001
CAUSE:
Errors indicate that the sum of all BI extent sizes is greater then 2 GB BI file size limit.
FIX:
The error occurs because of how the Database Manager reads and writes to the Before Image file. Prior to version 9 the BI file was looked at as single file, regardless of the # of extents involved. If the sum of the all BI extent sizes exceeded 2 gig you would experience these errors. Unfortunately, the prostrct utility allowed you to create these extents without adhering to internal limits. The bug with prostrct is fixed in 8.3C and 9.1A of Progress.
Fix your databases current structure file to remove unnecessary bi files so that the sum of all bi extents will not exceed 2 gig.
1. Truncate the bi file. Syntax: proutil dbname -C truncate bi
2. Use remove option to prostrct command to remove unnecessary bi extents.
Syntax: prostrct remove dbname extent-type-token [area-name]
extent-type-token is b for a bi extent.