Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.

So we had a user who's database became "Bad" (SQLCODE -1006 (SQLE_FILE_BAD_DB)). It was just one instance and the user had not syncronized the database in quite awhile. Can anyone explain under what circumstances an ultralite database can become "Bad" and common practices to avoid this in the future? Thanks!

asked 22 Mar '13, 15:02

Jason's gravatar image

accept rate: 0%

This code is raised on startup if UL detects a corrupted database file (the first page in the database is inconsistent or the length of the file is incorrect). It is also raised on subsequent startup if UL is terminated during an uninterruptible operation, such as changing the encryption key.

permanent link

answered 22 Mar '13, 16:23

Tim%20McClements's gravatar image

Tim McClements
accept rate: 35%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 22 Mar '13, 15:02

question was seen: 2,184 times

last updated: 22 Mar '13, 16:23