My Oracle Support Banner

SQL*Loader Cannot Load Some Raw Data When NLS_LANG is Multi-Byte (Doc ID 2065115.1)

Last updated on JUNE 02, 2021

Applies to:

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

NOTE: In the document content below, the user information and data used represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Symptoms

SQL * LOADER will not successfully load the binary data to RAW datatype column, if the following conditions are met:

  1. You have specified the multi-byte character set to NLS_LANG and Database.
  2. The record delimiter is specified after binary data(binary data is specified as last column in loader control file).
  3. Binary data's last byte is first byte of multi-byte charcterset.
  4. The record delimiter is more than 2 bytes.


Example:

If you have set the NLS_LANG to the character set JA16SJIS and run the data load with the SQL * Loader as following:

 

Changes

 

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.