SQL*Loader with unsupplied CHARACTERSET setting on windows
399831Nov 24 2009 — edited Nov 27 2009Hi,
I have a exceptional behaviour on windows when loading data with the sql*loader and the pre-defined CHARACTERSET WE8MSWIN1252 in the CTL file.
The DIRECT=TRUE option in the PAR file is set.
The datafile contains special characters - e.b. ยง ASCII code 167 - which are not converted correctly on windows when too many records to load. I guess it might be a bug and the sql*loader tool should be updated...
- Solaris : Sql*loader with complete file (ca. 200 MB / 500.000 records) --> OK
- Windows: Sql*loader with 1 record in infile --> OK
- Windows: Sql*loader with complete file (ca. 200 MB / 500.000 records) --> NOT OK!!!
1.) Client system: Windows 2003 Server
NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
NLS_DATE_FORMAT="YYYY-MM-DD HH24:MI:SS"
NLS_TIMESTAMP_FORMAT="YYYY-MM-DD HH24:MI:SS"
Windows and file code page (chcp): CP1252
SQL*Loader: Release 10.1.0.2.0 - Production on Tue Nov 24 19:26:04 2009
2.) Client system: Solaris 5.10 / Sun, Sparc
NLS_LANG=AMERICAN_AMERICA.AL32UTF8
NLS_DATE_FORMAT="YYYY-MM-DD HH24:MI:SS"
NLS_TIMESTAMP_FORMAT="YYYY-MM-DD HH24:MI:SS"
LC_ALL=en_US.UTF-8
LANG=en_US.UTF-8
SQL*Loader: Release 10.2.0.4.0 - Production on Tue Nov 24 19:32:36 2009
3.) DB Server: Solaris 5.10 / Sun, Sparc
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0
NLS_CHARACTERSET: AL32UTF8
Thank you for response!
Regards,
Andreas