Skip to main content

Search

Welcome to Tibero GTS!

Immediate Job Execution When Changing Job Scheduler Status

Document Type | Troubleshooting

Category | Administration

Applicable Product Version | 7FS02PS

Document Number | TADTS061

 

Issue

When enabling a Job scheduler that was in a disabled state, the Job executes immediately,
and the LAST_START_DATE column is updated upon activation as the Job runs.
 

Reproduction Scenario

1. Create Table 

SQL> create table test(id number);

Table 'TEST' created.

 

2. Create Job Scheduler (Insert 1 every minute starting at 17:55)

SQL> BEGIN
   DBMS_SCHEDULER.create_job (
       job_name        => 'INSERT_JOB',
       job_type        => 'PSM_BLOCK',
       job_action      => 'BEGIN INSERT INTO test (id) VALUES (1); COMMIT; END;',
       start_date      => TO_TIMESTAMP(TO_CHAR(SYSDATE, 'YYYY-MM-DD') || ' 17:55:00', 'YYYY-MM-DD HH24:MI:SS'), 
       repeat_interval => 'FREQ=MINUTELY; INTERVAL=1',       
       enabled         => TRUE                                   
   );
END;
/ 

PSM completed.

 

3. Confirm Creation

SQL> SELECT run_count, enabled, state, START_DATE, LAST_START_DATE, next_run_date, failure_count 
FROM user_scheduler_jobs 
WHERE JOB_NAME='INSERT_JOB';  


 RUN_COUNT ENABLED STATE      START_DATE                                         LAST_START_DATE                                    NEXT_RUN_DATE                                      FAILURE_COUNT
---------- ------- ---------- -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- -------------
          TRUE               2025/05/19 17:55:00.000000 Asia/Seoul                                                                                                                                 


 

1 row selected

 

4. Disable Job

SQL> 
BEGIN
   DBMS_SCHEDULER.DISABLE('INSERT_JOB'); 
END;
/
PSM completed.

 

5. Confirm Disable

SQL> SELECT run_count, enabled, state, START_DATE, LAST_START_DATE, next_run_date, failure_count 
FROM user_scheduler_jobs 
WHERE JOB_NAME='INSERT_JOB';  

RUN_COUNT ENABLED STATE      START_DATE                                         LAST_START_DATE                                    NEXT_RUN_DATE                                      FAILURE_COUNT
---------- ------- ---------- -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- -------------
          FALSE              2025/05/19 17:55:00.000000 Asia/Seoul                                                                                                                                

1 row selected.

 

6. Check Table

SQL> select * from test;

0 row selected.

 

7. Enable Job

SQL> BEGIN
   DBMS_SCHEDULER.enable('INSERT_JOB'); 
END;
/ 

PSM completed.

 

8. Check Status (LAST_START_DATE Updated)

SQL> SELECT run_count, enabled, state, START_DATE, LAST_START_DATE, next_run_date, failure_count 
FROM user_scheduler_jobs 
WHERE JOB_NAME='INSERT_JOB';  

 RUN_COUNT ENABLED STATE      START_DATE                                         LAST_START_DATE                                    NEXT_RUN_DATE                                      FAILURE_COUNT
---------- ------- ---------- -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- -------------
        1 TRUE               2025/05/19 17:55:00.000000 Asia/Seoul              2025/05/19 15:50:34.000000 Asia/Seoul              2025/05/19 15:51:34.000000 Asia/Seoul                       

1 row selected.

 

9. Check Status (LAST_START_DATE Updated)

SQL> select * from test;

       ID
----------
        1

 

 

Cause

The Scheduler Job did not have broken status cleared, and the next_date was always set to the current time,causing the Job to execute immediately.
 
 
 
 

Solutions

By applying the patch, the issue can be resolved so that the Job executes at the user-specified time. (Applied Patch: 338849).
Note
Apply the patch through technical support provided by TmaxTibero.

 

 

 

 

 

Related to