Upgrade SQL Loader

Hi,
I am using oracle 8i client, I want to user sql loader with direct path, but it fetch some error with ORA-02371: Loader must be at least version 9.0.0.0.0 for direct path.
Is it possible to access sql loader with direct path in 8i.
Please help.
Anand

I just checked the Utilities manual and version 8.1 supports direct path; however the error indicates that direct path is not supporte for the 8.1 sqlldr program and a 10g target database.
02371, 00000, "Loader must be at least version %s.%s.%s.%s.%s for direct path"
// *Cause: The loader being used is incompatible with this version of the
// kernel.
// *Action: Upgrade your loader to at least the specified version or use the
// conventional path.
So upgrading the utility or using a conventional load are your only options. To upgrade I would think you would need to install the entire client. Note - you should be able to install into a new home and have multiple versions of the client available. You will just have to make sure the correct $ORACLE_HOME and search path are followed to run programs using the correct modules.
Again what makes you think the rest of your application will not run on a 9.2 or 10g client?
Are your sure conventional path is not fast enough? The bindsize and readsize parameters can be used to improve conventional path performance.
HTH -- Mark D Powell --

Similar Messages

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-704 and ORA-12154: error messages when trying to load data with SQL Loader

I have a data base with two tables that is used by Apex 4.2. One table has 800,000 records . The other has 7 million records
The client recently upgraded from Apex 3.2 to Apex 4.2 . We exported/imported the data to the new location with no problems
The source of the data is an old mainframe system; I needed to make changes to the source data and then load the tables.
The first time I loaded the data i did it from a command line with SQL loader
Now when I try to load the data I get this message:
sql@loader-704 Internal error: ulconnect OCISERVERATTACH
ORA-12154: tns:could not resolve the connect identifier specified
I've searched for postings on these error message and they all seem to say that SQL Ldr can't find my TNSNAMES file.
I am able to connect and load data with SQL Developer; so SQL developer is able to find the TNSNAMES file
However SQL Developer will not let me load a file this big
I have also tried to load the file within Apex (SQL Workshop/ Utilities) but again, the file is too big.
So it seems like SQL Loader is the only option
I did find one post online that said to set an environment variable with the path to the TNSNAMES file, but that didn't work..
Not sure what else to try or where to look
thanks

Hi,
You must have more than one tnsnames file or multiple installations of oracle. What i suggest you do (as I'm sure will be mentioned in ed's link that you were already pointed at) is the following (* i assume you are on windows?)
open a command prompt
set TNS_ADMIN=PATH_TO_DIRECTOT_THAT_CONTAINS_CORRECT_TNSNAMES_FILE (i.e. something like set TNS_ADMIN=c:\oracle\network\admin)
This will tell oracle use the config files you find here and no others
then try sqlldr user/pass@db (in the same dos window)
see if that connects and let us know.
Cheers,
Harry
http://dbaharrison.blogspot.com

SQL*Loader error ORA-00600 and ORA-26095

Hi all,
We have a problem with the SQL*Loader Utility. We use an 8i-Database (8.1.7) and SQL*Loader 9.2.0.1.0. We have no Trims or other functions active in the control file and do a direct path load.
It used to work properly until this morning.
Now we have the following errors (it is in German - but I can translate it):
Satz 90153: Abgelehnt - Fehler in Tabelle SCHEMA1.T_IMPORT.
ORA-00600: Interner Fehlercode, Argumente: [klaprs_50], [7], [], [], [], [], [], []
... about 50 equal errors
Specify SKIP=90171 when continuing the load.
SQL*Loader-926: OCI-Fehler; uldlm:OCIDirPathFinish fÃ¼r Tabelle SCHEMA1.T_IMPORT
ORA-26095: Nicht verarbeitete Stream-Daten vorhanden
SQL*Loader-2026: Der Ladevorgang wurde abgebrochen, weil er nicht fortgesetzt werden kann.
Specify SKIP=90171 when continuing the load.
Trnaslation:
00600 - Internal error code, arguments: ...
OCI-Fehler = OCI error
fÃ¼r Tabelle = for table
ORA-26095: Nicht verarbeitete Stream-Daten vorhanden = Non processed stream data existing
SQL*Loader-2026: Der Ladevorgang wurde abgebrochen, weil er nicht fortgesetzt werden kann. = Load process has been cancelled as it cannot be continued.
Has anyone got a clue?!?!?!

Hi,
It's very clear that import 9i is for an import into 9i database.
Upgrade 8i to 9i indicates that we can make an export 8i from 8i database and import 9i into 9i database, but never use a tools like export from other version...
If you want import data from 9i database into 8i use exp tools 8i, and imp 8i.
I devise you to read Metalink note 132904.1 - compatibility matrix for export & import between different oracl version.
Nicolas.

Is there any difference in Oracle 9i SQL Loader and Oracle 10g SQL Loader

Hi
Can anyone tell me whether is there any difference in Oracle 9i SQL Loader and Oracle 10g SQL Loader?
I am upgrading the 9i db to 10g and wanted to run the 9i SQL Loader control files on upgraded 10g db. So please let me know is there any difference which I need to consider any modifications in the control files..
Thank you in advance
Adi

answered

SQL*Loader-273: READBUFFERS may be used only in direct path.

Hi,
I am trying to upgrade from OWB 10G to 11G. y map from flat file to stage maps work fine in 10G. when i upgrade the maps to 11G i get the error:
Error
RPE-01013: SQL Loader reported error condition, number 1.
SQL*Loader: Release 11.1.0.7.0 - Production on Fri May 8 15:10:20 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL*Loader-273: READBUFFERS may be used only in direct path.
SQL*Loader: Release 11.1.0.7.0 - Production on Fri May 8 15:10:20 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL*Loader-273: READBUFFERS may be used only in direct path.
if i go to configure and make the READBUFFERS to = 0 then the map works fine. this used to work fine in 10G. I compared the .CTL file of sql loder and i notice the 10G sql loader file did not care for this property being set. while in 11G .ctl file i see the readbuffer property being set. though i can make the map run in 11G i can not go to each map and then reset it. ...Please help.
Thanks

IN 10 G environment
a.)Direct path = False.
b.) Read buffers = 4 (defaults to 4)
10G Code generated :
-- Oracle Warehouse Builder
-- Generator Version : 10.1.0.4.0
-- Created Date : Mon May 11 10:16:31 CDT 2009
-- Modified Date : Mon May 11 10:16:31 CDT 2009
-- Created By : owb_repository
-- Modified By : owb_repository
-- Generated Object Type : SQL*Loader Control File
-- Generated Object Name : GFHGF
-- © 2003 Oracle Corporation. All Rights Reserved.
OPTIONS ( ERRORS=50, BINDSIZE=50000, ROWS=200, READSIZE=65536)
LOAD DATA
CHARACTERSET WE8MSWIN1252
INFILE 'C:\EAND.dat'
INTO TABLE "{{ORACLE10G.Schema}}"."EAND"
APPEND
REENABLE DISABLED_CONSTRAINTS
FIELDS
"PERSON_SSN_SOURCE" POSITION (3:3) CHAR
IN 11 G environment
a.)Direct path = False.
b.) Read buffers = 4 (for new maps crated defaults to 0)
-- Generator Version : 11.1.0.7.0
-- Created Date : Mon May 11 10:06:37 CDT 2009
-- Modified Date : Mon May 11 10:06:37 CDT 2009
-- Created By : OWB_WUSER
-- Modified By : OWB_WUSER
-- Generated Object Type : SQL*Loader Control File
-- Generated Object Name : "GFHGF"
-- Copyright © 2000, 2007, Oracle. All rights reserved.
OPTIONS (BINDSIZE=50000,ERRORS=50,ROWS=200,READSIZE=65536)
LOAD DATA
CHARACTERSET WE8MSWIN1252
INFILE '{{ETL_FILE_LOC.RootPath}}{{}}EAND.dat''
BADFILE '{{ETL_FILE_LOC.RootPath}}{{}}EAND'
READBUFFERS 4
CONCATENATE 1
INTO TABLE "STAG"."EAND"
TRUNCATE
REENABLE DISABLED_CONSTRAINTS
"PERSON_SSN_SOURCE" POSITION (3:3) CHAR
my question is even as both the properties in 10G and 11G are same why does .ctl file generated in 11G has statement "READBUFFERS 4" while this is neglected in owb 10G generated .ctl file? Please Help.
Edited by: user591315 on May 11, 2009 8:14 AM
Edited by: user591315 on May 11, 2009 8:16 AM

Running SQL Loader through PL/SQL

Hi All,
Is there a utility package that can be used to run SQL LOADER through PL/SQL?
Regards

External tables are new in 9i.
If you need to call SQL*Loader in 8i, you'd be stuck with the Java stored procedure/ external procedure approach. Of course, this might also be an impetus to upgrade, since 8.1.7 leaves error correction support at the end of the year.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

SQL Loader + CLOB

Dear buddies,
Please guide me with this.
LOAD DATA
INFILE 'D:\load\dat\Enquiry_reply.dat'
BADFILE 'D:\load\bad\Enquiry_reply.bad'
DISCARDFILE 'D:\load\dat\discard\Enquiry_reply.dsc'
replace INTO TABLE OES_Enquiry FIELDS TERMINATED BY '['
*(Reply CLOBFILE("D:\load\dat\oes_enquiry_reply.dat") TERMINATED BY '[')*
Whats wrong here in this?
I am getting error:
SQLLoader-350: Syntax error at line 6.*
Expecting "," or ")", found "CLOBFILE".
*(Reply CLOBFILE("D:\load\dat\enquiry_reply.dat") TERMINATED BY '['*
Please advice me on how to go about it.
Thanks in advance.
Nith

This forum is meant for issues with database upgrades - pl re-post in the SQL*Loader forum (Export/Import/SQL Loader & External Tables
HTH
Srini

SQL*Loader-524 using sqlldr

I am getting the following error while running sqlldr80 on 8.0.6.3.1 version.
SQL*Loader-524: partial record found at end of datafile
I followed metalink note 1058890.6 that tells about the bug 735710.
The problem gets resolved when I give a line feed end of datafile.
My problem is the whole system has to be automated where I cannot manually provide a new line in datafile that is automatically placed in a directory from where sqlldr reads it.
Please advice.

You can simply process the file by sed on Unix (on Windows you can implement cygwin to add Unix functionality) or by Perl (works on both Windows and Unix) to add that extra linefeed automatically.
Which obviously is a workaround. You would better upgrade from Oracle 8.0.6, which was desupported many, many years ago.
Sybrand Bakker
Senior Oracle DBA

How to load a default value in to a column when using sql loader

Im trying to load from a flat file using sql loader.
for 1 column i need to update using a default value
how to go about this?

Hi!
try this code --
LOAD DATA
   INFILE 'sample.dat'
   REPLACE
   INTO TABLE emp
   empno   POSITION(01:04) INTEGER EXTERNAL NULLIF empno=BLANKS,
   ename   POSITION(06:15) CHAR,
   job         POSITION(17:25) CHAR,
   mgr       POSITION(27:30) INTEGER EXTERNAL NULLIF mgr=BLANKS,
   sal        POSITION(32:39) DECIMAL EXTERNAL NULLIF sal=BLANKS,
   comm   POSITION(41:48) DECIMAL EXTERNAL DEFAULTIF comm = 100,
   deptno POSITION(50:51) INTEGER EXTERNAL NULLIF deptno=BLANKS,
   hiredate POSITION(52:62) CONSTANT SYSDATE
)-hope this will solve ur purpose.
Regards.
Satyaki De.

How can we tell if SQL*Loader is working on a TABLE?

We have a process that requires comparing batches with LDAP information. Instead of using an LDAP lookup tool, we get a nightly directory file, and import the two COLUMNs we want via SQL*Loader (REPLACE) into an IOT. Out of three cases, two just check the first COLUMN, and the third needs the second COLUMN as well.
We did not think of using External TABLEs, because we cannot store files on the DB server itself.
The question arises, what to do while the file is being imported. The file is just under 300M, so it takes a minute or so to replace all the data. We found SQL*Loader waits until a transaction is finished before starting, but a query against the TABLE only waits while it is actually importing the data. At the beginning of SQL*Loader's process, however, a query against the TABLE returns no rows.
The solution we are trying right now is, to have the process that starts SQL*Loader flip a flag in another TABLE denoting that it is unavailable. When it is done, it flips it back, and notes the date. Then, the process that queries the information, exits if the flag is currently 'N'.
The problem, is, what if SQL*Loader starts inbetween the check of the flag, and the query against the TABLE. How do we guarantee that it is still not being imported.
I can think of three solutions:
1) LOCK the ldap information TABLE before checking the flag.
2) LOCK the record that the process starting SQL*Loader flips.
3) Add a clause to the query against the TABLE checks that there are records in the TABLE (AND EXISTS(SELECT * FROM ldap_information).
The problem with 3) is that the process has already tagged the batches (via a COLUMN). It could, technically reset them afterwards, but that seems a bit backwards.

Just out of curiosity, are you aware that Oracle supplies a DBMS_LDAP package for pulling information from LDAP sources? It would obviously be relatively easy to have a single transaction that deletes the existing data, loads the new data via DBMS_LDAP, and commits, which would get around the problem you're having with SQL*Loader truncating the table.
You could also have SQL*Loader load the data into a staging table and then have a second process either MERGE the changes from the staging table into the real table (again in a transactionally consistent manner) or just delete and insert the data.
Justin

Loading two tables at same time with SQL Loader

I have two tables I would like to populate from a file C:\my_data_file.txt.
Many of the columns I am loading into both tables but there are a handful of columns I do not want. The first column I do not want for either table. My problem is how I can direct SQL Loader to go back to the first column and skip over it. I had tried using POSITION(1) and FILLER for the first column while loading the second table but I got THE following error message:
SQL*Loader-350: Syntax error at line 65
Expecting "," or ")" found keyword Filler
col_a Poistion(1) FILLER INTEGER EXTERNALMy control file looks like the following:
LOAD DATA
INFILE 'C:\my_data_file.txt'
BADFILE 'C:\my_data_file.txt'
DISCARDFILE 'C:\my_data_file.txt'
TRUNCATE INTO TABLE table_one
WHEN (specific conditions)
FIELDS TERMINATED BY ' '
TRAILING NULLCOLS
col_a FILLER INTEGER EXTERNAL,
col_b INTEGER EXTERNAL,
col_g FILLER CHAR,
col_h CHAR,
col_date DATE "yyyy-mm-dd"
INTO TABLE table_two
WHEN (specific conditions)
FIELDS TERMINATED BY ' '
TRAILING NULLCOLS
col_a POSITION(1) FILLER INTEGER EXTERNAL,
col_b INTEGER EXTERNAL,
col_g FILLER CHAR,
col_h CHAR,
col_date DATE "yyyy-mm-dd"
)

Try adapting this for your scenario.
tables for the test
create table test1 ( fld1 varchar2(20), fld2 integer, fld3 varchar2(20) );
create table test2 ( fld1 varchar2(20), fld2 integer, fld3 varchar2(20) );
control file
LOAD DATA
INFILE "test.txt"
INTO TABLE user.test1 TRUNCATE
WHEN RECID = '1'
FIELDS TERMINATED BY ' '
recid filler integer external,
fld1 char,
fld2 integer external,
fld3 char
INTO TABLE user.test2 TRUNCATE
WHEN RECID <> '1'
FIELDS TERMINATED BY ' '
recid filler position(1) integer external,
fld1 char,
fld2 integer external,
fld3 char
data for loading [text.txt]
1 AAAAA 11111 IIIII
2 BBBBB 22222 JJJJJ
1 CCCCC 33333 KKKKK
2 DDDDD 44444 LLLLL
1 EEEEE 55555 MMMMM
2 FFFFF 66666 NNNNN
1 GGGGG 77777 OOOOO
2 HHHHH 88888 PPPPP
HTH
RK

Creating SQL-Loader script for more than one table at a time

Hi,
I am using OMWB 2.0.2.0.0 with Oracle 8.1.7 and Sybase 11.9.
It looks like I can create SQL-Loader scripts for all the tables
or for one table at a time. If I want to create SQL-Loader
scripts for 5-6 tables, I have to either create script for all
the tables and then delete the unwanted tables or create the
scripts for one table at a time and then merge them.
Is there a simple way to create migration scripts for more than
one but not all tables at a time?
Thanks,
Prashant Rane

No there is no multi-select for creating SQL-Loader scripts.
You can either create them separately or create them all and
then discard the one you do not need.

SQL Loader (Oracle 8.1.5 on Suse 6.3) Internal Error

Hi all,
I try to insert data with SQL Loader on Linux (Suse 6.3) and get the following message:
SQL*Loader-704: Internal error: ulmtsyn: OCIStmtExecute (tabhp) [-1073747572]
ORA-00942: table or view does not exist
The control file and data file did work on another platform.
Please help me!
Thanks,
Thies Mauker

Lee Bennett (guest) wrote:
:Hi
:I have successfully installed Oracle 8.1.5 Enterprise edition
on
:Suse 6.2 and applied the 8.1.5.0.1 patch set,
NO!
SuSe 6.2 have a patch file for Oracle made from their developers.
Never use Oracle 8.1.5.0.1 patch file that doesn't work because
us bugged.
Use SuSe 6.2 Oracle patch set.
(don't remember the web page where you can download it but a
search with word "oracle" from SuSe homepage will lead you to
it)
-Stefano
null

Decode Not working in sql loader

I had a requirement of loading flatfile into staging table using SQL Loader, One of the columns in the the Flat file is having values FALSE or TRUE and my requirement is that I load 0 for FALSE and 1 for TRUE which can be achieved by simple DECODE function...I did use decode and tried to load several times but did not work. What might be the problem
LOAD DATA
INFILE 'sql_4ODS.txt'
BADFILE 'SQL_4ODS.badtxt'
APPEND
INTO TABLE members
FIELDS TERMINATED BY "|"
( Person_ID,
FNAME,
LNAME,
Contact,
status "decode(:status, 'TRUE', '1','FALSE','0')"
I did try putting a trim as well as SUBSTR but did not work....the cloumn just doent get any values in the output (just null or say free space)
Any help would be great.....

Hello user8937215.
Please provide a create table statement and a sample of data file contents. I would expect DECODE or CASE to work based on the information provided.
Cheers,
Luke
Please mark the answer as helpful or answered if it is so. If not, provide additional details.
Always try to provide create table and insert table statements to help the forum members help you better.

Upgrade SQL Loader

Similar Messages

Maybe you are looking for