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

DMA erreur message (CCM4.2(3)srb4b---> CUCM7.1(5)

Hi,

Can you help me de fix this DMA msg error.

Thanks in advance

Racim

DATA PROCESSING TESTS REVEALED AN ISSUE WHICH GENERATED THE FOLLOWING EVENT: 
The error number is:  [-691]
The error message is:  [-691 Missing key in referenced table for referential constraint
]
The following additional event information is available: 
  This record was not processed because another record it needs,
  (see reference name listed below), is missing.  This likely may be due to a previous error
  already reported in the log above, or the result of Directory Services Export issues
  reported separately, or due to missing Product, Locale, or other add-on definition CSV
  files that should exist on the source system but do not.
  SUGGESTED ACTION:  Resolve all prior reported issues.  If none, look at the Suspected Field,
  if listed, for an indication of what data reference could not be resolved.  Some hints: 
   - if ...DirGroup related, check for a Directory Export failure
   - if ...Locale related, check for a missing Locale Plug-In
  Re-execute DMA when all other issues are addressed.
Suspected Field/Item Is [DMABack_Admin.tk_troubleshootingtrace_tkservice]
TABLE NAME IS [troubleshootingtrace ]
fkprocessnode             '6cee9db2-27fb-4c7d-9530-dfec38d30fe1'
  pkid                     '3a31b103-e0d6-4ab3-94a1-f7d3cf5e339e'
  tkservice                6                       
  tracelevel               1                       
  usercategories           1                       
  enable                   'T'                     
  numfiles                 250                     
  numlines                 10000                   
  numminutes               1440                    
  includenondevicetraces   'F'                     
  usexml                   'F'                     
  devicetypemonitorflag    'T'                     
  devicenamemonitorflag    'F'                     
  filetraceflag            'T'                     
  outputdebugstringflag    'F'                     
  maxfilesize               1000                  

4 REPLIES

Re: DMA erreur message (CCM4.2(3)srb4b---> CUCM7.1(5)

Did you run the Migration Utility to validate the database before you ran DMA?  It looks like you've got something slightly scrambled in there.  This is common if a customer enabled MLA, added users to groups, and then deleted the phones the users had previously been associated with.  That problem is very recognizable since any attempt to open any of the DMA groups affected will result in an error.

New Member

Re: DMA erreur message (CCM4.2(3)sr4b---> CUCM7.1(5)

Yes I did, curiously I ran a second DMA and I still have the previous error but the DMA status was : (The results are : Export - Successful. Validation - Successful with warning(s).)

Re: DMA erreur message (CCM4.2(3)sr4b---> CUCM7.1(5)

Ok. You have something wrong in the database, and it's more than you can go through on a board posting. Get TAC involved to help you out. They have folks dedicated to this type issue.

Cliff

NOTICE OF CONFIDENTIALITY:

The information contained in this email transmission is confidential information which may contain information that is legally privileged and prohibited from disclosure under applicable law or by contractual agreement. The information is intended solely for the use of the individual or entity named above.

If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking of any action in reliance on the contents of this email transmission is strictly prohibited.

If you have received this email transmission in error, please notify us immediately by telephone to arrange for the return of the original transmission to us.

New Member

Re: DMA erreur message (CCM4.2(3)sr4b---> CUCM7.1(5)

No errors atfer reseting trace configuration setting.

Regard,

Racim

383
Views
0
Helpful
4
Replies
CreatePlease to create content