We are using OCI for one of our high-performant batch processing
servers.
The original reason behind using OCI was a belief it would give us a
better performance than implementing array operations using PROC. This
was probably a mietaken belief since PROC is nothing but a facade and
we are planning to phase it out actually.
We atarted out a couple of years ago with Oracle 7 and we had to do
relatively little modifications while upgrading to 8 and none at all
having recently upgraded to 9i.
Practice says it's quite backward compatible but Oracle does not
guarantee anything. Also, Oracle may replace old OCI calls with new
ones that peform better, and that the new PROC compiler will
automatically map to. This is even worse than "hard" incompatibility
since your application will compile and run just fine but without
taking advantage of new performance improvements.
"Martin Bertolino" <moc.xlat_at_bxm> wrote in message news:<%WPm8.6436$JZ6.149037_at_dfw-read.news.verio.net>...
> Does anybody in these groups have any experiences, good and/or bad, on the
> usage of the Oracle C++ Call Interface (OCCI) product for long
> running server applications?
>
> We have several server applications that currently use a home grown class
> library that makes using OCI somewhat pallatable, but keep having to add
> features to support different Oracle functionalities/features that distract
> us from developing the actual features of our applications.
>
> I have been looking into OCCI for some time now, but I was wondering if
> anybody could comment on the quality and reliability of this product,
> especially in the context of long running application servers.
>
> I'm also interested in any information regarding the session pooling
> capabilities, and how it handles the dabase server going down for some
> reason.
>
> Thanks for any feedbak.
>
> Martin Bertolino
> TALX Corporation
Received on Sat Mar 23 2002 - 13:13:05 CST
