I have 3 corrupt database dumps salvaged from a WinPro 2000 box with a damaged disk running ASE 12.5.3. When attempting to load the databases into a win10 ASE 12.5.3 server, 692 & 834 error messages are being raised.
Is there a way to load the database and have the server ignore these errors. My thoughts are that whatever portion of the database that is not corrupt would still be important information that my client can capture. Had this error not occurred during a load, it would be possible to run the dbcc page command(as well as some other dbcc's) and determine the object(s) associated with the corrupted page(s). Perhaps objects or partial objects that haven't been corrupted, can be bcp'd out and loaded into a healthy database.
I'm listing the text of the error message below:
WARNING! If the 692 error is not a soft error (one that exists only in memory), the problem is severe. Sybase Technical Support may be able to help you recover from the error. However, this recovery procedure often results in loss of data; if this is unacceptable, you will probably need to restore from backups.
I contacted Sybase for an engagement to recover as much of this database as is possible. I was told since there is no support/maintenance agreement, they could not help me even though my client would be willing to pay.
Thank you in advance for all your collective assistance. Any suggestion/direction is most appreciated.
Rob
