Major Alarm - Database status

[Benja]

Hello,
I need some assistance with Major alarm on 3300 ICP.
Database status alarm. While running DBMS full check, there is an error in the line corp_dir

View:  21  station_hunt_dat  Tuples (Max):  11264   (Current):     55           
View:  22  station_hunt_inf  Tuples (Max):    176   (Current):     11           
View:  23  corp_dir          Tuples (Max):  19999   (Current):   3685           
Next key error ***                                                             
Return Code is Success                                                         
Key is                                                                         
17005370656369616C69747920202020                                               
20202020202020373030352020202020                                               
20202020202020202020202020202020                                               
 20                                                                             
Offset is 1                                                                     
View:  24  trunk_hunt_copy   Tuples (Max):    112   (Current):      0           
View:  25  trunk_hunt_data   Tuples (Max):  19600   (Current):     63 

If I check Logs I found this one

Log Type:    Software
Log Number:    1169
Severity:    Warning
Date:    2015/Aug/11
Time:    10:32:54
Source:    Call Control - Software
Description:    DBMS (DBTAUDIT) : Verify_Corp_Dir Records should have same digit string, but do not.
Records are 2338 and 51
Module:    Main
File Name and Line Number:    log_outputs_util_en.c;1595

3300 was rebooted couple of times, but still same issue.

Thank you!

[ralph]

You have a corrupted database.
I expect that the only solution is to backup the system and then restore it.   Reboots will not help resolve this.

One thing you ~might~ be able to try is to export the telephone directory to Excel and see if you find something unusual.
If you do then see if you can find that record and delete it.
I'm not thinking that will actually work but it's a real easy thing to try.

Ralph

[mszodiac]

I've seen this same problem before, and I agree with ralph.  Do database backup and restore.