In fact, this problem is very intuitive, which is what you use in the C # project Oracal.DataAcess.dll The version of the file is the same as the one installed on your computer ODAC.EXE ( ODP.NET )Version inconsistency, whether it’s 32-bit or 64 bit platform inconsistency, or version inconsistency, anyway, it’s the mismatch that causes the problem. There are many specific solutions on the Internet, so I won’t go into details here.
But this time I had a strange problem. I have many on my machine ODAC.EXE Version, including two 64 bit, a 32-bit, and clearly I use in C # Oracle.DataAccess.dll The version of is exactly the same as an ODAC, but the exception “the provider is not compatible with the version of Oracle client sometimes” is thrown, which makes me very puzzled. What’s more strange is that this exception is not thrown out every time. Sometimes it doesn’t exist. That is to say, the connection between my code and the database, which can or can’t be connected, all depends on luck.
After a long search, we finally found the root of the problem. Because this is a legacy project, I downloaded it locally and saw the files circled in this project. Although I felt strange, I didn’t care too much. But it is these documents that cause the above problems. When I remove these files and recompile them, everything is OK and I can connect to the database normally. Therefore, the reason for this summary is that in the C # project of Oracle, you should not introduce OCI files casually. (at the moment, I don’t know why predecessors introduced these documents when they did this project.)
Read More:
- Oracle12c client32 bit installation error: [ins-20802] Oracle net configuration assistant failed
- Virtual environment: error: virtualenv is not compatible with this system or executable
- Version 1.8.0_201 of the JVM is not suitable for this product. Version: 11 or greater is required.
- Oracle database file is damaged, Error:ORA-01033 :ORACLE initialization or shutdown in progress
- Start eclipse and prompt version 1.7.0_ 79 of the JVM is not suitable for this product. Version: 1.8 or greater i…
- Eclipse specifies JDK version to start, and resolves version XXXX of the JVM is not suitable
- Failed to create Oracle Oracle home user solution appears in oracle12c installation
- raise RuntimeError(“tf.placeholder() is not compatible with “ RuntimeError: tf.placeholder() is not
- About errors:! Package natbib error: Bibliography not compatible with author year citations
- The binary version of its metadata is 1.5.1, expected version is 1.1.16
- The MAC system installs MySQL client, and the error is solved_ config not found
- About error:! Package natbib error: Bibliography not compatible with author year citations
- The python version output from the command line is inconsistent with the python version in the current CONDA environment
- ERROR 1148 (42000): The used command is not allowed with this MySQL version
- RuntimeError: module compiled against API version 0xe but this version of numpy is 0xd
- After node.js is installed, use the instruction node version in vscode to show that it is not an external or internal instruction. The solution is as follows:
- [solved] runtimeerror: module compiled against API version 0xc but this version of numpy is 0xb
- 【.Net Core】using declarations‘ is not available in C# 7.3. Please use language version 8.0 or greate
- Could NOT find CUDNN: Found unsuitable version “..“, but required is at least “6“
- [error record] as compilation error (Android support plugin version is too high | upgrade Android studio to the latest version)