Cisco Headend System Release 2.7 Guia Da Instalação
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Run the checkDB Script
740020 Rev H
111
Analysis of checkDB Logfile
Line Numbers
Explanation
Lines 17 through 25
These lines identify 5 DHCTs with MAC address entries
in the secure_micro table, but without a required
corresponding entry in the hct_profile table. The
checkDB script therefore concludes that these are
orphaned records and recommends that they be deleted.
in the secure_micro table, but without a required
corresponding entry in the hct_profile table. The
checkDB script therefore concludes that these are
orphaned records and recommends that they be deleted.
Lines 26 and 27
These lines indicate that there are no orphaned records
in the sm_auth_profile and the sm_pkg_auth tables with
respect to the secure_micro table.
in the sm_auth_profile and the sm_pkg_auth tables with
respect to the secure_micro table.
Lines 28 through 32
These lines identify 502 DHCTs with serial number
entries in the emm table, but without a required
corresponding entry in the hct_profile table. The
checkDB script therefore recommends that they be
deleted.
entries in the emm table, but without a required
corresponding entry in the hct_profile table. The
checkDB script therefore recommends that they be
deleted.
Lines 33 and 34
These lines indicate that there are no potential error
conditions with the pdkeycertificates table.
conditions with the pdkeycertificates table.
Lines 35 through 51
These lines identify 14 DHCTs with very old EMMs. The
checkDB script prompts you to either restage or delete
them.
checkDB script prompts you to either restage or delete
them.
Line 52
Line 52 indicates that there are no DHCTs in the
database with EMMs that are in danger of expiring
database with EMMs that are in danger of expiring
Line 53
Line 53 indicates that there are no orphaned
authorization records in the database.
authorization records in the database.
Lines 54 and 55
These lines indicate that there are 3600 DHCT entries in
the hct_profile table with NULL values in the hctt_oui,
hctt_id, or hctt_revision fields. These NULL values result
from running a script for handling mismatched
hardware type errors.
the hct_profile table with NULL values in the hctt_oui,
hctt_id, or hctt_revision fields. These NULL values result
from running a script for handling mismatched
hardware type errors.
Note: When the quantity of DHCTs with NULL values
in the previously mentioned fields exceeds 1 percent of
the DHCTs in the hct_profile table, the checkDB script
notifies you.
in the previously mentioned fields exceeds 1 percent of
the DHCTs in the hct_profile table, the checkDB script
notifies you.