OCI call hangs up in a 64 bit app converted from 32 bit.

[Prahalad Appaji]

With reference to my previous thread

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1019332

we finally narrowed down the issue to an OCI call => OCIDescribeAny

Using WDB ( GUI version of gdb ) stepping through the code the application works just fine until it hits an OCI call called OCIDescribeAny. The parameters in the call are not null, examined by debugger. The call looks like this.

status = OCIDescribeAny(mConnection-getServiceContextHandle(),
mConnection->getErrorHandle(),
(text *)tablename.c_str(),
tablename.length(),
OCI_OTYPE_NAME,
0, OCI_PTYPE_TABLE,
describeHandle);

Note that it does not behave consistently. i.e it does not always get stuck but happens once in a while.

Any help

[Steven E. Protter]

Shalom,

Intermittant problem. It may be effected by a memory leak or other bad coding practices built into the original application code.

It also may be effected by system resources or how busy the system is.

It would be helpful to run the code through the debugger and to analyze system conditions to try and isolate the factor that causes the problem.

SEP