Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> Re: 9i OO4O/OLEDB connections randomly failing when using Oracle Names

Re: 9i OO4O/OLEDB connections randomly failing when using Oracle Names

From: Jared Still <>
Date: Thu, 15 Dec 2005 10:21:42 -0800
Message-ID: <>

Hi Rich,

I've had similar troubles with Onames.

This problem has appeared in a couple of apps.

One is a web app which makes numerous connections, as web apps are wont to do.

Another is a financial tool that makes a number of connections when a report is run.

Both connect through ODBC.

You may be able to tnsping the DB all day without seeing a failure. A way to emulate app behavior would be a script that makes numererous connects/disconnects to the db.

You might like to take a look at ML Note 179184.1.

It claims the bug is fixed in newer versions of the 9i client, but it doesn't appear to be true.

Using a client patched to, the bug still occurrs.

The only fix so far that I have found is to use tnsnames.ora. Not a good workaround, but that was the only way to make these 2 apps work.

Upgrading to a 10g client *migth* work, but is not certified with the apps in question.

OID is planned, which I hope will eliminate this.


On 12/7/05, Jesse, Rich <> wrote:
> So, we've finally upgraded from the 8.0.5 client to During
> testing, I had used a TNSNAMES.ORA file on the test boxes in order to be
> able to redirect production DB connections to test. But I had upgraded
> my PC first and still used our production ONAMES 8.1.7 server, and all
> was well. And the Guinea Pig initial limited deployment of about 30-40
> users using the production ONAMES server also showed no issues.
> Of course once we went live (last Thursday), all heckfire broke loose.
> Some OO4O/OLEDB VB apps would randomly break. Sometimes a program would
> error out with an ACCVIO at 0x00000000619156bd (sometimes
> 0x00000000619156b4). And sometimes the app would just silently
> disappear. And sometimes the apps would work. One user had a different
> error box popup that had the same error, but also noted the module was
> orantcp9.dll.
> I see MetaLink has a few bugs listed with orantcp9.dll and ONAMES. One
> says to upgrade ONAMES to 9i. So I installed a test ONAMES
> server on my Linux box and point a test machine's SQLNET.ORA to look at
> it for ONAMES resolution. Errors disappear! But as my PC isn't
> production- or backup-ready (in fact the power supply toasted
> yesterday!) I installed ONAMES on a Solaris box and pointed
> the test box's SQLNET.ORA at it. The apps fail again. What???!?? I
> toggle the SQLNET.ORA back to my Linux box and all's well again. Huh???
> The temporary fix is to replace ONAMES on the Windohs (Citrix) servers
> with a hardcoded TNSNAMES.ORA, but this is hardly a solution. I don't
> need the hassle of pushing out 500+ TNSNAMES.ORA files worldwide
> everytime there's a change to the list of available DBs.
> Anyone else experienced this? I've also seen mention that LDAP/OID
> resolution is affected, but there's no concrete anything on MetaLink.
> I've opened a TAR also, but thought I'd splatter the issue here. Also,
> my apologies, but as I'm not a Winders programmer, I don't know what the
> difference is between the several different methods of connecting a VB
> or .NET app to Oracle or if I'm even using "OO4O/OLEDB" correctly.
> Thoughts???
> TIA,
> Rich
> Rich Jesse System/Database Administrator
> QuadTech, Sussex, WI USA
> --

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

Received on Thu Dec 15 2005 - 12:23:55 CST

Original text of this message