User-Defined Datatype Not Converted Correctly For Columns Defined As Null (Doc ID 727729.1)

Last updated on JANUARY 19, 2017

Applies to:

Oracle SQL Developer - Version 1.5 to 1.5.4
Information in this document applies to any platform.

Symptoms

When using SQL*Developer Migration Workbench 1.5.1 columns using Sybase user-defined datatype of
'int' that are defined as 'NULL' are not converted correctly, they are converted to datatype
'intn' instead of a number datatype in Oracle.
Columns using the user-defined datatype defined as 'NOT NULL' are translated correctly.

For example, a Sybase user-defined datatype is created as -

1> sp_help SWID
2> go
Type_name Storage_type Length Prec Scale Nulls Default_name Rule_name Access_Rule_name Identity
--------------- --------------- ----------- ---- ----- ----- --------------- --------------- ---------------- --------
SWID int 4 NULL NULL 0 NULL NULL NULL 0 

The Sybase create table script is -

create table TEST_1 (
swId SWID not null,
swMaxId SWID null,
timestamp
)


This is converted to the following Oracle create statement - 

CREATE TABLE TEST_1 (
swId NUMBER(12,0) NOT NULL,
swMaxId intn(4,0),
timestamp NUMBER(8,0)
);

 

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