From the ODP FAQ:
Q: In ODP.NET 10.2.0.2 and higher, why
does the same ODP.NET provider have
two different version numbers?
A: For ODP.NET 10.2.0.2 and higher,
the same ODP.NET binaries have two
different version numbers when viewed
from either .NET products (e.g. Visual
Studio 2005 would see version
184.108.40.206) or when viewed from Oracle products (e.g. Oracle Universall
Installer would see version
10.2.0.2.20). Prior to ODP.NET 10.2.0.2, the latter versioning was employed exclusively. The use [of] the
second versioning method was necessary
to properly support .NET policy files
for .NET Framework 1.x and 2.0.
Here is the version scheme:
For example, if the ODP.NET product
version number is 220.127.116.11.20, the
corresponding ODP.NET assembly
- .NET Framework 1.x version: 18.104.22.168
- .NET Framework 2.0 version: 22.214.171.124
Your version therefore refers to Oracle 126.96.36.199, for the .NET 2.0 framework.