This appendix describes only the features of OCI that apply to the Windows 2003, Windows 2000, and Windows XP operating systems. Windows NT is no longer supported.
This chapter contains these topics:
The Oracle Call Interface for Windows package includes:
Oracle Call Interface (OCI)
Required Support Files (RSFs)
Oracle Universal Installer
Header files for compiling OCI applications
Library files for linking OCI applications
Sample programs for demonstrating how to build OCI applications
The OCI for Windows package includes the additional libraries required for linking your OCI programs.
"About OCI Instant Client" for a simplified OCI installation option
OCI is included in the default Oracle Database installation. When you install Oracle Database, Oracle Universal Installer creates the OCI files in the
precomp directories under the
ORACLE_BASE\ORACLE_HOME directory. These files include the library files needed to link and run OCI applications, and link with other Oracle for Microsoft Windows products, such as Oracle Forms.
ORACLE_BASE\ORACLE_HOME directory contains the following directories described in Table D-1 that are relevant to OCI.
Table D-1 ORACLE_HOME Directories and Contents
Executable and help files
Oracle Call Interface directory for Windows files
Header files, such as
Object Type Translator utility and default configuration file
When OCI is installed, a set of sample programs and their corresponding project files are copied to the
\oci\samples subdirectory. Oracle recommends that you build and run these sample programs to verify that OCI has been successfully installed and to familiarize yourself with the steps involved in developing OCI applications.
To build a sample, run a batch file
(make.bat)at the command prompt. For example, to build the
cdemo1.c sample, enter the following command in the directory
C:> make cdemo1
After you finish using these sample programs, you can delete them if you choose.
ociucb.c program should be compiled using
ociucb.bat. This batch file creates a DLL and places it in the
\bin directory. To load user callback functions, set the environment registry variable
For Microsoft Visual C++, specify
\ORACLE_BASE\ORACLE_HOME\oci\lib\msvc in the libraries section of the Option dialog box. For the Borland compiler, specify
For example, if you are using Microsoft Visual C++ 8.0, you must put in the appropriate path,
\oracle\db_1\oci\include, in the Directories page of the Options dialog in the Tools menu.
The only Microsoft Visual C++ releases supported for the current OCI release are 7.1 or later.
Your compiler's documentation for specific information about compiling your application and special compiler options
The OCI calls are implemented in dynamic-link libraries (DLLs) that Oracle provides. The DLLs are located in the
\bin directory and are part of the Required Support Files (RSFs).
Oracle only provides the
oci.lib import library for use with the Microsoft compiler. Borland compiler is also supported by Oracle for use with OCI. Oracle recommends that applications must always link with
oci.lib to avoid relinking or compilation with every release.
oci.lib with the Microsoft compiler, you do not have to indicate any special link options.
Oracle recommends that applications be linked with
oci.lib, which takes care of loading the correct versions of the Oracle DLLs.
The following directories are searched in this order by the
LoadLibrary() function for client DLL loading:
Directory from which the application is loaded or the directory where
oci.dll is located
The 32-bit Windows system directory
(system32). Use the
GetWindowsDirectory() function of the Windows API to obtain the path of this directory.
The 16-bit Windows directory
(system). There is no Win32 function that obtains the path of this directory, but it is searched.
Directories that are listed in the
PATH environment variable
To run an OCI application, ensure that the entire corresponding set of Required Support Files (RSFs) is installed on the computer that is running your OCI application.
The XA application programming interface (API) is typically used to enable an Oracle Database to interact with a transaction processing (TP) monitor, such as:
IBM Transarc Encina
You can also use TP monitor statements in your client programs. The use of the XA API is supported from OCI.
The Oracle XA Library is automatically installed as part of Oracle Database Enterprise Edition. Table D-2 lists the components created in your Oracle home directory. The
oci.lib import library contains the XA exports.
Table D-2 Oracle XA Components
To compile and link an OCI program with the Oracle XA Library:
.c by using Microsoft Visual C++ or the Borland compiler, making sure to include
\rdbms\xa in your path.
.obj with the libraries shown in Table D-3:
Table D-3 Link Libraries
The database supports the use of XA dynamic registration. XA dynamic registration improves the performance of applications interacting with XA-compliant TP monitors. For TP monitors to use XA dynamic registration with an Oracle Database on Windows, you must add either an environmental variable or a registry variable to the Windows systems on which your TP monitor is running. See either of the following sections for instructions:
Adding an environmental variable at the command prompt affects only the current session.
To Add an Environmental Variable:
From the computer where your TP monitor is installed, enter the following at the command prompt:
C:\> set ORA_XA_REG_DLL = vendor.dll
In this example,
.dll is the TP monitor DLL provided by your vendor.
Adding a registry variable affects all sessions on your Windows system. This is useful for computers where only one TP monitor is running.
ORA_XA_REG_DLLin the Value Name text box.
REG_EXPAND_SZfrom the Datatype list.
.dllin the String field, where
.dllis the TP monitor DLL provided by your vendor.
The registry exits.
Distributed TP: The XA Specification (C193) published by the Open Group
See the Web site at:
Your specific TP monitor documentation:
Oracle Database Development Guide, "Developing Applications with Oracle XA," for more information about the Oracle XA Library and using XA dynamic registration
For Oracle Tuxedo information see
To take advantage of objects, run the Object Type Translator (OTT) against the database to generate a header file that includes the C structs. For example, if a
PERSON type has been created in the database, OTT can generate a C struct with elements corresponding to the attributes of
PERSON. In addition, a null indicator struct is created that represents null information for an instance of the C struct.
The INTYPE File Assistant is not available, starting with Oracle Database 10g Release 1.
Note that the
CASE specification inside the intype files, such as
CASE=LOWER, applies only to C identifiers that are not specifically listed, either through a
TRANSLATE statement in the intype file. It is important to provide the type name with the appropriate cases, such as TYPE
Person and Type
PeRsOn, in the intype file.
OTT on Windows can be invoked from the command line. A configuration file can also be named on the command line. For Windows, the configuration file is
ottcfg.cfg, located in