SQL * Loader loading ORDSYS object setting properties

Hi,
I have table where am storing image as ORDSYS.ORDIMAGE.
I am using SQL*loader to load the image coloum. Below shown is the extract of the load file
Image COLUMN OBJECT
          source COLUMN OBJECT
               localData_fname FILLER CHAR(128),
               localData LOBFILE (Image.source.localData_fname) TERMINATED BY EOF
with this, I am able to load the image. now i want to set the other properties of ORDImage object like description.
How can i do that? please can anyone help me in this?
Edited by: 896943 on Dec 8, 2011 6:23 PM

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

Similar Messages

  • Urgent :SQL Loader Arabic Character Set Issue

    HI all,
    I am loading arabic characters into my database using SQL Loader using a fixed length data file. I had set my characterset and NLS_LANG set to UTF8.When I try to load the chararacter 'B' in arabic data i.e. ' لا ' , it gets loaded as junk in the table. All other characters are loaded correctly. Please help me in this issue and its very urgent.
    Thanks,
    Karthik

    Hi,
    Thanks for the responses.
    Even after setting the characterset to arabic and the problem continues to persist. This problem occurs only with the character "b".
    Please find my sample control file,input file and nls_parameters below:
    My control file
    LOAD DATA
    characterset UTF8
    LENGTH SEMANTICS CHAR
    BYTEORDER little endian
    INFILE 'C:\sample tape files\ARAB.txt'
    replace INTO TABLE user1
    TRAILING NULLCOLS
    name POSITION(1:2) CHAR(1),
    id POSITION (3:3) CHAR(1) ,
    salary POSITION (4:5) CHAR(2)
    My Input file - Fixed Format
    ?a01
    ??b02
    ?c03
    The ? indicates arabic characters.Arabic fonts must be installed to view them.
    NLS_PARAMETERS
    PARAMETER     VALUE
    NLS_LANGUAGE     ARABIC
    NLS_TERRITORY     UNITED ARAB EMIRATES
    NLS_CURRENCY     ?.?.
    NLS_ISO_CURRENCY     UNITED ARAB EMIRATES
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD/MM/RR
    NLS_DATE_LANGUAGE     ARABIC
    NLS_SORT     ARABIC
    NLS_TIME_FORMAT     HH12:MI:SSXFF PM
    NLS_TIMESTAMP_FORMAT     DD/MM/RR HH12:MI:SSXFF PM
    NLS_TIME_TZ_FORMAT     HH12:MI:SSXFF PM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD/MM/RR HH12:MI:SSXFF PM TZR
    NLS_DUAL_CURRENCY     ?.?.
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     CHAR
    NLS_NCHAR_CONV_EXCP     FALSE

  • SQL*Loader - How to set numeric seperator in Controlfile for float external

    I need to use "FLOAT EXTERNAL" instead of "to_number" and I want ensure that the correct numeric separator is set.
    At "to_number it look like:
    col1 "to_number(:col1,'99999999999999999.99999999999999999','NLS_NUMERIC_CHARACTERS=''.,''')")
    But how should I set the numeric separator at this case, without changing datatype FLOAT EXTERNAL?
    LOAD DATA
    INFILE "test.dat"
    INTO TABLE "t1" REPLACE
    FIELDS TERMINATED BY "     "
    TRAILING NULLCOLS
    "c1" FLOAT EXTERNAL
    I need a way to set the numericseparator in the controlfile, for the whole controlfile or for the "FLOAT EXTERNAL" column.
    Can someone give me an advice?
    BR
    roland

    Sure I could set it at environment, but I write a program which generate controlfiles for the datafiles, because this I want ensure that the datafiles can be correct imported independed of the environment settings.
    So a need a way to set it in the controlfile:(.

  • Add "Trailing Nullcolls" to sql loader control files generated by OWB

    Hi gurus,
    I've got a problem loading data with SQL Loader. I need to add the parameter "trailing nullcols" into the SQL Loader control file generated by OWB. I don't want to do this by saving the skript on my hard disk and run it manually, so any ideas where I can put this parameter? I am using OWB 10.1 on a windows 2000 machine.
    Thanks
    Stephan

    Hi,
    I found the solution to problem.
    1; Select the mapping where you map your source flat file to a table.
    2; Right click on the mapping and select "configure"
    3; Go Sources and Targets -> YOUR_TABLE_NAME -> SQL*Loader Parameters
    4; Set Trailing Nullcols = true :-)
    Thank you to anyone looking at this problem.
    Greetings
    Stephan

  • SQL*Loader characterset

    Database: 10.2.0.1
    sql> select * from nls_database_parameters t where t.parameter like '%CHARACTERSET%';
    PARAMETER VALUE
    ==============================================
    NLS_CHARACTERSET AL32UTF8
    NLS_NCHAR_CHARACTERSET AL16UTF16
    OS: RHEL5
    $ export | grep LANG
    declare -x LANG="en_US.UTF-8"
    declare -x NLS_LANG="GERMAN_GERMANY.WE8ISO8859P1"
    I have file in latin1 codepage.
    When I create external table (organization external type oracle_loader) I have problems with loading the Ü symbols in this file to the database:
    a;b;c;Ü;d <- row inserted
    Ü;a;b;c;d <- row inserted
    a;b;c;d;Ü <- row failed to insert
    KUP-04021: field formatting error for 1 field
    KUP-04101: record 1 rejected in file latin1.csv
    When I explicitly create external table with "characterset WE8ISO8859P1" clause the latin1 file loads successfully.
    When I load the UTF8 file using external table which was created without clause "characterset WE8ISO8859P1" the file is loads OK too.
    I want to know the process - why the characterset conversion from latin1 file (WE8ISO8859P1) to UTF8 database for some reason fails?
    Is there possible to import latin1 files and do not specify the codepage in the external table DDL (seems that NLS_LANG env variable does not affect SQL*Loader external table)?
    From documentation:
    Specifying the CHARACTERSET parameter tells SQL*Loader the character set of the input datafile. The default character set for all datafiles, if the CHARACTERSET parameter is not specified, is the session character set defined by the NLS_LANG parameter. Only character data (fields in the SQL*Loader datatypes CHAR,  VARCHAR, VARCHARC, numeric EXTERNAL, and the datetime and interval datatypes) is affected by the character set of the datafile.
    Edited by: lynx™ on 15.07.2010 7:46

    Hi Andre,
    this is how I teach my classes normally!
    You need to be aware of some changes you make with NLS_TERRITORY, which is part of NLS_LANG:
    --> if you set NLS_TERRITORY to anohter value then you implicitly change the settings for NLS_NUMERIC_CHARACTERS => , although it is the same with america and australia obviousely the first digit here is the decimal separator and the second one is the grand seperator, thisn can destroy all numeric values if it is set impropper !!!
    NLS_DATE_FORMAT,
    NLS_TIMESTAMP_FORMAT,
    AND NLS_CURRENCY.
    SYS @10gR2 SQL select * from v$nls_parameters
    PARAMETER VALUE
    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AMERICA
    NLS_CURRENCY $
    NLS_ISO_CURRENCY AMERICA
    NLS_NUMERIC_CHARACTERS .,NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT DD-MON-RRNLS_DATE_LANGUAGE AMERICAN
    NLS_CHARACTERSET WE8ISO8859P1
    NLS_SORT BINARY
    NLS_TIME_FORMAT HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY $
    NLS_NCHAR_CHARACTERSET AL16UTF16
    NLS_COMP BINARY
    NLS_LENGTH_SEMANTICS BYTE
    NLS_NCHAR_CONV_EXCP FALSE
    19 rows selected.
    SYS @10gR2 SQL > alter session set NLS_TERRITORY=australia;
    SYS @10gR2 SQL > select * from v$nls_parameters
    2 ;
    PARAMETER VALUE
    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AUSTRALIA
    NLS_CURRENCY $
    NLS_ISO_CURRENCY AUSTRALIA
    NLS_NUMERIC_CHARACTERS .,
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT DD/MON/RR
    NLS_DATE_LANGUAGE AMERICAN
    NLS_CHARACTERSET WE8ISO8859P1
    NLS_SORT BINARY
    NLS_TIME_FORMAT HH12:MI:SSXFF AM
    NLS_TIMESTAMP_FORMAT DD/MON/RR HH12:MI:SSXFF AM
    NLS_TIME_TZ_FORMAT HH12:MI:SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT DD/MON/RR HH12:MI:SSXFF AM TZR
    NLS_DUAL_CURRENCY $
    NLS_NCHAR_CHARACTERSET AL16UTF16
    NLS_COMP BINARY
    NLS_LENGTH_SEMANTICS BYTE
    NLS_NCHAR_CONV_EXCP FALSE

  • FORCE_LOGGING=YES and Unrecoverable option of SQL LOADER

    Hi All,
    I have small query regarding FORCE_LOGGING=YES and Unrecoverable option of SQL Loader.
    We have our Database set with FORCE_LOGGING=YES option.
    We have huge amount of transaction happen using SQL Loader. For the SQL Loader we have set the option direct=true and unrecoverable.
    The Unrecoverable option won't generate the redo logs while loading, but as we have FORCE_LOGGING=YES.
    Whice option will take effect? Will it still generate redo logs?
    Thanks for your help,
    Manoj

    Yes - it will still generate redo. Like I wrote, setting FORCE_LOGGING = TRUE for the database utterly guarantees there will be no nologging operations.
    In fact, only direct path inserts have the option of being nologging in the first place. Non direct path (aka conventional) inserts always generate redo anyway.
    There is a lot of confusion around this area of Oracle, and I don't think it's documented as well as it could be. If you're still a little unsure, asktom.oracle.com is an excellent website where you can find further explanation (search for 'nologging').

  • Sql*loader converst float to scientific format.

    hi all,
    I have a table x with a column "colx" defined as a float(64). this column has values in it as follows: x.colx = 12345678.9123456
    I create another table y with, you guessed it, "coly" as float(64).
    If I create a sql*loader dat file called x2y.dat with the float data and load it into sql*loader as a float it converts it to scientific format.
    Is there a way of avoiding this conversion.
    Thanks all in advanced,
    signed, oracle tard.

    All, just some additional info that I dug up on Metalink that will help when unloading data from an oracle db and inserting it into another db using sql*loader. This script will ensure the float is preserved.
    rocr
    -- unload_fixed.sql
    set tab off
    set heading off feedback off echo off verify off
    set space 1 pagesize 0 linesize 120
    accept owner prompt 'What schema owns the table to be unloaded? '
    accept table_name prompt 'What table is to be unloaded? '
    accept default_precision prompt 'No. of digits for precision: '
    accept default_scale prompt 'No. of digits for scale? '
    -- Generate the unload script
    spool unload_fixed2.sql
    select 'SET HEADING OFF FEEDBACK OFF ECHO OFF VERIFY OFF'||chr (10)||
    'SET SPACE 0 PAGESIZE 0 TERMOUT OFF TRIMSPOOL ON'
    from dual;
    -- Calculate the sum of all output field lengths and set the output record size
    select 'SET LINESIZE '||
    (sum (decode (data_type,
    'CHAR', data_length,
    'VARCHAR', data_length,
    'VARCHAR2', data_length,
    'DATE', 14,
    'NUMBER', decode (data_precision, '',
    &default_precision + 2,
    greatest (data_precision - data_scale, 1) +
    decode (data_scale, 0, 0, 1) + data_scale) + 1,
    'FLOAT', &default_precision + 2,
    data_length)))
    from dba_tab_columns
    where owner = upper ('&&owner') and
    table_name = upper ('&&table_name');
    -- Generate an appropriate SQL*Plus COLUMN command to control
    -- formatting of each output field
    select 'COLUMN '||rpad ('"'||column_name||'"', 32)||' FORMAT '||
    rpad (decode (data_type,
    'CHAR', 'A'||data_length,
    'VARCHAR2', 'A'||data_length,
    'VARCHAR', 'A'||data_length,
    'DATE', 'A14',
    'NUMBER', decode (data_precision, '',
    rpad ('0', &default_precision - &default_scale,
    '9')||'.'||rpad ('9', &default_scale, '9'),
    rpad ('0', greatest (data_precision -
    data_scale, 1), '9')||decode (data_scale, 0, '',
    '.')||decode (data_scale, 0, '',
    rpad ('9', data_scale, '9'))),
    'FLOAT', rpad ('0', &default_precision - &default_scale,
    '9')||'.'||rpad ('9', &default_scale, '9'),
    'ERROR'),40)||' HEADING ''X'''
    from dba_tab_columns
    where owner = upper ('&&owner') and
    table_name = upper ('&&table_name')
    order by column_id;
    -- Generate the actual SELECT statement to unload table data
    select 'SPOOL &&owner..&&table_name..DAT' from dual;
    column var1 noprint
    column var2 noprint
    select 'a' var1, 0 var2, 'SELECT '
    from dual
    union
    select 'b', column_id, decode (column_id, 1, ' ', ' , ')||
    decode (data_type, 'DATE', 'to_char ('||'"'||column_name||
    '"'||', ''YYYYMMDDHH24MISS'') '||'"'||column_name||'"',
    '"'||column_name||'"')
    from dba_tab_columns
    where owner = upper ('&&owner') and
    table_name = upper ('&&table_name')
    union
    select 'c', 0, 'FROM &&owner..&&table_name'
    from dual
    union
    select 'd', 0, ';'
    from dual
    order by 1,2;
    select 'SPOOL OFF' from dual;
    select 'SET TERMOUT ON' from dual;
    spool off
    -- Generate the SQL*Loader control file
    set lines 120 pages 0
    spool &&owner..&&table_name..CTL
    select 'a' var1, 0 var2, 'OPTIONS(DIRECT=TRUE)'
    from dual
    union
    select 'b', 0, 'LOAD DATA'
    from dual
    union
    select 'c', 0, 'INFILE ''&&owner..&&table_name..DAT'''
    from dual
    union
    select 'd', 0, 'BADFILE &&owner..&&table_name..BAD'
    from dual
    union
    select 'e', 0, 'DISCARDFILE &&owner..&&table_name..DSC'
    from dual
    union
    select 'f', 0, 'DISCARDMAX 999'
    from dual
    union
    select 'm', 0, 'INTO TABLE &&owner..&&table_name'
    from dual
    union
    select 'n', column_id, rpad (decode (column_id, 1, '(', ',')||
    '"'||column_name||'"', 31)||
    decode (data_type,
    'CHAR', 'CHAR('||data_length||')',
    'VARCHAR', 'CHAR('||data_length||')',
    'VARCHAR2', 'CHAR('||data_length||')',
    'DATE', 'DATE(14) "YYYYMMDDHH24MISS"',
    'NUMBER', 'DECIMAL EXTERNAL ('||decode (data_precision,
    '', &default_precision + 2,
    greatest (data_precision - data_scale, 1) +
    decode (data_scale, 0, 0, 1) + data_scale + 1)||')',
    'FLOAT', 'DECIMAL EXTERNAL ('||to_char (&default_precision +
    2)||')', 'ERROR--'||data_type)||' NULLIF ("'||
    column_name||'" = BLANKS)'
    from dba_tab_columns
    where owner = upper ('&&owner') and
    table_name = upper ('&&table_name')
    union
    select 'z', 0, ')'
    from dual
    order by 1, 2;
    spool off
    -- Cleanup
    clear column
    clear break
    clear compute
    undef owner
    undef table_name
    undef default_precision
    undef default_scale

  • General class and setting properties vs specific inner class

    This is a general question for discussion. I am curious to know how people differentiate between instantiating a standard class and making property adjustments within a method versus defining a new inner class with the property adjustments defined within.
    For example, when laying out a screen do you:
    - instantiate all the objects, set properties, and define the layout all within a method
    - create an inner class that defines the details of the layout (may reference other inner classes if complex) that is then just instantiated within a method
    - use some combination of the two depending on size and complexity.
    - use some other strategy
    Obviously, by breaking the work up into smaller classes you are simplifying the structure since each class is taking on less responsibility, as well as hiding the details of the implementaion from higher level classes. On the other hand, if you are just instantiating an object and making some SET calls is creating an inner class overkill.
    Is there a general consensus for an approach? I am curious to hear the approach of others.

    it's depends on your design..
    usually, if the application is simple and is not expected to be maintain (update..etc..) than I just have all the building of the gui within the same class (usually..the main class that extends JFrame).
    if the application follows the MVC pattern, than I would have a seperate class that build the GUI for a particular View. I would create another class to handle the ActionEvent, and other event (Controller)
    I rarely use inner class...and only use them to implements the Listerner interface (but only for simple application)..

  • Loading Objects with SQL*Loader

    When loading a column object with SQL*Loader, is it possible to specify a column specific 'TERMINATED BY' clause in the control file?
    I've successfully defined column-level termination characters for regular columns and nested tables, but can't seem to find any way of achieving the same result with column objects.

    When loading a column object with SQL*Loader, is it possible to specify a column specific 'TERMINATED BY' clause in the control file?
    I've successfully defined column-level termination characters for regular columns and nested tables, but can't seem to find any way of achieving the same result with column objects.

  • SQL Loader:  Is it possible to set a variable?

    Hallo All,
    I am loading data with SQL Loader and find that I can set particular fields to particular values using 'CONSTANT'. That's great. However, I am loading multiple files into the same format and so would like to 'label' each load. This would be done by setting a variable before each load and then using this to write the load month (e.g. '200901') into the column 'SOURCE_FILE' in the destination table.
    I imagine the syntax would look something like this ...
    LOAD DATA
    strSource = '200809'
    INFILE 'source_data_200809.csv'
    strSource = '200810'
    INFILE 'source_data_200810.csv'
    strSource = '200811'
    INFILE 'source_data_200811.csv'
    APPEND
    INTO TABLE DESTINATION_TABLE
    FIELDS TERMINATED BY ";" OPTIONALLY ENCLOSED BY '"'
    TRAILING NULLCOLS
    (CUSTNO char,
    BARCODE char,
    NAME char,
    SOURCE_FILE char :strSource)
    Then, for each load I would reference the variable strSource and write the appropriate month into a column/field in the table.
    I have been googling and trawling through the documentation but I cannot seem to find a way to do this. Is it possible? Or maybe there is another method/way/trick to do this? Or maybe it is just a question of syntax?
    Any ideas?
    Regards,
    Alan Searle

    Hi Kamran,
    I took a look at that thread and there were some tips including details about sending parameters through the command line ...
    SQLLDR CONTROL=controlfile.ctl, DATA=yourdatafile.csv
    But here I would need to also be able to send a parameter that I could pick up and use within SQL Loader. This might be ...
    SQLLDR CONTROL=controlfile.ctl, DATA=source_data_200809.csv VAR=200809
    ... here I would write the value '200809' to a column in the table being loaded (so that I could track back to the source of the load).
    I checked the documentation but it doesn't seem to be possible to send a variable in this way.
    Any other tips?
    Regards,
    Alan

  • How to set default directory for SQL LOADER

    hi all,
    i wanted to know how can we setup a default directory for SQL LOADER if at all we can. i connot place my control and data files in local system and use them at command prompt. rather i wanted to know if we can set default directory that the loader can use. this requirement is basically to enable all the clients to upload the data placed on the server and use the loader utility.
    thanks in advance,
    Basavraj

    Ella,
    You don't say which version of SQL Developer you are using via Citrix, but just setting the SQLDEVELOPER_USER_DIR hasn't worked for a long time (see Re: SQLDEVELOPER_USER_DIR does not function anymore). Also, since version 1.5, the default for the user directory (now set via ide.user.dir as shown below) is under the user profile area (relative to %APPDATA%), which you should be able to write to, even on Citrix.
    Assuming that neither of those help, you will need to get whoever installed SQL Developer on the Citrix C: drive to modify the sqldeveloper.conf to have a line like, where the path exists for everyone who will be using the shared SQL Developer (assumes everyone has a H: drive):
    AddVMOption -Dide.user.dir=H:\sqldeveloperAn alternative (depending on how you start SQL Developer via Citrix), is to create your own shortcut to start SQL Developer with something like:
    sqldeveloper -J-Dide.user.dir="%SQLDEVELOPER_USER_DIR%"theFurryOne

  • SQL*Loader-282: Unable to locate character set handle for character set ID

    How do I fix this error that i'm getting when running SQL Loader and connecting to an Oracle 10g database. I'm on 10g client.
    SQL*Loader-282: Unable to locate character set handle for character set ID (46).
    Here's the NLS parameter settings in database: select * from v$nls_parameters
    PARAMETER     VALUE
    NLS_LANGUAGE     AMERICAN
    NLS_TERRITORY     AMERICA
    NLS_CURRENCY     $
    NLS_ISO_CURRENCY     AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD-MON-RR
    NLS_DATE_LANGUAGE     AMERICAN
    NLS_CHARACTERSET     WE8ISO8859P15
    NLS_SORT     BINARY
    NLS_TIME_FORMAT     HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY     $
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     CHAR
    NLS_NCHAR_CONV_EXCP     TRUE
    Message was edited by:
    evo

    Yep that's it, thanks, I found out about V$NLS_PARAMETERS:
    SQL> select * from v$nls_parameters;
    PARAMETER                  VALUE
    NLS_LANGUAGE               AMERICAN
    NLS_TERRITORY              AMERICA
    NLS_CURRENCY               $
    NLS_ISO_CURRENCY           AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CALENDAR               GREGORIAN
    NLS_DATE_FORMAT            DD-MON-RR
    NLS_DATE_LANGUAGE          AMERICAN
    NLS_CHARACTERSET           WE8ISO8859P1
    NLS_SORT                   BINARY
    NLS_TIME_FORMAT            HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT       DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT         HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT    DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY          $
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_COMP                   BINARY
    NLS_LENGTH_SEMANTICS       BYTE
    NLS_NCHAR_CONV_EXCP        FALSEGiven that 9i is not available for Solaris x86,
    how do I change NLS_NCHAR_CHARACTERSET to something that
    will work, like UTF-8?
    Thanks
    Ed

  • SQL Loader Constraints with Column Objects and Nested Tables

    I am working on loading a Table that (god forbid) contains columns, column objects, and nested tables (which contains several depth of column objects). My question is does SQL Loader have a hidding undocumented feature where it states how the column objects must be grouped in refereneced to the nested tables within the loader file? I can load the various column objects, and nested tables fine right now, however, I am loading them all in strange and insane order. Can anyone answer this question? Thanks.
    Peter

    I just noticed that my email is wrong. If you can help, plese send email to [email protected]
    thanks.

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

  • Want to use sequence object of oracle when loading data in sql loader

    Hi,
    I want to use sequence when loading data in sqll loader, but the problem is i could not use sequence object of oracle to load the data by sql loader, i can use sequence of sql loader.
    I want to use sequence object because in later entries this sequence object will be used.If i use sequence of sql loader how can i use oracle sequence object
    Is there any other option

    I have a simillar problem, I also want to use a sequence when loading data by the SQL Loader.
    My control file is:
    load data
    infile '0testdata.txt'
    into table robertl.tbltest
    fields terminated by X'09'
    trailing nullcols
    (redbrojunos,
    broj,
    dolazak,
    odlazak nullif odlazak=blanks,
    komentar nullif komentar=blanks)
    And the datafile is:
    robertl.brojilo.nextval     1368     17.06.2003 08:02:46     17.06.2003 16:17:18     
    robertl.brojilo.nextval     2363     17.06.2003 08:18:18     17.06.2003 16:21:52     
    robertl.brojilo.nextval     7821     17.06.2003 08:29:22     17.06.2003 16:21:59     
    robertl.brojilo.nextval     0408     17.06.2003 11:20:27     17.06.2003 18:33:00     ispit
    robertl.brojilo.nextval     1111     17.06.2003 11:30:58     17.06.2003 16:09:34     Odlazak na ispit
    robertl.brojilo.nextval     6129     17.06.2003 14:02:42     17.06.2003 16:23:23     seminar
    But all records were rejected by the Loader, for every record I get the error:
    Record 1: Rejected - Error on table ROBERTL.TBLTEST, column REDBROJUNOS.
    ORA-01722: invalid number

Maybe you are looking for