ODI Loading Data Via a Mapping Fails with Connection Closed Errors using MS SQL Server 2017
Last updated on FEBRUARY 22, 2018
Applies to:
Oracle Data Integrator - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
In ODI Studio 12.2.1.3.0, a one-to-one mapping was created to move data from the Oracle database to Microsoft SQL Server 2017. This mapping always fails to execute with several different errors as follows:
Errors Received
- Connection closed to Microsoft SQL Server
- Error informing the user that the Microsoft SQL Server does not support the numeric precision for conversion.
Error stacks could be like:
Steps to Reproduce Issue
The issue can be reproduced at will with the following steps:
- Create a mapping in ODI 12.2.1.3.
- Add an Oracle Database source model to the mapping.
- Add a Microsoft SQL Server 2017 model to the mapping.
- Ensure that no conversion is done via the mapping - simply data movement
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms