McDewey

In cases where there are large number of CDRs present in the billing tables and deleting the partitions does not bring the record count below the 2M or HWM limit, CAR holds at least two days data in the database. When the record count in the database reaches the 2M or HWM limit: a. CAR loader stops processing the new records. b. CAR starts purging the records from the oldest partition till the record count reaches 2M or HWM limit. If the record count does not fall below the 2M or HWM limit even after deleting the records, CAR holds at least two days records and stops the CAR loader. Also, CAR sends an e-mail notification to CAR administrator to proceed with manual purge. Following an upgrade, the Configure Automatic Database Purge > MAX DATABASE AGE parameter will be changed to one of the following: • If the MAX DATABASE AGE in the old version is between 1 and 60, it will be configured to 60 in the new version. • If the MAX DATABASE AGE in the old version is between 60 and 180, it will be configured to the same age in the new version. • If the MAX DATABASE AGE in the old version is more than 180, it will be configured to 180 in the new version. CAR System Event Log 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. Generate Event Log 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 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 1minute after the Scheduler starts, and 1minute after the Scheduler repopulates the schedules every day at midnight (00.00). The Task Monitor periodically (every 5minutes) 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: Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 46 CDR Analysis and Reporting CAR System Event Log