MIDRANGE dot COM Mailing List Archive



Home » JAVA400-L » October 2005

Re: SQL exception SQL7008



fixed

I am somewhat familiar with the SQL7008 message. It is a little notorious. 
Essentially it means that the table you are trying to update is not 
journaled. If I may guess, are you attempting to use the native DB2 
driver, locally on the iSeries? As the iSeries seems to be one of the few 
platforms where transaction support is not enabled by default, some JDBC 
drivers have a problem with a committable database action. If you are 
using the default setting of "autocommit" or you issue a commit in your 
own code, you will receive an SQL7008 unless you have a journal receiver 
defined for the tables you are attempting to update.

The quick way around this is to connect to the driver with the following 
properties:

            Connection nativeDriverConnection = null;
            try {
                final Properties properties = new Properties ();
                // The following DB2 directive is needed to prevent an
                // SQL7008 error on files that are not journaled.
                properties.put ("transaction isolation", "none");
                Class.forName("com.ibm.db2.jdbc.app.DB2Driver");
                nativeDriverConnection =
                        DriverManager.getConnection("jdbc:db2://"
                                                    + 
as400.getSystemName(),
                                                    properties);
            } catch (ClassNotFoundException e) {
                LOGGER.error("Error in DataCollector.getConnection "
                             + "loading JDBC driver 
com.ibm.db2.jdbc.app.DB2Driver",
                             e);
            }

I hope this helps.


Jeff Furgal / MIMIX Product Architect
Lakeview Technology, Inc.
Suite 600
1901 S. Meyers Rd.
Oakbrook Terrace, IL 60181

furgalj@xxxxxxxxxxxxxxxx 





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact