Issue While Migrating Blob Data Using Omwb: Sql*Loader-309 (Doc ID 301706.1)

Last updated on SEPTEMBER 15, 2013

Applies to:

Oracle Migration Workbench - Version 10.1.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 16-Sep-2013***


Symptoms

THE  WORKAROUND MENTIONED IN THIS NOTE IS NOT MAINTAINED BY ORACLE SUPPORT.

Migrating data of a foreign database with OMWB in offline mode can cause SQL*Loader to fail with error:

SQL*Loader-309: No SQL string allowed as part of <blob column> field specification

Changes

 SIDE NOTE:

This procedure is only necessary for OMWB or older SQL Developer releases. The SQL Developer 3.2 handles this now automatically and the manual states:

 

1.18.11 Migration -

Generate Stored Procedure for Migrate Blobs Offline: Causes a stored procedure named CLOBtoBLOB_sqldeveloper (with execute access granted to public) to be created if the schema contains a BLOB (binary large object); this procedure is automatically called if you perform an offline capture. If this option is not checked, you will need to use the manual workaround described in Section 2.2.8.1.4, "Populating the Destination Database Using the Data Files".


Then more details can be found in the section:

2.2.8.1.4 Populating the Destination Database Using the Data Files

...

■Enable the Generate Stored Procedure for Migrate Blobs Offline SQL Developer preference (see Migration: Generation Options).
■Use the following Workaround.

 

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