Re: Decode in SQLLDR script too long. Workaround?

"Elton Saulsberry" <me_at_devnull.net> wrote in message news:Ne%77.694$Tj3.32892_at_e420r-atl2.usenetserver.com... I have a sqlldr control file with the following decode:

 TERMINATION_ID POSITION(057:071) CHAR "DECODE(UPPER(:TERMINATION),
'USER-REQUEST', 1,
'LOST-CARRIER', 2,
'LOST-SERVICE', 3,
'IDLE-TIMEOUT', 4,
'SESSION-TIMEOUT', 5,
'ADMIN-RESET', 6,
'ADMIN-REBOOT', 7,
'PORT-ERROR', 8,
'NAS-ERROR', 9,
'NAS-REQUEST', 10,
'NAS-REBOOT', 11,
'PORT-UNNEEDED', 12,
'PORT-PREEMPTED', 13,
'PORT-SUSPENDED', 14,
'SERVICE-UNAVAILABLE', 15,
'CALLBACK', 16,
'USER-ERROR', 17,
'HOST-REQUEST', 18,

 -1)"

This results in this error:

SQL*Loader-350: Syntax error at line 26. Token longer than max allowable length of 258 chars
'PORT-UNNEEDED', 12,

  ^

It seems my decode is too long for sqlldr to handle. Can anyone suggest a workaround for this?
Thanks,
Elton

--
Elton Saulsberry
esaulsberry at jumpon dot net

Sure

- Please don't post in HTML
- put those translations in a separate table, and 'massage' the data after
the load.

Hth,

Sybrand Bakker, Senior Oracle DBA