Generic selectors
Exact matches only
Search in title
Search in content
Search in posts
Search in pages
  1. DB Best Documentation
  2. Error mapping rules
Migration Platform
  • Overview
  • Product features
    • Release notes
    • Source and target platforms
    • Third-party applications
  • Getting started
    • Creating a new project
    • Ora2Pg installation
    • Tree view filtering
    • Compatible ODAC versions
    • Opening an existing project
    • Connecting to servers
      • Connecting to an Azure SQL Database
      • Connecting to an Oracle database
      • Connecting to a PostgreSQL database
      • Connecting to a Microsoft SQL Server database
    • Command timeout
  • Mapping
    • Object mapping
    • Error mapping rules
    • Data types mapping
  • Schema conversion
  • Schema comparison
  • Data comparison
  • Data migration
    • Migration task
      • Creating migration tasks
      • Templates
      • Migration options
      • Task actions
      • Task statuses
      • Errors or non-standard situations
    • Installing migration agent
      • Installing and uninstalling the data migration agent
      • Registering the migration agents
    • Project settings
  • Test organizer
    • Creating tests
    • Auto-generating tests
    • Groups and tests execution
    • Groups and tests states and execution statuses
    • Tests moving logic
    • Importing and exporting tests
    • Advanced comparison options
    • Creating reports
    • Error handling
  • Data store
  • Development project
  • System requirements
  • Hot keys
  • Known issues
  • Support

Error mapping rules

  • Share
    • Share via Facebook
    • Share via Twitter
    • Share via Linkedin

The Error mapping rules tab allows for handling errors and making sure they perform the same way in both the source and target databases in the Test Organizer module. The default error list is made by our DBAs, however, the list can be modified by adding or removing new and existing rules. The list contains the most common error scenarios for each pair of source and target databases.

The error description shows the error codes and message differences between the source and target databases in relation to their syntax.

A list of error rules

Figure 1. Default error mapping rules list

The most common usage scenario is when tests with the error status need to be passed. You can see some of the objects having the error status in Test Suite of the Test Organizer module.

Test with the error status

Figure 2. Test resulted in error

To make the test pass, you should enable the Compare error messages option. For that measure, select the tested object, click on the Advanced compare options tab. Then, scroll down to the bottom of the menu and check the Override parent options and Compare error messages options and press Save.

Advanced compare window

Figure 3. Error messages comparison enabled

After running the test, Migration Platform will automatically pass tests that match the default error mapping rules for both the source and target databases. If the test result still shows the error status, this means that the error scenario isn’t included in the default error mapping list and you need to add the error mapping rule manually.

To do that, copy the error codes and messages for both the source and databases, head over to the Mapping module, open the Error mapping rules tab, and press Add. In the opened window, paste the copied error codes and messages in the corresponding fields and press Save. It is sufficient to enter either error codes or messages.

Error rule creating

Figure 4. Creating an error rule

Then, return to the Test Organizer module and run the test for the object that previously had the error status.

Successful test

Figure 5. The passed test

As displayed above, the test passed successfully.


Didn’t find the answer?

You can report problems, ask questions or share ideas for improvements on our email [email protected].

Did this page help you?

Provide Feedback
Next Overview

Did this page help you? Yes

Thanks for letting us know that we did a great job.

Did this page help you? No

Thanks for letting us know that there is a problem on this page.

Send Feedback

Feel free to share your ideas or occurred issues with us. The DB Best team will be happy to make our documentation better.

Please, specify your email address so that we can reach out to you to clarify your question. Also, we will use this email address to notify you about solving the issue.

* marks the mandatory fields

Dark theme Light theme

© 2002–2021 DB Best Technologies, LLC. All rights reserved.