android - error -305 on UPDATE

[Former Member]

My android app is using an udb file. My problem is on an UPDATE statement, when i execute it the first time everything works properly but when I do it the second time (I execute the prepared SQL statement and the query string is still clean), I get this error:

09-27 15:07:35.920: WARN/System.err(19311): com.ianywhere.ultralitejni12.implementation.JniException: UltraLiteJ Error[-305]: I/O error 200017 -- transaction rolled back

Any helping idea in what might be the reason? thank you in advance

[chris_keating]

A -305 error indicates that there was a problem during I/O operations. Are you seeing this issue only with UPDATEs i.e., SELECT, INSERT, DELETE statements all seem to work ok? Can you run a ulvalidate (on the desktop) against this db?

[Former Member]

yes, the other query are working and also an update query is working but only the first time. When i do that 2 times, the second time is not working...

[Former Member]

How are you connecting to the database? I think that the most likely causes for an I/O error are writing to an unmounted file system or attempting to write to a file locked by another thread or process.

[Former Member]

Thanks for your reply. What do you mean with "How are you connecting to the database?" You would like to know all the methods I use?

[Former Member]

furthermore, is there any documentation for android dev using afaria sybase in their application?

[former_SQLA_member1694876]

That I/O error number indicates that UltraLite read a page from the database file and found unexpected data in the page header. If there's not another explanation, it indicates the storage medium corrupted the data -- that is, returned something different than what was written.

If you can reproduce this problem with a new database, please submit the repro to Sybase as a bug report.

As Chris mentioned, you can run the ulvalid tool against the database to see if it thinks anything is wrong. Copy the database back to your PC, and run 'ulvalid -v -c dbf=mydatabase.udb'.

[Former Member]

For the query sequence which is throwing an exception, do they use the same connection, or does each iteration create its own connection to the database? If the latter, does the connection string specifify a database name or a file name? In other words, is it possible that the second update could be fouling when it tries to write to a still-locked file or file segment?

(Caveat: I haven't worked with Ultralite on Android yet, but I'm presuming that a file-based connection may not automatically detect whether it or not it can really write to the file -- I just have vague recollections of Linux growing fur and fangs when it came to mixing file locks and multi-threaded processes.)

[Former Member]

My problem was an error in the classes I use. While I projected the app in such a way as I open the connection only at the beginning and use a singleton class for this; I figured out that some classes open the connection again! Fixing it I dont get the same problem. Thanks a lot for your help/time

PS: My question about documentation-for-android-dev-using-afaria is still valid.

[VolkerBarth]

Glad you got it:) - Is there any answer that seems acceptable?

For the Afaria question, I'd recommend a new question on its own (and no, I don't know the answer...)

[Former Member]

yes, the W.Clardy comment was helpful.

For the Afaria question, I am going to post a new question soon.

Thanks

[Former Member]

this is what I do

*query="UPDATE ..."; try { statement=DB_conn.prepareStatement(query); result=statement.execute(); DB_conn.commit(); statement.close(); } catch(ULjException e) { e.printStackTrace(); }

    return result;*