Contents
- Release Notes for Cisco Service Control Collection Manager, Release 5.1.0
- Introduction
- Accessing Cisco Service Control Documentation
- Supported Platforms
- Supported External Databases
- Upgrading Cisco Service Control Manager
- Release 5.1.0 New Features
- Changes in Scripts, Tables, and RDRs
- Caveats
- Resolved Caveats in Release 5.1.0
- Open Caveats in Release 5.1.0
- Related Documentation
- Obtaining Documentation and Submitting a Service Request
First Published: February 18, 2015
Release Notes for Cisco Service Control Collection Manager, Release 5.1.0
Note
This document supports all 5.1.0 releases.
Introduction
The Cisco Service Control Collection Manager is an implementation of RDR-collection software. The software receives raw data-records (RDRs) from Cisco SCE devices, and performs pre-aggregation and persistency into a database or text-files in CSV format.
This document outlines the new features and states known caveats.
For a list of the caveats that apply to Cisco Service Control Collection Manager, Release 5.1.0, see the Caveats.
Accessing Cisco Service Control Documentation
To access the online Cisco Service Control documentation site, do the following:
On cisco.com, go to the following page: http://www.cisco.com/web/psa/products/index.html
From the Select a category list, select Service Exchange.
From the Select a subcategory list, select the desired Cisco Service Control category.
From the Select a product list, select the desired Cisco Service Control product.
Supported Platforms
The Cisco Service Control Collection Manager and its database are software components that run on a server platform. They can be installed on any of the following configurations:
Intel machine (64-bit) running 64-bit version of Red Hat Enterprise Linux 5.x, 64-bit versions of Red Hat Enterprise Linux 6.x (6.0 to 6.3)
Intel machine (64-bit) running 64-bit versions of CentOS. (Requires Cisco Service Control Collection Manager version 3.6.5 or higher.)
Cisco Unified Computing System (UCS) server model R210-2121605 with a Intel(R) Xeon(R) X5570 2.93 GHz CPU with 8 Cores (minimum memory 4 GB).
Intel machine (64-bit) running VMware Server or VMware ESX VMware-VMvisor-Installer-4.0.0-164009.x86_64.iso.
All configurations use a 32-bit Java Virtual Machine (JVM).
Caution
The Cisco Service Control Collection Manager must run on its own server platform. It cannot run on the same machine as the Cisco Subscriber Manager or other applications.
Note
You can find more operating system specific information for using the Cisco Service Control Collection Manager with the Cisco Service Control Management Suite in the Cisco Service Control Management Suite Collection Manager User Guide.
Upgrading Cisco Service Control Manager
For upgrade information, see the Cisco Service Control Manager Quick Start Guide at:http://www.cisco.com/c/en/us/support/service-exchange/service-control-collection-manager/products-installation-guides-list.html
Release 5.1.0 New Features
Changes in Scripts, Tables, and RDRs
Release 5.1.0 Table Changes
No new tables are added in 5.1.0 release.
List of tables updated for this release:
RPT_TOP_VIDEO_DOMAINS
RPT_TOP_VIDEO_HOSTS
RPT_VIDEO_RESOLUTION
RPT_VIDEO_DURATION
RPT_VIDEO_BITRATE
RPT_VIDEO_QOE
RPT_TOP_DEVICE_TYPE
RPT_TOP_USER_LOCATION
RPT_TOP_APN
RPT_TOP_NETWORK_TYPE
RPT_TOP_SGSN
RPT_TOP_MEID
RPT_TOP_HOME_AGENT
RPT_TOP_PCF
RPT_DEVICE_COUNT
RPT_TOP_HTTP_DOMAINS
RPT_TOP_HTTP_HOST
Caveats
The following sections list the resolved and open caveats for the specific releases. A resolved caveat is one fixed in the listed release. An open caveat is one that exists in the listed release.
Open Caveats in Release 5.1.0
- CSCul28854
Mysql 5.6 and later version tables are not dropped while Collection Manager is running with MySQL database.
Workaround:
- CSCuo34346
When the Oracle Scheduler is disabled, dbms_scheduler fails after the creation of the partitions.
Workaround:
Oracle Scheduler(DBMS_JOB) must be enabled
Stop CM
Login to 'sqlplus' as 'pqb_admin'
Example: [oracle@localhost ~]$ sqlplus pqb_admin
Run the following SQL query:SELECT 'EXEC DBMS_JOB.RUN(' || JOB || ')' RUN FROM USER_JOBS WHERE WHAT LIKE 'P_MANAGE_PARTITION%'Example:SQL> SELECT 'EXEC DBMS_JOB.RUN(' || JOB || ')' RUN FROM USER_JOBS WHERE WHAT LIKE 'P_MANAGE_PARTITION%'; RUN ----------------------------------------------------------- EXEC DBMS_JOB.RUN(567) EXEC DBMS_JOB.RUN(568) EXEC DBMS_JOB.RUN(569) EXEC DBMS_JOB.RUN(570) EXEC DBMS_JOB.RUN(571) EXEC DBMS_JOB.RUN(565) EXEC DBMS_JOB.RUN(566) 7 rows selected.Execute the result as command in the 'sqlplus' prompt
Example:SQL> EXEC DBMS_JOB.RUN(567) PL/SQL procedure successfully completed. SQL> EXEC DBMS_JOB.RUN(568) PL/SQL procedure successfully completed. SQL> EXEC DBMS_JOB.RUN(569) PL/SQL procedure successfully completed. SQL> EXEC DBMS_JOB.RUN(570) PL/SQL procedure successfully completed. SQL> EXEC DBMS_JOB.RUN(571) PL/SQL procedure successfully completed. SQL> EXEC DBMS_JOB.RUN(565) PL/SQL procedure successfully completed. SQL> EXEC DBMS_JOB.RUN(566) PL/SQL procedure successfully completed.Start CM
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation, at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.
Copyright © 2015, Cisco Systems, Inc. All rights reserved.