Skip to Main Content
Forums

Berkeley DB Family

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

History of BerkeleyDB

527197Aug 16 2006 — edited Aug 16 2006
Hello,
a not so technical question for once ;-). I want to properly introduce BerkeleyDB in my thesis (and there is lots of material)- however Iam having a hard time finding a reliable source about its history. For example: when were the first public releases? Could someone give me a hint where to look?

Best regards,

Rüdiger

Comments

Tridus

As an update, this seems to happen if sqlnet.ora is found at all. I can remove everything from sqlnet.ora it and it still happens. If I rename sqlnet.ora to something else, the problem goes away, it picks up tnsnames.ora, and things work just fine.

Tridus

Just posting to add that it's still an issue with the 3.1 release version.

Alex Keh-Oracle

My dev team found the bug. It looks like a regression. We filed a bug (31867606) on your behalf and will work on a fix.

2 people found this helpful
Tridus

Great, thank you!

KlausER

We are experiencing the same issue.

As a workaround I have renamed the sqlnet.ora. I am not sure if this causes any side effects.

We have already filed an issue on github: https://github.com/oracle/dotnet-db-samples/issues/99

Alex Keh-Oracle

This bug has been fixed and will be part of our next ODP.NET 19.10 release.

Alex Keh-Oracle

While you're waiting for a fix, there are a couple workarounds. You can either:

  1. Include the System.DirectoryServices.Protocols NuGet package or
  2. Don't set TnsAdmin via OracleConfiguration. Use other means to get the configuration info.
1 person found this helpful
KlausER

Including the package System.DirectoryServices.Protocols solved the problem for us.

Many thanks for the quick response.

User_UU1WZ

It seems like the the core version is prone to this, too.
Are you aware of that ?

User_UU1WZ

Ok this was non-sense... I´m sorry...
The question to ask would be: What exactly do I need to get the fix ? Using Oracle.Enitity.Framework.Core 3.19.80 still results in that issue - I still need to include the protocols package...

Alex Keh-Oracle
Answer

Oracle uploaded a fix for this bug last night on NuGet Gallery. You can download it here: https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core/

Marked as Answer by Tridus · Oct 22 2020
Tridus

Works great, thanks Alex!

Tridus

If you're only pulling in Oracle.EntityFramework.Core, it's probably grabbing the minimum version of Oracle.ManagedDataAccess.Core that it requires, which is where the bug is present.
Go into NuGet and get Oracle.ManagedDataAccess.Core 2.19.91 specifically. That resolves the issue.

1 person found this helpful
1 - 13
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Sep 13 2006
Added on Aug 16 2006
#berkeley-db
1 comment
868 views