Encounter SQL*Loader-510 error

When try to load data from flat file to Oracle,the size is around 6 million row,below error was throwed.
SQL*Loader-510: Physical record in data file (yadayadayada) is longer than the maximum(1048576)
SQL*Loader-2026: the load was aborted because SQL Loader cannot continue.
Anyone has idea about this,thanks..
Message was edited by:
user588299

Hi,
I think that the error has occured if the target table column lenght is smaller than the one that you are sending fromt he control file
Also there is an option 'reject unlimited ' that you can use in control file so even if errors occurs while uploading the file through SQL LOADER it will skip that record and carry on with the next.
In that way i think the load shouldnt get aborted.
You can also have a log file that may log out these bad data.
Thanks

Similar Messages

SQL*Loader-510: Physical record in data file (clob_table.ldr) is long

If I generate loader / Insert script from Raptor, it's not working for Clob columns.
I am getting error:
SQL*Loader-510: Physical record in data file (clob_table.ldr) is long
er than the maximum(1048576)
What's the solution?
Regards,

Hi,
Has the file been somehow changed by copying it between windows and unix? Ora file transfer done as binary or ASCII? The most common cause of your problem. Is if the end of line carriage return characters have been changed so they are no longer /n/r could this have happened? Can you open the file in a good editor or do an od command in unix to see what is actually present?
Regards,
Harry
http://dbaharrison.blogspot.co.uk/

Sql loader 510

I am loading a file with some BLOBs. Most of the data seems to have loaded ok but I am now getting this error:
SQL*Loader-510: Physical record in data file
(c:\Sheets_2005.dat) is longer than the maximum(20971520)
The ctl file was auto generated by Migration Workbench...i have added the options in....
options (BINDSIZE=20971520, READSIZE=20971520)
load data
infile 'c:\sheets_2005.dat' "str '<EORD>'"
append
into table SHEETS
fields terminated by '<EOFD>'
trailing nullcols
(REFNO,
SHEETNO,
DETAIL CHAR(100000000)
MESSAGE,
SIZE_)
Any ways around this error?
Thanks

Hello,
Can you tell me which plugin you are using?
option#1
Cause: I think from the error message it appears that the datafile has a physical record that is too long.
If that is the case, try changing the length of the column [this problem could be most likely at the blob/clob column]. Also try Using CONCATENATE or CONTINUEIF or break up the physical records.
OPTION#2
If you are using sql server or sybase plugin, this workaround may work:
Cause: Export of Binary data may be bit too big. Hence it needs to be converted to the HEX format. Thus produced HEX data can be saved into a clob column.
The task is split into 4 sub tasks
1. CREATE A TABLESPACE TO HOLD ALL THE LOB DATA
     --log into your system schema and create a tablespace
     --Create a new tablespace for the CLOB and BLOB column
     --You may resize this to fit your data ,
     --Remember that we save the data once as CLOB and then as BLOB
     --create tablespace lob_tablespace datafile 'lob_tablespace' SIZE 1000M AUTOEXTEND ON NEXT 50M;
2. LOG INTO YOUR TABLE SCHEMA IN ORACLE
     --Modify this script to fit your requirements
     --START.SQL (this script will do the following tasks)
          ~~Modify your current schema so that it can accept HEX data
          ~~Modify your current schema so that it can hold that huge amount of data.
          ~~Modify the new tablespace to suite your requirements [can be estimated based on size of the blobs/clobs and number of rows]
          ~~Disable triggers, indexes & primary keys on tblfiles
3. DATA MOVE: The data move now involves moving the HEX data in the .dat files to a CLOB.
     --The START.SQL script adds a new column to <tablename> called <blob_column>_CLOB. This is where the HEX values will be stored.
     --MODIFY YOUR CONTROL FILE TO LOOK LIKE THIS
          ~~load data
          ~~infile '<tablename>.dat' "str '<er>'"
          ~~into table <tablename>
          ~~fields terminated by '<ec>'
          ~~trailing nullcols
          ~~(
          ~~ <blob_column>_CLOB CHAR(200000000),
          ~~)
The important part being "_CLOB" appended to your BLOB column name and the datatype set to CHAR(200000000)
     --RUN sql_loader_script.bat
     --log into your schema to check if the data was loaded successfully
     --now you can see that the hex values were sent to the CLOB column
     --SQL> select dbms_lob.getlength(<blob_column>),dbms_lob.getlength(<blob_column>_clob) from <tablename>;
4. LOG INTO YOUR SCHEMA
     --Run FINISH.SQL. This script will do the following tasks:
          ~~Creates the procedure needed to perform the CLOB to BLOB transformation
          ~~Executes the procedure (this may take some time a 500Mb has to be converted to BLOB)
          ~~Alters the table back to its original form (removes the <blob_column>_clob)
          ~~Enables the triggers, indexes and primary keys
Good luck
Srinivas Nandavanam

SQL*Loader-925: Error while parsing a cursor (via ocisq)

Receiving the following error message when trying to use SQLLoader (on NT) >>>
SQL*Loader-925: Error while parsing a cursor
(via ocisq)
ORA-00942: table or view does not exist
Trying to use the application for the first time, logon using userid for which sqlplus operates, and the table does exist under the user schema, as owner.
ctl and dat file are correct. Log file gives me no further detail of the errors.
Are there any configuration settings or something required for this app?
Thanks

Thanks Warren. I was concentrating more on the first line of the error.
You are right. The issue was of insufficient privileges. The table did not have all the necessary grants provided.

SQL*Loader-930: Error parsing insert statement for column

we upload data on daily basis in application throug apps user and these table are invloved
1. DEV_RA_INTERFACE_LINES_ALL(owner is a apps)
2.RA_INTERFACE_LINES_ALL(owner is a AR)
we do steps
1 delete record from DEV_RA_INTERFACE_LINES_ALL table
2 delete record from RA_INTERFACE_LINES_ALL table
3 load data using sql loader with apps user
4 insert in RA_INTERFACE_LINES_ALL table
we want to change user i mean these step do dataupload user not apps
we give the proper rights to dataupload like select,delete and insert rights on these table to dataupload user but when i going to load data throug sql loader we receive error
SQL*Loader-930: Error parsing insert statement for column APPS.DEV_RA_INTERFACE_
LINES_ALL.ORIG_SYSTEM_BILL_ADDRESS_ID.
ORA-00904: "F_ORIG_SYSTEM_BILL_ADDR_REF": invalid identifier
and if i insert data through apps then done.

make sure that u have no speces left
between lines.
give the path of control file path correctly.

SQL*Loader-523 error in solaris sh script

I have a SQLLdr script that I want to call from a unix shell (sh) script. We are running on Solaris 8. When we run from the command line the Sqlldr works, when we run from within a shell script, we are getting an STD ERR -2 error. I have tried running SQLldr with the -s (silent option) and silent = all but it doesn't seem to be helping.
I pasted the error that I am getting below.
Thanks,
Greg
SQL*Loader: Release 8.1.5.0.0 - Production on Wed Jul 19 15:20:48 2000
(c) Copyright 1999 Oracle Corporation. All rights reserved.
SQL*Loader-523: error -2 writing to file (STDERR)

...Ugh, it was working for about 5 seconds on my test page, but now it's just giving me an exit status of 137(Anyone have any clue what this means? I can't find anything that tells me what these exit number means and it's really starting to bug me) after I commented and uncommented a few lines to check to see what caused it to work...Hah! Works again. New Question time:
LD_PRELOAD, what does this variable have to do with SQL*Loader, since I'm using it in the apache start-up to do some stuff with oci8[No idea if it's necessary] and when I, assumedly, set it to "null" it works, but when it keeps my initial value it breaks and gives me my 137 error status with my original errors.

SQL*Loader-925: Error while uldlfca: OCIStmtExecute (ptc_hp)

Hi my table loading is failing with the floowing error. But same table is loading daily without any problem. I tried again but failed with the same message.
SQL*Loader-2026: the load was aborted because SQL Loader cannot continue.
SQL*Loader-925: Error while uldlfca: OCIStmtExecute (ptc_hp)
ORA-03114: not connected to ORACLE
SQL*Loader-2026: the load was aborted because SQL Loader cannot continue.
SQL*Loader-925: Error while uldlgs: OCIStmtExecute (ptc_hp)
ORA-03114: not connected to ORACLE
SQL*Loader-925: Error while uldlgs: OCIStmtFetch (ptc_hp)
ORA-24338: statement handle not executed
How to solve this problem?
Thanks
Prashanth

user614414 wrote:
Hi BluShadow,
Nothing is changed recently. Loading is happening for other files at sametime, when this loading is failed. I have renamed and recreated the table, then it is working fine. similar problem occured today for some other table.
May i know, for any other reason it will happen?You've only supplied us with an error message and that's what the error message indicates.
If you want more help, you need to supply more details.

SQL*Loader-929: Error parsing insert statement for table

Hi,
I get the following error with SQL*Loader:
Table MYTABLE loaded from every logical record.
Insert option in effect for this table: INSERT
Column Name Position Len Term Encl Datatype
IDE FIRST * ; CHARACTER
SQL string for column : "mysequence.NEXTVAL"
CSI_NBR 1:10 10 ; CHARACTER
POLICY_NBR 11:22 12 ; CHARACTER
CURRENCY_COD 23:25 3 ; CHARACTER
POLICY_STAT 26:27 2 ; CHARACTER
PRODUCT_COD 28:35 8 ; CHARACTER
END_DAT 44:53 10 ; CHARACTER
FISCAL_COD 83:83 1 ; CHARACTER
TOT_VAL 92:112 21 ; CHARACTER
SQL*Loader-929: Error parsing insert statement for table MYTABLE.
ORA-01031: insufficient privileges
I am positive that I can SELECT the sequence and INSERT into the table with the user invoking sql*loader.
Where does that "ORA-01031" come from?
Regards
...

Options:
1) you are wrong about privileges OR
2) you have the privilege only when you connect via SQL*Plus (or whichever other tool you used to test the insert).
Is it possible that during your test you enabled the role which granted you the INSERT privilege - and that SQL*Loader doesn't do this?
Can you see the table in this list?
select *
from user_tab_privs_recd
where table_name='MY_TABLE'
and owner='table owner whoever';
select *
from user_role_privs;Any roles where DEFAULT_ROLE is not YES?
HTH
Regards Nigel

SQL*Loader-951: Error calling once/load initialization

Dear all,
11g on solaris 10.
Dear all,
When loading data using the below :
sqlldr username/password@db control=data.ctl direct=true errors=10000 readsize=1048576 log=databill.log
data loading successful.
but when am speeding up the same and trying to load as below :
sqlldr username/password@db1 control=databill.ctl direct=true errors=10000 Parallel=true bindsize= 5048576 multithreading=true log=databill.log
SQL*Loader-951: Error calling once/load initialization
ORA-26002: Table username.table has index defined upon it.
If I drop index, and run the same it works fine.. is there way I can speed up the insert (append) using the above
sqlldr username/password@db1 control=databill.ctl direct=true errors=10000 Parallel=true bindsize= 5048576 multithreading=true log=databill.log
control file :
UNRECOVERABLE
LOAD DATA
INFILE "databill.dat" "str X'0c'"
BADFILE "databill.bad"
DISCARDFILE "databill.dis"
APPEND
PRESERVE BLANKS
INTO TABLE username.databill_TEST
FIELDS TERMINATED BY X'07' TRAILING NULLCOLS
Thanks
Kai

Thanks ,
when using ,
sqlldr username/password@db1 control=databill.ctl direct=true errors=10000 Parallel=true readsize=1048576 bindsize= 5048576 multithreading=true log=databill.log
12048217 Rows successfully loaded.
0 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
Date cache:
   Max Size:      1000
   Entries :       424
   Hits    : 81540372
   Misses :         0
Bind array size not used in direct path.
Column array rows :    5000
Stream buffer bytes: 256000
Read   buffer bytes: 1048576
Total logical records skipped:          0
Total logical records read:      12048217
Total logical records rejected:         0
Total logical records discarded:        0
Total stream buffers loaded by SQL*Loader main thread:     3767
Total stream buffers loaded by SQL*Loader load thread:    11300
Run began on Thu Dec 17 19:36:01 2009
Run ended on Thu Dec 17 19:42:16 2009
Elapsed time was:     00:06:14.25
CPU time was:         00:02:29.55when using
sqlldr username/password@db control=data.ctl direct=true errors=10000 readsize=1048576 log=databill.log
12048217 Rows successfully loaded.
0 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
Date cache:
   Max Size:      1000
   Entries :       424
   Hits    : 81540372
   Misses :         0
Bind array size not used in direct path.
Column array rows :    5000
Stream buffer bytes: 256000
Read   buffer bytes: 1048576
Total logical records skipped:          0
Total logical records read:      12048217
Total logical records rejected:         0
Total logical records discarded:        0
Total stream buffers loaded by SQL*Loader main thread:     3767
Total stream buffers loaded by SQL*Loader load thread:    11300
Run began on Thu Dec 17 04:29:05 2009
Run ended on Thu Dec 17 04:37:04 2009
Elapsed time was:     00:07:58.95
CPU time was:         00:03:04.94How can I acheive maxium loading performance, what do I have to add to this :
sqlldr username/password@db1 control=databill.ctl direct=true errors=10000 Parallel=true readsize=1048576 bindsize= 5048576 multithreading=true log=databill.log
Please guide
Kai

SQL*Loader-929: Error

Hi
I am getting following error
SQL*Loader-929: Error parsing insert statement for table XXEEG.XXCONV_NOR_OKS_CON_HEADERS.
ORA-00947: not enough values
while running SQL*Loader. I have same number and types of columns in target table, data file and in control file even after I am getting this error. One thing I want to mention is that there are some fields in my data file which are NULL. But I think this should not create any problem.
Please If any one can give the answer then it will be very helpful for me.

Hi,
I am generating control file using a shell script and that shell script runs SQL*LOADER using that generated control file. The following control file is generating.
Control file:
OPTIONS (SKIP=1)
load data
INFILE '/home/C9976680/xxconv_nordic_oks_header.csv'
TRUNCATE
into table xxeeg.XXCONV_NOR_OKS_CON_HEADERS
fields terminated by "," optionally enclosed by '"' trailing nullcols
ID "xxconv_nordic_contract_pkg.get_seq_val('HDR')",
BATCH_NUMBER "xxconv_nordic_contract_pkg.get_batch_no(to_date(:START_DATE,'MM/DD/YYYY'),to_date(:END_DATE,'MM/DD/YYYY'))",
CONTRACT_NUMBER,
CONTRACT_VERSION,
ORACLE_CONTRACT_NUMBER "xxconv_nordic_contract_pkg.get_orcl_kno(:CONTRACT_NUMBER,CONTRACT_VERSION))",
START_DATE "to_date(:START_DATE,'MM/DD/YYYY')",
END_DATE "to_date(:END_DATE,'MM/DD/YYYY')",
STATUS,
PARTY_ID,
BILL_TO_ID,
SHIP_TO_ID,
ACCOUNTING_RULE_TYPE,
INVOICE_RULE_TYPE,
PAYMENT_TERMS,
INT_SALESREP_NAME,
EXT_SALESREP_NAME,
RENEWAL_CONTACT_NAME,
ISR_ZONE,
ORBITAL_PROFILE_ID,
CCHOLDER_NAME,
CC_ZIP,
CUST_PO,
CC_NO,
CC_EXPIRY_DATE,
ERROR_MESSAGE,
INTERFACED_STATUS_FLAG CONSTANT "N",
ERROR_STACK
Log file:
SQL*Loader: Release 8.0.6.3.0 - Production on Wed Feb 13 02:01:11 2008
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Control File: /opt/egapmdev/ebmdappl/xxeeg/bin/xxconv_nordic_oks_header.ctl
Data File: /home/C9976680/xxconv_nordic_oks_header.csv
Bad File: /opt/egapmdev/ebmdappl/xxeeg/bin/xxconv_nordic_oks_header.bad
Discard File: none specified
(Allow all discards)
Number to load: ALL
Number to skip: 1
Errors allowed: 50
Bind array: 64 rows, maximum of 65536 bytes
Continuation: none specified
Path used: Conventional
Table XXEEG.XXCONV_NOR_OKS_CON_HEADERS, loaded from every logical record.
Insert option in effect for this table: TRUNCATE
TRAILING NULLCOLS option in effect
Column Name Position Len Term Encl Datatype
ID FIRST * , O(") CHARACTER
BATCH_NUMBER NEXT * , O(") CHARACTER
CONTRACT_NUMBER NEXT * , O(") CHARACTER
CONTRACT_VERSION NEXT * , O(") CHARACTER
ORACLE_CONTRACT_NUMBER NEXT * , O(") CHARACTER
START_DATE NEXT * , O(") CHARACTER
END_DATE NEXT * , O(") CHARACTER
STATUS NEXT * , O(") CHARACTER
PARTY_ID NEXT * , O(") CHARACTER
BILL_TO_ID NEXT * , O(") CHARACTER
SHIP_TO_ID NEXT * , O(") CHARACTER
ACCOUNTING_RULE_TYPE NEXT * , O(") CHARACTER
INVOICE_RULE_TYPE NEXT * , O(") CHARACTER
PAYMENT_TERMS NEXT * , O(") CHARACTER
INT_SALESREP_NAME NEXT * , O(") CHARACTER
EXT_SALESREP_NAME NEXT * , O(") CHARACTER
RENEWAL_CONTACT_NAME NEXT * , O(") CHARACTER
ISR_ZONE NEXT * , O(") CHARACTER
ORBITAL_PROFILE_ID NEXT * , O(") CHARACTER
CCHOLDER_NAME NEXT * , O(") CHARACTER
CC_ZIP NEXT * , O(") CHARACTER
CUST_PO NEXT * , O(") CHARACTER
CC_NO NEXT * , O(") CHARACTER
CC_EXPIRY_DATE NEXT * , O(") CHARACTER
ERROR_MESSAGE NEXT * , O(") CHARACTER
ERROR_STACK NEXT * , O(") CHARACTER
INTERFACED_STATUS_FLAG CONSTANT 'N'
Column ID had SQL string
"xxconv_nordic_contract_pkg.get_seq_val('HDR')"
applied to it.
Column BATCH_NUMBER had SQL string
"xxconv_nordic_contract_pkg.get_batch_no(to_date(:START_DATE,'MM/DD/YYYY'),to_date(:END_DATE,'MM/DD/YYYY'))"
applied to it.
Column ORACLE_CONTRACT_NUMBER had SQL string
"xxconv_nordic_contract_pkg.get_orcl_kno(:CONTRACT_NUMBER),to_char(:CONTRACT_VERSION))"
applied to it.
Column START_DATE had SQL string
"to_date(:START_DATE,'MM/DD/YYYY')"
applied to it.
Column END_DATE had SQL string
"to_date(:END_DATE,'MM/DD/YYYY')"
applied to it.
SQL*Loader-929: Error parsing insert statement for table XXEEG.XXCONV_NOR_OKS_CON_HEADERS.
ORA-00947: not enough values
Table Structure:
CREATE TABLE XXEEG.XXCONV_NOR_OKS_CON_HEADERS
( ID NUMBER CONSTRAINT HEAD_ID_PK PRIMARY KEY,
BATCH_NUMBER NUMBER,
CONTRACT_NUMBER VARCHAR2(50),
CONTRACT_VERSION NUMBER,
ORACLE_CONTRACT_NUMBER VARCHAR2(300),
START_DATE varchar2(20),
END_DATE varchar2(20),
STATUS VARCHAR2(20),
PARTY_ID NUMBER,
BILL_TO_ID NUMBER,
SHIP_TO_ID NUMBER,
ACCOUNTING_RULE_TYPE VARCHAR2(50),
INVOICE_RULE_TYPE VARCHAR2(50),
PAYMENT_TERMS VARCHAR2(50),
INT_SALESREP_NAME VARCHAR2(50),
EXT_SALESREP_NAME VARCHAR2(50),
RENEWAL_CONTACT_NAME VARCHAR2(50),
ISR_ZONE VARCHAR2(50),
ORBITAL_PROFILE_ID VARCHAR2(50),
CCHOLDER_NAME VARCHAR2(50),
CC_ZIP NUMBER,
CUST_PO VARCHAR2(50),
CC_NO NUMBER,
CC_EXPIRY_DATE varchar2(20),
ERROR_MESSAGE VARCHAR2(1000),
INTERFACED_STATUS_FLAG VARCHAR2(1),
ERROR_STACK VARCHAR2(2000)
Functions used above:
FUNCTION get_batch_no(p_start_date DATE, p_end_date DATE) RETURN NUMBER IS
BEGIN
RETURN 1;
END get_batch_no;
FUNCTION get_orcl_kno(p_contract_number VARCHAR2, p_contract_version NUMBER) RETURN VARCHAR2 IS
BEGIN
RETURN 'M'||p_contract_number||'v'||p_contract_version;
END get_orcl_kno;
FUNCTION get_seq_val (p_seqtype VARCHAR2) RETURN NUMBER IS
v_seqno NUMBER;
BEGIN
IF UPPER(p_seqtype) = 'HDR' THEN
SELECT XXCONV_NOR_HDR_S.NEXTVAL
INTO v_seqno
FROM dual;
RETURN v_seqno;
END IF;
IF UPPER(p_seqtype) = 'LINE' THEN
SELECT XXCONV_NOR_LINE_S.NEXTVAL
INTO v_seqno
FROM dual;
RETURN v_seqno;
END IF;
IF UPPER(p_seqtype) = 'SUBLINE' THEN
SELECT XXCONV_NOR_SUBLINE_S.NEXTVAL
INTO v_seqno
FROM dual;
RETURN v_seqno;
END IF;
IF UPPER(p_seqtype) = 'BILL_SCH' THEN
SELECT XXCONV_NOR_BILL_SCH_S.NEXTVAL
INTO v_seqno
FROM dual;
RETURN v_seqno;
END IF;
IF UPPER(p_seqtype) = 'PMS' THEN
SELECT XXCONV_NOR_PMS_S.NEXTVAL
INTO v_seqno
FROM dual;
RETURN v_seqno;
END IF;
IF UPPER(p_seqtype) = 'TEST' THEN
SELECT XXCONV_NOR_WARRANTY_S.NEXTVAL
INTO v_seqno
FROM dual;
RETURN v_seqno;
END IF;
END get_seq_val;
-----------------------------------

SQL*Loader-350 Error

I got a SQL*Loader-350 error due to a FILLER statement in my control file. I have known the cause is Concurrent Manager uses SQL*Loader 8.0.6 and the FILLER option is available from 8.1.7. The e-Business Suite version is 11.5.0.
May I upgrade SQL*Loader to 8.1.7 or it could generate inconsistences in the suite ?
I would appreciate your comments.
César Rengifo

it depends, upgrading the Oracle Home on an existing Oracle Technology Stack might not be viable option due to dependancies.
other method i can think of is install the new Oracle home in a different location, write a shell script for the concurrent job, the shell script will set the new environment installed and use the SQL Loader from the New Home to perform the Job.

Sql*loader-604 Error occurred on an attempt to commit

Hi,
Iam trying to insert data in to dept table using sqlloader.It worked fine for first 2 attempts but when iam trying it later its giving an error.
E:\ sqlldr userid=scott/tiger@test,control='E:\oracle\dept.ctl'
sql*loader-604 Error occurred on an attempt to commit
ora-03114: not connected to oracle
Regards,
Krithika

ora-03114: not connected to oracle
Your DBA might have wriiten a procedure to Kill an Oracle session if idle for 15 mins or so or he might have killed the session for some maintenance purpose and that to forcefully . Try reconnectiing again

Data Loading using SQL* Loader giving errors..

While loading the data using SQL* Loader, I came across the following errors:
- SQL*Loader-00604 Error occurred on an attempt to commit
- ORA-01041 internal error. hostdef extension doesn't exist
My Control and Data files have proper Carriage Returns i.e. the last line of both the files is blank.
So, if somebody know about this, plz help me.
Thanx

ORA-00604 error occurred at recursive SQL level string
Cause: An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).
Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support Services
This kind of error occurs when data dictionary is
query a lot.
Joel P�rez

SQL*Loader-128: Error in Concurrent program of type SQL* Loader

Hi,
Am facing below error with CP of SQL*Loader execution format. Both Control and data files are placed under bin directory under CUSTOM TOP.
CP doesnt have any parameter. I believe we dont need to pass login details to a CP. So how can we default the DB Login to SQL Loader in CP?
Appreciate your quick help.
SQL*Loader-128: unable to begin a session
ORA-01017: invalid username/password; logon denied
SQL*Loader: Release 10.1.0.5.0 - Production on Wed Dec 14 02:03:59 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL*Loader-128: unable to begin a session
ORA-01017: invalid username/password; logon denied
Program exited with status 1
Concurrent Manager encountered an error while running SQL*Loader for your concurrent request 1040692.
Review your concurrent request log file for more detailed information.
Here the Control and Data file for the same.
Control file:
LOAD DATA
INFILE 'XXX_Customer_Master.dat'
BADFILE 'Customer_bad.bad'
DISCARDFILE 'Customer_discard.bsc'
APPEND
INTO TABLE XXX_AR_CUSTOMERS_INT FIELDS TERMINATED BY "|" OPTIONALLY ENCLOSED BY '"'
ORIG_SYSTEM_PARENT_REF ,
ORIG_SYSTEM_CUSTOMER_REF,
CUSTOMER_NAME,
CUSTOMER_NAME_PHONETIC,
COUNTRY,
STATE,
CITY,
ADDRESS1,
POSTAL_CODE,
RECORD_NUMBER          SEQUENCE(MAX, 1),
CREATED_BY                CONSTANT -1,
CREATION_DATE           CONSTANT SYSDATE,
CUSTOMER_TYPE          CONSTANT 'R',
INSERT_UPDATE_FLAG           CONSTANT 'I',
LAST_UPDATE_DATE           CONSTANT SYSDATE,
LAST_UPDATE_LOGIN          CONSTANT -1,
LAST_UPDATED_BY          CONSTANT -1,
ORG_ID               CONSTANT 102,
PRIMARY_SITE_USE_FLAG     CONSTANT 'Y',
SITE_USE_CODE          CONSTANT 'BILL_TO'
*Data file:*
'XXX_Customer_Master.dat'
50|792086|Test Customer |Test Customer |759843055|Australia|VIC|MELBOURNE|"Level 4 457 St Kilda Road"|3004
59|792232|Test Customer |Test Customer |751756404|Australia|ACT|Tuggeranong|PO Box 1035|2901

Do we have to create soft link like we create for host program directory ?How to Register a Host Concurrent Program in Applications [ID 156636.1]
How To Create A Custom Concurrent Program With Host Method and Pass Parameters To The Shell Script [ID 266268.1]
How To Setup A Custom Concurrent Host Program [ID 147455.1]
Also, please see (How to Use 9i or 10g Features in SQL*Loader for Apps? [ID 423035.1]).
Thanks,
Hussein

SQL Loader and Error ORA-01847/ORA-01839

Hi,
While using the direct loading in SQL-LOADER when we get the ORA-01847/ORA-01839 all the other records are getting errorred out. It goes fine with the conventional loading.
Should I use some parameters or anything to make sure that all the other records are not rejected when we get the ORA-01847/ORA-01839 error while going with the DIRECT loading.
Thanks
Jibin

In internet I found this short message:
“AL32UTF8 is a multi-byte characterset,that means some characters are stored in more than 1 character, that's true for these special characters.
If you have same table definitions in both databases you likely face error ORA-12899.
This metalink note discusses this problem, it's also applicable to sqlloader:
Import reports "ORA-12899: Value too large for column" when using BYTE semantic
Doc ID: Note:563893.1”
By metalink, I can see the Note linked to a one Oracle Internal Bug for Oracle 11g.....
I'm waiting you suggestion... thanks very much in advance.
Regards.
Giovanni

Encounter SQL*Loader-510 error

Similar Messages

Maybe you are looking for