Dump and load required

Yahoo Archive
1
The bad news is that the date mismatch error is the result of the timestamp on the b1 file being out of sync with the .db file and is not a result of a corrupt .db file. The BUILDB command remedied the timestamp problem but created only a minimal control area (DB) that does not match the actual data extent (d1). In other words, the build made things marginally worse.

The good news is that none of this indicates any actual data loss but you will need to force enter the b1 which will flag the DB as corrupt and then allow you to enter but only to perform a Dump & Load. The dump and load is tedious and a little bit time consuming but not overwhelmingly so. The potential for data loss is limited to actual corruption of the d1 file. The rest of the files can be pretty much hosed and a dump and load will recreate them.

Michael

Michael Barry
Aspacia Systems Inc
866.566.9600
312.803.0730 fax
http://www.aspacia.com/

On Jan 16, 2013, at 7:07 PM, C <rotary1@...> wrote:

> Vantage 8.03 Progress 10.1
>
> Server crashed and mfgsys db would not load.
> Log showed a mismatch:
>
> *******
> Last Open Date mismatch.
> Extent D:\epicor\mfgsys803\db\mfgsys.b1 has a different last opened date ....
>
> Control area has a last open date of ....
> Probable backup/restore error.
> Database is damaged. See documentation.
> ******
>
> This seems easy enough. I could not get past this until I renamed the mfgsys.db file and then performed a BUILDDB.
>
> I am now able to actually start the db in progress explorer.
> However, I can not do anything. The error logs show that I need to dump and reload the data. If I try to run admin tools, I get messages
>
> *******
> System error: cannot read field 57 from record, not enough fields.
> System error: failed to extract field 57 from record (table -1) with recid 67731
> ...
> ...
> ...
>
> *******
> and ultimately this shows ** stget: out of storage.
>
> Everywhere I turn, the tools tell me that I need to dump and load.
>
> I have some progress documentation that say I should be able to do this from the data administration and data dictionary tools. When I attempt to connect to the db via physical name(d:\epicor\mfgsys803\db\mfgsys, I get a repeat of the system errors above. The first line of the message states:
>
> **Your database was damaged. Dump its data and reload it. (37).
>
> There was something stating that I could do this in binary mode and hinting that I could do this en masse, but I only seem to find a todo regarding dumping piece by piece.
>
> Can anyone shed some light on this? It is a production db that has been down for two days, and I am sure you all know the state of backups...... :(
>
>



[Non-text portions of this message have been removed]
2
Vantage 8.03 Progress 10.1

Server crashed and mfgsys db would not load.
Log showed a mismatch:

*******
Last Open Date mismatch.
Extent D:\epicor\mfgsys803\db\mfgsys.b1 has a different last opened date ....

Control area has a last open date of ....
Probable backup/restore error.
Database is damaged. See documentation.
******

This seems easy enough. I could not get past this until I renamed the mfgsys.db file and then performed a BUILDDB.

I am now able to actually start the db in progress explorer.
However, I can not do anything. The error logs show that I need to dump and reload the data. If I try to run admin tools, I get messages

*******
System error: cannot read field 57 from record, not enough fields.
System error: failed to extract field 57 from record (table -1) with recid 67731
...
...
...

*******
and ultimately this shows ** stget: out of storage.

Everywhere I turn, the tools tell me that I need to dump and load.

I have some progress documentation that say I should be able to do this from the data administration and data dictionary tools. When I attempt to connect to the db via physical name(d:\epicor\mfgsys803\db\mfgsys, I get a repeat of the system errors above. The first line of the message states:

**Your database was damaged. Dump its data and reload it. (37).

There was something stating that I could do this in binary mode and hinting that I could do this en masse, but I only seem to find a todo regarding dumping piece by piece.

Can anyone shed some light on this? It is a production db that has been down for two days, and I am sure you all know the state of backups...... :(
3
I worked with this in the past, it's actually a huge pain in the ass to do
and get working, and sometimes it does result in data loss.

There is some, but not a ton of information out on the web that you can
cobble together to help you get this fixed. A whole bunch of googling
various pieces of the errors can get many of the answers needed. Once you
can get the db working in a basic form, you can do either an ASCII or Binary
dump and load of the data to try to recover.

Have you called Epicor at all? They definitely have the tools to help you
get the database dumped and loaded and repaired.

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
C
Sent: Wednesday, January 16, 2013 10:07 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Dump and load required

Vantage 8.03 Progress 10.1

Server crashed and mfgsys db would not load.
Log showed a mismatch:

*******
Last Open Date mismatch.
Extent D:\epicor\mfgsys803\db\mfgsys.b1 has a different last opened date
....

Control area has a last open date of ....
Probable backup/restore error.
Database is damaged. See documentation.
******

This seems easy enough. I could not get past this until I renamed the
mfgsys.db file and then performed a BUILDDB.

I am now able to actually start the db in progress explorer.
However, I can not do anything. The error logs show that I need to dump and
reload the data. If I try to run admin tools, I get messages

*******
System error: cannot read field 57 from record, not enough fields.
System error: failed to extract field 57 from record (table -1) with recid
67731 ...
...
...

*******
and ultimately this shows ** stget: out of storage.

Everywhere I turn, the tools tell me that I need to dump and load.

I have some progress documentation that say I should be able to do this from
the data administration and data dictionary tools. When I attempt to connect
to the db via physical name(d:\epicor\mfgsys803\db\mfgsys, I get a repeat
of the system errors above. The first line of the message states:

**Your database was damaged. Dump its data and reload it. (37).

There was something stating that I could do this in binary mode and hinting
that I could do this en masse, but I only seem to find a todo regarding
dumping piece by piece.

Can anyone shed some light on this? It is a production db that has been down
for two days, and I am sure you all know the state of backups...... :(




------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links