Help!! can't restore the database, Error: 8206, Severity: 21

Discussion:

(too old to reply)

y***@synergy.com.tw

2005-09-03 10:31:29 UTC

Dear All,

When we restore the database backup, we got the following error then user
database can't log into anymore.

Error: 8204, Severity: 20, State: 4
Expected to receive system catalog id. Instead 8 was received.
..
..
..
Error: 8206, Severity: 21, State: 3
Object 9 was not found in Sysindexes.
..
..

Is there anyone got this before?

Please give me some recommends.

Thanks in advance!

Best Thanks,
Salu

unknown

2005-09-04 01:34:29 UTC

Permalink

Dear All,

We also try to by-pass the user database via update sysdatabases.status=-32768,
but it still not working.

Our environment :

O.S. : windows 2000 server sp3
DB version : ASE 12.5.3/EBF 12461 ESD#2
Client version : Sybase Client-Library/12.5.1/P-EBF12117 ESD #5

Please help us to fix this!!

Best Thanks,
Salu

Post by y***@synergy.com.tw
Dear All,
When we restore the database backup, we got the following error then user
database can't log into anymore.
Error: 8204, Severity: 20, State: 4
Expected to receive system catalog id. Instead 8 was received.
..
..
..
Error: 8206, Severity: 21, State: 3
Object 9 was not found in Sysindexes.
..
..
Is there anyone got this before?
Please give me some recommends.
Thanks in advance!
Best Thanks,
Salu

Bret Halford

2005-09-04 16:09:22 UTC

Permalink

This is probably not going to be an easy error to work around. I'm not suprised
the bypass recovery isn't helping - that tends to help in cases where there are
problems with the log itself during recovery. In this case, it is saying that
the entry for the sysprotects table is missing for some reason from the sysindexes
table. That shouldn't happen, and there is no easy way to get around it.

The two most likely causes of this kind of error are a corrupt dump file or
some kind of problem with the data devices.

You might try either creating a new database on a different set of devices
and attempt the load into that database (if you get the same error then the
problem is almost certainly with the dump file itself).

If you have an older dump of the database, you might try loading that.

This is otherwise an issue that you will probably need to work closely with
tech support to resolve..

-bret

Post by y***@synergy.com.tw
Dear All,
We also try to by-pass the user database via update sysdatabases.status=-32768,
but it still not working.
O.S. : windows 2000 server sp3
DB version : ASE 12.5.3/EBF 12461 ESD#2
Client version : Sybase Client-Library/12.5.1/P-EBF12117 ESD #5
Please help us to fix this!!
Best Thanks,
Salu

unknown

2005-09-09 06:07:57 UTC

Permalink

Dear Bret,

Thanks your suggestion.

We had contacted Tech Support, but the problem still doesn't fix too.
The clean dump file is half month ago. It's a bad news for us.
We lost most of data.

Anyway, we have been built steps by steps and need more time to enter data.

Best Thanks,
Salu

Post by Bret Halford
This is probably not going to be an easy error to work around. I'm not suprised
the bypass recovery isn't helping - that tends to help in cases where there are
problems with the log itself during recovery. In this case, it is saying that
the entry for the sysprotects table is missing for some reason from the sysindexes
table. That shouldn't happen, and there is no easy way to get around it.
The two most likely causes of this kind of error are a corrupt dump file or
some kind of problem with the data devices.
You might try either creating a new database on a different set of devices
and attempt the load into that database (if you get the same error then the
problem is almost certainly with the dump file itself).
If you have an older dump of the database, you might try loading that.
This is otherwise an issue that you will probably need to work closely with
tech support to resolve..
-bret