Table Of Contents
Release Notes for Data Migration Assistant (DMA) Release 6.1(1a)
Contents
Introduction
New and Changed Information for Data Migration Assistant 6.1(1a)
New and Changed Information for Data Migration Assistant 6.1(1)
Export and Validation Errors
Expanded Explanations for DMA Errors
Directory Message Improvements
Database Message Improvements
Examples of the Most Commonly Seen Error Messages
Location of Logs
Consolidated Log Information
DMA TAR File Size Valiation
Menu Option Changes
DMA Provides More Feedback When Validation Fails
Name of the Shortcut That Is Used to Launch DMA Changed
Caveats
Caveats That Are Resolved in Data Migration Assistant 6.1(1a)
Caveats That Are Resolved in Data Migration Assistant 6.1(1)
Resolved Caveats
UsingBug Toolkit
Open Caveats
Obtaining Documentation and Submitting a Service Request
Cisco Product Security Overview
Release Notes for Data Migration Assistant (DMA) Release 6.1(1a)
Updated February 19, 2008
This document includes the information that comprised the Release Notes for Data Migration Assistant (DMA) Release 6.1(1). Table 1 displays additions and updates that were made to the document specifically for DMA 6.1(1a).
Table 1 Information Added or Updated
|
Date
|
Change
|
February 8, 2008 |
Under New and Changed Information for DMA 6.1(1a), added the "Export and Validation Errors" section and "Expanded Explanations for DMA Errors" section |
|
February 8, 2008 |
Under Caveats, added "Caveats That Are Resolved in Data Migration Assistant 6.1(1a)" section. Updated the "Introduction" section |
|
|
February 15, 2008 |
Under Caveats, updated Table 3 |
February 19, 2008 |
Under "Introduction" section added pertinent information. Under New and Changed Information for DMA 6.1(1a), added "Database Message Improvements" section. |
February 25, 2008 |
Under Location of Logs, added "Infrequently used Intermediate Result runtime trace files that are stored at C:\Program Files\Cisco\Trace\DBL and C:\Install\DBInstall" section |
Contents
These release notes discuss the following topics:
•
Introduction
•New and Changed Information for Data Migration Assistant 6.1(1a)
•New and Changed Information for Data Migration Assistant 6.1(1)
•Caveats
•Obtaining Documentation and Submitting a Service Request
•Cisco Product Security Overview
Introduction
Note Cisco Unified CallManager 4.1(3) and 4.2(3) run in a Windows environment, and Cisco Unified Communications 6.0(1a) and 6.1(1a) run in a Linux environment.
Data Migration Assistant (DMA) Release 6.1(1a) assists you with the first step in migrating date from supported Cisco Unified CallManager 4.x releases to Cisco Unified Communications Manager 6.1(1a) by exporting Cisco Unified CallManager 4.x data in a format that Cisco Unified Communications Manager 6.1(1a) can read.
DMA exports Windows-based data to a format that Cisco Unified Communications Manager 6.0(1a) or 6.1(1a) can import. The Cisco Unified Communications Manager 6.0(1a) or 6.1(1a) installation process converts the exported data as needed for Cisco Unified Communications Manager 6.0(1a) or 6.1(1a) , which completes the data migration.
DMA also assists the migration of Cisco Emergency Responder(CER) 1.3.x to 2.0(x).
DMA saves the data that it exports in a tape archive (tar) file in a location that you specify.
In addition to creating an export, DMA also performs a set of migration compatibility tests (data validation) on the exported Unified CM 4.x data
•If DMA discovers issues, either in the export itself, or in the data validation, then DMA may report some type of "Failure." Do not consider such a message alarming.
•Even when DMA completes successfully, but especially if any "Error" or "Warning" occurs, the user should examine the generated messages. These messages may be
–Simply information about auto-data-correction that will be performed in the migration.
–Alerts to let you know the problems that DMA encountered as it attempted to check the data.
Generally, these problems require user expertise to determine how best to alter the data to remove the migration incompatibility.
Note You must install and run DMA Release 6.1(1a) on the Cisco Unified CallManager publisher server before you upgrade to Cisco Unified Communications Manager 6.1(1a). If you make any configuration changes to Cisco Unified Communications Manager after you run DMA, the system does not retain these changes when you upgrade.
Note Do not consider the DMA Export a substitute for a system backup. You cannot use it to restore your Cisco Unified Communications Manager system in the unlikely event that you are unable to complete your upgrade.
New and Changed Information for Data Migration Assistant 6.1(1a)
The following sections contain information that is new or changed for this release of Data Migration Assistant:
•Export and Validation Errors
•Expanded Explanations for DMA Errors
•Database Message Improvements
New and Changed Information for Data Migration Assistant 6.1(1)
The following sections contain information that is new or changed for release 6.1(1) of Data Migration Assistant:
•Location of Logs
•Consolidated Log Information
•DMA TAR File Size Valiation
•Menu Option Changes
•DMA Provides More Feedback When Validation Fails
•Name of the Shortcut That Is Used to Launch DMA Changed
Export and Validation Errors
During export and validation phases, the DMA framework launches processes to invoke underlying components .exe files to export or validate the Cisco Unified Communications Manager database, directory, CAR or CER data. The system reports problems that are detected by or that occur in any processing of these components. If the problems are incompatible with performing further DMA operations, the problems get reported to the DMA framework. This enables the DMA framework to report the location of the problem more precisely and to return control to the user more promptly, so the issue may be investigated and corrected. \
Expanded Explanations for DMA Errors
Note The term "DMA Errors" refers to a number of types of user messages. In some cases, these messages do in fact reflect errors in DMA program framework or component execution. Such errors can result from installation, setup, environmental, or other special circumstances. They often comprise part of a DMA execution in which DMA operated correctly, but it identified issues in the underlying directory or in Unified CM 4.x data that the user must address.
Logs include expanded explanations for some DMA errors. The resulting error messages now include the device name (name and type)/userID, error/issue, and action that is required to clear the error. This information gives you a better understanding of what caused the error and how you can resolve it.
**********************************************************
Error: Failed to backup DCD.
Failed to execute command 'dcbckdib backup C:\DMA\DirExport\Output\dbinstalldir' which
backups the directory data
Condition: Failed to execute "dcbckdib backup" command
Solution: Verify that the DCD service is running. If yes, please backup the directory
manually before upgrade using the command "dcbckdib backup <dir>"
**********************************************************
Directory Message Improvements
Table 2 comprises the improvements that have been made to user-viewed messages.
Table 2 Directory Message Improvements
|
Old Message
|
Condition
|
Changed Message
|
Solution
|
Locale mapping not found for $singleValue. User=$userKey |
The locale that is present in the directory for the user is not available in the database. |
No change. |
Verify that the locale mapped for this user is present and is a valid locale and is available the database. |
IPMA: User PKID not found for IPMA-Assist=$ipmaAAValue. IPMA admin=$userKey |
Either the user does not exist in the directory or has been tagged invalid. |
IPMA-Assist=$ipmaAAValue for user=$userKey" not found. Invalid user. |
Verify that the user exists in the directory and is a valid Cisco Unified Communications Manager user; that is, User with profiles. |
IPMA: User PKID not found for IPMA-Assist=$readLine. IPMA-Admin=$userKey, TxtFile=$txtFileURL |
Either the user does not exist in the directory or has been tagged invalid. |
IPMA-Assist=$readLine for user=$userKey not found in TxtFile=$txtFileURL. Invalid user. |
Verify that the user exists in the directory and is a valid Cisco Unified Communications Manager user; that is, User with profiles. |
PKID not found for member $grpMemValue, GroupName=$grpNameKey |
Either the user does not exist in the directory or has been tagged invalid. |
Member = $grpMemValue with GroupName=$grpNameKey not found. Invalid user. |
Verify that the user exists in the directory and is a valid Cisco Unified Communications Manager user; that is, User with profiles. |
PKID not found for member $memberName, GroupName=$grpNameKey |
Either the user does not exist in the directory or has been tagged invalid. |
Member = $grpMemValue with GroupName=$grpNameKey not found. Invalid user. |
Verify that the user exists in the directory and is a valid Cisco Unified Communications Manager user; that is, User with profiles. |
Default end user group $ccmEndUserGroupName not found in the list of default groups |
End user group was not available in the default migration group.s |
No change. |
Contact TAC. |
PersonalAddressBook: EndUser PKID not found for userName = $pabUserName, PAB-DN=$pabDN |
Either the user does not exist in the directory or has been tagged invalid. |
PersonalAddressBook: EndUser $pabUserName not found. Invalid user. PAB-DN=$pabDN |
Verify that the user exists in the directory and is a valid Cisco Unified Communications Manager user; that is, User with profiles. |
PersonalAddressBook: $pabUserName has origNickname greater than 50 characters long. $origNickname |
PersonalAddressBook: PAB user has nickname that is greater than 50 characters long. |
No change. |
Change the nickname to less than 50 characters; else the nickname will be changed during migration. |
PersonalPhoneBook: EndUser not found for $pabFastDialUserName |
Either the user does not exist in the directory or has been tagged invalid. |
No change. |
Verify that the user exists in the directory and is a valid Cisco Unified Communications Manager user; that is, User with profiles. |
PersonalPhoneBook: for user $pabFastDialUserName, contact=$pabContact has personalFastDialIndex beyond 0 to 500 range. Ignoring this contact |
The fast dial index goes beyond 500 range. |
Personal Fast Dial Index for user $pabFastDialUserName, contact $pabContact is beyond 0 to 500 range. Ignoring the user |
Modify the index to a range of 0-500. |
PKID not found in database for Device or DeviceProfile=$devValue for user=$userKeyVal |
The device that is found in the directory does not exist in the database. |
Device or DeviceProfile=$devValue for user=$userKeyVal not found in the database ALSO put a check for if value = "" |
Verify that the user is associated to a valid device or a device profile. |
KEY:$lcKey User cannot be repaired. AppProfileOwner=$newOwner and $userSearchAttr=$lcKey |
The respective profiles do not exist for this user. The profile that is being pointed to by the user is owned by a user that does not exist or is invalid. |
$lcKey user is invalid. A user that does not exist or is invalid owns the profiles for this user. $newOwner owns the profiles. |
Verify that the user exists in the directory and is a valid Cisco Unified Communications Manager user; that is, User with profiles. |
Number of orphan entries of $cleanObjClassName = $orSize |
Message indicates the number of orphan entries. |
This should only get thrown for users and not for profiles because the customer does not need to know about profiles. For profiles, one can just trace the list. |
See the solutions that are provided for individual users. |
Number of duplicate entries entries found in $csvObjectFileName = $dupSize |
Multiple users eist with the same id; or multiple profiles exist with the same owner. |
No change. |
The duplicate entries get removed automatically in the tar ball. One needs to remove them manually from the directory.The list follows. |
$cleanObjClassName for key $name |
None. |
No change. |
None. |
Number of duplicate entries entries found in $csvObjectFileName = $dupSize |
Multiple users exist with the same id; or multiple profiles exist with the same owner. |
No change. |
The duplicate entries get removed automatically in the tar ball. One needs to remove them manually from the directory.The list follows. |
$name is duplicate. |
None. |
No change. |
None. |
LDAP Bind Failed ErrorCode = $bindResult->error LDAP_URL = ".$uri->host_port. LDAP_HOST = ".$uri->host. LDAP_PORT = ".$uri->port. LDAP_DN = $MgrDN |
LDAP bind failed. |
No change. |
See the LDAP error. |
DN:$dnEntry has SingleValueAttribute:$AttributeName pointing to an invalid user:DN=$dnStr |
The value that is stored in a directory attribute is invalid. |
The SingleValue Attribute $AttributeName of the DN $dnEntry contains a user $dnStr that does not exist in the directory or is tagged invalid. |
Verify that the user exists in the directory and is a valid Cisco Unified Communications Manager user; that is, User with profiles. |
DN:$dnEntry has MultivaluedAttribute:$AttributeName pointing to an invalid User DN:$dnStr; |
The value that is stored in a directory attribute is invalid. |
TheMultivalues Attribute $AttributeName of the DN $dnEntry contains a user $dnStr that does not exist in the directory or is tagged invalid. |
Verify that the user exists in the directory and is a valid Cisco Unified Communications Manager user; that is, User with profiles. |
$EUUid has an invalid numplan ($DnorP) - it does not exist in the database\nIgnoring the user |
Primary Extension for this user is invalid. It does not exist in the databas.e |
Numplan ($DnorP) for User $EUUid is invalid. Ignoring the user. |
Associate the user with a valid primary extension/numplan. |
validateOrphan: UserID:$userID: Attribute ciscoatUserProfileString is found empty. |
The user does not contain a valid pointer to the User profile. |
UserID:$userID: is invalid - Attribute ciscoatUserProfileString is found empty. |
Verify that the user is a valid Cisco Unified Ccommunications Manager user. |
validateOrphan: UserID:$userID: Entry UserProfile is not found in search |
The User profile for the user does not exist.. |
UserID:$userID: is invalid - User profile not found in LDAP search. |
Verify that the user is a valid Cisco Unified Communications Manager user. |
validateOrphan: UserID:$userID: Attribute ciscoatAppProfile is found empty. |
The user does not contain a valid pointer to the Application profile. |
UserID:$userID: is invalid - Attribute ciscoatAppProfile is found empty. |
Verify that the user is a valid Cisco Unified Communications Manager user. |
validateOrphan: UserID:$userID: Entry ApplicationProfile is not found in search |
The Application profile for the user does not exist. |
UserID:$userID: is invalid - Application profile not found in LDAP search. |
Verify that the user is a valid Cisco Unified Communications Manager user. |
Database Message Improvements
DMA Data Validation executes the same operations on customer data as will be performed in the actual upgrade. This enables DMA to catch problems that might cause the upgrade to fail. Be aware that catching these errors during data validation, while the Cisco Unified CallManager 4.x system is still available and operating, is very important.
Because you cannot anticipate and test for every variation of a data problem variations in advance, the mechanism used to catch these errors depends on the built-in error reporting in the general-purpose database tools that are used. Unfortunately, the error messages that result are not very specific. They do not specify the problem and solution in terms that are familiar to the user.
Enhancements in this release now provide additional commentaries that are relevant to Cisco Unified Communications Manager on a few of the most commonly seen error messages.
Examples of the Most Commonly Seen Error Messages
•The -691 Referential Integrity Error
•The -11005 IDS Connection Failure Error
•The -271 IDS I/O Related Error
•The -391 Null Value Error
•The -239 Duplicate Record Error
•The -530 Constraint Violation Error
The -691 Referential Integrity Error
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.
The -11005 IDS Connection Failure Error
This is a hard error probably related to a DMA installation problem. It is a general issue
and NOT related to the record / request being processed. DMA was unable to perform
migration testing due to this failure. This reflects an installation or system failure.
Likely causes include:
- improper prior uninstall of the DBMS in a DMA upgrade
- a bad Informix password perhaps containing backslashes
- a system or disk or space related issue
SUGGESTED ACTION: Uninstall and re-install DMA carefully following all documented
procedures.
The -271 IDS I/O Related Error
This is a transient error related to DMA/DB data access issues. It is a general issue.
While possibly related to the record / request being processed, it does not indicate a
problem with that record / request. DMA was unable to perform migration testing due to a
failure accessing the data. This may have been due to resource constraints on the system
or other activity.
SUGGESTED ACTION: Re-boot the server and re-execute DMA.
The -391 Null Value Error
This record was not processed because it is missing a required value. This could also be
caused by specifying the value NULL in a required field.
SUGGESTED ACTION: Check the Suspected Field information and record contents, if provided,
to determine which data needs to be filled in and for which record. Update that record to
specify the required data and then re-execute DMA.
The -239 Duplicate Record Error
This record was not processed because another record exists with the same key value in a
field, (or combination of fields), required to be unique. For example, CM 4.x permits
multiple NumPlan entries with the same DNorPattern+RoutePartition value combination.
Later CUCM versions enforce uniqueness in these combined values.
SUGGESTED ACTION: Check the Suspected Field information and record contents, if provided,
to determine which data may be causing the uniqueness violation. Find the records sharing
these values and determine and make the appropriate changes to remove the duplication.
Then re-execute DMA.
The -530 Constraint Violation Error
This record was not processed because it contains a value which is incompatible with the
restrictions associated with this setting. (See reference name listed below).
SUGGESTED ACTION: Check the documented setting range limits for the problem field.
Correct the setting to be compatible with the requirements of CUCM version to which you
intend to migrate. Then re-execute DMA.
Location of Logs
This section contains information concerning the location of log files.
Find DMA installation-time generated log files at C:\Program Files\Common Files\Cisco\Logs
•C:\Program Files\Common Files\Cisco\Logs\<DMAInstall MM-DD-YYYY HH.mm.ss.log> where MM-DDYY HH-mm.ss specifies the date and time.
•C:\Program Files\Common Files\Cisco\Logs\DMAInstUI.log
•C:\Program Files\Common Files\Cisco\Logs\InstallUtils.log
•C:\Program Files\Common Files\Cisco\Logs\DMA\IDSInstall.log
•C:\Program Files\Common Files\Cisco\Logs\DMA\dbcmds.log
Find any runtime log files that are generated by the DMA framework and its underlying components that are stored at C:\Program Files\Cisco\Trace\DMA\
•C:\Program Files\Cisco\Trace\DMA\DMA<TraceMM-DD-YY.log> where MM-DD-YY specifies the date.
•C:\Program Files\Cisco\Trace\DMA\DMAStatus*.log
•C:\Program Files\Cisco\Trace\DMA\Progress\AllProgress.log
•C:\Program Files\Cisco\Trace\DMA\Progress\*.*
•C:\Program Files\Cisco\Trace\DMA\DB\*.log - this includes files like datavalidation.log, installdbw1.log, exportdb.log etc
•C:\Program Files\Cisco\Trace\DMA\DirExport\log\*.* - this includes directory export logs.
•C:\Program Files\Cisco\Trace\DMA\DMAErrors.log - consolidated errors from all components
•C:\Program Files\Cisco\Trace\DMA\DMAWarnings.log- - consolidated warnings from all components
•C:\Program Files\Cisco\Trace\DMA\DMAAutoCorrected.log - consolidated auto corrected files from all components
Infrequently used Intermediate Result runtime trace files that are stored at C:\Program Files\Cisco\Trace\DBL and C:\Install\DBInstall
•C:\Program Files\Cisco\Trace\DBL -- dbl_installdb*.txt -- detailed trace from database access operations performed from within database export and validation operations
•C:\Program Files\Cisco\Trace\DBL -- installdb* -- pre-consolidation trace from database export and validation operations
•C:\Install\DBInstall\ -- * -- Various, (see timestamps to determine what applies), logs from any CM 4 install and upgrade operations including DMA pre-migration
Consolidated Log Information
After a DMA export, you can access new buttons on the status window that allow you to view the errors, warnings, and auto-correction logs that DMA created.
The logs contain the following information:
•Errors Log (DMAErrors.log)—Errors that are found during the DMA export data and data validation phases. You must review and fix these errors in the Windows system before rerunning DMA export.
•Warnings Log (DMAWarnings.log)—Warnings that are found during the DMA export and data validation phases. The warnings indicate that some data does not comply with all rules in the version of Cisco Unified Communications Manager to which you are attempting to upgrade. Cisco strongly recommends that you address the warnings and run DMA again prior to running the upgrade. Using a DMA archive that contains warnings may result in a loss of functionality after the Cisco Unified Communications Manager upgrade.
•Auto-corrected Log (DMAAutoCorrected)—Data that is not compliant with the Cisco Unified Communications Manager schema, but for which correction logic exists, which will be applied at migration time. Review the auto-corrected logs. If you do not agree with the changes, make your own changes and run DMA again.
DMA TAR File Size Valiation
DMA checks the size of the TAR file during the DMA export process. If the TAR file exceeds 2 GB, the export fails.
Menu Option Changes
The Backup buttons and menu options changed to Export to more accurately indicate the function that is performed by DMA. DMA does not back up data but rather exports it to a format that can be read by appliance-based versions of Cisco Unified Communication Manager.
DMA Provides More Feedback When Validation Fails
In the past, DMA created a DMAExport.tar file after exporting the CCM/CAR/CAPF/CER data and then continued with the validation. The following validation results can occur:
•Failed
•Successful
•Successful with warnings
From the DMAExport.tar file itself, customers cannot tell whether the validation was successful.
New Design:
The tar file does not get generated immediately after the export data. It now generats after the validation result is known and the tarball is named based on the validation results:
•If the DMA export and validation succeed, the tarball gets named DMAExportSuccessful<mm-dd-yy>#<hh:mm>.tarball (where mm-dd-yy represents the date, and hh:mm represents the time).
•If the DMA export succeedsl and the validation contains warnings, the tarball gets named DMAExportWithWarnings<mm-dd-yy>#<hh:mm>.tarball (where mm-dd-yy represents the date, and hh:mm represents the time).
Note Customers should correct the warnings and rerun DMA.
•If the DMA export succeeds and validation contains errors, the tarball gets named DMAExportFailed<mm-dd-yy>#<hh:mm>.tarball (where mm-dd-yy represents the date, and hh:mm represents the time).
Note Customers should correct the errors and rerun DMA.
Name of the Shortcut That Is Used to Launch DMA Changed
Previously, the shortcut that was used to launch DMA was named DMAAdmin.This release names it Cisco DMA.
You can see the new shortcut by choosing Start > Cisco Data Migration Assistant.
For More Information
For more information on Data Migration Assistant 6.1(1), refer to the following document:
•Data Migration Assistant 6.0(1) User Guide
Caveats
This section contains information about the caveats that get resolved by this release of DMA and information about how to create your own list of resolved and open caveats.
•Caveats That Are Resolved in Data Migration Assistant 6.1(1a)
•Caveats That Are Resolved in Data Migration Assistant 6.1(1)
•Resolved Caveats
•Open Caveats
Caveats That Are Resolved in Data Migration Assistant 6.1(1a)
This section contains a partial list of the defects that are resolved in this release of Data Migration Assistant. You can obtain a full list by reviewing and implementing the information in "UsingBug Toolkit" section
CSCsl27492 - The Need Exists for User Friendly Validation Errors.
CSCsl31392 - The Need Exists for Expanded Explanations for 5 Additional Error Causes in DMA.
CSCsm19889 - The Need Exists for Improved Error and Warning Messages.
Caveats That Are Resolved in Data Migration Assistant 6.1(1)
This section contains a partial list of the defects that are resolved in this release of Data Migration Assistant. You can obtain a full list by reviewing and inplementing the information in "UsingBug Toolkit" section
•CSCsk18230 DMA Should Provide More Feedback When Validation Fails (DMA tarball name change)
•CSCsk35989 DMA Export Process Adds Logic to Handle Different CSA Versions
•CSCsk21760 The Need Exists for the DMAAdmin Shortcut to be Renamed Cisco DMA
•CSCsj24610 The Need Exists for Improved DMA Uninstall Process
•CSCsl59697 DMA Backup Hangs, and Informix Service Does Not Start
•CSCsk12791 After an Aborted DMA Installation, the Publisher Server Is Sluggish
•CSCsj96134 DMA The Need Exists for Pre-Exec Log/Trace Scrub
•CSCsk62050 DirExport Fails to Export Users
•CSCsk60617 Directory Export Failure Does Not Get Reported to DMA Framework
•CSCsk70423 Encrypted Password Shows in Plain Text in DMA Trace Files
•CSCsj95364 DMA Does Not Export Users If the ProfileOwner and UserId Do Not Match
•CSCsj82405 LDAP Users Missing in the Cisco Unified Communications Manager Database after DMA and Upgrade
•CSCsk22663 DMA Ignore PAB Entries for Users
•CSCsj94674 DirExport Should Export Users with an Unambiguous Numplan
•Improved user messaging and data migration validation, increased auto-correction, and condensed/consolidated/clarified user messaging.
–Invalid obsolete CSS for CFA data now gets auto-corrected.
CSCsj01673 DMA Fails Migration When CSSForCFA SQL Table Contains Invalid Contents
–Corrected spurious data validation warning message
CSCsh38822 DMA Validation Err on Default Credential Policy rec in CredentialPolicy
–General Log File / Message Issues
CSCsj93506 Post-integration Log Consolidation Work
CSCsj98562 installdbw1.log.Error File Did Not List an Error
CSCsk57172 DMA Log File Reports Incorrect Regex for VoiceMessagingProfileName
–Clarified the most frequently detected DMA DB Migration Verification Issue Message
CSCsk41050 DMA Message for Referential Integrity Issues Needs User-oriented Text
–Removed validation warnings that are related to migration issue that was corrected in prior ES
CSCsl19404 Too Restrictive Auto-Attendant Prompt Name Rules Exist
•Improved migrating from older versions - upgrades from older Cisco Unified Communications Manager releases prior to 4.2 encountered failures or slowness in the pre-migration phase of the DMA database export. These issues were addressed, and some performance improvements got added:
–Increased speed of migration from older systems with numerous devices
CSCsk74085 Long DMA Pre-Migration Times Caused by Excessive Device Updates
CSCsi71128 DMA Requires 28 Hours to Run on a System with Large Number of Devices
–Corrected issues that caused unexplained pre-migration failures or incorrect decisions to perform pre-migration processing:
CSCsk56867 DMA Performs Pre-Migration in Staged Upgrade When All Servers Are Not Staged
CSCsk41261 DMA Reports Backup Failure on 4.1.3 to 6.0.1 Migration
Resolved Caveats
You can find the latest resolved caveat information for Data Migration Assistant by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
Tip You need an account with Cisco.com to use the Bug Toolkit to find open and resolved caveats of any severity for any release.
To access the Bug Toolkit, log on to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.
UsingBug Toolkit
Known problems (bugs) get graded according to severity level. These release notes contain descriptions of
•All severity level 1 or 2 bugs.
•Significant severity level 3 bugs.
You can search for problems by using the Cisco Software Bug Toolkit.
To access Bug Toolkit, you need the following items:
•Internet connection
•Web browser
•Cisco.com user ID and password
To use the Software Bug Toolkit, follow these steps:
Procedure
Step 1 Acccess the Bug Toolkit, http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Step 2 Log in with your Cisco.com user ID and password.
Step 3 If you are looking for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field and click Go.
Tip Click Help on the Bug Toolkit window for information about how to search for bugs, create saved searches, create bug groups, and so on.
Open Caveats
Table 3 describes possible unexpected behaviors in Data Migration Assistant.
Tip For more information about an individual defect, click the associated Identifier in Table 3 to access the online record for that defect, including workarounds.
Understanding the Fixed-in Version and the Integrated-in Fields in the Online Defect Record
When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in these fields identifies the list of Cisco Unified Communications Manager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified Communications Manager releases.
Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1; however, the version information that displays for the Cisco Unified Communications Manager maintenance releases may not be as clearly identified.
Note Because defect status continually changes, be aware that Table 1 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the UsingBug Toolkit.
Tip Bug Toolkit requires that you have an account with Cisco.com. By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
.
Table 3 Open Caveats as of 2/15/2008
|
Identifier
|
Headline
|
CSCsl59710 |
DMA: Install and configuration of the Informix product, (used to perform DMA export data migration validation tests), results in the creation of a mirror (backup duplicate) copy of the Informix data files on the D: drive. The DMA install framework is to enact an automatic workaround in order to prevent drive space issues in DMA execution. This relates to a defect filed with IBM against the Informix product (IBM's PMR # 50711). |
CSCsl78801 |
DMA shows validation warnings for unknown device. |
CSCsm26559 |
DMA exported delete.csv file. |
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html. If you require further assistance please contact us by sending email to export@cisco.com.
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0711R)
© 2008 Cisco Systems, Inc. All rights reserved.
Printed in the USA on recycled paper containing 10% postconsumer waste.
