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. And see here for current known issues.

New Member

CDR Database Error - Error Code 10012 - CUCM 8.6.2

Hi,

we are running CUCM 8.6.2 and I get at CAR webpage the following error message and CDR data also are not written to SFTP server since 2 weeks.

Before everything was working fine. 2 weeks ago we changed the IP-address of CUCM publisher and subscriber.

CDR database error 10012.jpg

I already tried these steps but it`s not working and I still get the same error:

>>>Please verify also the status for the following services:

"Cisco SOAP - CDRonDemand Service" = active on the publisher server

"Cisco CDR Repository Manager" = active on the publisher server

"Cisco CDR Agent" = active on all the callmanager servers in your cluster.

"CAR Schedular" = active on publisher server only.

If still the same then, please try the following:

1. Disable the "CDR Enabled Flag" parameter in all the servers in your cluster.

2. Restart the "Cisco CDR Agent" service in all the servers in your cluster.

3. Restart the "Cisco CDR Repository Manager" service in the publisher server.

4. Restart the "Cisco Database Layer Monitor" service in all the servers in your cluster.

5. Enable again the "CDR Enabled Flag" parameter in all the servers in your cluster.

Can anybody help me in this issue to make CDR working again? Thanks.

BR
Michael

14 REPLIES

CDR Database Error - Error Code 10012 - CUCM 8.6.2

Hi Micheal

Please give a look to the following page

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080933fcf.shtml#error2

HTH

Regards

Carlo

Please rate all helpful posts

"The more you help the more you learn"

Please rate all helpful posts "The more you help the more you learn"
New Member

CDR Database Error - Error Code 10012 - CUCM 8.6.2

Hi Carlo,

I had already this morning before this thread a look to the link you wrote.

But everytime I run actually a SQL query against CAR database I get the following error:

Failed to get Connection.Connector(NOT CONNECTED: Driver=com.informix.jdbc.IfxDriver;)

BR

Michael

New Member

CDR Database Error - Error Code 10012 - CUCM 8.6.2

Hi,

at CDR webpage I also get the error Cisco CAR DB serice is not running.

Try to start the Cisco CAR DB service from CLI:

Service Manager is running

Cisco CAR DB[STARTING]

Cisco CAR DB[STARTING]

Cisco CAR DB[STARTING]

Cisco CAR DB[STARTING]

Component is not running

Cisco CAR DB[NOTRUNNING]

Would a restart of the publisher maybe help to solve the issue?

BR

Michael

Silver

CDR Database Error - Error Code 10012 - CUCM 8.6.2

We have the same issue after IP address changes - did you ever find a fix?

Many thanks!

Art

New Member

Art, did you find a fix?

Art, did you find a fix?

New Member

Did anyone find a fix for

Did anyone find a fix for this?

I am having a similar issue after upgrade from 8.6.2 to 10.5.2 and configuring a domain name.

Thanks. 

New Member

Does it happen all the time? 

Does it happen all the time?  I do get this error, but its only if I try to run a report against a different DID or extension immediately following a successful report. Essentially, I can log into CDR, run a report then I have to log out and log back in to do another, and so on ....and so on.... Otherwise I will get the error page every time I try to do multiple reports on unique numbers.

New Member

I get it everytime when i'm

I get it everytime when i'm searching for a particular extension.

A CDR dump does seem to work just fine and has all the correct data. 

New Member

I was able to resolve the

I was able to resolve the issue by doing the following:

1-Disable "CDR Enabled flag" Service Parameter on each server individually:                        

2-Reset these services (Individually on each server as well)        

        a. Cisco CAR Scheduler.

        b. Cisco CAR Web Agent.

       c. Cisco CDR Agent.

       d. Cisco CDR Repository Manager 

3 -Re-enable "CDR Enabled flag" Service Parameter on each server individually again.

Thanks.

New Member

It works! Many thanks. I have

It works! Many thanks. I have the same problem in CUCM 10.5.

Note: This procedure does not affect the service.

we restart the publisher and

we restart the publisher and it works fine

admin:utils service list

Requesting service status, please wait...
System SSH [STARTED]
Cluster Manager [STARTED]
Service Manager is running
Getting list of all services
>> Return code = 0
A Cisco DB[STARTED]
A Cisco DB Replicator[STARTED]
Cisco AMC Service[STARTED]
Cisco AXL Web Service[STARTED]
Cisco Audit Event Service[STARTED]
Cisco Bulk Provisioning Service[STARTED]
Cisco CAR DB[STARTED]
Cisco CAR Scheduler[STARTED]
Cisco CAR Web Service[STARTED]
Cisco CDP[STARTED]
Cisco CDP Agent[STARTED]
Cisco CDR Agent[STARTED]
Cisco CDR Repository Manager[STARTED]
Cisco CTIManager[STARTED]
Cisco CTL Provider[STARTED]
Cisco CallManager Admin[STARTED]
Cisco CallManager Cisco IP Phone Services[STARTED]
Cisco CallManager Personal Directory[STARTED]
Cisco CallManager SNMP Service[STARTED]
Cisco CallManager Serviceability[STARTED]
Cisco CallManager Serviceability RTMT[STARTED]
Cisco Certificate Authority Proxy Function[STARTED]
Cisco Certificate Change Notification[STARTED]
Cisco Certificate Expiry Monitor[STARTED]
Cisco Change Credential Application[STARTED]
Cisco DRF Local[STARTED]
Cisco DRF Master[STARTED]
Cisco Database Layer Monitor[STARTED]
Cisco Dialed Number Analyzer[STARTED]
Cisco Dialed Number Analyzer Server[STARTED]
Cisco DirSync[STARTED]
Cisco E911[STARTED]
Cisco ELM Admin[STARTED]
Cisco ELM Client Service[STARTED]
Cisco ELM DB[STARTED]
Cisco ELM Server[STARTED]
Cisco Extension Mobility[STARTED]
Cisco Extension Mobility Application[STARTED]
Cisco License Manager[STARTED]
Cisco Location Bandwidth Manager[STARTED]
Cisco Log Partition Monitoring Tool[STARTED]
Cisco RIS Data Collector[STARTED]
Cisco RTMT Reporter Servlet[STARTED]
Cisco SOAP - CDRonDemand Service[STARTED]
Cisco SOAP - CallRecord Service[STARTED]
Cisco Serviceability Reporter[STARTED]
Cisco Syslog Agent[STARTED]
Cisco Tomcat[STARTED]
Cisco Tomcat Stats Servlet[STARTED]
Cisco Trace Collection Service[STARTED]
Cisco Trace Collection Servlet[STARTED]
Cisco Trust Verification Service[STARTED]
Cisco Unified Mobile Voice Access Service[STARTED]
Cisco User Data Services[STARTED]
Cisco WebDialer Web Service[STARTED]
Host Resources Agent[STARTED]
MIB2 Agent[STARTED]
Platform Administrative Web Service[STARTED]
SNMP Master Agent[STARTED]
SOAP - Diagnostic Portal Database Service[STARTED]
SOAP -Log Collection APIs[STARTED]
SOAP -Performance Monitoring APIs[STARTED]
SOAP -Real-Time Service APIs[STARTED]
System Application Agent[STARTED]
Cisco CallManager[STOPPED] Service Not Activated
Cisco DHCP Monitor Service[STOPPED] Service Not Activated
Cisco ELM Resource API[STOPPED] Service Not Activated
Cisco Extended Functions[STOPPED] Service Not Activated
Cisco IP Manager Assistant[STOPPED] Service Not Activated
Cisco IP Voice Media Streaming App[STOPPED] Service Not Activated
Cisco Intercluster Lookup Service[STOPPED] Service Not Activated
Cisco Messaging Interface[STOPPED] Service Not Activated
Cisco TAPS Service[STOPPED] Service Not Activated
Cisco Tftp[STOPPED] Service Not Activated
Cisco UXL Web Service[STOPPED] Service Not Activated
Primary Node =true

New Member

CDR Database Error - Error Code 10012 - CUCM 8.6.2

Have you been able to resolve this issue? I am running into this on a 9.1.1.20000-5 cluster after the IP of the publisher was changed.

Thanks,

Michael

New Member

CDR Database Error - Error Code 10012 - CUCM 8.6.2

Hi,

yes we solve the problem but not with any suggestions made before.

We reinstalled the CUCM Pub after we faced these problems and used restore option using the last vaild backup.

After new installation of CUCM Pub everything is working fine.

BR

Michael

New Member

Did you end up having to

Did you end up having to reinstall for version 9? The same thing happened to me and we had changed the IP of the Publisher.

2871
Views
5
Helpful
14
Replies
CreatePlease login to create content