E1: DB: MS SQL to Oracle Database Column Padding Issues
(Doc ID 1052958.1)
Last updated on AUGUST 01, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
This document will cover a possible issue with conversion of Microsoft SQL database types to Oracle database types where the ANSI_PADDING has caused issues within a specific table or tables which will not allow SQL statements to run properly against the resulting dataset in an Oracle database.
The R98403 report used many times to copy data will not impact the actual data being read so the issue needs to be addressed at the database level either before a copy or conversion or after. Third party tools used for a SQL to Oracle data copy can likely be configured to address any data padding, however, this document will only cover the issue and an easy workaround for the resulting dataset regardless of the process used to copy the data.
This issue is not specific to EnterpriseOne, however, customers doing a conversion may run into some difficulties with certain tables where the primary key uses a alphanumeric field that had 'padding' enabled in the prior Microsoft SQL database.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|MS SQL to Oracle Database Column Padding Issues|