Kbase 19562: Error (23) caused instead of (444) under some circumstances
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
06/03/2000 |
|
SUMMARY:
Some customers have been experiencing the error (23) instead
of the expected (444) under several V8 releases and platforms.
--> error displayed:
SYSTEM ERROR: bfdiscon: rmrep failed. (23)
An unexpected system error occurred while attempting to write an updated data record to the database.
--> error expected:
** Attempt to expand record beyond the maximum allowed size. (444)
Records are made up of fields that vary in length. The size of an individual record is the sum of the sizes of all its fields. Records must always be less than 32,000 characters long. If necessary, try splitting your record into two records, in two files, with the same key values in both.
DESCRIPTION:
As an example one customer was trying to find the reason for
the error (23) they were hitting.
Actually the problem was not due to a corrupted index as
expected by some other kbases, because after checking all
the indexes of all the databases involved they found no error.
After couple of hours of research they managed to find that the problem was due to trying to add some text to a character variable
of a particular record and updating the database with that record.
Usually at the customers site the records were deleted before the length of the text added to the record attain the theoric limit
of 32K but the person doing this was now on vacation so the problem occured.
However the usual message for this should have been
(444): trying to expand a record beyond its maximum size
SOLUTION:
So in some cases this sort of situations can cause a 23 error
instead of 444 which is much more precise in that type of programming mistake. So they have worked this around by testing the length of the variable before trying to add more text in it.
(03/03/2000 KHELALA)
KBASE #19562