This content has been marked as final. Show 6 replies
This really isn't a bug but just known and documented behaviour. The scheduler can only accept SQL types as job argument values because it must store those values in a table prior to job execution. A boolean is not a SQL type (e.g. it can't be inserted into a table) so the scheduler can't store it into a table to use a a job argument.
The workaround is to create a wrapper procedure which accepts a VARCHAR2 or a NUMBER in place of the boolean and then converts the varchar2 or number into a boolean before calling the actual procedure. This workaround should work for booleans and for all PL/SQL types that are not SQL types.
Hope this helps,
That means clob/blobs are not allowed right?
Trying to submit a job to make the clob insert as async to save time on the transaction, but it seems it can not be done since the job action takes only < 4k characters.
Using the parameters it would be hard too, but i can create multiple parameters accepts varchar2 and keep doing write append.