Third Party Application Throws an ORA-12560. Trace Reveals The Connection Immediately Attempts a BEQ Connection
(Doc ID 1666200.1)
Last updated on MARCH 31, 2022
Applies to:Oracle Net Services - Version 184.108.40.206 to 220.127.116.11 [Release 8.0.6 to 12.1]
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
There are cases where a 3rd party successfully connect in one version of Oracle Net, but the same application can generate an ORA-12560 when using another version of Oracle Net.
The issue itself would be a certification issue with the application interfacing with the Oracle libraries. What works in one version of the client software may not work in another version if there are changes to any of the client side libraries (e.g. a change was made to Oracle's NLS libraries which the application is not aware of). It is also likely to occur with 32bit software on a 64bit operating system.
An Oracle Net trace file will show the application immediately requests to call an oranbeq DLL (the BEQ protocol adapter) as opposed to reading the tnsnames.ora file and proceeding on normally.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document