Re: about sqlnet 2.3

V. Bernabé <victorbm_at_mx2.redestb.es> wrote:
: Our problem is:
 

: We are building a large Windows 3.1 application with Visual
: Basic 3.0
: which has been connecting to Oracle through ODBC 2.0 (with the SQORA.DLL
: driver) and SQL*Net v1.2.9.
 

: This is totally normal, but the application is composed by
: several
: executable files which have been using an unique connection for all of
: them. ODBC needs tree handles to access to Oracle data: handle to the
: enviromment, hENV; handle to the connection, hDBC; and a handle to the
: statement, hSTMT; so we were passing the hENV and the hDBC (which was
: allocated in the first EXE) between EXEs and allocating memory for the
: hSTMT in each one. It works very well and reduces lots of time while
: going from one EXE to another.
 

: Now we are using the SQORA73N.DLL driver for ODBC and SQL*Net
: v2.1.5.
: and the problems begin to appear:
 

: Once we pass the handles of the connection to the second EXE we
: allocate memory for the Statement succesfully, but when it makes its
: first SELECT, the following message is presented: ORA-12571: TNS:packet
: writer failure. And both EXEs loose the connection.
 

: We have a lot of questions, so we were pleased if you answer to
: some of
: them:
 

: ¿What are the differences between the following products which
: could
: cause the loosing of the connection?
: ¿How SQL*Net v2.1.5. and SQORA73N.DLL manages the connection?
: ¿Why Oracle return us the error message (ORA-12571)?
: ¿How can we solve this problem?
 

: Thank you for helping us.

-- 
Hi,

I experienced a similar problem when I configured SQL*Net using 
SQL*Net Easy Configuration running W 3.11 againts Unix server using TCP. 
It generated a tnsnames.ora which contained sections for both port 1521 
and 1526. When I removed the section for port 1526 SQL*Net worked just fine. 
(My services file indicates port 1521 for the listener). 

It might not be the same problem but it is a tip.

The reason why SQL*Net Easy Configuration did this was that it is using a 
template that indicates both section. The template is 
ORACLE_HOME\network\cfg\tnsnamed.tcp. By removing the the section for port 
1526 I still could use SQL*Net Easy Configuration.

Rgds
Steinar Heggelund

----------------------------------------------------------------------------
I'm employed in the Norwegian consulting company Opus One AS. 
I have 7 years experience with Oracle products, mainly the database. 
We are a small company which offers consulting services in design,
implementation and tuning of databases and applications based on Oracle.

My postings represent my opinions and they may be wrong.