RE: JT400 SQLException -- "SQL0101N The statement is too long ortoocomplex"

Check out this link for the OS/400 maximum capacities.  Depending on what
OS/400 version your at, there is a definite limit to the length of a records
combined field lengths.

http://publib.boulder.ibm.com/iseries/v5r1/ic2924/tstudio/tech_ref/syslimit/

Tim

-----Original Message-----
From: java400-l-bounces+tkosacek=visioninfo.com@midrange.com
[mailto:java400-l-bounces+tkosacek=visioninfo.com@midrange.com]On Behalf
Of David Gibbs
Sent: Thursday, January 16, 2003 6:28 PM
To: java400-l@midrange.com
Subject: JT400 SQLException -- "SQL0101N The statement is too long or
toocomplex"


Folks:

One of the developers I work with is trying to implement DB2/400 functions
in a java application.

We're encountering a problem when we try to execute the following statement:

CREATE TABLE SiLocks (ID INTEGER NOT null, ArchiveID VARCHAR(255) NOT null,
RevisionID VARCHAR(80) NOT null, UserID VARCHAR(254) NOT null, LockTime
TIMESTAMP NOT null, Annotation CLOB(1073741824), ChangePackageID
VARCHAR(20), ProjectID CLOB(1073741824) NOT null, VariantProjectID
VARCHAR(254), Sandbox CLOB(1073741824), Hostname CLOB(1073741824), MemberID
CLOB(1073741824))

We're getting the following exception:

SQLException: SQLState(54001) vendor code(-101)
java.sql.SQLException: [SQL0101] SQL statement too long or complex.

If we reduce the CLOB sizes for some of the fields, the statement works.

Any idea why this would happen?

We're using JTOpen 3.1 and connecting to a V5R1 system.

Thanks!

david



_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/java400-l
or email: JAVA400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.