Index
C
- Component Object Model (COM)
- marking components as transactional 1.2
- programming with Oracle Call Interface and Microsoft Transaction Server 4.3
- registering in a Microsoft Transaction Server environment 4.2.1
- running in a Microsoft Transaction Server
- coordinated transaction 4.2.2
- running in an MS DTC-coordinated transaction 4.2.3
- using with Microsoft Oracle ODBC Driver 4.4.3
- using with the Oracle ODBC Driver and Microsoft Transaction Server 4.4.2
- computer on which Microsoft Transaction Server is installed
- installation requirements 2.2
- configuration requirements
- connection
- managing connection pooling 5.2
- connection attribute
- setting with ODBC 4.4.1
- connection pooling
- CREATE SESSION role 3.3.2.2
D
- database job-queue processes
- starting 3.3.2.1
- Data Manipulation Language (DML)
- using in shared server configurations 6.3
- DBMS_JOBS package 3.3.2.2
- DBMS_TRANSACTION package 3.3.2.2
- DCOM
- See: Distributed Component Object Model (DCOM)
- differences with OraMTSJoinTxn() function 4.3.6
- Distributed Component Object Model (DCOM) 1.1
- distributed transactions
- DML
- See: Data Manipulation Language (DML)
I
- in-doubt transactions
- initialization parameters
- installation requirements
- for computer on which Microsoft Transaction Server is installed 2.2
- installation requirements
- for computer running Oracle Fail Safe 2.1
- Microsoft Transaction Server 2.1
- Oracle Database Client 2.2.1
- Oracle ODBC Driver 2.2.1
- Oracle Services for Microsoft Transaction Server 2.2.1
- Service Pack 5.0 or greater 2.2.2
M
- Microsoft Distributed Transaction Coordinator (DTC) 1.2.1
- Microsoft Distributed Transaction Coordinator (MS DTC)
- Microsoft Transaction Server
- benefits 1.1
- changing the administrator username 3.3.2.2
- COM components running in a transaction 4.2.2
- components running in an MS DTC-coordinated transaction 4.2.3
- creating the administrator user account 3.3.2.2
- definition 1.1
- getting started with an Oracle Database 1.3
- installation requirements 2.1
- integration with an Oracle Database 1.2
- programming with Microsoft Oracle ODBC Driver 4.4
- programming with Oracle Call Interface 4.3
- programming with Oracle ODBC Driver 4.4
- registering COM components 4.2.1
- scheduling transaction recovery 3.3
- starting MS DTC 5.6
- using with Microsoft Oracle ODBC Driver 4.4.3
- using with the Oracle ODBC Driver 4.4.2
- MTS Recovery Service 2.4
- MTSSamples.dsn file
- using with the Oracle ODBC Driver 4.4.2
- mtssys username
- mtxstop.exe file
- running 6.2
O
- OCI_THREADED flag
- passing 4.3
- OCIInitialize function
- calling 4.3
- ODBC
- See: Open Database Connectivity (ODBC)
- omtssamp.sql script 4.4.3
- Open Database Connectivity (ODBC)
- configuring Microsoft Oracle ODBC Driver with Microsoft Transaction Server 4.4.3
- configuring the Oracle ODBC Driver with Microsoft Transaction Server 4.4.2
- Oracle ODBC Driver installation requirements 2.2.1
- programming with Microsoft Transaction Server 4.4
- setting the connection attribute 4.4.1
- using Microsoft Oracle ODBC Driver with Microsoft Transaction Server 4.4.3
- using the MTSSamples.dsn file with the Oracle ODBC Driver 4.4.2
- using the Oracle ODBC Driver with Microsoft Transaction Server 4.4.2
- using the SQL_ATTR_ENLIST_IN_DTC parameter 4.4.1
- using the SQLSetConnectAttr function 4.4.1
- Oracle Call Interface (OCI)
- enlisting an MS DTC-coordinated transaction 4.3.5
- obtaining pooled Oracle Call Interface connections 4.3.3
- obtaining pooled or standard Oracle Call Interface connections 4.3.5
- OraMTSEnlCtxGet() function 4.3.7
- OraMTSEnlCtxGet() function parameters 4.3.7
- OraMTSJoinTxn() function 4.3.9
- OraMTSOCIErrGet() function 4.3.11
- OraMTSOCIErrGet() function parameters 4.3.11
- OraMTSSvcEnlist() function 4.3.5
- OraMTSSvcEnlist() function parameters 4.3.5
- OraMTSSvcGet() function 4.3.3
- OraMTSSvcGet() function parameters 4.3.3
- OraMTSSvcRel() function 4.3.4
- programming with Microsoft Transaction Server 4.3
- releasing pooled Oracle Call Interface connections 4.3.4
- Oracle Database
- Oracle Database Client
- installation requirements 2.2.1
- Oracle Fail Safe 3.1, 3.5
- Oracle Home User 2.1
- Oracle MTS Recovery Service
- Oracle Recovery MTS Service 2.4
- Oracle Services for Microsoft Transaction 3.1
- Oracle Services for Microsoft Transaction Server
- installation requirements 2.2.1
- oramts_2pc_pending
- views 3.3.2.2.4
- ORAMTS_ABORT_MODE 5.5
- ORAMTS_CFLG_SYSDBALOGN flag
- using 4.3.3
- ORAMTS_CFLG_SYSOPRLOGN flag
- using 4.3.3
- ORAMTS_CONN_POOL_TIMEOUT registry parameter 5.2.1
- ORAMTS_NET_CACHE_MAXFREE registry parameter 5.2.1
- ORAMTS_NET_CACHE_TIMEOUT registry parameter 5.2.1
- ORAMTS_OSCREDS_MATCH_LEVEL registry parameter 5.2.1
- oramts.dll file
- definition 6.1
- oramtsadmin.sql script
- creating the PL/SQL package 3.3.2.2
- OraMTSEnlCtxGet() function
- Oracle Call Interface function 4.3.7
- OraMTSEnlCtxRel() function
- ORAMTSERR_ILLEGAL_OPER
- returning upon acquiring a connection 4.3.6
- ORAMTSERR_NOERROR
- OraMTSJoinTxn() function
- OraMTSOCIErrGet() function
- OraMTSSvcEnlist() function
- OraMTSSvcEnlistEx() function
- OraMTSSvcGet() function
- OraMTSSvcRel() function
- OraMTSTransTest() function
- syntax 4.3.10
- ORAOCI registry parameter
- setting 4.4.3