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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

SQL Data

For no reason ,CDR records have stopped being written to the SQL CDR DB. there are no errors replication if ok, any suggestions?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: SQL Data

>>>Verify that "Cisco CDR Insert" and "Cisco CDR Analysis and

Reporting Scheduler" services are running ONLY in the Publisher

Call Manager:

in your publisher callmanager server, go to start > programs >

administration tools > services > verify the status for services

"Cisco CDR Insert" and "Cisco CDR Analysis and Reporting Scheduler".

If they are not "started", please restart them (just right-click

on the service and select "restart").

If "Cisco CDR Insert" and "Cisco CDR Analysis and Reporting Scheduler"

are running also in the subscriber servers, please stop them.

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

>>>Verify service parameters in callmanager servers (publisher

and subscriber).

--go to ccm admin > service > service parameters > select a callmanager

server from the drop-down list > at "service" please select "Cisco

CallManager" > click on "advanced" > verify that the following

parameters are set to the correct values:

CDR Enabled Flag = True

CDR Log Calls with Zero Duration Flag = True

Call Diagnostics Enabled = True

***Repeat the same procedure for all callmanager servers in your

cluster***

--Now go to ccm admin > service > service parameters > select a

callmanager server from the drop-down list > at "service" please

select "Cisco Data Base Layer Monitor" > verify that the following

parameter is set to the correct value:

Max CDR Records = 1500000

***Repeat the same procedure for all callmanager servers in your

cluster***

--Now go to ccm admin > system > enterprise parameters > verify that

the following parameters are set to the correct values:

CDR File Time Interval (min) = 1

CDR Format = CDRs will be inserted into database

CDR UNC Path = \\\CDR

Local CDR Path = C:\Program Files\Cisco\CallDetail

***Repeat the same procedure for all callmanager servers in your

cluster***

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

>>>Please go to start > programs > administration tools > services and

restart the following services after hours:

1) Restart service "Cisco database Layer Monitor" on

publisher and subscriber servers.

2) Restart service "Cisco CDR Insert" on the publisher server.

3) Restart service "Cisco CDR Analysis and Reporting Scheduler"

on the publisher server.

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

>>>Run SQL querys:

In your publisher server, go to start > programs > SQL Server > Query

Analyzer > SQL Server: (local) ; Select "windows authentication" ;

click on "OK" > select the "ART" database from the drop-down menu. Run

the following queries (just copy and paste the following in the main

window, then click on the "execute query" icon):

delete from Tbl_Load_History

delete from Tbl_Dump_PkID

delete from Tbl_Error_Id_Map

delete from Tbl_Billing_Data

delete from Tbl_Billing_Error

delete from Tbl_Dump_CallDetailRecord

delete from Tbl_Dump_CallDetailRecordDiagnostic

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

2 REPLIES

Re: SQL Data

>>>Verify that "Cisco CDR Insert" and "Cisco CDR Analysis and

Reporting Scheduler" services are running ONLY in the Publisher

Call Manager:

in your publisher callmanager server, go to start > programs >

administration tools > services > verify the status for services

"Cisco CDR Insert" and "Cisco CDR Analysis and Reporting Scheduler".

If they are not "started", please restart them (just right-click

on the service and select "restart").

If "Cisco CDR Insert" and "Cisco CDR Analysis and Reporting Scheduler"

are running also in the subscriber servers, please stop them.

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

>>>Verify service parameters in callmanager servers (publisher

and subscriber).

--go to ccm admin > service > service parameters > select a callmanager

server from the drop-down list > at "service" please select "Cisco

CallManager" > click on "advanced" > verify that the following

parameters are set to the correct values:

CDR Enabled Flag = True

CDR Log Calls with Zero Duration Flag = True

Call Diagnostics Enabled = True

***Repeat the same procedure for all callmanager servers in your

cluster***

--Now go to ccm admin > service > service parameters > select a

callmanager server from the drop-down list > at "service" please

select "Cisco Data Base Layer Monitor" > verify that the following

parameter is set to the correct value:

Max CDR Records = 1500000

***Repeat the same procedure for all callmanager servers in your

cluster***

--Now go to ccm admin > system > enterprise parameters > verify that

the following parameters are set to the correct values:

CDR File Time Interval (min) = 1

CDR Format = CDRs will be inserted into database

CDR UNC Path = \\\CDR

Local CDR Path = C:\Program Files\Cisco\CallDetail

***Repeat the same procedure for all callmanager servers in your

cluster***

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

>>>Please go to start > programs > administration tools > services and

restart the following services after hours:

1) Restart service "Cisco database Layer Monitor" on

publisher and subscriber servers.

2) Restart service "Cisco CDR Insert" on the publisher server.

3) Restart service "Cisco CDR Analysis and Reporting Scheduler"

on the publisher server.

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

>>>Run SQL querys:

In your publisher server, go to start > programs > SQL Server > Query

Analyzer > SQL Server: (local) ; Select "windows authentication" ;

click on "OK" > select the "ART" database from the drop-down menu. Run

the following queries (just copy and paste the following in the main

window, then click on the "execute query" icon):

delete from Tbl_Load_History

delete from Tbl_Dump_PkID

delete from Tbl_Error_Id_Map

delete from Tbl_Billing_Data

delete from Tbl_Billing_Error

delete from Tbl_Dump_CallDetailRecord

delete from Tbl_Dump_CallDetailRecordDiagnostic

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

New Member

Re: SQL Data

that did the trick

thanks

89
Views
0
Helpful
2
Replies