Oracle Call Interface

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Oracle Call Interface" – news · newspapers · books · scholar · JSTOR (January 2014) (Learn how and when to remove this template message) The topic of this article may not meet Wikipedia's general notability guideline. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted. Find sources: "Oracle Call Interface" – news · newspapers · books · scholar · JSTOR (January 2014) (Learn how and when to remove this template message) (Learn how and when to remove this template message)

In computing, the Oracle Call Interface (OCI) consists of a set of

.

OCI offers a procedural API for not only performing certain database administration tasks (such as system startup and shutdown), but also for using

" between applications and the low-level database network protocol.

History

Oracle Corporation first released OCI (under the name HLI, the Host Language Interface) with Oracle Database version 6 in 1988. As HLI (and subsequently OCI) operated as wrappers for UPI, their original naming conventions closely resembled those of the UPI calls they were based upon. For example, the rollback statement: the call upirol in UPI became orol in OCI.

Later, in Oracle8 (released in 1997), OCI calls acquired more descriptive names; orol became OCITransRollback. Subsequent improvements have been made in every version of OCI, including 11g (released in 2007). Oracle Corporation claims that OCI is "So reliable that every SQL statement in the Oracle Database executes with OCI".^[1]

Implementations

OCI is so popular that, in addition to Oracle, several other vendors have implemented their own libraries compatible with the OCI API. To date, OCI-compatible libraries exist for the ANTs Data Server^{[citation needed]} (ADS), EnterpriseDB, and the Linter SQL RDBMS

OCI-based libraries

Several libraries are based on top of OCI, including:

• Oracle's Type-II JDBC Driver (part-Java, part native)
• Oracle's enhanced
  object-relational
  features of the Oracle database.
• Oracle's
  OLE DB
  Driver
• Oracle's
  ODBC
  Driver
• Oracle's .NET Data Provider, ODP.NET
• Microsoft's
  ODBC
  Driver for Oracle
• Easysoft's
  ODBC
  -Oracle Driver
• Trolltech's
  Qt C++ toolkit
  OCI driver (QOCI)

Due to the complexity of the OCI API, several easier-to-use OCI wrapper libraries also exist, such as:

• the open-source libsqlora8 library (deprecated).
• the open-source OCILIB library.
• the
  Open BSD licensed
  Oracle Template Library OTL library.

References

External links

• Official website
• Oracle Call Interface FAQ
• Public OCI Support Forum (OTN)