Release 8.1.7
Part Number A85259-01
 Library |
 Product |
 Contents |
 Index |
| Oracle Provider for OLE DB User's Guide Release 8.1.7 Part Number A85259-01 |
|
This appendix discusses OLE DB information that is specific to Oracle Provider for OLE DB. For generic OLE DB information that includes a detailed listing of all OLE DB properties and interfaces, see the Microsoft OLE DB Programmer's Reference Guide.
This section lists the datatype mappings between Oracle datatypes and OLE DB-defined types. Oracle Provider for OLE DB represents Oracle datatypes by using certain OLE DB-defined datatypes in the rowset as well as in parameters. OLE DB-defined types are also mapped to an Oracle datatype when creating tables.
Each Oracle datatype is mapped to a specific OLE DB datatype, as shown in Table A-1. This correspondence is used when datatype information is retrieved from an Oracle database.
Table A-1 Datatype Mappings
This section lists the properties supported by Oracle Provider for OLE DB. The read/write status and initial values are noted.
| Property | Status | Initial Value |
|---|---|---|
|
DBPROP_CURRENTCATALOG |
READ-ONLY |
null |
| Property | Status | Initial Value |
|---|---|---|
|
DBPROP_SESS_AUTOCOMMITISOLEVELS |
READ-ONLY |
DBPROPVAL_TI_CURSORSTABILITY | |
Oracle Provider for OLE DB sets other necessary properties if a particular property is set to VARIANT_TRUE.
This section identifies the OLE DB interfaces that are supported by Oracle Provider for OLE DB.
CoType TDataSource { interface IDBCreateSession; interface IDBInitialize; interface IDBProperties; interface IPersist; interface IDBInfo; interface ISupportErrorInfo; }
CoType TSession { interface IGetDataSource; interface IOpenRowset; interface ISessionProperties; interface IDBCreateCommand; interface IDBSchemaRowset; interface ISupportErrorInfo; interface ITransactionJoin; interface ITransactionLocal; interface ITransaction; }
CoType TCommand { interface IAccessor; interface IColumnsInfo; interface ICommand; interface ICommandProperties; interface ICommandText; interface IConvertType; interface IColumnsRowset; interface ICommandPrepare; interface ICommandWithParameters; interface ISupportErrorInfo; }
CoType TRowset { interface IAccessor; interface IColumnsInfo; interface IConvertType; interface IRowset; interface IRowsetInfo; interface IColumnsRowset; interface IConnectionPointContainer; interface IRowsetChange; interface IRowsetFind; interface IRowsetIdentity; interface IRowsetLocate; interface IRowsetRefresh; interface IRowsetScroll; interface IRowsetUpdate; interface ISupportErrorInfo; }
CoType TMultipleResults { interface IMultipleResults; interface ISupportErrorInfo; }
CoType TTransactionOptions { interface ITransactionOptions; interface ISupportErrorInfo; }
CoType TCustomErrorObject { interface IErrorLookup; }
The following metadata columns are supported by OraOLEDB's column rowset:
OraOLEDB provides the ability to trace the interface calls for debugging purposes. This feature has been provided to assist Oracle WorldWide Support in debugging customer issues.
The provider can be configured to record the following information:
In order to trace the interface calls, you must configure the following registry values for HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OLEDB\:
Valid Value: Any valid path and file name
TraceFileName specifies the file name that is to be used for logging trace information. If TraceOption is set to 0, the name is used as is. However, if TraceOption is 1, the thread ID is appended to the file name provided. See "TraceOption" below for more information.
Valid Values:
TraceCategory specifies the information that is to be traced. Combinations of different tracing categories can be made by simply adding the valid values. For example, set TraceCategory to 3 to trace all OLE DB interface method entries and exits.
Valid Values:
TraceLevel specifies the OLE DB objects to be traced. Because tracing all the entry and exit calls for all the OLE DB objects can be excessive, TraceLevel is provided to limit tracing to a single or multiple OLE DB objects. To obtain tracing on multiple objects, simply add the valid values. For example, if TraceLevel is set to 12 and TraceCategory is set to 3, the trace file will only contain method entry and exit for Command and Rowset objects.
The TraceLevel value must be set to session object (2) to trace global transaction enlistment and delistment information.
Valid Values:
TraceOption specifies whether to log trace information in single or multiple files for each Thread ID. If a single trace file is specified, the file name specified in TraceFileName is used. If multiple trace file is requested, a Thread ID is appended to the file name provided to create a trace file for each thread.
|
 Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
|