Source:Special Schedules: Difference between revisions

From SEPsesam
(revised jpegs)
mNo edit summary
Line 8: Line 8:
'''Example:'''
'''Example:'''


An hourly schedule Backup_ORACLE with command event ORACLE_PROD and Priority '1' is already defined.
An hourly scheduled backup for ORACLE with command event 'ORACLE_XE_full' and Priority '1' is already defined.


To disallow execution during 12:00 till 14:00 o'clock another schedule, e.g. block_ORACLE_1200-1400, must be defined with
To disallow execution during 12:00 till 14:00 o'clock another schedule, e.g. block_ORACLE_1200-1400, must be defined with
Line 16: Line 16:
[[Image:Blocking_schedule_execution_schedule.jpg|center]]
[[Image:Blocking_schedule_execution_schedule.jpg|center]]


This schedule, e.g. block_ORACLE_1200-1400 must be connected to the same command event, e.g. ORACLE_PROD,  
This schedule, e.g. block_ORACLE_1200-1400 must be connected to the same command event, e.g. 'ORACLE_XE_full',  
his priority must be higher then the other one, e.g. ''''2''''  
his priority must be higher then the other one, e.g. ''''2''''  
and the execution parameter ''''Blocking Date'''' ('Sperrtermin') must be enabled.
and the execution parameter ''''Blocking Date'''' ('Sperrtermin') must be enabled.

Revision as of 10:57, 5 August 2008

Special Schedules

In version 3.4.1.x a special version of programm sm_sepul_event revision 1.183.2.1 allows to define schedules which will block hourly execution of other schedules related to the same object. The blocking is done during the 'starting time window' of a further defined schedule.

Example:

An hourly scheduled backup for ORACLE with command event 'ORACLE_XE_full' and Priority '1' is already defined.

To disallow execution during 12:00 till 14:00 o'clock another schedule, e.g. block_ORACLE_1200-1400, must be defined with

  • weekly execution, from Monday till Friday
  • starting time 12:00 o'clock, duration 2 hours.

This schedule, e.g. block_ORACLE_1200-1400 must be connected to the same command event, e.g. 'ORACLE_XE_full', his priority must be higher then the other one, e.g. '2' and the execution parameter 'Blocking Date' ('Sperrtermin') must be enabled.