Unable to migrate sql server CLOBs To Oracle
(Doc ID 1253285.1)
Last updated on MARCH 09, 2023
Applies to:
Oracle SQL Developer - Version 2.1.1 and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Sql developer migration workbench. Migrating sql server 2005 to Oracle .
The convert to oracle model fails for clob conversion
The clob data is not very huge in size. It is less than 1000 Bytes and in some cases it is null. So how tp get around the null data issue and will it work if some default string for the column is mentioned in the oracle table.
Following is the example of the table which gets converted to oracle successfully. But data move fails and it gives a wrong error message saying invalid column successfully run.
All tables with clob columns fail during data move.
CREATE TABLE RADIUS_QA.WEBSVCRUN
(
WEBSVCRUNID NUMBER(20) NOT NULL,
IPADDRESS VARCHAR2(30 BYTE) DEFAULT (''),
RUNTYPE VARCHAR2(50 BYTE) DEFAULT (''),
RUNSTART DATE DEFAULT sysdate NOT NULL,
RUNEND DATE,
SUCCESSFULLRUN NUMBER(1) DEFAULT ((1)) NOT NULL,
CREATEDBY NUMBER(10) DEFAULT ((1)) NOT NULL,
CREATEDON DATE DEFAULT sysdate NOT NULL,
MODIFIEDBY NUMBER(10) DEFAULT ((1)) NOT NULL,
MODIFIEDON DATE DEFAULT sysdate NOT NULL,
ERRORMESSAGE VARCHAR2(4000 BYTE) DEFAULT (''),
STAMP TIMESTAMP(6) DEFAULT sysdate NOT NULL
)
Cause
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
| Symptoms |
| Cause |
| Solution |