waliwali / ibm-db

Automatically exported from code.google.com/p/ibm-db
0 stars 0 forks source link

Can't read dirty / Can't set: Read Uncommitted #164

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. start transaction on table (irrelevant of DRDA,JDBC,ODBC)
2. in another connection-instance: try to read from said table

What is the expected output? What do you see instead?
*expected*: some rows

*actual*: Fetch Failure: [IBM][CLI Driver][IDS/NT64] Could not position within 
a file via an index. SQLCODE=-245
or sometimes -244 Could not do a physical-order read to fetch next row.

What version of the product are you using? On what operating system?
current version (git master-branch) on Linux

Please provide any additional information below.
I know dirty reading is horrible, but sadly I'm building atop a horrible legacy 
system and need to be able to dirty read :(

thanks

Original issue reported on code.google.com by andr...@nuessle.in on 4 Nov 2014 at 3:36

GoogleCodeExporter commented 9 years ago
Error indicate that your table or index file get 
corrupted(http://publib.boulder.ibm.com/infocenter/idshelp/v111/index.jsp?topic=
/com.ibm.em.doc/errors_ids111.html).

Please run the oncheck utility to check and repair table and index. 

Original comment by rahul.pr...@in.ibm.com on 5 Nov 2014 at 6:47

GoogleCodeExporter commented 9 years ago
Hey Rahul,

no it actually gives me that error when the database is locked.

I get that when i do:

in a jdbc-workbench:
begin work;
update x set y='z'

and then with ibm_db(_django):  X.objects.filter(y='something')

so it really is a "can't read coz I'm in transaction"-error

Original comment by andr...@nuessle.in on 5 Nov 2014 at 10:43