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!

On Aug 6, 9:37*am, The Magnet <a... (AT) unsu (DOT) com> wrote:
If you are going to load the data in question into a CLOB column then
the sqlldr utility has the ability to load LOB's and each LOB can be a
file so the tabs, CR, and NL can be loaded.

You can also load the data via programs that insert the data in
question.

You can shove tab and NL into varchar2 columns for that matter. As
long as the data submitted to Oracle has tab and NL in it Oracle will
store it. If you transfer the data across platforms be sure you do
not translate it such as the ASCII FTP I do between Windows and UNIX
automatically converts Windows text file CR NL combinations in just NL
on windows.

HTH -- Mark D Powell --

On Aug 6, 6:37*am, The Magnet <a... (AT) unsu (DOT) com> wrote:
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

On Aug 6, 11:04*am, Mark D Powell <Mark.Powe... (AT) hp (DOT) com> wrote:

Well, maybe not the best way, but I was thinking of replacing the \t
with CHR(9) and the \n with CHR(10). I'll just parse the line. It
comes from MySQL with the line feed & tab stuff, so I'll just do a
parse / replace.

It is a one time thing, so I think that will do.