Oracle Provider for OLE DB Developer's Guide Release 9.2 Part Number A95498-01 |
|
This appendix describes 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 appendix contains these topics:
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.
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 |
---|---|---|
|
READ-ONLY |
|
Property | Status | Initial Value |
---|---|---|
|
READ-ONLY |
|
Oracle Provider for OLE DB sets other necessary properties if a particular property is set to VARIANT_TRUE
.
DBPROP_IROWSETLOCATE
is set to VARIANT_TRUE
, the following properties are also set to VARIANT_TRUE
:DBPROP_IROWSETSCROLL
is set to VARIANT_TRUE
, the following properties are also set to VARIANT_TRUE
:DBPROP_IROWSETUPDATE
is set to VARIANT_TRUE
, the following properties are also 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:
DBCOLUMN_IDNAME
DBCOLUMN_GUID
DBCOLUMN_PROPID
DBCOLUMN_NAME
DBCOLUMN_NUMBER
DBCOLUMN_TYPE
DBCOLUMN_TYPEINFO
DBCOLUMN_COLUMNSIZE
DBCOLUMN_PRECISION
DBCOLUMN_SCALE
DBCOLUMN_FLAGS
DBCOLUMN_BASECATALOGNAME
DBCOLUMN_BASECOLUMNNAME
DBCOLUMN_BASESCHEMANAME
DBCOLUMN_BASETABLENAME
DBCOLUMN_COMPUTEMODE
DBCOLUMN_ISAUTOINCREMENT
DBCOLUMN_ISCASESENSITIVE
DBCOLUMN_ISSEARCHABLE
DBCOLUMN_OCTETLENGTH
DBCOLUMN_KEYCOLUMN
OraOLEDB provides the ability to trace the interface calls for debugging purposes. This feature has been provided to assist Oracle Support Services in debugging customer issues.
The provider can be configured to record the following information:
Note: In order to record global transaction enlistment and delistment information, the |
In order to trace the interface calls, you must configure the following registry values for HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OLEDB\
:
TraceFileName
Valid Value: Any valid path and filename
TraceFileName
specifies the filename 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 filename provided. See "TraceOption" for more information.
TraceCategory
Valid Values:
0
= None1
= OLEDB Interface method entry2
= OLEDB Interface method exit4
= Distributed Transaction Enlistment and DelistmentTraceCategory
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.
TraceLevel
Valid Values:
0
= None1
= Data Source object2
= Session object4
= Command object8
= Rowset object16
= Error object64
= Multiple Results ObjectTraceLevel
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.
TraceOption
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 filename specified in TraceFileName
is used. If multiple trace file is requested, a Thread ID is appended to the filename provided to create a trace file for each thread.
|
Copyright © 1999, 2002 Oracle Corporation. All Rights Reserved. |
|