The driver is optimized to communicate directly and efficiently with Oracle servers using the Oracle server wire protocol. Our ODBC Driver for Oracle also fully supports all Oracle systems including Oracle 8.1.5 and higher from a single wire protocol ODBC driver. This driver is both database and platform independent driver; Disadvantage of Network Protocol driver. Network support is required on client machine. Requires database-specific coding to be done in the middle tier. Maintenance of Network Protocol driver becomes costly because it requires database-specific coding to be done in the middle tier. I installed both the 32 and 64-bit Oracle 11g drivers. I search my PC looking for files with the name 'tnsnames.ora' and found 3 in the following locations: 1. C: Oracle product 1120332bit CLIENT1 NETWORK ADMIN 2. C: Oracle product 1120364bit CLIENT1 NETWORK ADMIN 3. The ODBC Driver for Oracle enables an application to access data in an Oracle database through the ODBC interface. The driver can access local Oracle databases or it can communicate with the network through SQL.Net. The following diagram details this application and driver architecture. Oracle VM Windows Paravirtual (PV) Drivers Accelerate the performance of your virtual environment Windows paravirtual (PV) drivers are high-performance network and disk drivers that significantly reduce the overhead of the traditional implementation of I/O device emulation.
New Oracle Articles
Drivers Oracle Network & Wireless Cards Login
ODBC and Network Performance
The Open Database Connectivity (ODBC) product was initially developed by Microsoft as a generic database driver. Its architecture has now been generalized and many different vendors are offering open database connectivity products that are based on ODBC. ODBC consists of more than 50 functions that are invoked from an application using a call-level API. The ODBC API does not communicate with a database directly. Instead, it serves as a link between the application and a generic interface routine. The interface routine, in turn, communicates with the database drivers via a Service Provider Interface (SPI).
ODBC has become popular with database vendors such as Oracle, and Oracle is creating new ODBC drivers that will allow ODBC to be used as a gateway into their database products. Essentially, ODBC serves as the ?traffic cop? for all data within the client/server system. When a client requests a service from a database, ODBC receives the request and manages the connection to the target database. ODBC manages all of the database drivers, checking all of the status information as it arrives from the database drivers.
It is noteworthy that the database drivers should be able to handle more than just SQL. Many databases have a native API that requires ODBC to map the request into a library of functions. An example would be a SQL Server driver that maps ODBC functions to database library function calls. Databases without a native API (i.e., non-SQL databases) can also be used with ODBC, but they go through a much greater transformation than the native API calls.
Database connectivity using ODBC has a high amount of overhead in many Oracle applications. The inherent flexibility of ODBC means that the connection process to Oracle is not as efficient as a native API call to the database. Most companies that experience ODBC-related performance problems will abandon ODBC and replace it with a native communications tool such as the Oracle Call Interface (OCI). In sum, ODBC is great for ad hoc database queries from MS Windows, but it is too slow for most production applications. Now let?s turn our attention to Oracle replication and see how the replication parameters can affect Oracle performance.
While network tuning is very complex, let?s take a brief overview of the standard tools that are used in a UNIX environment to monitor network transmissions.