My Oracle Support Banner

LLS Fields Are Not Properly Loaded By SQL*Loader (Doc ID 2387364.1)

Last updated on OCTOBER 09, 2019

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - 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
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

NOTE: The document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

SQL*Loader does not load LLS fields properly. The LLS fields have a +1 offset in comparison with DB2 data.

Below is a short description of the issue:

1. In DB2 we have inserted:


CREATE TABLE TAB_NAME ( ID SMALLINT, C CLOB)

INSERT INTO TAB_NAME (ID, C) VALUES (1, '<Name1>')
INSERT INTO TAB_NAME (ID, C) VALUES (2, '<Name2>')
INSERT INTO TAB_NAME (ID, C) VALUES (3, '<Name3>')
INSERT INTO TAB_NAME (ID, C) VALUES (4, '<Name4>')

 2. When we insert into Oracle database with SQL*Loader LLS option we get:

SELECT ID, C FROM TAB_NAME;

ID C
---------- ------------------------------------------------------
2 <Name2>
3 <Name3>
4 <Name4>
1 <Name1>

 3. Lob file details:

2,'TIGERLOB.001.lob.0.5/'
3,'TIGERLOB.001.lob.5.6/'
4,'TIGERLOB.001.lob.11.5/'
1,'TIGERLOB.001.lob.16.7/'

-- content of resulting file TIGERLOB.001.lob :
<Name2><Name3><Name4><Name1>

 

Changes

 NONE

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.