Hi All,
we are running a progress 9.1C database on a Sco Unix server. We got the following error yesterday:
SRV 4: Out of free shared memory. Use -Mxs to increase.
we then ran prostrct
prostrct repair session begin for single on /dev/ttyp53. (451)
prostrct repair session end. (334)
and then started the database which gave the following information:
BROKER 0: Multi-user session begin. (333)
BROKER 0: Begin Physical Redo Phase at 5056 . (5326)
BROKER 0: SYSTEM ERROR: Invalid block 5967 for file /u1/mdsdat/automate.b1, max is 5967 (2329)
BROKER 0: SYSTEM ERROR: Possible file truncation, 5967 too big for database. (612)
BROKER 0: SYSTEM ERROR: The broker is exiting unexpectedly, beginning Abnormal Shutdown. (5292)
BROKER 0: drexit: Initiating Abnormal Shutdown
BROKER 0: ** Save file named core for analysis by Progress Software Corporation. (439)
BROKER 0: ** The database was last used Thu Mar 12 16:25:21 2009. (886)
BROKER 0: ** The before-image file expected Thu Mar 12 16:28:12 2009. (887)
BROKER 0: ** Those dates do not match, so you have the wrong copy of one of them. (888)
proutil -C truncate bi session begin for single on /dev/ttyp12. (451)
** The FORCE option was given, database recovery will be skipped. (33)
** Your database was damaged. Dump its data and reload it. (37)
.bi file truncated. (123)
proutil -C truncate bi session end. (334)
I then increased the -L lock table to 20 000 and started the database with these parameters. All users are currently working, but when i start the database we get the following error:
** Your database was damaged. Dump its data and reload it.
is there a way to repair database without a dump and reload?
Regards
Renaldo
we are running a progress 9.1C database on a Sco Unix server. We got the following error yesterday:
SRV 4: Out of free shared memory. Use -Mxs to increase.
we then ran prostrct
prostrct repair session begin for single on /dev/ttyp53. (451)
prostrct repair session end. (334)
and then started the database which gave the following information:
BROKER 0: Multi-user session begin. (333)
BROKER 0: Begin Physical Redo Phase at 5056 . (5326)
BROKER 0: SYSTEM ERROR: Invalid block 5967 for file /u1/mdsdat/automate.b1, max is 5967 (2329)
BROKER 0: SYSTEM ERROR: Possible file truncation, 5967 too big for database. (612)
BROKER 0: SYSTEM ERROR: The broker is exiting unexpectedly, beginning Abnormal Shutdown. (5292)
BROKER 0: drexit: Initiating Abnormal Shutdown
BROKER 0: ** Save file named core for analysis by Progress Software Corporation. (439)
BROKER 0: ** The database was last used Thu Mar 12 16:25:21 2009. (886)
BROKER 0: ** The before-image file expected Thu Mar 12 16:28:12 2009. (887)
BROKER 0: ** Those dates do not match, so you have the wrong copy of one of them. (888)
proutil -C truncate bi session begin for single on /dev/ttyp12. (451)
** The FORCE option was given, database recovery will be skipped. (33)
** Your database was damaged. Dump its data and reload it. (37)
.bi file truncated. (123)
proutil -C truncate bi session end. (334)
I then increased the -L lock table to 20 000 and started the database with these parameters. All users are currently working, but when i start the database we get the following error:
** Your database was damaged. Dump its data and reload it.
is there a way to repair database without a dump and reload?
Regards
Renaldo