ODP CONEX FAILS ERROR C# VISUAL STUDIO 2017 — oracle-tech

    Forum Stats

  • 3,715,654 Users
  • 2,242,821 Discussions
  • 7,845,480 Comments

Discussions

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

ODP CONEX FAILS ERROR C# VISUAL STUDIO 2017

e51b2f3e-eb00-4b9f-b9b2-6e33103c949b
edited February 2019 in ODP.NET

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:

OK.jpg

Also, when I try this way.

OldConex.jpg

However, When I try to connect with the new ODP. It fails.

Fails.jpg

Also, If i try with the Visual Studio wizard is the same result.

testFail.jpg

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,

e51b2f3e-eb00-4b9f-b9b2-6e33103c949b

Answers

  • Alex Keh-Oracle
    Alex Keh-Oracle Posts: 2,751 Employee
    edited February 2019

    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.

    e51b2f3e-eb00-4b9f-b9b2-6e33103c949b
  • AndrewSayer
    AndrewSayer Member Posts: 12,998 Gold Crown
    edited February 2019

    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.

    e51b2f3e-eb00-4b9f-b9b2-6e33103c949be51b2f3e-eb00-4b9f-b9b2-6e33103c949b
  • e51b2f3e-eb00-4b9f-b9b2-6e33103c949b
    edited February 2019

    @AndrewSayer

    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

Sign In or Register to comment.