SQL*Loader memory Fault

SQL*Loader runs fine when I am running using my login. However when I use a different login I get Memory fault error. Please share any thoughts if had experience this problem or any insights into what might be causing this problem
Thanks,
Pedapuli

The following is in the log:
SQL*Loader: Release 9.2.0.3.0 - Production on Thu Sep 7 11:44:06 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Memory fault

Similar Messages

SQL Loader Segmentation Fault

I'm trying to load a table (fixed length rows = 385 bytes, 78000k+ total bytes) and get a segmentation fault (core dump) as sqlldr is invoked. The log file is 0 bytes. I've tried changing the rows and buffers parms but no difference.
Any thoughts?

Oracle 9.2.0.4
SunOS 5.8
Please disregard this post - I used 'single quotes' instead of "doubles" in the script, so the login info was incorrect...

SQL Loader is creating a log file of 0 (zero) bytes.

Hello!!
I am using SQL Loader to load data from a .txt file to a Oracle table.
Following is the control file:
LOAD DATA
CHARACTERSET UTF8
CONTINUEIF LAST != "|"
INTO TABLE product_review_dtl
FIELDS TERMINATED BY '||' TRAILING NULLCOLS
indiv_review_id INTEGER EXTERNAL,
pid INTEGER EXTERNAL,
merchant_review_id INTEGER EXTERNAL,
merchant_user_id CHAR "SUBSTR(:merchant_user_id,1,20)",
review_status_txt CHAR "SUBSTR(:review_status_txt,1,20)",
review_create_date DATE "YYYY-MM-DD",
helpful_votes_cnt INTEGER EXTERNAL,
not_helpful_votes_cnt INTEGER EXTERNAL,
review_source_txt CHAR "SUBSTR(:review_source_txt,1,30)",
overall_rating_num INTEGER EXTERNAL,
comment_txt CHAR(4000) "SUBSTR(:comment_txt,1,4000)",
nickname CHAR "SUBSTR(:nickname,1,30)",
headline_txt CHAR "SUBSTR(:headline_txt,1,100)",
confirmed_status_grp INTEGER EXTERNAL "TO_NUMBER(SUBSTR(TO_CHAR(:confirmed_status_grp),1,5))",
location_txt CHAR "SUBSTR(:location_txt,1,100)"
Some records are loaded. A log file is also created but it is empty. Can you help me find out why the log file is empty?

user525235 wrote:
Hello Folks!!
I have 2 input files with different encoding (apparent in case of special characters).
File 1 loads successfully. For File 2 loader gives a memory fault while loading. Hence the log file is of 0 bytes. I still have no clue as to why is the loader giving a memory fault. It is not an OS level memory fault as analysed by the OS team. Please help!
Thanks in advance :)Unknown OS
Unknown database version
No details about what import command was used or the options specified
No samples / details of input files or their encoding
No details about exact error message of "memory fault"
No help is possible ;-)
Srini

Define variable in SQL Loader Control File

Hi,
I have an input file where the first line is the header record, followed by the detail records. For the processing, I do not need to store the fields of the header record but I need a date field from this header record and store in as part of the detail record in an oracle record row.
Is it possible to define a variable within the sql loader control file to store the value that I need in memory then use it when I do the sql insert by the sql loader?
Thanks for any advice.

Not sure that you can. But if your on unix/linux/mac its easy enough to write a shell script to populates the variables in a template file that you can then use as the ctl file. The perl template toolkit could be an option for that as well

SQL Loader bug

2 day ago I meet with problem to load text file to Oracle DB with
SQL statment in control file. It's my control file:
LOAD DATA
INFILE '/tmp/123/22-12.txt'
REPLACE
INTO TABLE VL_LOG
(date_time SYSDATE,
SOURCE POSITION(02:16)
"TRUNC(SUBSTR(:SOURCE,1,3))*16777216+TRUNC(SUBSTR(:SOURCE,INSTR(:
SOURCE,'.')+1,3))*65536+TRUNC(SUBSTR(:SOURCE,INSTR(:SOURCE,'.',1,
2)+1,3))*256+RTRIM(SUBSTR(:SOURCE,INSTR(:SOURCE,'.',-1)+1))",
DESTINATION POSITION(19:33)
"TRUNC(SUBSTR(:DESTINATION,1,3))*16777216+TRUNC(SUBSTR(:DESTINATI
ON,INSTR(:DESTINATION,'.')+1,3))*65536+TRUNC(SUBSTR(:DESTINATION,
INSTR(:DESTINATION,'.',1,2)+1,3))*256+SUBSTR(:DESTINATION,INSTR(:
DESTINATION,'.',-1)+1)",
bytes POSITION(54:72) INTEGER EXTERNAL)
When I run SQL Loader with this control file my Linux 5.2
(kernel 2.0.36) say:
Segmentation fault(core dumped).
Later I test this and now may say, that error is only when length
of SQL statment more than 201 bytes(symbols). I think, that input
buffer for this statment to small and loader fault when attempt
to translate incomlete string. I know, that Loader may translate
statments only shorter 258 symbols, and when statment string
greater 258 show error, but not core dumped!
Alex Zykov.
Russia,Tomsk.
null

255 is default length. If you need more - specify it exactly as char(2000). You searched wrong forums. I'd suggest you to read manuals instead:
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96652/ch06.htm#1006961

SQL*Loader permission issue?

I have set up a run_all script on LINUX to invoke SQL*Loader for each table to be loaded. I can run this as the Oracle owner just fine. When I try to let the developer run this on dev, they get the following:
SQL*Loader: Release 9.2.0.1.0 - Production on Tue Apr 25 08:55:18 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL*Loader-128: unable to begin a session
ORA-01034: ORACLE not available
ORA-27121: unable to determine size of shared memory segment
Linux Error: 13: Permission denied
They can use SQL*Plus on the command line with the userid and password from the SQL*Loader file. I don't want to have to run these for them every time, so any help or ideas would be greatly appreciated!

Hi
Has the same ORACLE_HOME variable value of the Oracle owner and the developer?
Ott Karesz
http://www.trendo-kft.hu

SQL LOADER CONTROL FILE

hi,
Can one call procedures and functions inside a control file in SQL Loader ...alternatively how can one use case inside a control file ...
How to implement the the following code in a control file:
SELECT CASE
WHEN INSTR(UPPER(returnname),'SCHEDULE') > 0 THEN 'S'
WHEN INSTR(UPPER(returnname),'RETURN') > 0 THEN 'R'
WHEN INSTR(UPPER(RETURNNAME),'BREAKDOWN') > 0 THEN 'B'
ELSE returnname
END
AS returns
FROM tableexample
Please let me know ..

regarding your first question :
data_file TT.dat :
SCHEDULE
RETURN
BREAKDOWN
HOLIDAY
WEEKEND
schedule
return
breakdown
holiday
weekend
control_file TT.ctl :
load data
insert
into table dummy_test
(TEXT position(01:20) char
,TEXT_b position(01:20) char " decode(upper(:TEXT),'SCHEDULE','S','RETURN','R','BREAKDOWN','B',:TEXT) "
parameter_file TT.par :
userid=user/password
DATA=TT.dat
CONTROL=TT.ctl
ERRORS=99999
load file into table :
sqlldr parfile=TT.par
log-file TT.log :
SQL*Loader: Release 8.1.6.2.0 - Production on Thu Feb 26 16:01:23 2004
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Control File: TT.ctl
Data File: TT.dat
Bad File: TT.bad
Discard File: none specified
(Allow all discards)
Number to load: ALL
Number to skip: 0
Errors allowed: 99999
Bind array: 64 rows, maximum of 65536 bytes
Continuation: none specified
Path used: Conventional
Table DUMMY_TEST, loaded from every logical record.
Insert option in effect for this table: INSERT
Column Name Position Len Term Encl Datatype
TEXT 1:20 20 CHARACTER
TEXT_B 1:20 20 CHARACTER
SQL string for column : " decode(upper(:TEXT),'SCHEDULE','S','RETURN','R','BREAKDOWN','B',:TEXT) "
Table DUMMY_TEST:
10 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.
Space allocated for bind array: 2816 bytes(64 rows)
Space allocated for memory besides bind array: 0 bytes
Total logical records skipped: 0
Total logical records read: 10
Total logical records rejected: 0
Total logical records discarded: 0
Run began on Thu Feb 26 16:01:23 2004
Run ended on Thu Feb 26 16:01:23 2004
Elapsed time was: 00:00:00.58
CPU time was: 00:00:00.10
SQL > select * from dummy_test ;
TEXT TEXT_B
SCHEDULE S
RETURN R
BREAKDOWN B
HOLIDAY HOLIDAY
WEEKEND WEEKEND
schedule S
return R
breakdown B
holiday holiday
weekend weekend
10 rows selected.
SQL>
Does it solve your problem ?
Regards,
Rainer

SQL*Loader halt loading large varray object

I was using sql*loader of Oracle 8i NT, trying to load some records with
varray (some records have lots of array elements, up to several thousands).
however, after several hundreds records loaded, sql*loader became very slow,
and virtually stopped at some point. I watched the system resouces taken by
sql*loader, it simply drove my NT out of physical memory (it occupied
hundreds meg of physical mem). I set virtual memory to very large, and
didn't help neither. My whole datafile is only 60MB, although several lines
have 250K chars in single line/record. but such record only takes sql*loader
one minute to load if I load it individually.
However, if I load the records 100 after 100 in "append" mode (loading 100,
then load next 100 with skipping previous loaded records), it works fine,
the loader only occupied 60 meg physical mem, and released the mem when I
started next 100 manually. This is really bizzare for that sql*loader seems
doesn't know how to unload the memory if I chose to load the whole data file
automatically. I tried to manipulate the ROWS and BINDSIZE options, doesn't
help much.
Does anyone has any idea about this strange thing? Is there any other way to
load data into Oracle tables? I can't believe sql*loader will take several
days to load only 60mb exteral text file.
Thanks!
John
null

There is no 'setDescription' method available with the ordimage type. You can use putMetadata if that works for you.
Otherwise, you would have to build a custom data-type based on the ordimage type in order to store your 'description'.

SQl loader not loading records

I have my control file like this
options (skip=1)
LOAD DATA
INFILE xxx.csv
into table xxx
TRUNCATE
FIELDS TERMINATED BY ',' optionally enclosed by '"'
RECORD_STATUS,
ITEM_NUMBER,
Sql loader not loading records and giving error like .......
Commit point reached - logical record count 14
Commit point reached - logical record count 26
Commit point reached - logical record count 84
Commit point reached - logical record count 92
and successfully loaded only 41 records among 420 records
Plz help me

HI Phiri,
Thx for your reply.Here is the log file.
SQL*Loader: Release 8.0.6.3.0 - Production on Wed May 12 21:26:30 2010
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Control File: saba_price_break_allcur_test.ctl
Data File: saba_price_break_allcur_test.csv
Bad File: saba_price_break_allcur_test.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 SABA_PRICE_BREAK_ALLCUR_TEST, loaded from every logical record.
Insert option in effect for this table: TRUNCATE
Column Name Position Len Term Encl Datatype
RECORD_STATUS FIRST * , O(") CHARACTER
ITEM_NUMBER NEXT * , O(") CHARACTER
PA1 NEXT * , O(") CHARACTER
PA2 NEXT * , O(") CHARACTER
UOM_CODE NEXT * , O(") CHARACTER
RANGE_PRICING NEXT * , O(") CHARACTER
RANGE_FROM NEXT * , O(") CHARACTER
RANGE_TO NEXT * , O(") CHARACTER
PRICING_ATTRIBUTE NEXT * , O(") CHARACTER
PRICING_METHOD NEXT * , O(") CHARACTER
PRICE_BREAK_LINE_NO NEXT * , O(") CHARACTER
TEMPLATE_NAME NEXT * , O(") CHARACTER
ITEM_DESC NEXT * , O(") CHARACTER
PRICE_USD NEXT * , O(") CHARACTER
PRICE_EUR NEXT * , O(") CHARACTER
PRICE_GBP NEXT * , O(") CHARACTER
PRICE_JPY NEXT * , O(") CHARACTER
GL_ACCOUNT NEXT * , O(") CHARACTER
LONG_DESC NEXT * , O(") CHARACTER
STATUS NEXT * , O(") CHARACTER
MESSAGE NEXT * , O(") CHARACTER
Record 12: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 13: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 27: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 28: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 29: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 30: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 31: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 32: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 33: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 34: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 35: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 36: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 37: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 38: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 39: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 40: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 41: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 42: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 43: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 44: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 45: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 46: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 47: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 48: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 49: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 50: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 51: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 52: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 53: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 54: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 55: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 56: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 57: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 58: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 59: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 60: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 61: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 62: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 63: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 64: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 65: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 66: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 67: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 68: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 69: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 70: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 73: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 74: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 87: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 91: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 92: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
MAXIMUM ERROR COUNT EXCEEDED - Above statistics reflect partial run.
Table SABA_PRICE_BREAK_ALLCUR_TEST:
41 Rows successfully loaded.
51 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.
Space allocated for bind array: 65016 bytes(12 rows)
Space allocated for memory besides bind array: 0 bytes
Total logical records skipped: 1
Total logical records read: 92
Total logical records rejected: 51
Total logical records discarded: 0
Run began on Wed May 12 21:26:30 2010
Run ended on Wed May 12 21:27:06 2010
Elapsed time was: 00:00:36.08
CPU time was: 00:00:00.00

Where is SQL*Loader error message in oracle 8i documentation?

I have error message which is SQL*Loader-522: lfiopn failed for
file (D:\xiaw\Badfiles\faculty_info.BAD). I can't find the
solution from oracle 8i documentation. Can someboday help me?
Thanks
wei

Wei:
They're in Chapter 24 of the Error Messages manual:
SQL*Loader-00522 lfiopn failed for file (string)
Cause: LFI failed to open the file.
Action: Check for any possible operating system errors and/or
potential memory problems.
Hope this helps.
Peter

Need help with SQL*Loader not working

Hi all,
I am trying to run SQL*Loader on Oracle 10g UNIX platform (Red Hat Linux) with below command:
sqlldr userid='ldm/password' control=issue.ctl bad=issue.bad discard=issue.txt direct=true log=issue.log
And get below errors:
SQL*Loader-128: unable to begin a session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
Can anyone help me out with this problem that I am having with SQL*Loader? Thanks!
Ben Prusinski

Hi Frank,
More progress, I exported the ORACLE_SID and tried again but now have new errors! We are trying to load an Excel CSV file into a new table on our Oracle 10g database. I created the new table in Oracle and loaded with SQL*Loader with below problems.
$ export ORACLE_SID=PROD
$ sqlldr 'ldm/password@PROD' control=prod.ctl log=issue.log bad=bad.log discard=discard.log
SQL*Loader: Release 10.2.0.1.0 - Production on Tue May 23 11:04:28 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL*Loader: Release 10.2.0.1.0 - Production on Tue May 23 11:04:28 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Control File: prod.ctl
Data File: prod.csv
Bad File: bad.log
Discard File: discard.log
(Allow all discards)
Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array: 64 rows, maximum of 256000 bytes
Continuation: none specified
Path used: Conventional
Table TESTLD, loaded from every logical record.
Insert option in effect for this table: REPLACE
Column Name Position Len Term Encl Datatype
ISSUE_KEY FIRST * , CHARACTER
TIME_DIM_KEY NEXT * , CHARACTER
PRODUCT_CATEGORY_KEY NEXT * , CHARACTER
PRODUCT_KEY NEXT * , CHARACTER
SALES_CHANNEL_DIM_KEY NEXT * , CHARACTER
TIME_OF_DAY_DIM_KEY NEXT * , CHARACTER
ACCOUNT_DIM_KEY NEXT * , CHARACTER
ESN_KEY NEXT * , CHARACTER
DISCOUNT_DIM_KEY NEXT * , CHARACTER
INVOICE_NUMBER NEXT * , CHARACTER
ISSUE_QTY NEXT * , CHARACTER
GROSS_PRICE NEXT * , CHARACTER
DISCOUNT_AMT NEXT * , CHARACTER
NET_PRICE NEXT * , CHARACTER
COST NEXT * , CHARACTER
SALES_GEOGRAPHY_DIM_KEY NEXT * , CHARACTER
value used for ROWS parameter changed from 64 to 62
Record 1: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 2: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 3: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 4: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 5: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 6: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 7: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 8: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 9: Rejected - Error on table ISSUE_FACT_TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 10: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 11: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 12: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 13: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 14: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 15: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 16: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 17: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 18: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 19: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 20: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 21: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 22: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 23: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 24: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 39: Rejected - Error on table TESTLD, column DISCOUNT_AMT.
Column not found before end of logical record (use TRAILING NULLCOLS)
MAXIMUM ERROR COUNT EXCEEDED - Above statistics reflect partial run.
Table TESTLD:
0 Rows successfully loaded.
51 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.
Space allocated for bind array: 255936 bytes(62 rows)
Read buffer bytes: 1048576
Total logical records skipped: 0
Total logical records read: 51
Total logical records rejected: 51
Total logical records discarded: 0
Run began on Tue May 23 11:04:28 2006
Run ended on Tue May 23 11:04:28 2006
Elapsed time was: 00:00:00.14
CPU time was: 00:00:00.01
[oracle@casanbdb11 sql_loader]$
Here is the control file:
LOAD DATA
INFILE issue_fact.csv
REPLACE
INTO TABLE TESTLD
FIELDS TERMINATED BY ','
ISSUE_KEY,
TIME_DIM_KEY,
PRODUCT_CATEGORY_KEY,
PRODUCT_KEY,
SALES_CHANNEL_DIM_KEY,
TIME_OF_DAY_DIM_KEY,
ACCOUNT_DIM_KEY,
ESN_KEY,
DISCOUNT_DIM_KEY,
INVOICE_NUMBER,
ISSUE_QTY,
GROSS_PRICE,
DISCOUNT_AMT,
NET_PRICE,
COST,
SALES_GEOGRAPHY_DIM_KEY
)

"ORA-00054 Resource Busy Error" when running SQL*Loader in Parallel

Hi all,
Please help me on an issue. We are using Datastage which uses sql*loader to load data into an Oracle Table. SQL*Loader invokes 8 parallel sessions for insert on the table. When doing so, we are facing the following error intermittently:
SQL*Loader-951: Error calling once/load initialization
ORA-00604: error occurred at recursive SQL level 1
ORA-00054: resource busy and acquire with NOWAIT specifiedSince the control file is generated automatically by datastage, we cannot modify/change the options and test. Control File for the same is:
OPTIONS(DIRECT=TRUE, PARALLEL=TRUE, SKIP_INDEX_MAINTENANCE=YES)
LOAD DATA INFILE 'ora.2958.371909.fifo.1' "FIX 1358"
APPEND INTO TABLE X
x1 POSITION(1:8) DECIMAL(15,0) NULLIF (1:8) = X'0000000000000000',
x2 POSITION(9:16) DECIMAL(15,0) NULLIF (9:16) = X'0000000000000000',
x3 POSITION(17:20) INTEGER NULLIF (17:20) = X'80000000',
IDNTFR POSITION(21:40)   NULLIF (21:40) = BLANKS,
IDNTFR_DTLS POSITION(41:240)   NULLIF (41:240) = BLANKS,
FROM_DATE POSITION(241:259) DATE "YYYY-MM-DD HH24:MI:SS" NULLIF (241:259) = BLANKS,
TO_DATE POSITION(260:278) DATE "YYYY-MM-DD HH24:MI:SS" NULLIF (260:278) = BLANKS,
DATA_SOURCE_LKPCD POSITION(279:283)   NULLIF (279:283) = BLANKS,
EFFECTIVE_DATE POSITION(284:302) DATE "YYYY-MM-DD HH24:MI:SS" NULLIF (284:302) = BLANKS,
REMARK POSITION(303:1302)   NULLIF (303:1302) = BLANKS,
OPRTNL_FLAG POSITION(1303:1303)   NULLIF (1303:1303) = BLANKS,
CREATED_BY POSITION(1304:1311) DECIMAL(15,0) NULLIF (1304:1311) = X'0000000000000000',
CREATED_DATE POSITION(1312:1330) DATE "YYYY-MM-DD HH24:MI:SS" NULLIF (1312:1330) = BLANKS,
MODIFIED_BY POSITION(1331:1338) DECIMAL(15,0) NULLIF (1331:1338) = X'0000000000000000',
MODIFIED_DATE POSITION(1339:1357) DATE "YYYY-MM-DD HH24:MI:SS" NULLIF (1339:1357) = BLANKS
)- it occurs intermittently. When this job runs, no one will be accessing the database or the tables.
- When we do not run in parallel, then we are not facing the error but it is very slow (obviously).

Just in case, I am also attaching the Datastage Logs:
   Item #: 466
   Event ID: 1467
   Timestamp: 2009-06-02 23:03:19
   Type: Info
   User Name: dsadm
   Message: main_program: APT configuration file: /clu01/datastage/Ascential/DataStage/Configurations/default.apt
     node "node1"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
     node "node2"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
     node "node3"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
     node "node4"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
      node "node5"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
     node "node6"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
    node "node7"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
   node "node8"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
   Item #: 467
   Event ID: 1468
   Timestamp: 2009-06-02 23:03:20
   Type: Warning
   User Name: dsadm
   Message: main_program: Warning: the value of the PWD environment variable (/clu01/datastage/Ascential/DataStage/DSEngine) does not appear to be a synonym for the current working directory (/clu01/datastage/Ascential/DataStage/Projects/Production). The current working directory will be used, but if your ORCHESTRATE job does not start up correctly, you should set your PWD environment variable to a value that will work on all nodes of your system.
   Item #: 468
   Event ID: 1469
   Timestamp: 2009-06-02 23:03:32
   Type: Warning
   User Name: dsadm
   Message: Lkp_1: Input dataset 1 has a partitioning method other than entire specified; disabling memory sharing.
   Item #: 469
   Event ID: 1470
   Timestamp: 2009-06-02 23:04:22
   Type: Warning
   User Name: dsadm
   Message: Lkp_2: Input dataset 1 has a partitioning method other than entire specified; disabling memory sharing.
   Item #: 470
   Event ID: 1471
   Timestamp: 2009-06-02 23:04:30
   Type: Warning
   User Name: dsadm
   Message: Xfmer1: Input dataset 0 has a partitioning method other than entire specified; disabling memory sharing.
   Item #: 471
   Event ID: 1472
   Timestamp: 2009-06-02 23:04:30
   Type: Warning
   User Name: dsadm
   Message: Lkp_2: When checking operator: Operator of type "APT_LUTProcessOp": will partition despite the
preserve-partitioning flag on the data set on input port 0.
   Item #: 472
   Event ID: 1473
   Timestamp: 2009-06-02 23:04:30
   Type: Warning
   User Name: dsadm
   Message: SKey_1: When checking operator: A sequential operator cannot preserve the partitioning
of the parallel data set on input port 0.
   Item #: 473
   Event ID: 1474
   Timestamp: 2009-06-02 23:04:30
   Type: Warning
   User Name: dsadm
   Message: SKey_2: When checking operator: Operator of type "APT_GeneratorOperator": will partition despite the
preserve-partitioning flag on the data set on input port 0.
   Item #: 474
   Event ID: 1475
   Timestamp: 2009-06-02 23:04:30
   Type: Warning
   User Name: dsadm
   Message: buffer(1): When checking operator: Operator of type "APT_BufferOperator": will partition despite the
preserve-partitioning flag on the data set on input port 0.
   Item #: 475
   Event ID: 1476
   Timestamp: 2009-06-02 23:04:30
   Type: Info
   User Name: dsadm
   Message: Tgt_member: When checking operator: The -index rebuild option has been included; in order for this option to be
applicable and to work properly, the environment variable APT_ORACLE_LOAD_OPTIONS should contain the options
DIRECT and PARALLEL set to TRUE, and the option SKIP_INDEX_MAINTENANCE set to YES;
this variable has been set by the user to `OPTIONS(DIRECT=TRUE, PARALLEL=TRUE, SKIP_INDEX_MAINTENANCE=YES)'.
   Item #: 476
   Event ID: 1477
   Timestamp: 2009-06-02 23:04:35
   Type: Info
   User Name: dsadm
   Message: Tgt_member_idtfr: When checking operator: The -index rebuild option has been included; in order for this option to be
applicable and to work properly, the environment variable APT_ORACLE_LOAD_OPTIONS should contain the options
DIRECT and PARALLEL set to TRUE, and the option SKIP_INDEX_MAINTENANCE set to YES;
this variable has been set by the user to `OPTIONS(DIRECT=TRUE, PARALLEL=TRUE, SKIP_INDEX_MAINTENANCE=YES)'.
   Item #: 477
   Event ID: 1478
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Lkp_2,6: Ignoring duplicate entry at table record 1; no further warnings will be issued for this table
   Item #: 478
   Event ID: 1479
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,0: SQL*Loader-951: Error calling once/load initialization
   Item #: 479
   Event ID: 1480
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,0: ORA-00604: error occurred at recursive SQL level 1
   Item #: 480
   Event ID: 1481
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,0: ORA-00054: resource busy and acquire with NOWAIT specified
   Item #: 481
   Event ID: 1482
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,6: SQL*Loader-951: Error calling once/load initialization
   Item #: 482
   Event ID: 1483
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,6: ORA-00604: error occurred at recursive SQL level 1
   Item #: 483
   Event ID: 1484
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,6: ORA-00054: resource busy and acquire with NOWAIT specified
   Item #: 484
   Event ID: 1485
   Timestamp: 2009-06-02 23:04:41
   Type: Fatal
   User Name: dsadm
   Message: Tgt_member_idtfr,6: The call to sqlldr failed; the return code = 256;
please see the loader logfile: /clu01/datastage/Ascential/DataStage/Scratch/ora.23335.478434.6.log for details.
   Item #: 485
   Event ID: 1486
   Timestamp: 2009-06-02 23:04:41
   Type: Fatal
   User Name: dsadm
   Message: Tgt_member_idtfr,0: The call to sqlldr failed; the return code = 256;
please see the loader logfile: /clu01/datastage/Ascential/DataStage/Scratch/ora.23335.478434.0.log for details.

SQL*Loader-522

Can anyone tell me what this means, or direct me to a tutorial on this matter.
I used it to upload lots of files and there are a couple of files where I get this error message :
SQL*Loader-522: lfiopn failed for file (bnbdk.BAD)
Greetings Daffyrinzwind

SQL*Loader-522: lfiopn failed for file (name)
Cause: LFI failed to open the file.
Action: Check for any possible operating system errors and/or potential memory problems.

Code Template Design - SQL LOADER

Hi,
We extract data from 12 csv files which have 10+ million rows using SQL Loader into staging table. We use each of these tables in at least two different mappings to populate our Dimensions & Facts.
Now moving to CT's -
Using Code Template,
Code Template LCT_FILE_TO_ORACLE_SQLLDR and DEFAULT_ORACLE_TARGET_CT , i am able to load the data into the staging table. But this involves loading the data into work table and then into our Staging table. So we are loading our data twice.
So I decided to write my own code template which loads the data from file directly to staging table bypassing work table.
Developed an Integration CT which write's data directly to my staging table.
But the issue is , I am miissing the audit. The CT does not shows me any record count it processed. This might be issue since i don't have any work tables.
Is there a way we can capture audit ?
Regards,
Samurai.

Hi David,
I was thinking of getting the details from log file (using jytho) but did not know how to update the audit statistics. If you can get me that, it would be great.
I go through all your blogs :-) . I am following the baby step as per your blog :-) I am moving towards bulk loading.
Trying to design a CT
a) SQL Loader
1) Create a named pipe in unix to hold data into memory
2) Bulk load data from MYSQL or SYBASE into a named pipe
3) Then load the data into oracle table using SQLLoader
4) Drop the named pipe
OR
b) External Table
1) Bulk load data from MYSQL or SYBASE into a file ( zip the data)
2) Then load the data into oracle external table with preprocessor option
From our past experience in our current enviornment, quering or transforming data across external table with 10+ million rows was slower than a doing it across a table ( dba's will come after me for issuing such statements). So was trying to use SQL loader first.
Regards,
Samurai.
BTW You know me by other name.
Edited by: Samurai on Mar 4, 2010 3:12 PM

Can memory faults be a big problem?

I'm wondering if memory faults
a) do impact operation of an in-memory DB (and can hard- and software provider prevent it)
b) have a larger impact on in-memory DBs than on disk-based DBs
See related links:
http://en.wikipedia.org/wiki/Memory_tester
http://en.wikipedia.org/wiki/Error_detection_and_correction#Error-correcting_memory

In addition to the possibility Zeeshan mentions of keeping multiple copies in RAM, it is important to note that at least for BWA, RAM is not the primary datastore. All data is written to disk. Data is then loaded into RAM from the disk-based store when it is needed. Hopefully there is room in the RAM for all data to be loaded at all times, but BWA does not require that this is the case. I call this caching, but some disagree with that definition.
I assume, but do not know, that this is the case with HANA and the ICE as well and that all writes are logged to disk so that there is no data-loss in the event of a power or hardware failure.
The way that most in-RAM storage systems achieve transactional persistence is by writing a sequential log file (called a write-ahead-log) and flushing the log file to disk. The log file records each transaction before the client is notified that the transaction is complete. This log file can then be used to reconstruct the most recent state of the database in the event of a failure. At some point the full dataset at a point in time is reconstructed on disk, usually based on the representation in RAM, and then the log file up to that point can be discarded.
Cheers,
Ethan

SQL*Loader memory Fault

Similar Messages

Maybe you are looking for