- 3,715,654 Users
- 2,242,821 Discussions
- 7,845,480 Comments
Forum Stats
Discussions
Categories
- 17 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 1.6K Databases
- 467 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 22 Multilingual Engine
- 487 MySQL Community Space
- 3 NoSQL Database
- 7.6K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 416 SQLcl
- 42 SQL Developer Data Modeler
- 184.8K SQL & PL/SQL
- 21K SQL Developer
- 1.9K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.1K Development Tools
- 8 DevOps
- 3K QA/Testing
- 247 Java
- 5 Java Learning Subscription
- 10 Database Connectivity
- 66 Java Community Process
- 1 Java 25
- 9 Java APIs
- 141.1K Java Development Tools
- 6 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 10 Java SE
- 13.8K Java Security
- 3 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 125 LiveLabs
- 30 Workshops
- 9 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 3 Deutsche Oracle Community
- 10 Español
- 1.9K Japanese
- 2 Portuguese
ODP CONEX FAILS ERROR C# VISUAL STUDIO 2017

Hi,
I was facing this issue. Hope someone could help me.
The database has the following:
SELECT * FROM V$VERSIONBANNEROracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit ProductionPL/SQL Release 11.2.0.4.0 - ProductionCORE 11.2.0.4.0 ProductionTNS for IBM/AIX RISC System/6000: Version 11.2.0.4.0 - ProductionNLSRTL Version 11.2.0.4.0 - Production
For another part, I have the latest Visual Studio Enterprise 2017 - Version 15.9.7
When I do this simple code:
Also, when I try this way.
However, When I try to connect with the new ODP. It fails.
Also, If i try with the Visual Studio wizard is the same result.
To give extra information the versions of both DLL are:
According to dotPeek
Oracle.DataAccess, Version=2.112.1.0, Culture=neutral, PublicKeyToken=89b483f429c47342
For the other from nuget:
<package id="Oracle.ManagedDataAccess" version="18.3.0" targetFramework="net47" />
Best Regards,
Answers
-
I couldn't find an existing known issue matching your error message and situation. I would recommend opening up an Oracle SR and providing support with your managed ODP.NET level 7 trace. A lot of activities occur upon opening a connection. The trace will tell us what specific activity is causing the failure.
Your other option is to post the trace in this thread, but I would not recommend it. It would expose a whole lot of your client and DB internal info.
-
ORA-20000 is (usually) raised by non-Oracle PL/SQL using raise_application_error. I suggest you chat to your DBA about any logon triggers set up on the DB - it very much looks like this has been put in place on purpose to restrict connections.
-
I think is what you say but I'm still wondering. Why does it work with first option but not with the last?
I've been using the same credentials, same databse the only difference is the DLL.
Oracle.ManagedDataAccess --> Is not working to my Oracle 11g Database, any idea?
Best Regards