01-07-2011 03:09 AM - edited 03-16-2019 02:44 AM
Hi
I was hoping someone here could point me in the right direction, we're trying to upgrade from 4.2 to 7.1.5, unfortunately whenever we try to run the DMA we get the error
[10:33:11 AM] Beginning Cisco CallManager export from xx.xx.xx.xx. (IP removed)
[10:33:11 AM] DMA does not export subscriber node data.
[10:33:11 AM] Failed to export Cisco CallManager data.
[10:33:11 AM] Failed to export Cisco CallManager data.
[10:33:11 AM] Export information file(s) not saved, due to unsuccessful export.
the DMA trace log errors out at this point:
[10:33:11 AM] Exiting function modSQLGetDb with return value = CCM0300
[10:33:11 AM] Inside Function modSQLCheckSubscription
[10:33:11 AM] Extracting subscription information from Ccm0300.
[10:33:11 AM] modSQLCheckSubscription=Subscriber
[10:33:11 AM] Inside function modOuputStatusHtmlStr
[10:33:11 AM] Exit function modOuputStatusHtmlStr
[10:33:11 AM] DMA does not export subscriber node data.
[10:33:11 AM] Inside function modOuputStatusHtmlStr
[10:33:11 AM] Exit function modOuputStatusHtmlStr
[10:33:11 AM] Failed to export Cisco CallManager data.
[10:33:11 AM] Inside function modTraceDMAFrameWorkLog
[10:33:11 AM] Exit function modTraceDMAFrameWorkLog
[10:33:11 AM] original DBConnection0 = DSN=CiscoCallManager;SERVER=UKCCM01;DA-
TABASE=CCM0300;Trusted_Connection=yes
[10:33:11 AM] modBackupCCM = Failure
[10:33:11 AM] Inside function modOuputStatusHtmlStr
[10:33:11 AM] Exit function modOuputStatusHtmlStr
[10:33:11 AM] Failed to export Cisco CallManager data.
[10:33:11 AM] Error in modBackupCCM: 0
[10:33:11 AM] False
[10:33:11 AM] Inside function modSaveSettings
[10:33:11 AM] Exit function modSaveSettings
[10:33:11 AM] Inside function modOuputStatusHtmlStr
[10:33:11 AM] Exit function modOuputStatusHtmlStr
[10:33:11 AM] Inside function modOuputStatusHtmlStr
[10:33:11 AM] Exit function modOuputStatusHtmlStr
[10:33:11 AM] Export information file(s) not saved, due to unsuccessful expor-
If anyone could give me any pointers I'd be really grateful.
Thanks
Gareth
01-07-2011 03:52 AM
This can be due to a database replication issue.
Try to check the replication with DBL Helper.
Here is the link:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801e7ddf.shtml
Pierre.
01-07-2011 04:20 AM
Thanks Pierre
Just an FYI we ran the Update assistant and recieved the following success notifications, although the DMA still fails
Validation successful.
Cisco Unified CallManager Upgrade Utility, running on Cisco Unified CallManager 4.2(3) Publisher UKCCM01 (xx.xx.xx.xx), has completed. You may now upgrade Cisco Unified CallManager.
To exit Cisco Unified CallManager Upgrade Utility, click Finish.
Cisco Systems recommends you obtain the latest backup utility from CCO and back up the CallManager data.
Cisco Unified CallManager Upgrade Utility has created a log file for each check, as well as this Summary.html report, in the following directory.
C:\Program Files\Common Files\Cisco\Logs\UPGRADEASST-01-07-2011_09.45.28
Validation Checklist
Software Version Validation: Validation successful.
Database Location Setting Validation: Validation successful.
DC Directory Health Check: Validation successful.
Domain Validation: Validation successful.
Security Settings Validation: Validation successful.
Cisco Unified CallManager Database Replication Status: Validation successful.
Resource Validation: Validation successful.
Hardware Validation: Validation successful.
I am busy running the DBLHelper reinitialise process now, hopefully this sorts it out (although it's been running for 2+ hours now on a 54mb database)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide