Validations and Common Error Messages
Common validation error messages are documented in the table below. However, there can be other kinds of errors (for example, unexpected privilege related errors).
| Error message | Reason |
|---|---|
|
Output argument type of the procedure must be NUMBER. |
The procedure specified has an |
|
Function or procedure not found. |
Check the name of the function or procedure in the custom package. Could be case mismatch or privilege issue too. |
|
No output type found. |
There is no |
|
Only 1 output argument allowed. |
There is more than one |
|
Input arg not a scalar measure. |
Only scalar string measures and string constants are allowed as input. Check whether quotes are missing in case of constants. |
|
Expecting <type> but received <type>. |
Mismatch in argument type between PL/SQL function or procedure signature
and the arguments passed to |
|
Only 1 measure allowed on the LHS. |
There can be only 1 measure on the LHS of the |
|
RHS size must be more than 2. First 2 args are package name and procedure name. |
Not enough arguments passed in to
the |
|
LHS must be a measure |
Found LHS to be a constant instead of a measure. |
|
LHS must be a scalar measure. |
There is an LHS measure but it is not scalar. |
|
LHS measure must be of type integer. |
There is an LHS measure and it is not scalar, but it is not of type |
|
Number of input args <number> does not match the procedure signature number <number>. |
Mismatch in number of arguments
between PL/SQL function or procedure signature and the arguments passed to |
|
ExecPLSQLExpression incrementalEval not supported! |
If other errors are bypassed and |
|
PL/SQL type <type> is not supported. |
Unexpected type in the PL/SQL function or procedure signature. |