SQLBase Trouble -- Please Help

October 10, 2005 9:37 AM

SQLBase Trouble -- Please Help I've got an old version of ADP's software which is no longer supported. It giving an error from the SQLBase portion: 00803 Fatal SQLBase System Failure (ROW UEP). The service (running on Win2k Server) terminates when this happens, and this happens when anyone tries to log on to the software. What do I need to do to fix this?
posted by kc0dxh to Computers & Internet (3 answers total)

Google brings up these pages as directly relevant. See particularly the first three linked results - they look promising. Gotta say, this is really obscure -- Google Groups is usually my first stopping-off point for stuff like this, and it turns up nothin'.

The cause of your problem is identified by the first linked page in that result set as a crash due to a corrupt row page (803 is Unexpected End of Page). It goes on to suggest some possible remedy steps. Excerpts below:

Crash due to a Corrupt Row Page

All of the following steps may be done on a current database file or a restore from backup. If the current database file is used, there will be no need to roll the database forward after cleaning the corrupt data. However, if a restore from backup is used, the log files associated with transactions since the backup will need to be rolled forward ( rollforward procedure ) if the data associated with the transactions is not going to be lost.

Listed below are some of the most common errors associated with corrupt row pages and the meaning of the acronym found in the error code. If the error number appears in the FAIL.SQL, the database should be stopped and recovered as soon as possible.

Database Error Corresponding SqlBase Action Failed
803 ROW UEP Row - unexpected end of page

posted by killdevil at 11:48 AM on October 10, 2005

Best answer: Looking a little further, here is the whole SQLBase Crash Recovery Techniques tech doc as an MS Word document.

This version has all of the illustrations intact.
posted by killdevil at 11:55 AM on October 10, 2005

Best answer: Here are more results from Google Groups now that we know that the problem is a corrupt row page. Good luck!
posted by killdevil at 12:10 PM on October 10, 2005