Access to AS400 with ODBC: Error SQL 7008

[Giovanna]

I try to access at AS400 table with ODBC driver and when i try to edit a table with component TUniTable i have an error:
[IBM][ISeries Access ODBC Driver][DB2 ODB] SQL 7008 - Table not valid for operation
This table is not under journal.
Best Regard.
Giovanna Cellitti.

[bork]

Hello

This error is unique to DB2 on the AS/400. The DB2 error SQL7008 is returned when an update is attempted to a table on the AS/400 that is not journalled with an Isolation Level that requires journalling. There are two way to resolve this error.

1. Enable journalling for the table you are attempting to update.
2. Set your Isolation level to NONE (5.0 and Higher) or NO_COMMIT (all previous versions).

[Giovanna]

I try to set IsolationLevel= 'ilReadUnCommitted' on the UniTransaction component and i have same problem. Why?
Thank you.
Giovanna Cellitti

[bork]

To resolve your issue you should change the settings of your ODBC driver (not TUniConnection).

A step by step instruction for changing settings of your ODBC driver you can find here:
http://www.microsoft.com/communities/ne ... &sloc=&p=1

But if you want to turn on journaling for the table you can find more detailed information about it here:
http://www.websina.com/bugzero/faq/exception-as400.html

[Giovanna]

I had already set the option to 'Commit' to 'NONE' but with a version of the ODBC driver 09.00.08.00, as suggested i updated the driver.
After i tried to do step by step as suggested but I have the same problem. I resolve only if I put on Journaling, what should I do?
Thank you
Giovanna Cellitti

[bork]

Our UniDAC components are using functionality and behaviour of the ODBC drivers installed on your computer. Unfortunately we can not change the ODBC drivers behaviour. If you are not satisfied with the driver work or you can not set it up properly, you should ask this ODBC driver's developer.

[Giovanna]

I tried to connect with HIT driver ODBC and the result is not changed. If the problem is the driver ODBC (client access/HIT) why only with yours TUniTable component i have problem? I have no problem with TTable component...
Thank you
Giovanna Cellitti

[Giovanna]

I solved it by replacing TUniTable with TUniQuery.

Best regards

Giovanna Cellitti

[Dimon]

It is good to see that the problem has been solved. Feel free to contact us if you have any further problems.

[alfredalfred]

why only with yours TUniTable component i have problem? I have no problem with TTable component...
Thank you


waleeed

[MaximG]

Please clarify whether the issue is reproduced if you replace the TUniTable component with TUniQuery.

[C32]

Hi,

Could someone please help to know how to create and resolve this error mentioned in subject line of this thread?

For the file which is not journaled and even journaled, I tried all the below Commit mode options in Advance server options still could not generate this error :-

Commit mode:

Commit immediate(*None)
Read uncommited (*CHG)
Read commited(*CS)
Repeatable read (*ALL)
Serializable (*RR)

***************************
also tried by changing various Connection types available under IBM i Access Windows ODBC Driver Connect:

1) Use ODBC access mode
2) Use ODBC access mode, Call allowed
3) Limit to Read/Call(Select and Call statements allowed)
4) Limit to Read-Only (Select statements only)

But could not generate that error(SQL7008).

So someone could please advise how to create this error and then resolve this error so that it will help to understand this error in a better way?



Thanks

[C32]

Hi,

Could someone please advise ?


Thanks.