OracleCommandBuilder BindByName=true raises Exception — oracle-tech

    Forum Stats

  • 3,708,745 Users
  • 2,241,117 Discussions


Howdy, Stranger!

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

OracleCommandBuilder BindByName=true raises Exception

Christoph WagnerChristoph Wagner Posts: 2 Red Ribbon
edited August 2020 in ODP.NET

We are currently in the process of replaceing the deprecated MS DataProvider with the current Oracle.Managed.DataAccess components.

In order to provide seemless integration we followed the recommended BindByName=true setting for OracleCommands, as this was the default for the MS Provider.
We use this as an Application wide setting in our App.config file. Basically this works, but we are now facing a Problem with the OracleCommandBuilder in combination with DataAdapters.
Dureing comman creation the Builder seems to create the commands with the respected App.config setting (BindByName=true) but unfortunatly create commands that rely on the BindByPosition (BindByName=false) setting.
This leads to an exception when we create and execute the DataAdapter.Update(...) method for the first time. Howerver subsequent calls to Update(...) will succeed.

Attached I have created a simple demo to show the problem. I this demo i rely on Oracle's sample HR Schema. But this error will be raised in any case

Any help is greatly appreciated.

Thanks in advance,


DB Version: Oracle

MS .Net 4.8 Console Application

Christoph Wagner


  • Alex Keh-OracleAlex Keh-Oracle Posts: 2,720 Employee
    edited August 2020

    Hi Christoph,

    I was able to reproduce your error using the test case you provided. I filed bug 31806772 for my dev team to fix the problem.

    Christoph Wagner
  • Christoph WagnerChristoph Wagner Posts: 2 Red Ribbon


    any news on this one? Have to ask here as i am not able to see the Bug in MyOracleSupport portal.

    Thanks in advance.

  • Alex Keh-OracleAlex Keh-Oracle Posts: 2,720 Employee

    Hi Christoph,

    I don't have any new news to report. I have made the bug publicly accessible in My Oracle Support so that you can now see it and track if you prefer.

Sign In or Register to comment.