New one...ORA-03115

[GregW]

Threaded program, with each transaction spawning a thread and each thread creating a data module with a dedicated OracleSession and multiple OracleQuery objects (some subset of which will actually be used).

19 hours post-launch, I get ORA-03115: unsupported network datatype or representation. Quick lookup says: "A user bind or define, or an ORACLE function is not supported by this heterogeneous SQL*Net connection."

Program environment have a 7.3.4.something Oracle client on NT4SP6a. The database is AIX-hosted 8.1.6.something.

The query executing is a stored proc call with 19 input parameters and 11 output, all bind variables of type varchar or float and all argument values for this invocation look sane. This particular stored proc is invoked probably 10000 times per day, so I don't think there's anything inherently wrong with the size or definition of the argument list.

On thing I see is that at roughly the same time I get a sqlnet.log that indicates a broken connection to the DB. "TNS-12547: Partner has unexpectedly gone away, usually during process startup." I don't see anything particularly interesting in the listener's log file.

Any nudges?

 

[Marco Kalter]

It seems a bit like Oracle bug #1399350. Have you verified this on a Net8 client?

------------------
Marco Kalter
Allround Automations

 

[GregW]

Haven't tried on Net8 yet. Read the referenced bug topic. It happened again today, after about a 22-hour uptime. Seems to have occured on TOracleSession.Commit, because I've got an exception handler like:
try
myQuery.Execute;
mySession.Commit;
except
// dumps SQL and argument list
end;

The dump from the exception handler shows data in the proc's output args and looks sane, but the data generated by the call are not present in the database (there's a missing sequence number).

Will see about getting an updated OCI layer in place.

 

[GregW]

Upgraded to OCI 8.1.7 yesterday. Put back the DOA-based client program today and things are worse. Access Violation in orageneric8.dll as soon as transactions start flowing in. I see a few other posts related to that kind of behavior in threaded apps, but nothing for quite some time. Any pdate on that issue?

G