Weirdest solution I had to learn the hard way….
Oracle ODP Provider for .NET likes to have the parameters of the OracleCommand object added in the same order as they appear in the declaration of the stored procedure (Package/Package Body) in the database.
Oracle will throw ambiguous errors regarding datatypes not matching or missing arguments – it’s really difficult to trouble shoot, but the answer is to simply sync the parameters order in the OracleCommand object with the order they appear in the database (on the signature of the stored procedure).
HTH – Dave
Comments on this entry are closed.