Quickbooks Connection Lost

Sybase Error

Sybase Anywhere Error Code 13724, –715

Error Description: Contents of backup files are inconsistent

Sybase Error Codes: 13724
Adaptive Server Anywhere SQLCODE : –715



The resolution for Error message #–715 can also be found on the Sybase Anywhere website under "Contents of backup files are inconsistent". If the data recovery procedure does not work to resolve the database assertion, then it is recommended that you open a Technical Support request at http://www.filerepair.net/recovery.

File Repair Inc. has a data salvage service for the salvage of data from a corrupt database. This is a paid service, accessed by opening a File Repair Request. There is a fee for corrupted data recovery and file repair.

How to salvage data from a corrupted Sybase Anywhere database

  1. Start the database using the database server and connect to the database using iSQL by executing the following commands: dbeng9 asa.db

    dbisql -c "UID=DBA;PWD=SQL;ENG=ASA"

  2. Execute the following statement from Interactive SQL:

    SELECT * FROM "DBA"."table_name"
    ORDER BY id ASC
    > > # c:\unload\table_name.dat

    This outputs data from the table_name table starting at the first primary key entry until the database asserts.

  3. Restart the database, and then connect to Interactive SQL by executing the following commands: dbeng9 asa.db

    dbisql -c "UID=DBA;PWD=SQL;ENG=ASA"

  4. Execute the following statement from Interactive SQL:

    SELECT * FROM "DBA"."table_name"
    ORDER BY id DESC
    > ># c:\unload\table_name.dat

    This outputs as much data as possible from the table_name table, starting at the last primary key entry until the database asserts. The > ># syntax appends any new rows generated by the SELECT statement to the table_name.dat file. To verify how much data is missing from the table_name table, open the table_name.dat file in a text editor. There may be some data loss when attempting to salvage data from the corrupt table. If there is significant data loss, then try and determine a range of the primary keys where excessive data loss exists. When a range has been determined attempt to salvage more data from the table based on the range of primary keys in the SELECT statement.

  5. Restart the database and connect to Interactive SQL using the following commands: dbeng9 asa.db

    dbisql -c "UID=DBA;PWD=sql;ENG=ASA"

  6. Execute the following command in Interactive SQL:

    SELECT * FROM "DBA"."table_name"
    WHERE id BETWEEN 2500 AND 3000
    ORDER BY id ASC
    > ># c:\unload\table_name.dat

    To salvage the greatest amount of data from the corrupt table, change the range of the primary keys in the BETWEEN clause until the database asserts. This process can be long and tedious if the corruption is widely spread throughout the table. Commonly, corruption in a table is grouped in ranges based on the primary key, but this is not always the case. If there are multiple indexes on the table, use the different indexes for the WHERE and ORDER BY searching conditions. Dropping the indexes and primary key on the table may also produce more data using a SELECT statement. The more data that can be salvaged from the corrupt table, the better the integrity of the data that will exist when the new database is created.

    For information about index hints, see http://download.sybase.com/pdfdocs/awg0900e/dbrfen9.pdf - Page 445.

If the data recovery procedure does not work to resolve the database assertion, then it is recommended that you open a Technical Support request at http://www.filerepair.net/recovery.



Sybase and the marks listed are trademarks of Sybase, Inc. ® indicates registration in the United States of America.
All other company and product names mentioned may be trademarks of the respective companies with which they are associated.
Copyright Quickbooks Connection Lost 2009-2017. All Rights Reserved.