Error creating job into trigger using DBMS_SCHEDULER.

Question

Hi,
I am trying to create job using dbms_scheduler package. I have one trigger on insert event on one table. I am creating job using following syntax.
CREATE OR REPLACE TRIGGER TRG_BI_JOB_CONFIG BEFORE INSERT ON JOB_CONFIG FOR EACH ROW
DECLARE
BEGIN
     DBMS_SCHEDULER.Create_Job(job_name => 'my_job1'
                         ,job_type => 'PLSQL_BLOCK'
                         ,job_action => 'delete_temp'
                         ,start_date => TO_DATE('15-JUL-2003 1:00:00 AM', 'dd-mon-yyyy hh:mi:ss PM')
                              ,repeat_interval => 'FREQ=DAILY'
                         ,enabled => TRUE
                         ,comments => 'DELETE FOR job schedule.');
EXCEPTION
WHEN OTHERS THEN RAISE;
END;
but I am getting following error while inserting into JOB_CONFIG table.
ORA-04092: cannot in a trigger
ORA-06512: at "PRAKASH1.TRG_BI_JOB_CONFIG", line 41
ORA-04088: error during execution of trigger
same above statement If I am running from sqlplus then It is creating job without error. If I am creating job using DBMS_JOB into trigger then It is also working fine but this package is depricated from oracle10g so I cannt use it any more.
My Oracle version is 'Oracle DATABASE 10g RELEASE 10.2.0.1.0 - Production'.
can anyone help me in this context.

Answer 1

I have a few comments on this thread as an Oracle dbms_scheduler developer.
- Oracle takes backward compatibility very seriously. Although dbms_job is deprecated, the interface will continue to work indefinitely. The deprecation of dbms_job is so that customers will be encouraged to take advantage of the more powerful dbms_scheduler. It is extremely unlikely that entire blocks of functionality will ever be removed. There is currently no plan to remove dbms_job functionality (and even if there were, doing so would be strenuously opposed by many users).
- lots of internal Oracle database components are standardizing on using dbms_scheduler (resource manager, materialized views, auto sql tuning etc). This is good evidence that it will continue to be the recommended scheduling method for the foreseeable future - not even the concept of a replacement exists. It is also under active development.
- The reason for the automatic commit is that a dbms_scheduler job is a full database object like a stored procedure or a table. So a call to dbms_scheduler.create_job is like executing a DDL which takes effect immediately. A dbms_job job is mostly just a row in a table so a call to dbms_job.submit behaves like regular DML. There are many advantages to a job being a full database object but DDL behaviour is an unfortunate requirement of this.
Hope this clears a few things up, reply with any questions.
-Ravi