DMA Warning

Unanswered Question
Feb 13th, 2010

I have a CM server running version 4.1(3), and going to migrate to 6.1(4). I finished running DMA without "Errors" but I got many " Warnings" from the file "DMAWarnings.log".  Does anyone knows the message like below.

Does it cause any impact to the overall DMA files, or I can ignore this warning and keeping upgrading to CM 6 ??

Thanks

Row: 4753 SQL error: -391(extensionmobilitydynamic.pkid)
   Error executing "update Device set Name='SEP00156316CD01' where pkid='be8742b1-6a64-45eb-b8ba-d9a1f9650a69'": [Informix][Informix ODBC Driver][Informix]Unspecified System Error =  -391. sqlerrm(extensionmobilitydynamic.pkid)
      pkid                          be8742b1-6a64-45eb-b8ba-d9a1f9650a69     NOT MODIFIABLE
      Name                          SEP00156316CD01
      Description                  
      tkModel                       30006     NOT MODIFIABLE
      tkDeviceProtocol              0
      tkProtocolSide                1
      SpecialLoadInformation       
      fkDevicePool                  9cd97f17-2d64-48f2-ae2f-a6ffd191f3d7
      fkPhoneTemplate               404d3a28-498c-4e1d-9057-2714edf43b7b
      fkCallingSearchSpace          b634d3fe-2b54-4dbe-bb4f-13ef2ba1d348
      CtiID                         4753     NOT MODIFIABLE
      tkClass                       1
      fkProcessNode                      NOT MODIFIABLE
      DefaultDTMFCapability         0
      fkLocation                    51471e48-916c-46a0-bb0f-38e6f8044dcd
      tkProduct                     30018
      DialPlanWizardGenID          
      DeviceLevelTraceFlag          false
      fkEndUser                     a7e6ed8f-35dc-4a55-b457-1991910fe926
      AllowHotelingFlag             true
      tkDeviceProfile               0
      ikDevice_DefaultProfile       8a8f6414-218e-4373-82d7-cc8bce559651
      fkMediaResourceList          
      UserHoldMOHAudioSourceID     
      NetworkHoldMOHAudioSourceID    
      Unit                          0
      SubUnit                       0     NOT MODIFIABLE
      XML                            <disableSpeaker>false</disableSpeaker><disableSpeakerAndHeadset>false</disableSpeakerAndHeadset><forwardingDelay>1</forwardingDelay><pcPort>0</pcPort><settingsAccess>2</settingsAccess><garp>1</garp><voiceVlanAccess>1</voiceVlanAccess><videoCapability>0</videoCapability><autoSelectLineEnable>1</autoSelectLineEnable><webAccess>1</webAccess><daysDisplayNotActive>1</daysDisplayNotActive><displayOnTime>07:30</displayOnTime><displayOnDuration>10:30</displayOnDuration><displayIdleTimeout>01:00</displayIdleTimeout><spanToPCPort>1</spanToPCPort>
      tkCountry                    
      tkUserLocale                 
      tkProduct_Base               
      fkCallingSearchSpace_AAR     
      fkAARNeighborhood            
      fkSoftkeyTemplate             06002195-a61b-4a4a-82da-0f6ae9af1e7e
      retryVideoCallAsAudio         true
      RouteListEnabled              false
      fkCallManagerGroup           
      tkStatus_MLPPIndicationStatus     2
      tkPreemption                  2
      tkStatus_BuiltInBridge        2
      mTPRequired                   false
      tkQSIG                        4     NOT MODIFIABLE
      tkPacketCaptureMode           0
      PacketCaptureDuration         60
      AuthenticationString         
      tkCertificateStatus           1
      UpgradeFinishTime             2005:11:26:17
      fkMlppDomain                 
      TransmitUTF8                  false
      ignorePI                      false
      tkNetworkLocation             0
      V150ModemRelayCapable         false
      tkCertificateOperation        1
      fkSecurityProfile             783651e3-dc4a-4fd1-823f-50aeca13c8fe
      fkDialRules                  
      fkCallingSearchspace_reroute    
      fkCallingSearchspace_refer    
      unattended_port               false
      tkDTMFSignaling               1
      requireDTMFReception          false
      publicKey                    
      fkSIPProfile                 
      RFC2833Disabled               false
      AllowCTIControlFlag           true
      DateTimeInserted             
      sshpassword                  
      sshuserID                    
      fkCallingSearchspace_restrict    
      fkMatrix_Presence             ad243d17-98b4-4118-8feb-5ff2e1b781ac
      fkCommonPhoneConfig           ac243d17-98b4-4118-8feb-5ff2e1b781ac
      tkkeyauthority                0
      tkSIPCodec_MTPPreferredOrigCodec     1
      md5hash                      
      SRTPAllowed                   false
      isStandard                    false     NOT MODIFIABLE
      resetToggle                   false
      tkReset                       2
      VersionStamp                  1266074560-a895ea2b-9031-4cdc-9be4-b641a8d933e7
      fkCommonDeviceConfig          b256171c-dc45-4f90-a82e-c4fdee89da7d
      huntListForVM                 false
      remoteDevice                  false
      tkStatus_DeviceMobilityMode     2
      DNDTimeout                    0
      tkDNDOption                   0
      tkRingSetting_DND            
      IsDualMode                    false     NOT MODIFIABLE
      fkCallingSearchspace_CgPNTransform    
      fkEndUser_Mobility           
      tkOutboundCallRollover        0
      tkPhonePersonalization        3
      tkStatus_joinacrosslines      2
      tkBarge                       3
      ikDevice_PrimaryPhone        
      tkStatus_AudibleAlertingIdle     2
      tkStatus_AudibleAlertingBusy     2
      IsActive                      true
      tkStatus_AlwaysUsePrimeLine     2
      tkStatus_AlwaysUsePrimeLineForVM     2

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Tommer Catlin Tue, 02/16/2010 - 08:47

Hard to say, but its pointing to this device that has Extension Mobility.  It this device does not use EM, then its safe to say you can ignore.  It may have been not setup correctly to use EM.  Or the devive was logged in to EM when you ran EM.

My advice with any DMA CUCM upgrade is to run the DMA, grab the file and build it in the lab.  The biggest hurdle you have with any DMA is how the import from the TAR file goes during the 6.x or 7.x installation.  If it fails during install, then at least you know ahead of time. 

I like to do this:

- Build out (2) phones in 4.x.

- Register the (2) phones in 4.x

- DMA the 4.x server

- Build the 6.x/7/x CUCM server with the DMA file in the lab

- Take the (2) phones from 4.x and register them with new 6/7.x server. (Use manual IP config on the phones)

- test calls between the phones, CUCM active/standy, etc.

If all works, you are set to upgrade/migrate.

anthony.lo Wed, 02/17/2010 - 01:35

I can fix the problem by installing the CDR Analysis and Reporting tool before running DMA. I guess it is somehow related to the CDR reports. Anyways, thanks so much for your suggestions.

Actions

This Discussion