Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

CDR Database Marked as Suspect

This is 1P+7S cluster

CCM: 4.0(2a)es88

OS: Win2000sr7

CDRs are inserted into a database "MindDB".

Since last 2/3 days the CDRs are not being inserted and a event viewer error message is generated as

-------------------

Error: 1105, Severity: 17, State: 2

Could not allocate space for object 'CallDetailRecordDiagnostic' in database 'CDR' because the 'PRIMARY' filegroup is full.

-------------------------

This is probably because CDR.mdf and CDR_LOG.ldf files have grown too large (9GB and 5 GB respectively).

Before we could remedy this, today morning an error message is received in event viewer

--------------------

Error: 3314, Severity: 21, State: 4

Error while undoing logged operation in database 'CDR'. Error at log record ID (431923:4347:11).

-------------------------

After the above message the system is contineously generating following events

---------------------------

Error: 9001, Severity: 21, State: 1

The log for database 'CDR' is not available.

----------------------------

In enterprise manager, when clicked on CDR database, it generated an error message, telling the database is marked as suspect by recovery.

Any ideas how to remedy this

1 REPLY
Green

Re: CDR Database Marked as Suspect

Here is a MS Article that explains how to get the database status reset.

http://support.microsoft.com/default.aspx?scid=kb;en-us;180500

In short, run this from query analyzer

use master

exec sp_resetstatus cdr

Restart SQL Server

Verify that the database is not longer marked suspect.

Then run this from query analyzer.

DBCC NEWALLOC

DBCC TEXTALL

DBCC CHECKDB

If the trans log is large, perform the

following in query analyzer.

dump tran "cdr" with no_log

dbcc shrinkdatabase (cdr)

130
Views
0
Helpful
1
Replies
CreatePlease to create content