Database Administration (MOSC)

MOSC Banner

DBMS_Scheduler, job start after startup database

"Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.8.0.0.0"

after a planned time out for maintenance we noticed that oracle scheduler start a job who's start_date was in maintenance time slot.

how to prevent this?


example:

job_start_time 02:00 PM

shutdown 12:00 AM

startup 04:00 PM

job starts immediatly after startup at 04:00 PM


that's how it happened

job_name, req_start_date, actual_start_date

xxx_RMAN_BACKUP_INCR_JOB 03.12.2020 21:15:00 04.12.2020 19:21:27

xxx_RMAN_BACKUP_INCR_JOB 04.12.2020 21:15:00 04.12.2020 23:06:22

while startup was 04.12.2020 19:21:27.


so what happened was that two (2) INCREMENTAL LEVEL=0 rman backups are created from a 2TB database, what is not wanted.


are there any job or global attribute to manage the behavior?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center