Oracle: Expanded non LONG bind data supplied after actual LONG or LOB colum

Question

I am getting this error message when I try to insert clob into oracle table.
ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column. This error message is kind of misleading. For this error message, I should reorder the list of columns which means that the column with LONG RAW should come at end. So I reordered the list to make the LONG RAW column come at end. But I was still getting this error message. So I found out that data that needs to be inserted into the clob is causing this error.
Here is my code for inserting clob.
                    byte[] bytes1 = .....
                    statement.setAsciiStream(index, new ByteArrayInputStream(bytes1), bytes1.length);I don't know what is wrong with this code. I have been using this for a while and now it is throwing an exception.
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:213)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:952)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1160)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3390)
I am using JDK5 and Oracle 10g driver.
Please help me.

Answer 1

I have these columns,
ROW_DESC - Char
Table_id - Char
Blob_desc - Char
Blob1 - Blob
LOB_DATE - Date
CLOB1_DESC - Char
CLOB1 - Clob
CHAR_25_Col - Char
VBIN_400_Col - Long Raw.
But what I noticed is that the one causing the problem is not actually Long Raw column. "CLOB1" is the one causing a problem. The database is configured as unicode (AL32UTF8). When I tested it against another database with non-unicode, it works fine with same table description. So somehow it is unable to bind unicode large clob data.
I ran into this problem while I was inserting data from the source table to the target table.
Here is how I read from the resultset.
                    InputStream inputStream = resultSet.getAsciiStream(index + 1);
                    if (inputStream == null) {
                        return null;
                    ByteArrayOutputStream outputStream = new ByteArrayOutputStream();
                    byte[] buffer = new byte[1024];
                    int length;
                    do {
                        length = inputStream.read(buffer);
                        if (length > 0) {
                            outputStream.write(buffer, 0, length);
                    } while (length > 0);
                    byte[] resultBytes = outputStream.toByteArray();Here is how I bind parameters.
                    statement.setAsciiStream(index, new ByteArrayInputStream(resultBytes), resultBytes.length);If i use "((OraclePreparedStatement) statement).setStringForClob", then it works, but it will impact the performance, because I need to convert the clob to string.
is there any way to do it without converting to string object?
Thanks.