The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
CAR provides logs that you can use to track the status of the various activities. The event log tracks events that the CAR Scheduler triggers, such as automatically generated reports, loading of CDRs, report deletions, and database purging.
The event log provides a report on the status of the activities that the CAR Scheduler controls. The event log report shows whether the tasks started, completed successfully, or are in progress.
This section describes how to generate the event log report. The event log includes a list of tasks/reports that are scheduled on a daily, weekly, or monthly basis.
This release of Cisco Unified Communications Manager introduces the Task Monitor and Database Maintenance as new features.
TaskMonitor monitors the status of other jobs and cleans up Informix Dynamic Server (IDS) memory when necessary by using the IDS command "onmode -F." DatabaseMaintenance runs the IDS-recommended optimized database maintenance "update statistics" procedures.
Task Monitor begins about 1 minute after the Scheduler starts, and 1 minute after the Scheduler repopulates the schedules every day at midnight (00.00). The Task Monitor periodically (every 5 minutes) monitors the status of all jobs for the day from the tbl_event_log with the exception of the following jobs: PopulateSchedules, TaskMonitor, DatabaseMaintenance, and DailyCdrLoad.
When a task does not start on schedule because a previous task is still running, you may see something like the following trace message:
2008-02-14 08:00:04, 602 WARN [main] services. Scheduler - runTasks(): Job [DailyCdrLoad] thread is busy, hence it will be removed from today’s schedule and not be started!”
The Scheduler gives a grace period to periodically sleep for 10 seconds and then check whether the task thread is complete. The Scheduler sleeps up to 2 minutes total. If the task thread is not complete after the 2 minutes of wait, the next task gets removed from the current schedule, and does not run until its next scheduled time.
The following table displays the list of tasks/reports and how often they are scheduled.
Task Monitor1 |
|
Database Maintenance2 |
|