Re: SQLLDR Invalid Number on Record 2: Windows to Unix

Thanks for offering to help. I ended up figuring it out. I'm a little embarassed as the problem was much simpler than I assumed. I had an incorrect, and not needed, parameter on the INFILE clause.

By the way, what method is most common for loading data into Oracle tables? SQLLDR? Stored Procedures? VB/JAVA programs? Something Else?

Volker Hetzer wrote:
> Volker Hetzer schrieb:
>
> > You can check by doing an export (exp ...). It normally tells you
> > about server and client encoding right at the start.
> exp userid=name/password_at_database tables=dual
> This will give you something like this:
>
> Export: Release 9.2.0.6.0 - Production on Thu Oct 12 17:57:42 2006
>
> Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
>
>
> Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 -
> Production
> With the Partitioning, OLAP and Data Mining options
> Export done in US7ASCII character set and UTF8 NCHAR character set
> server uses AL32UTF8 character set (possible charset conversion)
>
> About to export specified tables via Conventional Path ...
> EXP-00011: DXDSUPPORT.DUAL does not exist
> Export terminated successfully with warnings.
>
>
> Lots of Greetings!
> Volker
>
>
> --
> For email replies, please substitute the obvious.
Received on Thu Oct 12 2006 - 14:20:43 CDT