SQL LOADER message : Point de validation COMMIT atteint - nombre d'enreg

Hello
I am loading a csv file into an oracle table via SQL LOADER
Each time i invoke it i get the folowing message :
SQL LOADER message : Point de validation <COMMIT> atteint - nombre d'enregis. logiques 52. (i am french version of apex)
And the table is left empty.
The translation of the above message is :
SQL LOADER Validation Point <COMMIT> reached. number of logical records 52
What doese it mean ?
Thanks in advance.

Yes
my table is empty and
and this is my control file :
load data
infile 'i:\csvs\mvh051.csv'
into table mvhist051
fields terminated by ';' optionally enclosed by '"'
(ETABLI,NUPIECE,NUMLIGNE,DATEOP,JOURNAL,COMPTE,CODEN,LIBELLE,MONTANT,SENS,DATEVALEUR,OPERATION,NPIECE,CORIG,SOLDE,MVAPUR)
hear is a sample of bide file :
5100;2052;1;01/01/2005;ARB;1120060;0;report de solde 2004;6122867,27;D;01/01/2005;98;;1
5100;2053;1;01/01/2005;ARB;1120070;0;report de solde 2004;223639,17;D;01/01/2005;98;;1
5100;2054;1;01/01/2005;ARB;1261000;0;report de solde 2004;4680204207,00;D;01/01/2005;98;;1
5100;2055;1;01/01/2005;ARB;1271100;0;report de solde 2004;81895715591,44;D;01/01/2005;98;;1
ETABLI;NUPIECE;NUMLIGNE;DATEOP;JOURNAL;COMPTE;CODEN;LIBELLE;MONTANT;SENS;DATEVALEUR;OPERATION;NPIECE;CORIG;SOLDE;MVAPUR
Please not that the last line is the heading columns names. I dont under stand why
it is copied.

Similar Messages

SQL Loader Messages in Java (What do they mean?)

Hi,
I have been able to execute SQL Loader from a Servlet and I have also been able to retrieve the exit code by calling
{returnCode = process.waitFor()}.
I know that a "0" in the exit code indicates a successful execution. However what do the values larger than "0" mean? Does anyone know where I can find out more about these messages.? My servlet container is WebLogic 7.1 on Windows 2000.
Thanks,
Jimmy

indeed it was. no one mentioned a region pitch number, but that doesn't mean anything, of course, people fail to mention all kinds of important bits.
Still the OP said he just dropped a loop in the timeline.
::shrug:: i dunno

Sql loader & decimal point

Hello,
I need to import data with field containing floating point number. When I do this load on linux it goes ok. But when I try to load the same data from my windows there is problem with decimal point character. (My oracle server is 9i on linux).
I trid to use after logon trigger to issue statement alter session set nls_numeric_characters (enclosed in execute immediate statement) but it don't helped me.
Thanks for advice
sasa

ok.
I have following values in file to import:
45.5
50.3
60.2
38.7
("." is decimal point)
If I use sqlldr on linux it is imported correctly. If I try to to import data from windows machine I get error message ORA-01722: Invalid number. So somewhere on my windows machine is set another decimal separator and i would like to change it to ".". But i don't know where I can change it.
Is it more understandable?

I parallelize the use of SQL*Loader.But it always commit per 89 rows

I parallelize the use of SQL*Loader. But it always commit per 89 rows. How can I set Commit Row Number?

enlarge the BINDSIZE= and ROWS= option or better use DIRECT=TRUE
(and no need to parallelize [whatever this is in your case])

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 with decimal commas

Dear All,
I am loading data for a German client and the delivered files contain numeric data with decimal commas. For example 123,5 instead of 123.5
I've been googling like mad on this one and there is a lot of chatter about setting NLS_LANG and/or NLS_NUMERIC_CHARACTERS but none of this seems to work in the SQL Loader environment.
I imagine that I will end up cobbling together a complicated thing with TO_NUMBER or with another function but I really can't believe that SQL Loader doesn't have a simple switch to flip from point to comma.
Or have I overlooked something?
Any tips would be a great help.
Regards,
Alan Searle

I am on a client's PC and don't have access to administrative settings.
And also, I cannot be sure that whoever runs the load function in the future will check this.
It is therefore important that I find a way to set this in SQL Loader without any other dependencies.
I think I will probably end up processing it as a string and then translating it to numeric. But this seems like a sledge hammer to crack a nut.
Regards and thanks,
Alan

SQL Loader and Floating Point Numbers

Hi
I have a problem loading floating point numbers using SQL Loader. If the number has more than 8 significant digits SQL Loader rounds the number i.e. 1100000.69 becomes 1100000.7. The CTL file looks as follows
LOAD DATA
INFILE '../data/test.csv' "str X'0A'"
BADFILE '../bad/test.bad'
APPEND
INTO TABLE test
FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY '"'
Amount CHAR
and the data file as follows
"100.15 "
"100100.57 "
"1100000.69 "
"-2000000.33"
"-100000.43 "
the table defined as follows
CREATE TABLE test
Amount number(15,4)
) TABLESPACE NNUT050M1;
after loading a select returns the following
100.15
100100.57
1100000.7
-2000000
-100000.4
Thanks in advance
Russell

Actually if you format the field to display as (say) 999,999,999.99, you will see the correct numbers loaded via SQL Loader.
null

SQL loader and commit

Hi,
I am trying to execute a sql loader script that populates many tables. The order of the tables in the script is very important because the table of the last table has a constraint with the first table of the script. So I need that sqlloader executes a commit after the filling of the first tables because if sql loader executes the script simply as it is written the last tables launches an error because the constraint is violated (the last table sees the first one empty).
How can I force a commit after a filling in sql loader?
The sctructure of the tables was not defined by me so I must not modify it (constraint included).
Thanks, bye bye.

Hi,
If you have to enable/disable manually the constraints you can execute:
DECLARE
v_ds_action VARCHAR2(7);
BEGIN
v_ds_action := 'DISABLE';
    FOR reg IN (SELECT * FROM user_constraints uc WHERE uc.constraint_type = 'R') LOOP
    EXECUTE IMMEDIATE 'ALTER TABLE ' || reg.table_name || ' ' ||
                      v_ds_action || ' CONSTRAINT ' || reg.constraint_name;
END LOOP;
FOR reg IN (SELECT * FROM user_constraints uc WHERE uc.constraint_type = 'C') LOOP
    EXECUTE IMMEDIATE 'ALTER TABLE ' || reg.table_name || ' ' ||
                      v_ds_action || ' CONSTRAINT ' || reg.constraint_name;
END LOOP;
FOR reg IN (SELECT * FROM user_constraints uc WHERE uc.constraint_type = 'U') LOOP
    EXECUTE IMMEDIATE 'ALTER TABLE ' || reg.table_name || ' ' ||
                      v_ds_action || ' CONSTRAINT ' || reg.constraint_name;
END LOOP;
FOR reg IN (SELECT * FROM user_constraints uc WHERE uc.constraint_type = 'P') LOOP
    EXECUTE IMMEDIATE 'ALTER TABLE ' || reg.table_name || ' ' ||
                      v_ds_action || ' CONSTRAINT ' || reg.constraint_name;
END LOOP;
END;
DECLARE
v_ds_action VARCHAR2(7);
BEGIN
v_ds_action := 'ENABLE';
FOR reg IN (SELECT * FROM user_constraints uc WHERE uc.constraint_type = 'P') LOOP
    EXECUTE IMMEDIATE 'ALTER TABLE ' || reg.table_name || ' ' ||
                      v_ds_action || ' CONSTRAINT ' || reg.constraint_name;
END LOOP;
FOR reg IN (SELECT * FROM user_constraints uc WHERE uc.constraint_type = 'U') LOOP
    EXECUTE IMMEDIATE 'ALTER TABLE ' || reg.table_name || ' ' ||
                      v_ds_action || ' CONSTRAINT ' || reg.constraint_name;
END LOOP;
FOR reg IN (SELECT * FROM user_constraints uc WHERE uc.constraint_type = 'C') LOOP
    EXECUTE IMMEDIATE 'ALTER TABLE ' || reg.table_name || ' ' ||
                      v_ds_action || ' CONSTRAINT ' || reg.constraint_name;
END LOOP;
FOR reg IN (SELECT * FROM user_constraints uc WHERE uc.constraint_type = 'R') LOOP
    EXECUTE IMMEDIATE 'ALTER TABLE ' || reg.table_name || ' ' ||
                      v_ds_action || ' CONSTRAINT ' || reg.constraint_name;
END LOOP;
END;
/Regards,

Can we give validations in sql loader

hi gems...
i want to populate a table through sql loader...but i have to give some conditions while inserting the records i.e. i have to give some checks and validations...
is it possible to give conditions in sql loader...
please help...

Probably you can use WHEN clause while loading the data. Please check the below documentation for more information.
http://download.oracle.com/docs/cd/E11882_01/server.112/e22490/ldr_control_file.htm#i1005657

SQL LOADER "LOGICAL COMMIT"

Hello ,
After each successful execution of sql loader ,it implicitly commits the underlying transactions .
Why this implicit commit is happening and Can disable this auto commit feature of sql loader ?
Thanks

Hi ,
We cannot stop the commit option in sqlloqder.
By using the ROWS parameter we can control the feature
For eg rows=200
The records will be committed after every 200 records are over only.
Thanks
USR0072

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

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

Function for column validation in SQl Loader control file.

Hello Gurus,
We have an requirement to create a function to validate all date and number columns in control file, and return 0/1 accordingly to valid_column which is last column . I have developed the function which accepts the number and date type columns as parameter and return Y/N. My question is, is there any way so that the function could be created without passing any parameter to it?
If yes, then how to call the function in control file?
I have been searching since a while on Google to find out any solution but could find out.
Using Oracle 11g Enterprise Edition Release 11.2.0.1.0
Thanks!
Edited by: Sush on Jul 5, 2012 2:23 AM
Edited by: Sush on Jul 5, 2012 4:16 AM
Edited by: Sush on Jul 5, 2012 7:28 AM

Hi Srini,
I have gone through this document and i couldn’t find out any solution. That’s why i was seeking help from you Gurus.
Thanks for your help, i think i have learnt few new things abt SQL Loader by studying this document :)
Thanks!

SQL*Loader output issue

Hi,
When I load a flat file with SQL*Loader (V 8.1.7 on Windows), I get output something like,
Commit point reached - logical record count 2352
Commit point reached - logical record count 2364
Commit point reached - logical record count 2376
Commit point reached - logical record count 2388
Commit point reached - logical record count 2400
If I want to change this, say I want this message for each 1000 records inserted, how can I do that?
I have tried options line bindsize or rows, but looks like they are for changing internal operation, but not this screen output.
Off course, I am talking about conventional path load.
Any ideas?
Thanks

set rows=1000 and increase the bindsize drastically.
From the docs here
If that size fits within the bind array maximum, the load continues--SQL*Loader does not try to expand the number of rows to reach the maximum bind array size. If the number of rows and the maximum bind array size are both specified, SQL*Loader always uses the smaller value for the bind array.

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

SQL LOADER message : Point de validation COMMIT atteint - nombre d'enreg

Similar Messages

Maybe you are looking for