PDF(130.5 KB) View with Adobe Reader on a variety of devices
ePub(243.1 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(350.2 KB) View on Kindle device or Kindle app on multiple devices
Updated:July 16, 2013
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.
A debug log is usually required if you submit a service request against Cisco Service Control Application for Broadband (SCA BB) Reporter. These debug logs contain the SQL used to generate the report and any error messages that might have occurred for issues such as a report contains no data or a report contains data you did not expect. This document describes how to generate a debug log for SCA BB Reporter.
Complete these steps in order to generate a debug log for SCA BB Reporter:
Step 1. Enable the Send debug messages to log option.
In the Reporter - SCA BB Console, choose Preferences > Reporter.
The Preferences dialog box appears.
Click Configuration, and check the Send debug messages to log check box.
Step 2. Run the report that caused the issue.
Once you enable debug messages (Step 1), run the exact report with which you experienced issues in order to populate the log with the data you require.
Step 3. Access the debug log.
In the Reporter - SCA BB Console, choose Help > About SCA BB Console.
The About SCA BB Console dialog box appears.
In the About SCA BB Console dialog box, click Configuration Details.
The Configuration Details dialog box appears.
In the Configuration Details dialog box, click View Error Log.
The error log is opened in your default web browser.
Navigate to the end of the file and scroll up in order to locate the data that relates to the report. You should notice the SQL command used to generate the report and use this entry in order to find the data that relates to your request.
Note: The entire contents of this file should be uploaded to any TAC service case related to this issue.