May 8, 2011 at 6:11 PM
Edited May 8, 2011 at 6:18 PM
Found the problems.
The Oracle function exceptions are caused by how the StoredProcedureReturnValue parameter in the BeginExecuteDbCommand class is handled.
It's tacked onto the end of the parameter list (presumably because SQL Server likes it there) & Oracle calls require that the return value be the first parameter.
As for the procedure out params, I was able to get my string/varchar2 Out parameters to properly update once I changed the dbParameter.Size = -1 statement in the same class to be a positive value.
I'll do some more experimentation with various return types, make some changes to the necessary library class(es) based on detecting an Oracle provider, then back to my Workflow solution.
This is not a particularly active topic, but thought I'd note this to save anyone else some time if they're using Oracle & the activity pack.