We use this SqlPLSqlcommand to get the result in 28 Arrays (OUT) and
another 7 strings. A total of 35 parameters.

CTD 1.5.1 PTF 6 and Oracle 8.1.7 clients. Most of the time it works
fine. But all of a sudden, we get Dr.Watson error.

Also SqlPLSqlCommand is called in other two places, but we only get
around 10 arrays back. Those places, I never got Dr.Watson.

Any clues will be very helpfull.

Thanks,
Mahesh.

Want to follow up. If anyone had any luck with this, please help me.

Thanks,
Mahesh.

maheshrm (AT) hotmail (DOT) com (Mahesh) wrote in message news:<b77532b8.0404220842.15d3428e (AT) posting (DOT) google.com>...

OK. After doing a lot of research, I have done the following to
eliminate memory issues with SQLPLSQLCommand.

There are a number of issue with using dynamic arrays in
SQLPLSQLCommand. First and foremost, whether you are passing a blank
array or with data, it always pass the array variable as LONG.

So when I was passing around 35 arrays, even though there are not much
data in them, it still passed 35 LONG variables.

So the solution was to reduce it to less than 10 arrays. I did that.
Along with reducing, from the Oracle Package, I started concatenating
the variables and send them back in 10 arrays rather than 35 arrays.
In the CTD program, I tokenized to split them back to 35.

Now there are no Dr.Watson and everything is working fine. Posted
this thinking that it might benefit others.

Thanks,
Mahesh.


maheshrm (AT) hotmail (DOT) com (Mahesh) wrote in message news:<b77532b8.0404280814.46670b3a (AT) posting (DOT) google.com>...