Diffeence b/w thin and thick driver

diffeence b/w thin and thick driver

This thread is moved from "Collections: Lists, Sets, and Maps" to here.

Similar Messages

Differences between Oracle JDBC Thin and Thick Drivers

If any body is looking for this information...
============================================================
I have a question concerning the Oracle JDBC thin vs. thick drivers
and how they might affect operations from an application perspective.
We're in a Solais 8/Oracle 8.1.7.2 environment. We have several
applications on several servers connecting to the Oracle database.
For redundancy, we're looking into setting up TAF (transparent
application failover). Currently, some of our apps use the Oracle
JDBC thin drivers to talk to the database, with a connection
string that like this:
 jdbc:oracle:thin:@host:port:ORACLE_SID 
In a disaster recovery mode, where we would switch the database
from one server to another, the host name in the above string
would become invalid. That means we have to shut down our application
servers and restart them with an updated string.
Using the Oracle OCI (thick) driver though, allows us to connect
to a Net8 service instead of a specific server:
 jdbc:oracle:oci8:@NET8_SERVICE_NAME 
Coupled with the FAILOVER=ON option configured in Net8, it is
then possible to direct a connection from the first server to
the failover database on another server. This is exactly what
we would like to do.
My question is, from an application perspective, how is the Oracle
thick driver different from the thin driver? If everything
else is "equal" (i.e. the thick driver is compatible with the
app servers) would there be something within the the thick/OCI
driver that could limit functionality vs. the thin driver?
My understand, which obviously is sketchy, is that the thick
driver is a superset of the thin driver. If this is the case,
and for example if all database connections were handled through
a configuration file with the above OCI connection string, then
theoretically the thick driver should work.
============================================================

In the case with the Oracle, they provide a thin driver that is a 100% Java driver for client-side use without the need of an Oracle installation (maybe that's why we need to input server name and port number of the database server). This is platform indipendent, and has good performance and some features.
The OCI driver on the other hand is not java, require Oracle installation, platform dependent, performance is faster, and has a complete list of all the features.

========================================================
I hope this is what you expect.
JDBC OCI client-side driver: This is a JDBC Type 2 driver that uses Java native methods to call entrypoints in an underlying C library. That C library, called OCI (Oracle Call Interface), interacts with an Oracle database. The JDBC OCI driver requires an Oracle (7.3.4 or above) client installation (including SQL*Net v2.3 or above) and all other dependent files. The use of native methods makes the JDBC OCI driver platform specific. Oracle supports Solaris, Windows, and many other platforms. This means that the Oracle JDBC OCI driver is not appropriate for Java applets, because it depends on a C library to be preinstalled.
JDBC Thin client-side driver: This is a JDBC Type 4 driver that uses Java to connect directly to Oracle. It emulates Oracle's SQL*Net Net8 and TTC adapters using its own TCP/IP based Java socket implementation. The JDBC Thin driver does not require Oracle client software to be installed, but does require the server to be configured with a TCP/IP listener. Because it is written entirely in Java, this driver is platform-independent. The JDBC Thin driver can be downloaded into any browser as part of a Java application. (Note that if running in a client browser, that browser must allow the applet to open a Java socket connection back to the server.
JDBC Thin server-side driver: This is another JDBC Type 4 driver that uses Java to connect directly to Oracle. This driver is used internally by the JServer within the Oracle server. This driver offers the same functionality as the client-side JDBC Thin driver (above), but runs inside an Oracle database and is used to access remote databases. Because it is written entirely in Java, this driver is platform-independent. There is no difference in your code between using the Thin driver from a client application or from inside a server.
======================================================
How does one connect with the JDBC Thin Driver?
The the JDBC thin driver provides the only way to access Oracle from the Web (applets). It is smaller and faster than the OCI drivers, and doesn't require a pre-installed version of the JDBC drivers.
import java.sql.*;
class dbAccess {
public static void main (String args []) throws SQLException
DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection
("jdbc:oracle:thin:@qit-uq-cbiw:1526:orcl", "scott", "tiger");
// @machineName:port:SID, userid, password
Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
while (rset.next())
System.out.println (rset.getString(1)); // Print col 1
stmt.close();
How does one connect with the JDBC OCI Driver?
One must have Net8 (SQL*Net) installed and working before attempting to use one of the OCI drivers.
import java.sql.*;
class dbAccess {
public static void main (String args []) throws SQLException
try {
Class.forName ("oracle.jdbc.driver.OracleDriver");
} catch (ClassNotFoundException e) {
e.printStackTrace();
Connection conn = DriverManager.getConnection
("jdbc:oracle:oci8:@qit-uq-cbiw_orcl", "scott", "tiger");
// or oci7 @TNSNames_Entry, userid, password
Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
while (rset.next())
System.out.println (rset.getString(1)); // Print col 1
stmt.close();
=================================================================

Wow, not sure what your question was, but there sure was a lot of information there...
There really is only one case where failover occurs, and it would not normally be in a disaster recovery situation, where you define disaster recovery as the obliteration of your current server farm, network and concievably the operational support staff. This would require a rebuild of your server, network etc and isn't something done with software.
Fail over is normally used for high availablity that would take over in case of hardware server failure, or when your support staff wants to do maintenance on the primary server.
Using the thin and thick driver should have ZERO affect on a failover. Transparent failover will make the secondary server the same IP as the primary, therefore the hostname will still point to the appropriate server. If you are doing this wrong, then you will have to point all your applications to a new IP address. This should be something that you tell your management is UNACCEPTABLE in a fail-over situation, since it is almost sure to fail to fail-over.
You point out that you are providing the TNSNAME, rather than the HOSTNAME when using the thick driver. That's true within your application, but that name is resolved to either a HOSTNAME, or IP ADDRESS before it is sent to the appropriate Oracle server/instance. It is resolved using either a NAME server (same as DNS server but for Oracle), or by looking at a TNSNAMES file. Since the TNSNAMES files profilerate like rabbits within an organization you don't want a fail over that will make you find and switch all the entries, so you must come up with a fail over that does not require it.
So, the application should not be concerned with either the hostname, or the IP address changing during fail over. That makes use of the thin or thick client acceptable for fail over.
Don't know if this will help, but this shows the communication points.
THIN DRIVER
client --> dns --> server/port --> SID
THICK DRIVER
client --> names server --> dns --> server/port --> SID
client --> tnsnames --> dns --> server/port --> SID

What is Thin and Thick Client ? Differences between the Two ? Which is Best

Dear All,
I like to develop both web-based and also standalone applications. i like to choose the best drivers for my applications. can anybody suggest which one to choose and what are the drawbacks in each driver ?
Thanks,
J.Kathir

Dear All,
I like to develop both web-based and
h web-based and also standalone applications. i like
to choose the best drivers for my applications. can
anybody suggest which one to choose and what are the
drawbacks in each driver ?I dont get what excatly you meaned by driver but basicaly a thin client means it only does the prescentation of data to its user and all the logics will be in a server. for every task it will connect to the server.
In a Thick client it can do more processing and it will connect to the server only for the tasks that it cant perform with the data it has in the client.
>
Thanks,
J.KathirHere is a general comparison between main features of thin/thick(fat) clients
Both thin and thick clients has their own advantages and disadvantages. most of time one wins when other fails.
1. Thin client extencvely uses the server to all its operations which will increace the network traffic and the load on the server. as a result the perfomance of the client will depend on the load and the resources available for the server
2. But all the logic is in the server so if you are developing multiple clients for the same application (Ex:- Standallone app, Web client, Mobile clients......) you will not need to duplicate logic in each client.
3. Fat clients reduce the load on server and less dependant on the server. but since they are fat they will take more processing power and memory on client computers.
4. If you are developing multiple clients as menctioned in 2 you will need to duplicate the logics written the clients

BEA recommendation for use of Thin or Thick driver of Oracle 10g

What is recommended by BEA to use Oracle Thin or thick driver for connecting to oracle 10g database from Weblogic Server 8.1.5?

nmyneni wrote:
What is recommended by BEA to use Oracle Thin or thick driver for connecting to oracle 10g database from Weblogic Server 8.1.5?Use the Oracle driver in the thin mode, not the thick/OCI mode.
The latter will expose you to native code bugs in OCI that
can kill an entire JVM.

JDBC Thin vs Thick Driver

Hello,
We are looking for differences between Oracle JDBC Thin and OCI (thick) driver with respect to
1. Peformance of the Java application.
2. Maintenance and administration
3. Known issues with OCI (thick) driver which is handled by Thin or vice versa.
4. Better security
Appreciate any help on the above.
Thanks and Regards,
Vamsi Mohan Harish

1. Performance of the Java application.
The difference in driver implementation is likely to be trivial compared to other considerations (network round trip time, application design, etc). However if you are really interested then chapter 19 of 'Java Programming with Oracle JDBC' by Donald Bales (O'Reilly) has some good information on this topic. It also happens to be available online: http://www.onjava.com/pub/a/onjava/excerpt/oraclejdbc_19/index.html
Keep in mind that it is a little out of date now - you should run tests using the current versions of the drivers.
2. Maintenance and administration
The JDBC Thin driver is typically easier to update/distribute, as installation consists of copying a .jar file or two. The only case where OCI has an advantage is in the use of Oracle's naming layer for database service abstraction. Of course this assumes the database server is listening for TCP/IP and not the legacy protocols that are only supported by OCI. Failover configurations using TAF are supported by OCI only. The newer 'Fast Connection Failover' feature of 10g RAC can also run over Thin though.
3. Known issues with OCI (thick) driver which is handled by Thin or vice versa.
In my experience each has a roughly equal number of bugs. I find it easier to track them down in the Thin driver though :-)
4. Better security
The security options for the Thin driver are more limited with regard to external authentication and support for some of the Oracle Advanced Security features. However, both support the basics like encrypted connections. Chapter 23 of the JDBC driver docs goes into more depth: http://download-west.oracle.com/docs/cd/B14117_01/java.101/b10979/toc.htm
Hope this helps.
Jonathan.

JDBC thin and thick clients

What is the difference between JDBC thin and JDBC thick clients and their usage ?

hi,
in sort tearms,
Oracle has a thin client driver which mean you can connect to a oracle database without the Oracle client installed on your machine.
Thick client would need the Oracle Client database drivers etc.. Drivers include JDBC-ODBC bridge drivers JDBC drivers depending on tns resolution.
thanks

Thick Driver Vs Thin Driver

Hello,
Could you please tell me what is the difference between Thin Driver and Thick Driver? Which we should use?
Is Type 1 and Type 2 Driver is Thick Driver? Please mention.
This have any aricle, please give the URL Thank you.
Thank you in Advance
balachandar

Look into this article. There is no such term called thick JDBC driver. But there are 4 types of JDBC drivers, You can google for more infomation.
http://www.stardeveloper.com/articles/display.html?article=2003082701&page=1
Regards
Bahadur Singh

Difference between Thin Drivers and Thick Drivers

hi all,
can any one tell me the difference between Thin Drivers and Thick Drivers.
regards
ravi

OCI is Oracle Call Interface. That's the lowest-level client API Oracle offers and the API that every thick client application eventually uses. For example, a C++ application using ADO would use the OLE DB driver which is itself written in OCI.
From a deployment standpoint, the major difference is that the thin driver can be deployed to any machine that has Java installed. The OCI driver can only be deployed to machines that have the Oracle client installed.
From a performance & functionality standpoint, there are features that only the OCI driver provides. Depending on the application, the OCI driver may also be faster.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Thick driver with Oracle 9i and Weblogic 6.1 or 7.0?

Hello,
Does anyone have a sample config file for their connection pool under
Webligic 6.1-7.0 which they wouldn't mind sharing?
It's pretty tough to find an example config file for this because
Oracle seems to refer to BEA's docs, and vice versa. In either case,
they're really vague about what values are needed in the various
fields. In the case that you've seen a document which covers this -
could you please forward me a link to it?
Thank you,
- Ryan

It seems that the config parms you have are for the thin driver - I
was hoping to find the parms for the thick driver specifically.
Thanks,
- Ryan
"Neo Gigs" <[email protected]> wrote in message news:<[email protected]>...
DriverName="oracle.jdbc.driver.OracleDriver"
URL="jdbc:oracle:thin:@192.168.101.20.:1521:ORA1"
"Ryan D'Silva" <[email protected]> wrote in message
news:[email protected]..
It might help - especially if the config requirements for the driver
haven't changed much since Oracle 7.
I'd appreciate being able to take a look at it,
- Ryan
"Neo Gigs" <[email protected]> wrote in message
news:<[email protected]>...
Mine is configuration of Oracle 7, you want it?
"Ryan D'Silva" <[email protected]> wrote in message
news:[email protected]..
Hello,
Does anyone have a sample config file for their connection pool under
Webligic 6.1-7.0 which they wouldn't mind sharing?
It's pretty tough to find an example config file for this because
Oracle seems to refer to BEA's docs, and vice versa. In either case,
they're really vague about what values are needed in the various
fields. In the case that you've seen a document which covers this -
could you please forward me a link to it?
Thank you,
- Ryan

Difference bewteen thin client and thick client

Hi:
can someone explain the difference between the thin client app and thick client app?

Thin Client: Little to no logic on front end. Typically a 3 tier architecture. Example is a web browser
Thick Client: Typically a client-server type architecture where some business logic/processing occurs on the front end

HFM Thin Client and Thick Client

Hi
can anyone tell me what is HFM thin client and thick client
Thanks

Thick client is the actual application client view. Most administrators limit that view to only them and provide a workspace (the thin client) as a method of accessing hfm. This is because more can be done in terms of metadata and security changes in the thick client than the thin client.

Jdbc thin to thick migraion

hi all,
i am trying to migrate an application to fat oci oracle drivers.
when using thin drivers there was never a problem but prformance was low.... (maybe
not well programmed?) but nevertheless i migrated somappliactions to fat drivers
and it was a whaoooo effect they performed a lot better so i decided to migrate
anything possibe to fat till this day....
when i sarted this censoed application in the wls 7 server i always got nuberformatexception
i think when the appliaction tried to parse float values from the database
following error ocured with 9.xx and 8.xxx oracle fat driver
####<
69:e9e6dc1becbcab34> <010051> <EJB Exception during invocation from home: j2ee.ProductSearchSessionBean_ae
teip_HomeImpl@29a747 threw exception: javax.ejb.EJBException: nested exception
is: javax.ejb.FinderException: Exception executing fi
nder 'findActiveByProductTypeIDApplicationIDExternalProdType':
java.sql.SQLException: java.lang.NumberFormatException: ,2
at java.lang.Integer.parseInt(Integer.java:409)
at java.math.BigInteger.<init>(BigInteger.java:311)
at java.math.BigInteger.<init>(BigInteger.java:440)
at java.math.BigDecimal.<init>(BigDecimal.java:153)
at weblogic.jdbc.oci.ResultSet.getBigDecimal(ResultSet.java:1074)
at weblogic.jdbc.jts.ResultSet.getBigDecimal(ResultSet.java:703)
at at.sybase.j2ee.com.shop.ejb.ProductBean_meu6z3__WebLogic_CMP_RDBMS.__WL_loadGroup0FromRS(ProductBean_meu6z3__WebLogic_
CMP_RDBMS.java:3081)
with thin driver everything was fine ....
any suggestions?
thx chris

Have you tried simply running oracle's thick driver? Our driver relies on OCI's
string representation of the data, to feed to the constructor for BigDecimal,
and I fear that OCI may be serving up a value in scientific notation, which
the BigDecimal constructor chokes on. The reason our driver does that is because the
metadata that the DBMS sends is insufficient for us to know what object to construct
from the value (it could change every row!). Oracle's drivers make a BigDecimal
natively for every numeric datum...
Joe
chris wrote:
hi all,
i am trying to migrate an application to fat oci oracle drivers.
when using thin drivers there was never a problem but prformance was low.... (maybe
not well programmed?) but nevertheless i migrated somappliactions to fat drivers
and it was a whaoooo effect they performed a lot better so i decided to migrate
anything possibe to fat till this day....
when i sarted this censoed application in the wls 7 server i always got nuberformatexception
i think when the appliaction tried to parse float values from the database
following error ocured with 9.xx and 8.xxx oracle fat driver
####<
69:e9e6dc1becbcab34> <010051> <EJB Exception during invocation from home: j2ee.ProductSearchSessionBean_ae
teip_HomeImpl@29a747 threw exception: javax.ejb.EJBException: nested exception
is: javax.ejb.FinderException: Exception executing fi
nder 'findActiveByProductTypeIDApplicationIDExternalProdType':
java.sql.SQLException: java.lang.NumberFormatException: ,2
at java.lang.Integer.parseInt(Integer.java:409)
at java.math.BigInteger.<init>(BigInteger.java:311)
at java.math.BigInteger.<init>(BigInteger.java:440)
at java.math.BigDecimal.<init>(BigDecimal.java:153)
at weblogic.jdbc.oci.ResultSet.getBigDecimal(ResultSet.java:1074)
at weblogic.jdbc.jts.ResultSet.getBigDecimal(ResultSet.java:703)
at at.sybase.j2ee.com.shop.ejb.ProductBean_meu6z3__WebLogic_CMP_RDBMS.__WL_loadGroup0FromRS(ProductBean_meu6z3__WebLogic_
CMP_RDBMS.java:3081)
with thin driver everything was fine ....
any suggestions?
thx chris

What is thin and fat client

Hi,
I would like to know
what is thin and fat client.
what is the difference between thin and fat client.
How to copy config only client. (No data copy)
Appreciate for your reply... I will reward the points.
Thanks
Atul-

Hi Atul,
Thin Clients
A thin client is designed to be especially small so that the bulk of the data processing occurs on the server. Although the term thin client often refers to software, it is increasingly used for the computers, such as network computers and Net PCs, that are designed to serve as the clients for client/server architectures. A thin client is a network computer without a hard disk drive. They act as a simple terminal to the server and require constant communication with the server as well.
Thick Clients
In contrast, a thick client (also called a fat client) is one that will perform the bulk of the processing in client/server applications. With thick clients, there is no need for continuous server communications as it is mainly communicating archival storage information to the server. As in the case of a thin client, the term is often used to refer to software, but again is also used to describe the networked computer itself. If your applications require multimedia components or that are bandwidth intensive, you'll also want to consider going with thick clients. One of the biggest advantages of thick clients rests in the nature of some operating systems and software being unable to run on thin clients. Thick clients can handle these as it has its own resources.
Thick vs. Thin - A Quick Comparison
Thin Clients
- Easy to deploy as they require no extra or specialized software installation
- Needs to validate with the server after data capture
- If the server goes down, data collection is halted as the client needs constant communication with the server
- Cannot be interfaced with other equipment (in plants or factory settings for example)
- Clients run only and exactly as specified by the server
- More downtime
-Portability in that all applications are on the server so any workstation can access
- Opportunity to use older, outdated PCs as clients
- Reduced security threat
Thick Clients
- More expensive to deploy and more work for IT to deploy
- Data verified by client not server (immediate validation)
- Robust technology provides better uptime
- Only needs intermittent communication with server
- More expensive to deploy and more work for IT to deploy
- Require more resources but less servers
- Can store local files and applications
- Reduced server demands
- Increased security issues
To copy only config client , there are few more profiles that you can choose in scc8
SAP_EXBC - SAP_UCSV with cross-client customizing
SAP_EXPA - SAP_ALL with cross-client customizing
SAP_EXPC - SAP_CUSV with cross-client customizing
if it helful reward points are appreciated
Message was edited by:
Pierluigi Demaria
Message was edited by:
Pierluigi Demaria

Issue encountered when Login as sysdba role using Thin Oracle JDBC Driver

Hello all,
we are now considering to use Thin oracle JDBC driver to create database in our project, but we met one issue when we tried to connect to oracle as sysdba role using Thin driver, and it throws java.sql.SQLException: Io Exception: SO Exception was generated, I have found some tips on oracle jdbc website and it says :
How do I connect as SYSDBA or SYSOPER?
The only way to do this is to use the Properties object when connecting, rather than specifying the username and password as strings. Put the username into the "user" property, and the password into the "password" property. Then, put the mode into the "internal_logon" property. Something like the following:
Properties props = new Properties();
props.put("user", "scott");
props.put("password", "tiger");
props.put("internal_logon", "sysoper");
Connection conn = DriverManager.getConnection (url, props);
When connecting as SYSDBA or SYSOPER using the Thin driver, the RDBMS must be configured to use a password file. See "Creating and Maintaining a Password File" in the "Oracle Database Administrator's Guide".
So, i did execute orapwd command to create a password file and also set remote_login_passwordfile=execlusive in my initxxx.ora initial parameter file, however, when i tried to connect, it failed.
private static void createEmsdbDatabase(){
String url = "jdbc:oracle:thin:@localhost:1521:";
StringBuffer sqlStatement = new StringBuffer();
sqlStatement.append("create database xxx");
sqlStatement.append("maxdatafiles 254 ");
sqlStatement.append("maxinstances 8 ");
sqlStatement.append("maxlogfiles 32 ");
sqlStatement.append("character set UTF8 ");
sqlStatement.append("national character set UTF8 ");
sqlStatement.append("DATAFILE 'c:\\oracle\\xxx\\system01.dbf' SIZE 18M REUSE ");
sqlStatement.append("logfile 'c:\\oracle\\xxx\\redo01.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo02.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo03.log' SIZE 2M REUSE ");
try {
DriverManager.registerDriver(new OracleDriver());
Properties props = new Properties();
props.put("user", "sys");
props.put("password", "password");
props.put("database","xxx");
props.put("internal_logon", "sysdba");
Connection conn = DriverManager.getConnection(url, props);
Statement statement = conn.createStatement();
statement.executeUpdate(sqlStatement.toString());
statement.close();
conn.close();
} catch (SQLException e) {
e.printStackTrace();
But what made me puzzled a lot is if i use OCI driver, it did work great, why??? guys, anybody knows, please give me some tips, thanks in advance.
regards,
Kaixuan @ Shanghai

clarify my question in detail:
Step 1 : create password file using orapwd command
Step 2 : create database instance using oradim command
Step 3 : login using sys as sysdba to startup database, e.g startup nomount pfile='...\initxxx.ora'
Step 4 : create database.
java code showing below:
private static void createEmsdbDatabase(){
String url = "jdbc:oracle:thin:@localhost:1521:";
StringBuffer sqlStatement = new StringBuffer();
sqlStatement.append("create database xxx ");
sqlStatement.append("maxdatafiles 254 ");
sqlStatement.append("maxinstances 8 ");
sqlStatement.append("maxlogfiles 32 ");
sqlStatement.append("character set UTF8 ");
sqlStatement.append("national character set UTF8 ");
sqlStatement.append("DATAFILE 'c:\\oracle\\xxx\\system01.dbf' SIZE 18M REUSE ");
sqlStatement.append("logfile 'c:\\oracle\\xxx\\redo01.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo02.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo03.log' SIZE 2M REUSE ");
try {
DriverManager.registerDriver(new OracleDriver());
Properties props = new Properties();
props.put("user", "sys");
props.put("password", "password");
props.put("database","xxx");
props.put("internal_logon", "sysdba");
Connection conn = DriverManager.getConnection(url, props);
Statement statement = conn.createStatement();
statement.executeUpdate(sqlStatement.toString());
statement.close();
conn.close();
} catch (SQLException e) {
e.printStackTrace();
issue was met here, when i tried to login as sysdba using sys, and in my java code, i use Thin driver, it then thrus exception, but when OCI driver is used, it works great, i don't know why.
that is, when i use "jdbc:oracle:oci8:@" as database URL and then properties.put("database","xxx"), it works great. but, when i use "jdbc:oracle:thin:@localhost:1521:" as database URL and then properties.put("database","xxx"), it failed. hopefully, i have clarified my question clearly. thanks.

JDBC Thin Server-side Driver 8.1.6

The readme.txt for the JDBC Thin driver
talks about a JDBC Thin driver for clients
and a JDBC Thin Server-side driver for
servers. Where is the Server-side driver?
In Oracle?

I believe the one from technet was created
under the Solaris environment. That is
the only difference that I know of.
null

Diffeence b/w thin and thick driver

Similar Messages

Maybe you are looking for