Re: SQLLDR Issue - again

A copy of this was sent to amerar_at_ci.chi.il.us (if that email address didn't require changing) On Tue, 21 Sep 1999 15:17:19 GMT, you wrote:

>
>
>Ok, the file is not a comma delimited file. It is fixed with and fixed
>column. Here is a cut from my control file:
>
>DATE_BILLING POSITION(118:125) DATE(8) "YYYYMMDD" NULLIF (DATE_BILLING
>= " "),
>
>I changed it to this:
>
>DATE_BILLING POSITION(118:125) DATE(8) "YYYYMMDD" "decode(DATE_BILL
>ING, '00000000' null, ' ', null)",
>
>I got this error message:
>
>SQL*Loader-417: SQL string (on column DATE_BILLING) not allowed in
>direct path.
>

you have direct = true on the sqlldr command line.

this bypasses the SQL engine and all of its features.

This makes the use of builtin functions like substr, instr, DECODE, not possible in sqlldr -- only sqlldr supported functionality is allowed.

either drop the "direct=true" on the command line or drop the use of decode.

>Any ideas?
>
>Thanks,
>
>Arthur
>amerar_at_ci.chi.il.us
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.

--
See http://govt.us.oracle.com/~tkyte/ for my columns 'Digging-in to Oracle8i'... Current article is "Part I of V, Autonomous Transactions" updated June 21'st  

Thomas Kyte                   tkyte_at_us.oracle.com
Oracle Service Industries     Reston, VA   USA

Opinions are mine and do not necessarily reflect those of Oracle Corporation Received on Tue Sep 21 1999 - 12:11:48 CDT