2005 PTF1 regression

forum.gupta.bugreport (2005-2010)
Jeff Luther
Site Admin
Site Admin
United States of America
Posts: 2370
Joined: 04 Mar 2017, 18:34
Location: Palm Springs, California

2005 PTF1 regression

Post by Jeff Luther » 03 Nov 2005, 23:19

 Posted by:  Jeff Luther 

FYI to all: I ran PTF1 yesterday for TD2005 (aka v4) and found that
my SqlCreateStatement() call to start a session in Oracle hung up
and never returned. (No Sql error generated, either.)

The "Uninstalling PTF1 on Windows" section in ReadMe.html explained
how to undo, and after running the Add/Remove utility in WinXP
was able to get back to 4.0.0. SqlCreateStatement() now connects
ok. No mention of any change to this function on the "List of
Defects Fixed" page.

Best Regards,
Jeff Luther/PC Design
info: www.pulpcards.com/gupta/

shyam

Re: 2005 PTF1 regression

Post by shyam » 08 Nov 2005, 07:22

 Posted by:  shyam 

Hi,

I have tested the SqlCreateStatement() function w.r.t Oracle Router and also
Oracle Oledb provider. I did not see any problem w.r.t this function. It was
returning true. I have Oracle 9i client connecting to Oracle 10g Server.

Let me know the Oracle Version that you are using.

Regards,
Shyam

Jeff Luther
Site Admin
Site Admin
United States of America
Posts: 2370
Joined: 04 Mar 2017, 18:34
Location: Palm Springs, California

Re: 2005 PTF1 regression

Post by Jeff Luther » 08 Nov 2005, 17:23

 Posted by:  Jeff Luther 

Shyam:

"the Oracle Version" - 10g, on both db and client sides.

- Jeff

shyam

Re: 2005 PTF1 regression

Post by shyam » 09 Nov 2005, 13:33

 Posted by:  shyam 

Hi,

We even have a 10g client with us and we did not see any problem. I don't
know what is causing the problem at your end.

Regards,
Shyam

Gerry Butler

Re: 2005 PTF1 regression

Post by Gerry Butler » 03 Dec 2005, 20:45

 Posted by:  Gerry Butler 

I have seen this behaviour in our environment. SQLWindows 2005 (no PTFs),
Oracle 8i, Oracle OLE DB Provider. Since we are in the process of
converting from SQLRouter to OLE DB, we have left our sql.ini file on our
client workstations in order to be able to still use the tools which are
dependent upon SQLRouter. So, if I want to connect to Oracle through a
SQLWindows application using OLE DB, I have to remember to rename or delete
the sql.ini file from our environment. Otherwise, it seems that even if you
try to connect using SqlCreateSession and SqlCreateStatement, the sql.ini
file "gets in the way" and tries to make router-based connections. Halting
an application started this way, renaming the sql.ini file and then
restarting the application occasionally will lock up the client workstation.
It happened to me yesterday. If I restart my client workstation, rename the
sql.ini file and restart my SQLWindows OLE DB application, life is good
again.

While we are on the topic, after making an OLE DB connection, doing some DML
work, and then calling SqlDisconnect on the SqlHandle and SqlFreeSession on
the SessionHandle, the SqlHandle has a value of 0h and the SessionHandle has
a value of 0h, but the connection at the backend is still alive. If I query
Oracle with SELECT * FROM V$SESSION, I still see the connection UNTIL I quit
the SQLWindows application. Is this a bug?

--
Gerry Butler

Return to “gupta.bugreport”

Who is online

Users browsing this forum: [Ccbot] and 0 guests