dbTalk Databases Forums  

assertion failed error

sybase.public.sqlanywhere.general sybase.public.sqlanywhere.general


Discuss assertion failed error in the sybase.public.sqlanywhere.general forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Doug Stone
 
Posts: n/a

Default assertion failed error - 11-09-2009 , 05:05 PM






We have a customer where it looks like their database and all their backups
are corrupt.
I am seeing a "checksum failure on page 11661" error when unloading the
database.
Is there a way to unload the db so that dbunload ignores errors and just
continues with the unload?
I was able to unload the entire db except for one table. This table happens
to be the largest in the db.
This customer's production db is now down.
Thanks,
Doug
p.s. version 10.0.1.3415

Reply With Quote
  #2  
Old   
R. Pods
 
Posts: n/a

Default Re: assertion failed error - 11-10-2009 , 06:52 AM






Doug,

you might want to try the UNLOAD SELECT statement with an ORDER BY ...
until it stops with the error. Then try a second time with the reversed
order (ASC replaced by DESC or vice versa). With some luck there'll be
only a small window of missing rows.

Of course there's always the chance to open a support case with Sybase
for data salvation, they got tools to dig deeper than we users.

HTH
Reimer

Doug Stone wrote:
Quote:
We have a customer where it looks like their database and all their
backups are corrupt.
I am seeing a "checksum failure on page 11661" error when unloading the
database.
Is there a way to unload the db so that dbunload ignores errors and just
continues with the unload?
I was able to unload the entire db except for one table. This table
happens to be the largest in the db.
This customer's production db is now down.
Thanks,
Doug
p.s. version 10.0.1.3415

Reply With Quote
  #3  
Old   
Doug Stone
 
Posts: n/a

Default Re: assertion failed error - 11-10-2009 , 08:41 AM



Thanks Reimer. I'll give that a try.
"R. Pods" <r.pods (AT) gmx (DOT) net> wrote

Quote:
Doug,

you might want to try the UNLOAD SELECT statement with an ORDER BY ...
until it stops with the error. Then try a second time with the reversed
order (ASC replaced by DESC or vice versa). With some luck there'll be
only a small window of missing rows.

Of course there's always the chance to open a support case with Sybase for
data salvation, they got tools to dig deeper than we users.

HTH
Reimer

Doug Stone wrote:
We have a customer where it looks like their database and all their
backups are corrupt.
I am seeing a "checksum failure on page 11661" error when unloading the
database.
Is there a way to unload the db so that dbunload ignores errors and just
continues with the unload?
I was able to unload the entire db except for one table. This table
happens to be the largest in the db.
This customer's production db is now down.
Thanks,
Doug
p.s. version 10.0.1.3415

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.