Document toolboxDocument toolbox

sp320_dbtidy_schedule

Owned by Jason Andrew
Oct 02, 2024

Contains the data used to tell when an FRU should be tidying expired job data from the database. Schedules can be defined at two levels: at the FRU level and at the system level. If a FRU has a schedule defined at the FRU level then it only uses that schedule, i.e. it does not combined this with the system level one. If there is no FRU level schedule for a FRU then it uses the system level schedule. If an FRU is not to have a schedule, i.e. it is not to perform database tidying then the sp213.fru_tidy_enabled value should be set to NO.

The system level schedule comprises the rows that have a fru_no set to the resp_unit_no of the root RU as found in sp058_responsibility_units.

 

Table Definition

Field
Type
Default
Nullable
fru_no number(4)   (error)
day_of_weeknumber(1)   (error)
time_of_dayvarchar2(5)   (error)
durationnumber(4)   (error)
batch_sizenumber(6)   (error)
tidy_intervalnumber(4)   (error)

Keys

primary key (fru_no, day_of_week, time_of_day) 
foreign key (fru_no) references sp058_responsibility_units (resp_unit_no) 
check (day_of_week between 0 and 6)

Column Descriptions

FieldDescription
fru_noThe FRU number. For the system default schedule this is the resp_unit_no for the root node in the RU hierarchy; as defined in sp058_responsibility_units – it is the RU that has a resp_unit_type of 2. 
day_of_weekNumber in the range 0 – Sun to 6 – Sat representing the day of the week. 
time_of_day  A 5 character time in the format hh:mi as a 24 hour time, which specifies when the tidy task starts, using the FRU’s timezone. DST issues are resolved by considering this time to be the duration past midnight.
durationSpecifies how long this task runs for, in minutes. This is approximate. If the batch_size is large then it could end up running past the end of the scheduled time.  
batch_size 

The number of jobs to be deleted in one batch. 

If the Batch Size is too big then the FRU can take so long to complete a batch deletion that the schedule lock timeout (schedlock_timeout) is exceeded.  This may cause the FRU to be restarted. The setting of this value in conjunction with the tidy_interval may need experienced guidance and you may wish to seek ServicePower’s help in setting these values.
tidy_interval 

The time in minutes between batches starting.

The batch_size and tidy_interval allows the FRU to delete jobs at a given rate. This allows other activity to occur whilst the FRU is also performing a tidy operation.