oracle - Changing start date for system jobs related to automatic statistics collections in 11g -


i have oracle database 11g enterprise edition release 11.2.0.1.0 - 64bit production running on windows 2008 r2 somehow got next run dates scheduled jobs set dates in year 2016. jobs created able reset start_date in turn caused next_run_date reset. jobs related oracle automatic statistics collections unable dms_scheduler.set_attribute work changing start_date values.

i tried resetting weekly window's dates per oracle document id 1450173.1 using sql following , did in fact reset values see within dba_scheduler_windows had no change dba_scheduler_jobs

begin dbms_scheduler.set_attribute ( name => '"sys"."monday_window"', attribute => 'start_date', value => '10-jun-15 10.00.00.000000000 pm us/central'); end; / 

the job names seeing issue on are:

rse$clean_recoverable_script ora$autotask_clean purge_log sm$clean_auto_split_merge bsln_maintain_stats_job mgmt_stats_config_job 

some of lack schedule names if try dbms_scheduler.set_attribute ones have schedule names follow error:

   begin dbms_scheduler.set_attribute ( name => '"sys"."bsln_maintain_stats_sched"', attribute => 'start_date', value => '10-jun-15 12.00.00.000000000 -05:00'); end; error report - ora-27476: "sys.bsln_maintain_stats_sched" not exist ora-06512: @ "sys.dbms_isched", line 4398 ora-06512: @ "sys.dbms_scheduler", line 2892 ora-06512: @ line 2 27476. 00000 -  "\"%s\".\"%s\" not exist" *cause:    database object specified not exist. *action:   reissue command using object exists or create new            object , reissue command. 

i did try execute jobs throws error well:

exec dbms_scheduler.run_job('"sys"."bsln_maintain_stats_job"', false) error report - ora-27476: "sys.bsln_maintain_stats_job" not exist ora-06512: @ "sys.dbms_isched", line 185 ora-06512: @ "sys.dbms_scheduler", line 486 ora-06512: @ line 1 27476. 00000 -  "\"%s\".\"%s\" not exist" *cause:    database object specified not exist. *action:   reissue command using object exists or create new            object , reissue command. 

tried run dbms_auto_task_immediate.gather_optimizer_stats ran had no change next_run_date values within dba_scheduler_jobs

i have tried using dbms_auto_task_admin.enable , dbms_auto_task_admin.disable 'auto optimizer stats collection' see if perhaps how trigger date resets did not. had suggest me perhaps restart of oracle result in resets of dates since windows start dates did reset , maybe ones in dba_scheduler_jobs somehow in memory restart changed nothing.

so ultimate question how can start_dates or next_run_dates reset?


Comments

Popular posts from this blog

javascript - gulp-nodemon - nodejs restart after file change - Error: listen EADDRINUSE events.js:85 -

Fatal Python error: Py_Initialize: unable to load the file system codec. ImportError: No module named 'encodings' -

javascript - oscilloscope of speaker input stops rendering after a few seconds -