We are migrate from MS Access to ORACLE(9.2.0.4) use
SQL*Loader. The problem we have are some of MS Access
dump records (ASCII output) have to several lines(EOL
before end of record). For example:
control file:
load data
infile 'data.asc'
into table test
fields terminated by ','optionally
This is a hack but ... you might want to look into ftp-ing a file to Unix,
run a 'tr' or 'sed' to get rid of the EOL character.
Thanks,
Nikhil
-Original Message-
Sent: Thursday, January 29, 2004 10:34 AM
To: Multiple recipients of list ORACLE-L
We are migrate from MS Access to
So, why don't you use migration workbench, when it's available?
On 01/29/2004 10:34:27 AM, dba1 mcc wrote:
We are migrate from MS Access to ORACLE(9.2.0.4) use
SQL*Loader. The problem we have are some of MS Access
dump records (ASCII output) have to several lines(EOL
before end of record). For
Thank you for answer. I did not said clearly. Most
records are fine. ONly some records have this
problem.
re-transfer from PC to UNIX will not fix problem.
--- Nikhil Khimani [EMAIL PROTECTED] wrote:
This is a hack but ... you might want to look into
ftp-ing a file to Unix,
run a 'tr'
You may want to add CONTINUEIF clause and try the load again
...
infile 'data.asc'
CONTINUEIF NEXT (1) != ''
into table test
...
For complete reference, see this URL:
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96652/ch05.htm#1005518
--
Thanks,
Krishna
of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: SQL Loader problem
Date: Tue, 29 Jul 2003 15:09:29 -0800
Sliced bread or not, the syntax problem will be the same since external
tables are modeled on SQL*Loader syntax... :-)
Anna, I suspect that there is confusion on the SQL*Loader concepts
Hi All,
I'm trying to use SQL Loader to load data from a text file into a table.
However, I always get error as column SKILL_DESCRIPTION field in data file
exceeds maximum length where the column SKILL_DESCRIPTION is declared as
varchar2(4000). I know the data is 4000 characters, but 1000
Try with external tables. The best thing since sliced bread.
On 2003.07.29 17:39, Anna Li wrote:
Hi All,
I'm trying to use SQL Loader to load data from a text file into a table.
However, I always get error as column SKILL_DESCRIPTION field in data file
exceeds maximum length where the column
Sliced bread or not, the syntax problem will be the same since external
tables are modeled on SQL*Loader syntax... :-)
Anna, I suspect that there is confusion on the SQL*Loader concepts of
external datatypes and internal datatypes, which incidentally is shared
by external tables currently.
After reading some archives on google, I came up with this solution:
Drop the index.
Use sqlldr to append to the table - for the id column, use:
(lc_rid sequence (max,1) ...)
Recreate the index.
However, when I did this, I received an error message saying that I
can't have duplicates in the
Saira
It looks like your index is being created on the LOC column, right?
CREATE UNIQUE INDEX LCI_LOC ON
LC_F(LOC)
So your change to the lc_rid column did not fix this problem.
Tom Mercadante
Oracle Certified Professional
-Original Message-
Sent: Tuesday, July 08, 2003 9:29 AM
To:
Ok. I must be legally blind :) Can this happen to anyone or just me?
I will try this again with my bifocals on.
Thank you for pointing it out kindly!!
Saira
-Original Message-
Sent: July 8, 2003 8:46 AM
To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
Saira
It looks like your index
I'm new to sqlldr and here is my control file:
LOAD DATA
INFILE '/home/oracle/116.csv'
BADFILE '/home/oracle/116.bad'
DISCARDFILE '/home/oracle/116.rej'
APPEND INTO TABLE LC_F
FIELDS TERMINATED BY ','
TRAILING NULLCOLS
(lc_rid,loc,loc_type,loc_size,sku,pkg,lot,uc1,uc2,uc3,zone,area,loc_stt,
Hi...
I would like to receive a bit of your help (I've been
looking at Metalink with no luck).
I'm having a sql*loader problem when I try to insert
records in a table field.
The problem is:
my data file has a column with MORE THAN 255
characters long, and sql*loader rejects the records
to receive a bit of your help (I've been
looking at Metalink with no luck).
I'm having a sql*loader problem when I try to insert
records in a table field.
The problem is:
my data file has a column with MORE THAN 255
characters long, and sql*loader rejects the records
that exceed that limit
8.1.7 on W2000
I am loading data and keep getting an error. The fields are text about 400+
characters. The column I am loading into is varchar2(4000). I keep getting
rejects with this error: Field in data file exceeds maximum length. Any
ideas as to why this is happening?
Thanks,
Ken
Bill:
I also found that I have to specify the size of the column even if the data
field is being skipped using filler!
Ken
-Original Message-
Sent: Friday, January 11, 2002 10:55 AM
To: Multiple recipients of list ORACLE-L
Subject:Re: SQL*Loader Problem
Where's what
I am loading data into an Oracle table (8.1.7 on W2000 server). I am
skipping fields (via filler) because I don't need to load them. However, I
am getting an error on one of the input fields (being skipped) - field in
data file exceeds maximum length. The record is a tilde ~ delimited flat
Could you have a special character like cr or nl that is causing this
problem or indicating the end of record before reading all fields?
-Original Message-
Sent: Wednesday, December 26, 2001 3:45 PM
To: Multiple recipients of list ORACLE-L
I am loading data into an Oracle table (8.1.7
Could be, but how do I read it?
Ken
-Original Message-
Sent: Wednesday, December 26, 2001 3:05 PM
To: Multiple recipients of list ORACLE-L
Subject:RE: Odd SQL Loader Problem
Could you have a special character like cr or nl that is causing this
problem or indicating
ts of list ORACLE-L
[EMAIL PROTECTED]
tle.wa.us
cc:
Sent
by:
Fax
to:
[EMAIL PROTECTED]
Subject: SQL*LOADER
problem
05/30/2001 08:05
PM
Please respond
to
ORACLE-L
Hi everyone.Having this typical problem with sql*loader.
I am extracting data out froma table and this
to:
[EMAIL PROTECTED]Subject: SQL*LOADER problem
8.1.7/Win2000
While loading a table with small tiff images (6k - 15K, out of line
Blob) and supporting data using SQL*loader we experienced a problem
that some of the images getting loaded aren't matching up with the
supporting data. Row 95 has the images from Row 1985, etc. Appears to
be
23 matches
Mail list logo