Re: Oracle 7.2 ODBC, Power Builder 5.02

I think that in order to help you out you need to provide some more information:

1. What is your development environment:
   1. Version of Oracle Connecting to:
   2. Client workstation Operating System:
   3. SQL*Net Version (16 or 32-bit) :
   4. ODBC Version
2. What is your production environment:
   1. Version of Oracle Connecting to:
   2. Client workstation Operating System:
   3. SQL*Net Version (16 or 32-bit) :
   4. ODBC Version
3. What is your Powerbuilder configuration to connect to Oracle?
4. What ODBC driver are you using to connect to Oracle?
5. Are you using the same ODBC Connection setup for Production and Development?

I think that by answering these questions, it will give us a better picture of
the environment you are working with.
Thanks!

P.S. Yes, your trace does help also.
Kenneth Wong <wongke_at_aecl.ca> wrote in article <E943qo.1Fv_at_cu23.crl.aecl.ca>...
>
>
> We have a problem connecting to an Oracle 7.2 database using ODBC with
 the following
> error message on NT 3.51 (and 4.0):
>
> Database Error: SQLSTATE = S1000
> [Oracle][ODBC Oracle Driver][Oracle OCI]ORA-12196: TNS received an error
 from TNS
>
> The sqlnet.log file contains the following:
>
> Fatal OSN connect error 12196, connecting to:
>

(DESCRIPTION=(CONNECT_DATA=(SID=PD73)(GLOBAL_NAME=QINSHAN1.world)(CID=(PROGR AM=TeddyBase (Alpha 2.1.1))(HOST=Windows NT PC)(USER=wongke)))(ADDRESS_LIST=(ADDRESS=(PROTOCOL=ipc)(KEY=QINSHAN1.world)) (ADDRESS=(COMMUNITY=tcp_comm.world)(PROTOCOL=TCP)(Host=qinshan1.candu.aecl.c a)(Port=1521))))
>
> VERSION INFORMATION:
> TNS for WINDOWS 32: Version 2.2.2.1.0 - Production
>
> Time: 23-APR-97 18:04:48
> Tracing not turned on.
> Tns error struct:
> nr err code: 12196
> TNS-12196: Message 12196 not found; No message file for
 product=NET20, facility=TNS
> ns main err code: 0
> ns secondary err code: 0
> nt main err code: 0
> nt secondary err code: 0
> nt OS err code: 0
>
> Of course, the application works fine in development environmental. In
 fact, if we start the application either from the file
> manager or from a DOS window, then it works fine too. We suspect it is
 some kind of set up problem. Any help or
> suggestions would be greatly appreciated.
>
  Received on Thu Apr 24 1997 - 00:00:00 CDT