Sql Loader Direct NFS Warning Messages While Loading Data With CHARACTERSET "JA16SJIS"
(Doc ID 2110581.1)
Last updated on NOVEMBER 23, 2020
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 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 images and/or 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.
Getting Sql Loader Direct NFS warning messages while loading data with CHARACTERSET "JA16SJIS" and the Data Source file location is on NFS.
The used Sql Loader Control file is like:
LOAD DATA CHARACTERSET "JA16SJIS"
INTO TABLE MY_TAB
FIELDS TERMINATED BY "|"
OPTIONALLY ENCLOSED BY '"'
Next Direct NFS warning messages are raised when using CHARACTERSET "JA16SJIS":
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
::Warning message CHARACTERSET "JA16SJIS"::
Path used: Conventional
Direct NFS: channel id  path [<HOSTNAME>] to filer [<HOSTNAME>] via local  is UP
Direct NFS: attempting to mount /<DIR> on filer <HOSTNAME> defined in mtab
Direct NFS: channel config is:
channel id  local  path [<HOSTNAME>]
 kgnfs_exec_remote_mount:2430: warn could not spawn oradism
Direct NFS: please check that oradism is setuid
Commit point reached - logical record count 1
1 Row successfully loaded.
If CHARACTERSET is "UTF8" in the sqlldr controlfile, there is no warning message.
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