1968046 - How to reset a MobiLink SQL Anywhere Remote with a Corrupted or Missing Transaction Log in a Synchronization Environment

• While using a SQL Anywhere database as a remote database for MobiLink synchronization, it is possible for the SQL Anywhere remote database to have its transaction log corrupted:

Database recovery in progress
Last checkpoint at Wed Jan 01 2014 00:00
Checkpoint log...
Transaction log: transaction-log.log...

Internal database error *** ERROR *** Assertion failed: 100902 (xx.x.x.xxxx)[database-name]
Unable to find table definition for table referenced in transaction log (page_no=0x%x, offset=0x%x)

or

Internal database error *** ERROR *** Assertion failed: 100903 (xx.x.x.xxxx)[database-name]
Unable to find table definition for table referenced in transaction log -- transaction rolled back

or

Internal database error *** ERROR *** Assertion failed: 100904 (xx.x.x.xxxx)[database-name]
Failed to redo a database operation (id=#, page_no=0x#, offset=0x###)

• It may also be possible for transaction logs to be deleted unexpectedly:
  
  

  Upload aborted at offset 000000102324
  We are looking for a transaction log file starting at offset 000000087352.
  Missing transaction log(s) before file "c:\mydatabase\140815AA.log" (starting at offset 000000092426).
  Scanning logs starting at offset 000000087352
  Processing transaction logs from directory "c:\mydatabase"
  Log scan starting at offset 000000102324

• Other error and assertion messages are also possible - they will indicate a failure with attempting to access the transaction log or apply the transaction log to the database.

• SAP SQL Anywhere (All platforms, all versions)
• MobiLink SQL Anywhere Client Utility (dbmlsync)

corruption , KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , How To