Cisco Agent Desktop

RASCAL Database Replication Validation

Document ID: 116245

Updated: Jul 31, 2013

Contributed by Kabeer Noorudeen, Linda Mordosky, and Anuj Bhatia, Cisco TAC Engineers.



This document describes how to quickly validate that the RASCAL database on Cisco Agent Desktop replicates. 



Cisco recommends that you have knowledge of these topics:

  • Cisco Agent Desktop (CAD)
  • Microsoft Structured Query Language (SQL) Finesse Server

Components Used

This document is not restricted to specific software and hardware versions.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Validate the RASCAL Database on the CAD

In order to validate the RASCAL database on the CAD, complete these steps:

  1. Check for the existence of craDistribution under System Databases.
  2. Check for a Local Publication on the A Side (publisher).
  3. Check for a Local Subscription on the B Side (subscriber).

Once replication is enabled, validate the SQL jobs in the SQL Agent on the master side.

In the category column, the REPL-Snapshot job creates an image of the publisher database and pushes it over to the subscriber database. The REPL-Merge job continues to replicate the data between publisher and subscriber after the initial data push. 

Note: The Status of the REPL-Merge should always be "Executing." The number of jobs varies according to the version of CAD used.

Once complete, compare the database to see if data is replicated.

Data written and used by the RASCAL service is contained within three tables:

  • FCRasCallLogWeek
  • FCRasRecordLog
  • FCRasStateLogToday

Right-Click on either or both of the FCRasCallLogWeek / FCRasStateLogToday tables, and select Properties.

Make note of the amount of records indicated in the Row count field for the selected table or tables. Then, view the Properties of the same table from the other database. It is not uncommon for the numbers between sides to be off slightly, particularly in large and busy call centers. However, if one side shows several thousand records, and the other shows zero, there is a problem.

Updated: Jul 31, 2013
Document ID: 116245