Re: Is OCI thread-safe?

In article <356B1565.68136413_at_vnet.ibm.com>, radu_at_vnet.ibm.com says...
> I seem to have the same problem:
> segmentation fault in:
> memset.memset
> kpumgs
> kpusc
> ..
> ..
> ocisq7
> ..etc.
>
> The environment consists of AIX 4.2.1, Oracle 7.3.2.3.0,
> Intersolv ODBC 3.02 and application with three threads,
> each thread having its own connection.
>
> Any ideas?
> Thank you,
>
> Radu Iorgulescu
>
> Eric Anderson wrote:
>
> > Is ORACLE's OCI library thread safe? I had assumed it was until recently
> > when I began getting some very peculiar runtime errors. Once under a heavy
> > load (maybe 5 or more concurrent database accesses, each on it's own
> > connection and cursor), my application will croak inside a function called
> > kpumgs() (I assume that's a function located somewhere deep in the oracle
> > libraries).
> >
> > My platform is ORACLE 7.3 enterprise for solaris/sparc.

I believe that OCI was not made thread safe until release 7.3.3. Even then it requires a call to OCI function opinit() to enable thread safety.

Bob Received on Wed May 27 1998 - 07:17:19 CDT