IndexBy table param in OracleCallableStatement creates 4MB byte[] with junk

Question

We have facing OutOfMemory error and the memory dump points to huge memory heap in a particular CallableStatement. One of the parameter to the CallableStatment is a index-by table and this is creating a 4MB byte array and holding on to it.
This is our call:
ocStmt.setPlsqlIndexTable(bindIndex[0],
translationData,
500,
translationData.length,
OracleTypes.VARCHAR,
2000);
translationData is a declared as "String[] translationData". When I print out the translationData.length, it comes as 40. In the memory dump, there is a byte[] parameter to this CallableStatment whose size is 4 MB and if I check the contents of it, the initial staring part is what we pass and rest is all nothing/junk.
One thing to note is that some of the elements in the translationData string array is null.
We also close this staement in the finally block. Do we need to do anything else, to remove this foot print from the memory?
OracleCallableStatement ocStmt = null;
try
// Prepare the statement and call the loader procedure
ocStmt = (OracleCallableStatement)mConn.prepareCall(sCreateTaskTranslations);
int[] bindIndex = new int[] { 1 };
Util.setStringValue(ocStmt,taskId,bindIndex);
Util.setIntValue(ocStmt,version,bindIndex);
ocStmt.setPlsqlIndexTable(bindIndex[0],
translationData,
500,
translationData.length,
OracleTypes.VARCHAR,
2000);
bindIndex[0]++;
//setInt method interprets a value of 0 as null
//call setIntNotNullValue to allow a value of 0 to be passed.
Util.setIntNotNullValue(ocStmt,rec_size,bindIndex);
Util.setBooleanValue(ocStmt,isVersionable,bindIndex);
ocStmt.executeUpdate();
catch(Exception e)
// Throw this Exception
finally
Util.closePreparedStatement(ocStmt);
Any pointers on why it is ending up with such a huge byte array? and how to avoid it?
Edited by: user641043 on Mar 23, 2010 12:33 PM

Answer 1

Hi,
I think you will be better of posting your question in call interface forum.
Oracle Call Interface (OCI)
Regards