Stephen,
I was using CHAR for the LONG column the error is actually on the
field in the file FOLLOWING the LONG column... I was getting a message
that the data was too large. So I did the following and it seems to be
working, although I can't get it to work via direct path this way:
I changed
Rachel,
I do not claim to be a guru, but I do happen to have Jonathan's book
here.
The first thing is what field type are you using for this memo field?
The book says you should use CHAR for VARCHAR2, CHAR, LONG and other
related.
What error are you getting?
Can you post the lines from the ctl
No. We are still with 8i.
--- [EMAIL PROTECTED] wrote:
> Are you on 9i?
>
> If so, setup the sql_load.txt file as an external
> table, and you
> can then use SQL and/ora PL/SQL to load your table
> the
> way you would like.
>
> Don't think you can do what you're asking directly
> from sqlldr.
>
Are you on 9i?
If so, setup the sql_load.txt file as an external table, and you
can then use SQL and/ora PL/SQL to load your table the
way you would like.
Don't think you can do what you're asking directly from sqlldr.
Jared
Bob Robert <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
06/26/
Bob
If you were on Unix, I would suggest you have a script that split your
input file into multiple files using one of the Unix utilities, then
executed SQL*Loader against each of those. Since you are on Windows, perhaps
someone has a suggestion that will apply there. I know there are Windows
ve
Try:
SICK_ACCRUAL POSITION(569:583) integer external(14),
VAC_ACCRUAL POSITION(585:599) integer external(14)
Helen
"Johnston, Steve" <[EMAIL PROTECTED]> wrote:
Thanks in advance for help, been lurking for a couple of weeks.I am using sqlldr73.exe to load a text file into an oracle 7.3.2.1.
Chaim,
Along these lines, can't you disable the not null constraint, load the
data, update the table/columns (UPDATE MY_TABLE SET THIS_COLUMN = 0
WHERE THIS COLUMN IS NULL) then re-enable the constraints?
David
Ron Rogers wrote:
>
> Chaim,
> If on the other hand the BLANK will not work proper
Chaim,
If on the other hand the BLANK will not work properly on a numeric filed that is to
be used in calculations. In that case you might want to have a 0(zero) loaded rather
than a null,blank. Then you could use the NVL clause in your controll statement where
the field type is numeric.
ROR m
You might want to look into the 'defaultif' option in the control file.
Prakash
-Original Message-
[mailto:[EMAIL PROTECTED]]
Sent: Friday, March 30, 2001 12:27 PM
To: Multiple recipients of list ORACLE-L
Maybe some could help me.
I'm having trouble trying to load a csv file with sq
Chaim,
Check out the sqlldr case studies on OTN. Ross has the right idea with
the NULLIF. Here's a general description from OTN:
Loading All-Blank Fields
Totally blank fields for numeric or DATE fields cause the record to be
rejected. To load one of these fields as null, use the NULLI
Just insert the string you want in the position you desire.
i.e.. (01110,"*",,,1,1,31460)
you would also have to specify the delimiters in the control file.
regards
Tavo
[EMAIL PROTECTED] wrote:
> Maybe some could help me.
> I'm having trouble trying to load a csv file with sqlldr. The
Title: RE: SQL*Loader help
There is something like DEFAULTIF NULL.
Happy RTFM'ing! :)
Thanks, I got that work out now.
It's an option (direct=true) in the control file in 8.1.6 was missing. But I still don't understand that 8.0.5 will be able to compile without this option. I'm running 8.0.5 on my local machine, but 8.1.6 is remote on a UNIX box. Will these different environment
Is
your mainframe using EBCDIC? If so there is a translation table that
explains what the "}" translates into. The sign of the field is trailing
(E.I.. at the end of the field for non-Cobolers)
These
indicate that the sign of the number is negative.
}=0
R=9
Q=8
P=7
O=6
N=5
M=4
L=-
K=-
J=
At 11:47 AM 3/23/01 -0800, you wrote:
The mainframe data looks like "0}", The table is designed as Number(10,2), The control file use zoned(10,2).
That looks like the internal representation for a signed number under COBOL. The least significant digit (LSD) is used to store the s
15 matches
Mail list logo
