Kbase 19024: Generating Reports and receive 1124 followed by 604 on start
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/11/1999 |
|
Generating Reports and receive 1124 followed by 604 on start
Title:
KnowledgeBase number: 19024
Creation Date: 1999/08/11
Modified Date: 1999/08/11
Version and Release Number: Early versions of 6 and 7 of Progress
Summary:
This kbase is being generated to document a Progress bug which deals
with sending output to a file and receiving 1124 messages which
shutdown the database. Then receive 604 errors on startup of the
database. The bug deals with having multiple databases on a machine
which when you total the # of extents, including .lk files the number
of open files is 255 or greater. If you met this configuration, and
were generating a report to a file and never received your report,
but instead received the errors mentioned above you may have hit
this bug.
The bug was that if you had more than 255 file descriptors open and
were sending a report to a file we may put the file into one of your
data extents. This bug has been fixed in the most recent releases of
Progress. If you suspect you are hitting this bug, please upgrade to
the latest version of Progress for your platform.
Bug scenario:
1. You are running a database on a machine that have several other
progress databases whose total # of extents is close to 250+
extents and may be be greater when you add in the .lk file for
all databases.
2. Now you are running a report and sending the output to a file on
disk. You notice that the file does not get created. Instead
you receive an 1124 error and the database crashes. The 1124
error is:
SYSTEM ERROR: wrong dbkey in block. Found <dbkey>, should be <dbkey2>
(1124)
3. Now upon startup of the database you receive an error 604 which
indicates that one of you database extents has the wrong creation
date. The 604 error is:
Extent <file-name> has the wrong creation date. (604)
You are sure that you did not change the extents. All you did was
attempt to start the database after the crash and received this
error. A scan of the database shows physical corruption in the
database.