Re: Oracle Import
From: patrick <pgovern_at_u.washington.edu>
Date: Fri, 6 Aug 2010 10:27:56 -0700 (PDT)
Message-ID: <3f238e51-bc59-4286-b0af-b46351dd0173_at_g21g2000prn.googlegroups.com>
On Aug 6, 6:37 am, The Magnet <a..._at_unsu.com> wrote:
> We are exporting data from MySQL to Oracle. According to the
> developers the data from MySQL contains new lines and tabs (\n, \r,
> \t).
>
> Is there a way to retain that in the message? The data is being
> imported into a CLOB column. Are there CHR for that? I think there
> is more than just a replace, so, I'm looking for ideas as I continue
> to search.
>
> Thanks!
Date: Fri, 6 Aug 2010 10:27:56 -0700 (PDT)
Message-ID: <3f238e51-bc59-4286-b0af-b46351dd0173_at_g21g2000prn.googlegroups.com>
On Aug 6, 6:37 am, The Magnet <a..._at_unsu.com> wrote:
> We are exporting data from MySQL to Oracle. According to the
> developers the data from MySQL contains new lines and tabs (\n, \r,
> \t).
>
> Is there a way to retain that in the message? The data is being
> imported into a CLOB column. Are there CHR for that? I think there
> is more than just a replace, so, I'm looking for ideas as I continue
> to search.
>
> Thanks!
Export file cannot use \t, \n as field or record delimiter.
In sqlldr control file specify those separators, e.g.,
load data
infile 'xxx.dat' "str '<R>'"
APPEND
into table XXXXXX.xxx_xx
REENABLE DISABLED_CONSTRAINTS
fields terminated by '<F>'
trailing nullcols
Assuming CLOB size is small enough you can also specify as as CHAR(64000) in the control file.
====>Patrick Received on Fri Aug 06 2010 - 12:27:56 CDT