Limitations when Performing Oracle Batching?

Question

I'm using Oracle Batching to perform updates. The Update statement has 99 params. Batching a total of 40 such SQLs. Observation is that rows 1 to X will be successful but X to 40 will not be updated.
Is there a limit to the number of params within a OraclePreparedStatement when perform batch updates? Is there a limitation somewhere in Oracle's JDBC Type 4 Driver?
Turned on Oracle logging, and noticed the following, which led me to suspect the above...
=====================================
data[0].items[0] has 2 bytes:
data[0].items[0] has 2 bytes allocated
c1 15
data[0].items[1] has 2 bytes:
data[0].items[1] has 2 bytes allocated
c1 15
data[0].items[2] has 2 bytes:
data[0].items[2] has 2 bytes allocated
c1 15
data[0].items[3] has 2 bytes:
data[0].items[3] has 2 bytes allocated
c1 15
data[0].items[4]=null
data[0].items[5]=null
data[0].items[6]=null
data[0].items[7]=null
data[0].items[8]=null
data[0].items[9]=null
data[0].items[10]=null
data[0].items[11]=null
data[0].items[12]=null
data[0].items[13]=null
data[0].items[14]=null
data[0].items[15]=null
data[0].items[16]=null
data[0].items[17]=null
data[0].items[18]=null
data[0].items[19]=null
data[0].items[20]=null
===================================== etc
please help, thanx :)

Answer 1

I've found out the cause of my problem. It was due to something that's described in Oracle's 9i documentation as "Premature Batch Flush". I'm using 8.1.7, but encountered the behaviour.
The following is an abstract from the documentation:
===================================
Premature batch flush happens due to a change in cached meta data.Cached meta
data can be changed due to various reasons,such as the following:
The initial bind was null and the following bind is not null
A scalar type is initially bound as string and then bound as scalar type or the
re erse
The premature batch flush count is summed to the return alue of the next
executeUpdate()or sendBatch()method.
===================================