Call to Package Procedure fails with wrong number or type of parameters

Question

I think its getting to the correct package and procedure since if I change the name slightly, I get an error about it not being defined.
Here is my Parameter set up:
OracleParameter[] theParams = new OracleParameter[26];
theParams[0] = new OracleParameter("P1",OracleDbType.Char,2);
theParams[1] = new OracleParameter("P2", OracleDbType.Char, 12);
theParams[2] = new OracleParameter("P3", OracleDbType.Char, 12);
theParams[3] = new OracleParameter("P4", OracleDbType.Char, 12);
theParams[4] = new OracleParameter("P5", OracleDbType.Double);
theParams[5] = new OracleParameter("P6", OracleDbType.Char, 12);
theParams[6] = new OracleParameter("P7", OracleDbType.Char, 12);
theParams[7] = new OracleParameter("P8", OracleDbType.Char, 12);
theParams[8] = new OracleParameter("P9", OracleDbType.Char, 10);
theParams[9] = new OracleParameter("P10", OracleDbType.Char, 3);
theParams[10] = new OracleParameter("P11", OracleDbType.Char, 2);
theParams[11] = new OracleParameter("P12", OracleDbType.Char, 2);
theParams[12] = new OracleParameter("P13", OracleDbType.Char, 2);
theParams[13] = new OracleParameter("P14", OracleDbType.Char, 6);
theParams[14] = new OracleParameter("P15", OracleDbType.Char, 6);
theParams[15] = new OracleParameter("P16", OracleDbType.Varchar2);
theParams[16] = new OracleParameter("P17", OracleDbType.Char, 2);
theParams[17] = new OracleParameter("P18", OracleDbType.Char, 16);
theParams[17].Direction = System.Data.ParameterDirection.Output;
theParams[18] = new OracleParameter("P19", OracleDbType.Char, 12);
theParams[18].Direction = System.Data.ParameterDirection.Output;
theParams[19] = new OracleParameter("P20", OracleDbType.Varchar2, 12);
theParams[20] = new OracleParameter("P21", OracleDbType.Varchar2);
theParams[21] = new OracleParameter("P22", OracleDbType.Char, 2);
theParams[22] = new OracleParameter("P23", OracleDbType.Char, 2);
theParams[23] = new OracleParameter("P24", OracleDbType.Char, 2);
theParams[24] = new OracleParameter("P25", OracleDbType.Char, 2);
theParams[25] = new OracleParameter("P26", OracleDbType.Char, 2);
Now the problem is that the package definition is declared using types from database table columns, for the most part.
So for those, I used the real types of those columns, like for CHAR(2) I used OracleDbType.Char with length 2.
There are just a few odd balls that I'm not sure about.
For new OracleParameter("P5", OracleDbType.Double);, this is a parameter defined usijng a column type, that is NUMBER(8). Not sure what to use here.
For the line theParams[15] = new OracleParameter("P16", OracleDbType.Varchar2);, the parameter definition for the procedure parameter is VARCHAR2. So I used that with no length specified. Is that correct?
The oddest is this one, theParams[19] = new OracleParameter("P20", OracleDbType.Varchar2, 12);, where the procedure parameter is defined as a type from another package. That in turn is defined as a RECORD:
TYPE t_log_rec IS RECORD (
log_seq t_handle -- VARCHAR2(12)
and t_handle is defined in terms of another table column, and that is defined as VARCHAR2(12).
Any help on how to map those Oracle types back to .Net Oracle data types and parameter definitions is appreciated.

Answer 1

PLSQL Record types cannot be passed directly via OCI (read client) apps, and can only be instantiated/passed from other PLSQL procedures.
You could create a wrapper procedure in the database that accepts all scalar types, which then converts the varchar2 into a t_log_rec and then calls the "real" procedure.
Or, you could instantiate a t_log_rec inside an anonymous block and call the real procedure via that anonymous block.
Varchar2 parameters need size defined. When you assign an IN param a value, size is implicitly defined. OUT parameters need to have size explicitly defined.
Hope it helps
Greg