Source:Special Schedules: Difference between revisions

From SEPsesam
No edit summary
Line 15: Line 15:
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_PROD  
and the execution parameter 'Blocking Date' ('Sperrtermin') must be enabled.
and the execution parameter 'Blocking Date' ('Sperrtermin') must be enabled.
[[Image:Blocking_Schedule.jpg|center]]

Revision as of 16:17, 16 June 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 schedule Backup_ORACLE with command event ORACLE_PROD is already defined. To disallow execution during 12:00 till 14:00 o'clock another schedule is defined with

  • daily execution
  • 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_PROD and the execution parameter 'Blocking Date' ('Sperrtermin') must be enabled.