Cisco Headend System Release 2.7 Installation Guide

Page of 252
 
Chapter 8    Identify and Correct Database Problems with the checkDB Script 
 
 
 
100 
4020695 Rev C 
Overview of the checkDB Script 
Types of Database Problems 
The following list identifies some of the potential problems that the checkDB script 
identifies: 
 
DHCT records in the DNCS database that do not have serial numbers 
Notes:   
 
DHCTs are required to have serial numbers. DHCT serial numbers are now 
used mainly with third-party applications such as the video-on-demand 
application. 
If the output of the checkDB script shows that you have DHCTs in your 
database without serial numbers, you can contact Cisco Services to assign 
serial numbers to those DHCTs. 
 
Records in various tables in the DNCS database that do not have required 
corresponding records in other tables 
Notes:   
 
Records that do not have required corresponding records in other tables are 
known as orphaned records. 
You can configure the checkDB script to automatically remove orphaned 
records from the DNCS database. 
 
DHCTs with a status of in-service that have EMMs ready to expire 
Note:  The checkDB.sh script will prompt you to either restage or delete DHCTs 
with EMMs ready to expire. 
 
Sites that are likely to experience a problem due to the DNCS generating 
duplicate subscription EMMs. (This is a very rare condition and is included in 
the checkDB utility as a precaution.) 
Notes: 
The checkDB script identifies this condition through the Highest eu_eid used 
for subscription pkgs field.  
Sites where this value exceeds 220 should report this condition to Cisco 
Services.