On Aug 16, 3:28 am, "pankaj_wolfhun..._at_yahoo.co.in"
<pankaj_wolfhun..._at_yahoo.co.in> wrote:
> On Jun 26, 7:01 pm, "pankaj_wolfhun..._at_yahoo.co.in"
>
>
>
> <pankaj_wolfhun..._at_yahoo.co.in> wrote:
> > On Jun 26, 6:47 pm, Mark D Powell <Mark.Pow..._at_eds.com> wrote:
>
> > > On Jun 26, 4:44 am, RJ <ridwan.je..._at_gmail.com> wrote:
>
> > > > Hi,
>
> > > > While working with SQLLDR to upload data I found that when the first
> > > > column is a DATE field it causes problems in the upload (for some
> > > > uncertain reason)
> > > > Try swapping the column sequence and uploading.
>
> > > TIA, please post back with the results.
>
> > > Also if you switch to a conventional load does it run successfully?
>
> > > Just curious
> > > -- Mark D Powell --
>
> > Thanks RJ, Mark.
> > If I go with conventional method, it goes fine.
>
> Sorry for such late response.
>
> RJ: I cant switch column names as it is an part of automated process
> and columns are getting fetched from oracle tables.
>
> Also conventional method is too slow as compared to direct method. How
> can make use of direct method here?
>
> TIA
So direct load doesn't like the TIMESTAMP type?
Could you use a staging table and direct load it as text and do the
conversion TO_TIMESTAMP() in a trigger that moves the data to the real
destination table? It is a workaround, but could be faster than a
conventional load.
Ed
Received on Mon Aug 20 2007 - 20:58:11 CDT
