Re: **HELP** Problem connecting to Oracle after Win95 upgrade

From: Yasuhiro Ushitaki <ushi_at_po.globe.or.jp>
Date: 1996/11/30
Message-ID: <01bbdec8$047320e0$LocalHost_at_ns.globe.or.jp>#1/1


Hi,

lawking <lng_at_vitgmis1.telstra.com.au> wrote in article <01bbdce3$a44fca00$6d2349ac_at_Lawking.telecom.com.au>...
> I used to connect to a Oracle database using SQL*Net 2.0 installed on a
> Windows 3.1 PC. But since I upgraded from 3.1 to Win95, I can't no
 longer
> connect to Oracle, instead I am getting an error message "ORA-12545
> TNS:name lookup failure".
>
> Does anyone knows the solution to the problem?

Are there initial files for oracle (ex. oracle.ini) on windows or oracle-bin directory. If you can't find those files, have to recover them from backup media or recover by taking re-installation. If tha's OKey, add PATH variable including oracle-bin (ex. C:\ORAWIN\BIN) in Autoexec.bat, and try.

Hope for working-out by only PATH correcting.

> And if I install SQL*Net for Win95, will all my applications that uses
> SQL*Net 2.0 for Win3.1 be able to run as before without any modification?

That product is for 32-bits' interface appl. So, you must migrate all appls for Win3.1 to for-Win95, if you wanto use SQL*Net for Win95.
But you can run your appls with SQL*Net 2.0 for Win3.1 on Win95 by no modifcation, if your appls supports WOW.

Ahh... poor expressions, following is example.

Excel95 + ODBC32 + SQL*Net95, this is OKey. Excel3.1 + ODBC16 + SQL*Net3.1, this is OKey,also. Appls3.1 + ODBC16 + SQL*Net3.1, OKey,OKey.(case on WOW-supporting)

Excel3.1 + ODBC16 or 32 + SQL*Net95, this is No Good. Appls3.1 + ODBC16 or 32 + SQL*Net95, this is No Good, also.

Hope for catching my meaning and for your help.

-- 
Yasuhiro Ushitaki / Toyo Information Systems Co.,Ltd.
Received on Sat Nov 30 1996 - 00:00:00 CET

Original text of this message