Obsolescence Notice: Oracle Objects for OLE
(Doc ID 1175303.1)
Last updated on DECEMBER 30, 2018
Applies to:Oracle Objects for OLE - Version 126.96.36.199 to 188.8.131.52 [Release 8.0.6 to 11.2]
Information in this document applies to Windows Platforms.
***Checked for relevance on 30-Dec-2018***
Oracle Objects for OLE (OO4O) is a COM-based data access driver that optimizes access to Oracle databases with an easy to use API. OO4O can be used in a variety of environments ranging from web applications to n-tier client/server applications. It can be used from virtually any programming or scripting language that supports the Microsoft COM Automation technology, such as Visual Basic, Visual C++, VBA in Excel, Active Server Pages, PowerBuilder, Delphi, Microsoft Internet Information Services, and Microsoft Distributed Transaction Coordinator.
In the 1990s, Microsoft developed the Component Object Model (COM), an architecture for inter-software component communication and easy software component re-use and evolution. Due to some inherent architecture problems and the emergence of Java’ multi-platform support, Microsoft abandoned COM for the .NET Framework. As such, COM exists mostly in legacy applications. No new application development occurs with COM now as far as Oracle Product Management has observed.
In the COM and Oracle Database realm, there are two primary methods for data access: ADO/OLE DB and OO4O. ADO/OLE DB was built as a uniform data access API for any COM component, much in the same as ODBC is. OO4O was built so that COM developers could take advantage of Oracle-specific features that weren’t exposed in ADO/OLE DB’s generic interface.
The mainstream COM data access was ADO/OLE DB by far since that was the official Microsoft-endorsed data access method in the 1990s. OO4O had a smaller, but dedicated user base, which required access to Oracle Database features from their client applications.
Nowadays, customers do enhance existing COM applications, but not very often when it comes to data access. Any enhancement requests and bugs usually are for Oracle’s OLE DB provider, but very little activity exists for OO4O in recent years.
Oracle Database 11g Release 2 is the last database version to contain the database component Oracle Objects for OLE. Database versions after Oracle Database 11g Release 2 will not contain Oracle Objects for OLE. Existing customers may continue to use Oracle Objects for OLE with existing Oracle Database versions that are covered under the Oracle’s lifetime support policy.
Customers may migrate their OO4O data access code to ADO/OLE DB. Or they may migrate the entire application to .NET (or Java or another application architecture) and use another driver.
Existing customers may continue to use OO4O with Oracle Database 11g Release 2 or previous database versions that are covered under the Oracle’s lifetime support policy.
For more information regarding the Oracle Support Policy, please refer to Oracle's Lifetime Support Policy and Technical Support Policies.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document