A Provider-Specific Information

Data Source Properties

Table A-2 lists data source properties.

DataSourceInfo Properties

Table A-3 lists DataSourceInfo properties.

Initialization and Authorization Properties

Table A-4 lists initialization and authorization properties.

Session Properties

Table A-5 lists session properties.

Rowset Properties

Table A-6 lists rowset properties.

Data Source

CoType TDataSource {
      interface IDBCreateSession;
      interface IDBInitialize;
      interface IDBProperties;
      interface IPersist;
      interface IDBInfo;
      interface ISupportErrorInfo;
   }

Session

CoType TSession {
      interface IGetDataSource;
      interface IOpenRowset;
      interface ISessionProperties;
      interface IDBCreateCommand;
      interface IDBSchemaRowset;
      interface ISupportErrorInfo;
      interface ITransactionJoin;
      interface ITransactionLocal;
      interface ITransaction;
   }

Command

CoType TCommand {
      interface IAccessor;
      interface IColumnsInfo;
      interface ICommand;
      interface ICommandProperties;
      interface ICommandText;
      interface IConvertType;
      interface IColumnsRowset;
      interface ICommandPrepare;
      interface ICommandWithParameters;
      interface ISupportErrorInfo;
   }

Rowset

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;
   }

Multiple Results

CoType TMultipleResults {
      interface IMultipleResults;
      interface ISupportErrorInfo;
   }

Transaction Options

CoType TTransactionOptions {
      interface ITransactionOptions;
      interface ISupportErrorInfo;
   }

Custom Error Object

CoType TCustomErrorObject {
      interface IErrorLookup;
   }

Registry Setting for Tracing Calls

To trace the interface calls, you must configure the following registry values for HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_HOMENAME\OLEDB\:

• TraceFileName

  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, then the thread ID is appended to the file name provided. See "TraceOption" for more information.

• TraceCategory

  Valid Values:

  • 0 = None

  • 1 = OLEDB Interface method entry

  • 2 = OLEDB Interface method exit

  • 4 = Distributed Transaction Enlistment and Delistment

  TraceCategory specifies the information that is to be traced. Combinations of different tracing categories can be made by adding the valid values. For example, set TraceCategory to 3 to trace all OLE DB interface method entries and exits.

• TraceLevel

  Valid Values:

  • 0 = None

  • 1 = Data Source object

  • 2 = Session object

  • 4 = Command object

  • 8 = Rowset object

  • 16 = Error object

  • 64 = Multiple Results Object

  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, 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:

  • 0 = Single trace file

  • 1 = Multiple trace files

  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.