Page 1 of 1

Bug in Assigning OraSession.ConnectString

Posted: Fri 27 Sep 2013 07:06
by a-s-z
Hi,

the ServiceName in ConnectString will get "transformed" to SID, when you assign sess2.ConnectString := sess1.ConnectString, so if you have a sess1 with server:1521:sn=sname, sess2 will try to connect to server:1521:sid=sname. :(

Problem seems to be in TDirectServerInfo.GetServerInfo, that does not qualify if sid or service name is used.


BTW: Critical update 9.1.4 is out, so I wonder why the announcment is missing?

Best regards,
Andre

Re: Bug in Assigning OraSession.ConnectString

Posted: Mon 30 Sep 2013 09:31
by AlexP
Hello,

Thank you for the information. We have fixed the problem. This fix will be included in the next ODAC version