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.

Similar Messages

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-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-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.

No insert Statements for EKKO EKPO in ST05 sql trace for transaction me21n

No insert Statements for EKKO EKPO in ST05 sql trace for transaction me21n.
IN ST05 I set a filter for ME21N and executed transaction to create a Purchase Order and then checked
ST05 but there is NO insert for EKKO or EKPO??
How Do I find in which columns of EKKO and EKPO data is inserted in ST05?
Edited by: DeepakNandikanti on Apr 28, 2010 8:27 AM

Hi,
I tried in my system and I can see INSERT statement on EKKO and EKPO tables. What exactly you are looking for? Some one else might have switched on the trace at the same time. Can you try again and see.
ST05=>Switch on trace
ME21N=>Create PO.
ST05=>Switch off and display trace.
In trace list search for EKKO and EKPO.
Column names are not shown in the trace list. It is the SQL trace and column list is generated dynamically like :A0, :A1....
@ Suhas,
That might be because the tables are updated via BAPIs ... Do you think SAP uses direct update statements on the DB tables ??
I didn't get above statement. Is there any other way of updation that happens when using BAPI? I believe that, even in case of BAPI there will be update task FMs called during database update. Please correct if i got it wrong.
Thanks,
Vinod.

Error when executing statement for table/stored proc

Hi All,
 I am getting this error when executing IDOC to JDBC (Stored Procedure) Scenario.
 In my stored procedure I have three insert statements to insert rows in to 3 tables.
 This stored procedure is working fine for two insert statements i.e,
 For this I have created data type for stored procedure with 10 elements and executed the scenario and was successfully running.
 when I added 3rd insert statement to stored procedure ie., when i added 5 more elements to the datatype (totally 15 elements) it starts giving the bellow error in Message Monitoring.
Exception caught by adapter framework: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC_1' (structure 'Statements'): java.sql.SQLException: General error
Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC_1' (structure 'Statements'): java.sql.SQLException: General error
 Note:- I have run the stored procedure with three insert statements in Sql Server, and also by calling an external program also, and was working fine.
 Note : Is there any structure needs to be follow when working with IDOC to Stored procedure.
I am struck up with the error, can any body resolve this issue.
Thanks in Advance,
Murthy

Hi narasimha,
 This seems to be any error due to incorrect query formation.In your receiver jdbc channel set the parameter logSQLstatement = true.you can find this parameter in the advanced mode. Using this parameter you will be able to see the sql query which is generated at runtime in the audit log in RWB.
Regards,
Pragati

File to JDBC :Error when executing statement for table/stored proc.

Hi,
I am getting following error when i am trying to insert data into z-table using JDBC recr adapter.
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'ZTEST' (structure 'STATEMENT'): java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'ZTEST'.
But the database table name 'ZTEST' exists in the system.
XML structure:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_RECR xmlns:ns0="http://urn:srini/FileToJDBC">
 <STATEMENT>
 <TEST action="INSERT">
 <table>ZTEST</table>
 <access>
 <ROLLNO>123</ROLLNO>
 <FIRSTNAME>ABC</FIRSTNAME>
 <LASTNAME>XYZ</LASTNAME>
 </access>
 </TEST>
 </STATEMENT>
</ns0:MT_RECR>
Regards,
Srinivas

Hi,
I have changed my MT str but still getting the same error.Is it possible to insert/ update a z-table using JDBC adapter.
XML str:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_RECR xmlns:ns0="http://urn:srini/FileToJDBC">
 <STATEMENT>
 <ZTEST action="INSERT">
 <access>
 <ROLLNO>123</ROLLNO>
 <FIRSTNAME>abc</FIRSTNAME>
 <LASTNAME>XYZ</LASTNAME>
 </access>
 </ZTEST>
 </STATEMENT>
</ns0:MT_RECR>
Regards,
Srinivas

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.

Error when executing statement for table/stored proc DB2 - Data Truncation

Hi,
I have one call sp in XI with n parameters int and two parameters out.
well, to implement the interface gives the following error
com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SPSAPAR9' (structure 'Statement'): java.sql.SQLException: The number of parameter values set or registered does not match the number of parameters
Thanks for your help
Ximena
Edited by: Ximena Gonzalez on Feb 19, 2008 11:50 AM
Edited by: Ximena Gonzalez on Feb 20, 2008 12:17 PM

My Error is change
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SAPPRG.SPSAPAR9' (structure 'Statement'): java.sql.DataTruncation: Data truncation
but de change DT SP
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:AlistReqDet2_MT xmlns:ns1="urn:proxl:tmuc:proxl01:AlistReqItems">
<Statement>
<SPSAPAR9 action="EXECUTE">
<table>SAPPRG.SPSAPAR9</table>
<ISAPNU1 isInput="TRUE" type="STRING">0080000353</ISAPNU1>
<ISAPEM1 isInput="TRUE" type="STRING">'LU'</ISAPEM1>
<ISAPC05 isInput="TRUE" type="STRING">15353</ISAPC05>
<ISAPSEC isInput="TRUE" type="STRING">10</ISAPSEC>
<ISAPLOT isInput="TRUE" type="STRING">'lats'</ISAPLOT>
<ISAPCA1 isInput="TRUE" type="STRING">10</ISAPCA1>
<ISAPCA2 isInput="TRUE" type="STRING">10</ISAPCA2>
<ISAPKIL isInput="TRUE" type="STRING">10</ISAPKIL>
<ISAPES1 isInput="TRUE" type="STRING">'T'</ISAPES1>
<ISAPSW isOutput="TRUE" type="STRING" />
</SPSAPAR9>
</Statement>
</ns1:AlistReqDet2_MT>

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

Error when executing statement for table/stored proc. : ORA-00911

Hi All,
I am posting IDOC->XI->JDBC, approx 5000 Idocs.
But few messages are giving following error in XI-_SXMB_MONI
Can any one guide me what is the cause of error? I check whole Idoc data I am not able to see bad character? can any once guide me what are the bad character in XML to post data in oracle? so that i can search in XML and how to avoide this error.
"com.sap.aii.af.ra.ms.api.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'HRP1001' (structure 'INSERT_PAD34'): java.sql.SQLException: ORA-00911: invalid character"

> I am talking about following IDOC.<ZRMD_A06> ->
> <E1PLOGI SEGMENT="1">-> <E1PITYP SEGMENT="1"> ->
> <E1PAD34 SEGMENT="1"> -><PROZT>0.00 #</PROZT>.
> Can we remove this # during message mapping in XI??
sure you can remove it using Replace function or by writing UDF.
as I am seing # is last character..so remove # with " " (single space) and then use the TRIM fucntion.
Thanks
Farooq.
*Rewards points if you find it useful*

VLD-1119: Unable to generate Multi-table Insert statement for some or all t

Hi All -
I have a map in OWB 10.2.0.4 which is ending with following error: -
VLD-1119: Unable to generate Multi-table Insert statement for some or all targets.*
Multi-table insert statement cannot be generated for some or all of the targets due to upstream graphs of those targets are not identical on "active operators" such as "join".*
The map is created with following logic in mind. Let me know if you need more info. Any directions are highly appreciated and many thanks for your inputs in advance: -
I have two source tables say T1 and T2. There are full outer joined in a joiner and output of this joined is passed to an expression to evaluate values of columns based on
business logic i.e. If T1 is available than take T1.C1 else take T2.C1 so on.
A flag is also evaluated in the expression because these intermediate results needs to be joined to third source table say T3 with different condition.
Based on value taken a flag is being set in the expression which is used in a splitter to get results in three intermediate tables based on flag value evaluated earlier.
These three intermediate tables are all truncate insert and these are unioned to fill a final target table.
Visually it is something like this: -
T1 -- T3 -- JOINER1
| -->Join1 (FULL OUTER) --> Expression -->SPLITTER -- JOINER2 UNION --> Target Table
| JOINER3
T2 --
Please suggest.

I verified that their is a limitation with the splitter operator which will not let you generate a multi split having more than 999 columns in all.
I had to use two separate splitters to achieve what I was trying to do.
So the situation is now: -
Siource -> Split -> Split 1 -> Insert into table -> Union1---------Final tableA
Siource -> Split -> Split 2 -> Insert into table -> Union1

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-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-930: Error parsing insert statement for column

Similar Messages

Maybe you are looking for