date-time-tz
Section: date-time
Default Value: GMT
Valid Values: Any valid Java time zone
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Specifies the time zone for the calendar. You can use any valid time zone that is supported by the version of the Java Runtime Environment (JRE) that runs the Genesys Info Mart Server. For more information about supported time zones, see the documentation about calendar time zones on the Java developer website or other public resources.
date-time-max-days-ahead
Section: date-time
Default Value: 366
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Specifies, in number of days, how far ahead the calendar dimension table will be populated. The default value specifies that the calendar dimension will be populated up to a year in advance (365 days + 1 day for leap years). Genesys does not recommend that you populate the calendar tables more than a year in advance, in case there are changes to DST or other international time standards that might invalidate the prepopulated data.
Note: Ensure that you populate the calendar far enough ahead to meet the requirements of your reporting intervals.
date-time-min-days-ahead
Section: date-time
Default Value: 183
Valid Values: Any positive integer
Changes Take Effect: At the next run of Job_MaintainGIM
Dependencies: None
Specifies, in number of days that remain in the prepopulated calendar, when the calendar table will be updated with the next batch of days ahead. The default value specifies that the maintenance job will update this calendar approximately 6 months before it expires.
Changing Calendar Dimension Values
This page describes how you can safely modify the settings that control the content of existing calendar dimension tables.
After the default or custom calendar dimension tables have been populated, you can safely change the values of the options in the [date-time] or custom [date-time-*] configuration section that control when Job_MaintainGIM populates the table with the next batch of calendar dimensions (date-time-min-days-ahead) and how far ahead the table will be populated (date-time-max-days-ahead).
However, if you want to change the values of any of the other date-time options during runtime, you must perform additional steps to avoid compromising the consistency of calendar data, which can adversely affect your reporting results. For example, if you change the time zone option (date-time-tz) without performing the additional steps, your reports might mix the results for different time zones within the same reporting interval.
The following procedure describes how to change calendar dimension tables.
Procedure: Changing calendar settings during runtime
Purpose: To change the values of the options that control population of an existing calendar dimension table without introducing inconsistencies into calendar data.Prerequisites
- If your deployment does not always use the latest Oracle Java SE platform JDK or JRE update release (which is Oracle’s preferred means of delivering timezone data updates), you have run the Java Timezone Updater Tool to update your JRE time zone data.
Steps
- If your deployment includes aggregation, stop aggregation. For information about stopping the aggregation process, see the Reporting and Analytics Aggregates User’s Guide.
- In Configuration Manager, change the settings for the date-time options in the Genesys Info Mart Application object, as required. For information about the available options and valid values, see the date-time Section in the Genesys Info Mart Configuration Options Reference.
- Manually truncate the corresponding calendar table in the Info Mart database.
- Run Job_MaintainGIM. For information about running the job manually, see Running a Job Immediately.
- If your deployment includes aggregation:
- Restart aggregation.
- Re-aggregate your data. For more information about re-aggregating data over a certain time range, see the Reporting and Analytics Aggregates User's Guide.