Re: sqlnet.ora causes catestrophic failure

On Mar 23, 3:05 pm, "slowly_tree" <Ryan.Tru..._at_gmail.com> wrote:
> I have inherited an ancient application (VB6) that talks to oracle 8
> and 10 via an oracle 9i connector. Have started moving an
> sqlnet.ora file onto client machines (so that I can quickly redirect
> db access after I upgrade dbs from 8 to 10). Most work correctly, but
> a cluster of them die on an VB6 error (catestrophic failure: ADODC1).

I have a bit of experience with VB6 communicating with Oracle 8i and 10g. Given the limited amount of information that you provided, I cannot determine the exact cause. I am guessing that the application is using data grids, or other similar controls that are meant to decrease development time. I personally dislike such controls due to performance and other issues. You may try patching VB 6 with one of the VB service packs, and then build a new setup package for the VB program and install the setup package on the computers that are having issues.

The problem may also be related to the version of ADO installed on the computer. Download and install the latest version of ADO (MDAC).

The problem may be related to the ODBC client. You may be using the Microsoft ODBC client for Oracle on some computers and the Oracle ODBC client on other computers. Double-check to make certain that the ODBC settings are identical from one computer to the next.

Differences in the tnsnames.ora file from one computer to the next may also be contributing to the problem.

Suggestions (in order):
* Verify that the tnsnames.ora, protocol.ora, and sqlnet.ora files are identical on computers that work correctly, and the computers that do not work correctly.
* Verify that the ODBC settings are identical on computers that work correctly, and the computers that do not work correctly. * Install the latest version of ADO (MDAC) on the clients that are not working properly.
* Use Microsoft's DEPENDS utility to verify that DLLs, OCXs, and other files required by the Visual Basic application are identicals on computers that work correctly, and the computers that do not work correctly.
* Consider enabling client side and server side tracing of traffic sent to/from the database.

Charles Hooper
PC Support Specialist
K&M Machine-Fabricating, Inc. Received on Sat Mar 24 2007 - 17:21:46 CDT