ORAMTS TRANSACTION FAILS WHEN USING FULLY QUALIFIED TNS CON STRING
Last updated on AUGUST 25, 2017
Applies to:Oracle Services for Microsoft Transaction Server - Version 188.8.131.52 to 184.108.40.206 [Release 11.1]
Oracle Provider for OLE DB - Version 220.127.116.11 and later
Information in this document applies to any platform.
Using fully qualified TNS alias entries in your applications connection string is causing errors and/or application stack dumps when enlisting in distributed transactions.
For Example: string constr1 = "user id=scott;password=tiger;data
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms