Column ambiguously defined ORA-00918

The code below results in ‘Column ambiguously defined ORA-00918’ This occurs if version of Oracle.EntityFrameworkCore is 3.19.80 Worked well in Oracle.EntityFrameworkCore 2.19.90

`class Order{ public int Id{get;set;} public DateTime? CompletionDate{get;set;} public bool IsActive{ var now = DateTime.Now return now<this.CompletionDate || CompletionDate==null; } }

class OrderDetail{ public int Id{get;set;} public int OrderId{get;set;} public Order Order{get;set;} }

(from od in db.OrderDetails.Include(d=>d.Order) select new {Id=od.Id, IsActive=od.Order.IsActive}).ToArray()`

[omon77]

@danko007 You can avoid this bug, by configuring your db context to use SQL compatible with Oracle 11g, that doesn’t have this bug: services.AddDbContext<yourDbContext>(options => options.UseOracle(yourDbConnectionString, b => b.UseOracleSQLCompatibility("11"))

[kvansaders]

@danko007 You can avoid this bug, by configuring your db context to use SQL compatible with Oracle 11g, that doesn’t have this bug: services.AddDbContext<yourDbContext>(options => options.UseOracle(yourDbConnectionString, b => b.UseOracleSQLCompatibility("11"))

This worked for me. Thanks!

<PackageReference Include="Oracle.EntityFrameworkCore" Version="3.19.80" />
<PackageReference Include="Microsoft.EntityFrameworkCore" Version="3.1.12" />
Oracle 12c EE

Interesting that it worked for you. I’m still getting the same error with Oracle 12.1.0.2 Running application is net5.0, within startup:

            services.AddDbContext<DNADbContext>(options =>
                options.UseOracle(
                    Configuration.GetConnectionString("DbContext"), b => b.UseOracleSQLCompatibility("11")
                ));

DBContext is within another library, netstandard2.1

<PropertyGroup>
    <TargetFramework>netstandard2.1</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Oracle.EntityFrameworkCore" Version="5.21.1" />
  </ItemGroup>

I tried using the EF package versions you specified, still with no resolution. When I repoint to a local 18XE though, it does work just fine.

Also - Is there something that would possibly need to be configured on the 12.1 server for b.UseOracleSQLCompatibility(“11”) to actually work?