Hey guys!

I am working on a sybase 9.0.2.3137 database which is working but keeps
giving errors during validation. I know that the database is corrupted so i
attempted to perform an unload/reload on the database by skipping the
corrupted table. I tried to salvage the data from my corrupted table using
"order by" on the column "transactiontime" which is basically my primary key
and i keep getting assertion failed errors.

EACH time i tried to use ORDER BY statement on my transactiontime table (to
be able to find between which dates the corruption is) i am getting an
assertion failed error saying:

"Error at line 1
Internal database error ***ERROR*** Assertion failed: 200707 (9.0.2.3137)
Invalid table page encountered during a table scan (table id 476, page
0x31c1) -- transaction rolled back"

Since i cant salvage the data using that ORDER BY statement, i decided to
fetch my information for each day since Feb 2007. If i do the following
command: "select * from tblcorruptedtable where transactiontime = date for
each day", i am able to get the data but sometimes i will get the assertion
failed error whatever date i use (i even tried more recent months). What is
even more weird, is that i will run the same command twice on the same day
and one time it will work, another time it will give me the assertion failed
error.

Is there anyway of recovering the data from that table or will i be stuck
dropping the table and restarting it without any data?

Thanks a lot!

In article <473c474b@forums-1-dub>, noemail (AT) noemail (DOT) com says...
Did you try just exporting its data with no ORDER BY or WHERE clause?
I.E. just "SELECT * FROM mytable OUTPUT TO..."

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

If you have a complete (set of) transaction log(s) from the time that the
database was created, or from the time of a good backup, then you could
create a new database (or start with the good back), dbtran the log, and
apply the resultant sql script to the new (or backup) database.
This will restore all of your data.
--
Mark Culp
SQLAnywhere Research and Development
iAnywhere Solutions Engineering
-------------------------------------------------------------------------
** Whitepapers, TechDocs, bug fixes are all available through the **
** iAnywhere Developer Community at http://www.ianywhere.com/developer **
-------------------------------------------------------------------------
SybaseInvestigator wrote:

<ns_dkerber (AT) ns_WarrenRogersAssociates (DOT) com> wrote

Hi, thanks for the quick reply!

Yes i actually tried to export the data to a text file without using the
order by / where statements and at some point during the export it will
crash with the assertion failed error.

After getting the error i checked the data in the exported file (which was
only 18 MB big and it should have been around 200 MB) and i wasnt able to
determine the corrupted dates because i was able to see data from the start
date and up to today in the file. So it means that the corruption seems to
be scattered a lot in that database table.

Hi Mark,

Thanks for the reply.

Unfortunately i do not have good old backups and old transaction logs as the
issue was occuring for a couple of weeks before i was notified.


"Mark Culp" <reply_to_newsgroups_only_please_nospam_mark.cul p (AT) iAnywhere (DOT) com>
wrote in message news:473C594F.80F1C4F4 (AT) iAnywhere (DOT) com...

If you have attempted to select around your data using a variety of
indexes and table scans (SELECT * FROM...), but still cannot access all
of the data (as per the instructions at:
http://www.ianywhere.com/developer/t...upt_pages.html
), you have two options:

1) Move forward and attempt to restore the data from other sources (hard
copies, etc.)

2) Open a case with Technical Support and request a salvage. The salvage
service is an additional cost on top of the case cost (if you do not
already have a support plan), and is billed at $360USD/hr, with a 1 hour
minimum commitment. The salvage engagement does not come with any
guarantees, but our engineers may be able to recover data from the
"middle" of the corruption that you may not be able to do with simple
SELECT statements.

-----

This is also an excellent time to review your backup and recovery
procedures. See: http://www.ianywhere.com/whitepapers/ASA_backup.html

A "typical" backup scenario involves frequent backups that perform the
following steps:

- Backup the database (using the dbbackup utility or the "BACKUP
DATABASE" SQL command)
- Make a copy of the back up to another file
- Start the backup copy on a separate server process
- Run dbvalidate on the backup copy
- Throw away the copy and keep the original backup

Regards,

SybaseInvestigator wrote:
--
Jeff Albion, Product Support Analyst
iAnywhere Solutions

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs :
http://downloads.sybase.com/swd/summ...&timeframe =0

Thank you very much for your help Jeff!


"Jeff Albion (iAnywhere Solutions)" <firstname.lastname (AT) ianywhere (DOT) com> wrote
in message news:473c7a35 (AT) forums-1-dub (DOT) ..