Re: Repost: SQLLOADER problem

Jon K.'s answer is nicely done.

Why unicode? Think.

The discard and bad files are intended as inputs to another digital process.

The log file is meant for human inspection, making it very native language (NLS) dependent.

That would be my thought on that answer.

RSH. PS: Just a theory.

"Ryan Gaffuri" <rkg100_at_erols.com> wrote in message news:a7m43f$l2u$1_at_bob.news.rcn.net...
> Why is it in unicode? Why arent the discard and bad file in unicode?
>
>
> "Jon K" <jon.dotonline_at_excitedot.com> wrote in message
> news:3c9e8d15_9_at_news.teranews.com...
> > It's in UNICODE format.
> >
> > NT's Notepad is the only editor that can't read them correctly. In
2000,
> > you can open the file, if it looks messed up 'save as' to ASCII format
to
> > 'fix' it.
> >
> > Quick fix, specify it with a WRI extension, then write/wordpad will be
> your
> > default editor.
> >
> >
> >
> > JON
> >
> >
> >
> >
> >
> > "Ryan Gaffuri" <rkg100_at_erols.com> wrote in message
> > news:a7jf5t$d7h$1_at_bob.news.rcn.net...
> > > I posted this recently.. but didnt get a full answer. I have an
annoying
> > > problem. When I make my log file and open it in Notepad it opens with
a
> > > bunch of ASCII characters in it. When I open it in Microsoft Word it
> does
> > > not have the ASCII characters and is formatted better but not totally
> > lined
> > > up.
> > >
> > > Is there a way to tell SQLLOADER how to output this file? Im deploying
> > this
> > > far from my work site for a non-technical client. The SQLLOADER will
be
> > run
> > > from a batch process. The client may need to check the log file if
there
> > are
> > > problems... etc... The discard and bad files can be viewed from
textpad
> > > without any problems.
> > >
> > > The client will be using a standard Windows NT environment. Is there
> > > something I can do with the output or is there something simple that I
> can
> > > recommend the client do?
> > >
> > >
> >
> >
>
>
Received on Mon Mar 25 2002 - 13:10:20 CST