Incorrect argument type encountered in function or method invocation. in main ~ foundjava

I am working with ORACLE SOA & OSB version 11.1.1.5.0. This error occurs if you use Oracle Business Rules and you forget to pass all the objects defined in your decision function. To elaborate: if in your decision function you have defined as inputs, let’s say, the objects Customerand Address, but in your code you only pass as input the object Customer, then you will get the error message above. To fix it either pass both objects, or remove the unused object from the input settings of your decision function.

The actual error oracle outputs is rather misleading. I spent three hours trying to find out what’s going on.

Read More »

ORA-01003: no statement parsed ~ foundjava

Not Java-related but since I started doing a bit of PL/SQL lately and I ran into this problem, I will post this. This error, in my case, was caused by having an Oracle keyword defined as a column name. For example the following

1 2 3 4 5 6

OPEN v_customer_recs FOR          SELECT sc.EVENT_ID,                 sc.OPEN_DATE,                 ND.DESCRIPTION AS COMMENT,  -- This will cause the error                 SC.BC_DATE            FROM CUSTOMERS sc, NEW_DESCRIPTION ND

will result in a ORA-01003: no statement parsed. The problem is that the COMMENT keyword is used as a column name. If you change this then the error will go away.

Read More »