Yesterday was writing a new feature for an online system. After writing, I found that the original database access layer has a small bugger, decided to update the DLL to the latest version of the use, Because the new version of the DLL is not Oracle.DataAccess.dll, but Oracle.ManagedDataAccess.dll, so the DLL is also updated. Update to find everything is OK. So I didn't do it anymore.
It turned out that the question came in the afternoon. Many users react to the problem of saving data for a business. An error that holds the "invalid length of the ora-01483:date or number bound variable" is reported. I checked from the program to the database field definition. No problem was found in the results. Then Baidu, Google. It's either a character-length issue or a Java-driven problem. Later I remembered the DLL that was replaced this morning and found that replacing it was normal. and replace it with new ones. The problem was finally found.
To the official web download the latest version of the Oracle.ManagedDataAccess.dll replacement on the OK.
Workaround for "Invalid length of ora-01483:date or number bound variable" (C # Version)