I think you have copied Oracle.DataAccess.dll to the target database while deploying the .NET stored procedure. That is why you are getting "System.TypeInitializationException".
Is it possible for you to -
1. Upgrade ODE(Oracle Database Extensions for .NET) to 11g as you are using ODT (Oracle Developer Tool for .NET) 11g?
2. Use ODT 10gR2 under VS2005/VS2003 which is compatible with ODE 10gR2?
As an afterthought - If you are comfortable working in .NET, you may try adding bindingRedirect for "Oracle.DataAccess" in "extproc.exe.config" in the database server's <OracleHome>\bin directory. You should redirect from 11g version to the 10gR2 version which is present in the database server machine.
Thank you, I resolved this issue. There was a DLL version mismatch due to my fumbling the install a couple of times.
Could you tell me how you managed to solve this problem?
I am stuck in the same situation (Re: ODE.NET 220.127.116.11.20 on 10g Database?!
I have 10g DB and 11g Tools, everything is loaded fine and does work giving the same Exception. It means I need ODE.NET? But it requires 11g DB. So, what is the solution?
This may be an old problem but it's still relevant in ODAC 11.
Go to your VS Project tab -> References -> select Oracle.DataAcess and check if "Specific Version" is set to *True* in its Properties.
If False then you get the TypeInitializationException, It is catchable.