Index
A C D E F G H I J M N O P R S T U V W
A
- account table
- using with Microsoft application demo, 4-3
- account.idl file, 4-5
- administrator username
- dropping, 7-8
- Microsoft Transaction Server, 3-6
C
- clients, 2-4
- configuration requirements, 3-2
- COM. See Component Object Model (COM)
- Component Object Model (COM)
- integration in a transaction, 5-2
- marking components as transactional, 1-3
- ODBC, 2-4
- on Windows 2000, A-2
- Oracle Objects for OLE, 2-4
- programming with ODBC and Microsoft Transaction Server, 5-26
- programming with Oracle Call Interface and Microsoft Transaction Server, 5-9
- programming with Oracle Objects for OLE and Microsoft Transaction Server, 5-29
- programming with Oracle Provider for OLE DB and Microsoft Transaction Server, 5-29
- registering in a Microsoft Transaction Server environment, 5-5
- running in a Microsoft Transaction Server
- coordinated transaction, 5-7
- running in an MS DTC-coordinated transaction, 5-8
- using with Microsoft's Oracle ODBC Driver and Microsoft Transaction Server, 5-28
- using with the Oracle ODBC Driver and Microsoft Transaction Server, 5-26
- computer on which Microsoft Transaction Server is installed
- configuration requirements, 3-2
- installation requirements, 2-4
- computer on which Oracle database is installed
- configuration requirements, 3-2
- installation requirements, 2-4
- configuration requirements
- modifying for Oracle Fail Safe, 3-11
- on client computer, 3-2
- on computer on which Microsoft Transaction Server is installed, 3-2
- on computer on which Oracle database is installed, 3-2
- CONNECT role, 3-6
- connection
- managing connection pooling, 6-3
- connection attribute
- setting with ODBC, 5-26
- connection pooling
- client side registry parameters, 6-3
- differences between Oracle Call Interface, Microsoft Transaction Server, and Oracle Net connection pooling, 7-7
- emptying connection pools, 7-4
- integration with Microsoft Transaction Server, 5-4
- managing connections, 6-3
- obtaining environment handles, 5-13
- obtaining service handles, 5-13
- releasing connections, 5-16
- responsibilities, 5-4
- using OraMTSSvcGet() function, 5-13
D
- Data Manipulation Language (DML)
- using in shared server configurations, 7-5
- database links
- with Microsoft Transaction Server, 7-5
- DBMS_JOBS package, 3-6
- DBMS_TRANSACTION package, 3-6
- DCOM. See Distributed Component Object Model (DCOM)
- demos
- directory installation location, 4-3
- Microsoft application demo, 4-2, 4-7
- running the Microsoft application demo, 4-5
- running the omtssamp.sql script, 4-5
- using the mtsdemousr username, 4-4
- using Visual C++, 4-5
- verifying Microsoft application demo installation, 4-5
- verifying the Oracle database includes the proper tables, 4-3
- Distributed Component Object Model (DCOM), 1-2
- distributed transactions
- in-doubt, 7-7
- DML. See Data Manipulation Language (DML)
E
- environment handles, 5-13
F
- features, new, xx
- FORCE_ANY_TRANSACTION privilege, 3-6
G
- getting started
- with Microsoft Transaction Server and an Oracle database, 1-5
H
- hardware configuration
- optimizing to improve performance, 6-2
I
- in-doubt transactions
- definition, 7-7
- JOB_QUEUE_PROCESSES initialization parameter, 3-5
- resolving, 3-3
- scheduling automatic recovery, 3-4
- starting SNP processes, 3-4
- viewing, 3-10
- initialization parameters
- JOB_QUEUE_PROCESSES, 3-5
- OS_ROLES, 6-5
- PROCESSES, 6-8
- SESSIONS, 6-8
- installation
- of Microsoft Transaction Server and an Oracle database on separate computers, 2-2
- of Microsoft Transaction Server and an Oracle database on the same computer, 2-2
- of Oracle MTS Recovery Service, 2-3
- installation requirements
- for client computer, 2-4
- for computer on which Microsoft Transaction Server is installed, 2-4
- for computer on which Oracle database is installed, 2-4
- for computer running Oracle Fail Safe, 2-3
- Microsoft Internet Information Server, 2-4
- Microsoft Transaction Server, 2-3, 2-4
- Oracle database server, 2-4
- Oracle Net Manager, 2-4
- Oracle Net Services for the client, 2-4
- Oracle Net Services for the server, 2-4
- Oracle Objects for OLE, 2-4
- Oracle ODBC Driver, 2-4
- Oracle Services for Microsoft Transaction Server, 2-4
- required RAM, 2-3
- Service Pack 5.0 or greater, 2-4
- SQL*Plus, 2-4
J
- JOB_QUEUE_PROCESSES initialization parameter, 3-5
M
- Microsoft application demo
- installation location, 4-3
- overview of database contents, 4-3
- running, 4-5
- running the omtssamp.sql script, 4-5
- using Microsoft Developer Studio, 4-6
- using Oracle Call Interface, 4-2
- using Oracle Provider for OLE DB, 4-7
- using the mtsdemousr username, 4-4
- using the Oracle ODBC Driver, 4-7
- using Visual C++, 4-5
- verifying installation, 4-5
- verifying the Oracle database includes the proper tables, 4-3
- Windows 2000, A-2
- Microsoft Developer Studio
- using with the Microsoft application demo, 4-6
- Microsoft Distributed Transaction Coordinator (MS DTC)
- COM components running in an MS DTC-coordinated transaction, 5-8
- enlisting, 5-19
- in a cluster, 3-11
- on Windows 2000, A-2
- responsibilities, 5-2, 5-4
- starting, 6-9
- using with Oracle Service for MTS, 2-3
- Microsoft Internet Information Server
- installation requirements, 2-4
- Microsoft Management Console
- installation methods, 2-4
- on Windows 2000, A-2
- Microsoft Transaction Server
- benefits, 1-2
- changing the administrator username, 3-6
- client computer responsibilities, 5-4
- COM components running in a transaction, 5-7
- components running in an MS DTC-coordinated transaction, 5-8
- connection pooling responsibilities, 5-4
- creating the administrator user account, 3-6
- database links, 7-5
- definition, 1-2
- designing an application with multiple databases, 7-5
- getting started with an Oracle database, 1-5
- increasing the timeout parameter on Windows 2000, A-3
- increasing the timeout parameter on Windows NT, 6-6
- installation requirements, 2-3, 2-4
- integration with an Oracle database server, 1-3
- migration from a previous installation, 2-5
- MS DTC responsibilities, 5-4
- Oracle Call Interface responsibilities, 5-4
- Oracle database server responsibilities, 5-4
- Oracle Objects for OLE responsibilities, 5-4
- Oracle ODBC Driver responsibilities, 5-4
- Oracle Provider for OLE DB responsibilities, 5-4
- programming with Microsoft's Oracle ODBC Driver, 5-26
- programming with Oracle Call Interface, 5-9
- programming with Oracle Objects for OLE, 5-29
- programming with Oracle ODBC Driver, 5-26
- programming with Oracle Provider for OLE DB, 5-29
- registering COM components, 5-5
- scheduling transaction recovery, 3-4
- starting MS DTC, 6-9
- three-tiered architecture model, 1-2
- using Oracle Call Interface with the Microsoft application demo, 4-2
- using with Microsoft's Oracle ODBC Driver, 5-28
- using with the Oracle ODBC Driver, 5-26
- Microsoft Transaction Server demos
- using Oracle Call Interface, 4-2
- using Oracle Provider for OLE DB with the Microsoft application demo, 4-7
- using the Oracle ODBC Driver with the Microsoft application demo, 4-7
- migration
- from a previous Oracle Services for Microsoft Transaction Server installation, 2-5
- requirements, 2-5
- MS DTC. See Microsoft Distributed Transaction Coordinator (MS DTC)
- mtsdemo username, 4-3
- using the account and receipt tables, 4-3
- using with Microsoft application demo, 4-3
- mtsdemousr username
- using the Microsoft application demo, 4-4
- MTSSamples.dsn file
- using with the Oracle ODBC Driver, 5-27
- mtssys username
- changing the password, 3-6
- default administrator user account, 3-6
- mtxstop.exe file
- running, 7-4
N
- net service name
- changes that impact connection pooling, 7-4
- network interconnects
- optimizing to improve performance, 6-2
- new features, xx
- nonpooled Oracle Call Interface connection
- OraMTSJoinTxn function, 5-23
O
- OCI. See Oracle Call Interface (OCI)
- OCI_THREADED flag
- passing, 5-10
- OCIInitialize function
- calling, 5-10
- ODBC. See Open Database Connectivity (ODBC)
- OLE DB. See Oracle Provider for OLE DB
- omtssamp.sql script, 4-5, 5-29
- OO4O. See Oracle Objects for OLE (OO4O)
- Open Database Connectivity (ODBC)
- configuring Microsoft's Oracle ODBC Driver with Microsoft Transaction Server, 5-29
- configuring the Oracle ODBC Driver with Microsoft Transaction Server, 5-27
- Oracle ODBC Driver installation requirements, 2-4
- Oracle ODBC Driver responsibilities, 5-4
- Oracle ODBC Driver with Microsoft Transaction Server, 5-4
- programming with Microsoft Transaction Server, 5-26
- setting the connection attribute, 5-26
- using Microsoft's Oracle ODBC Driver with Microsoft Transaction Server, 5-28
- using the MTSSamples.dsn file with the Oracle ODBC Driver, 5-27
- using the Oracle ODBC Driver with Microsoft Transaction Server, 5-26
- using the Oracle ODBC Driver with the Microsoft application demo, 4-7
- using the SQL_ATTR_ENLIST_IN_DTC parameter, 5-26
- using the SQLSetConnectAttr function, 5-26
- operating systems
- installation, 2-3
- Oracle Call Interface (OCI)
- caution against using OCITransCommit() and OCITransAbort(), 5-9
- connection pooling differences with Oracle Call Interface, Oracle Net, and Microsoft Transaction Server, 7-7
- de-enlisting an MS DTC-coordinated transaction, 5-17
- enlisting an MS DTC-coordinated transaction, 5-17, 5-19
- obtaining pooled or standard Oracle Call Interface connections, 5-18, 5-20
- obtaining pooled Oracle Call Interface connections, 5-14
- OraMTSEnlCtxGet() function, 5-20
- OraMTSEnlCtxGet() function parameters, 5-20
- OraMTSJoinTxn() function, 5-23
- OraMTSJoinTxn() function parameters, 5-23
- OraMTSOCIErrGet() function, 5-25
- OraMTSOCIErrGet() function parameters, 5-25
- OraMTSSvcEnlist() function, 5-17
- OraMTSSvcEnlist() function parameters, 5-17
- OraMTSSvcEnlistEx() function, 5-19
- OraMTSSvcEnlistEx() function parameters, 5-19
- OraMTSSvcGet() function, 5-13
- OraMTSSvcGet() function parameters, 5-13
- OraMTSSvcRel() function, 5-16
- OraMTSSvcRel() function parameters, 5-16
- OraMTSTransTest() function, 5-24
- OraMTSTransTest() function parameters, 5-24
- overview of connection pooling, 5-9
- programming with Microsoft Transaction Server, 5-9
- releasing pooled Oracle Call Interface connections, 5-16
- responsibilities, 5-4
- sample file location, 5-11
- using with the Microsoft application demo, 4-2
- Oracle database server
- changing init.ora file parameter settings, 6-8
- installation requirements, 2-4
- integration with Microsoft Transaction server, 1-3
- no Microsoft Transaction Server integration with releases prior to 8.0.6, 2-4
- responsibilities, 5-4
- Oracle Fail Safe
- installation requirements, 2-3
- modifying registry parameters, 3-11
- Oracle Manager for MTS Services snap-in
- no longer required, xxi
- Oracle MTS Recovery Service
- installation, 2-3
- resolving in-doubt transactions, 3-3
- trace file output, 7-3
- Oracle Net Manager
- installation requirements, 2-4
- Oracle Net Services for the client
- installation requirements, 2-4
- Oracle Net Services for the server
- installation requirements, 2-4
- Oracle Objects for OLE (OO4O)
- installation requirements, 2-4
- programming with Microsoft Transaction Server, 5-29
- responsibilities, 5-4
- with Microsoft Transaction Server, 5-4
- Oracle ODBC Driver. See Open Database Connectivity (ODBC)
- Oracle Provider for OLE DB
- integration with Microsoft Transaction Server, 5-4
- programming with Microsoft Transaction Server, 5-29
- responsibilities, 5-4
- using with the Microsoft application demo, 4-7
- Oracle Service for MTS
- deleting, 2-6
- deleting roles and privileges of inactive users, 2-10
- modifying Oracle Service for MTS in the registry, 2-11
- obsolete in Oracle9i, xx
- preparing to delete, 2-6
- using with MS DTC, 2-3
- Oracle Services for Microsoft Transaction Server
- installable product, 3-2
- installation methods, 2-4
- installation requirements, 2-4
- oramts_2pc_pending
- views, 3-9
- ORAMTS_CFLG_ALLDEFAULT flag
- description, 5-13
- ORAMTS_CFLG_NOIMPLICIT flag
- description, 5-14
- ORAMTS_CFLG_PRELIMAUTH flag
- description, 5-14
- using, 5-15
- ORAMTS_CFLG_SYSDBALOGN flag
- description, 5-14
- using, 5-15
- ORAMTS_CFLG_SYSOPRLOGN flag
- description, 5-14
- using, 5-15
- ORAMTS_CFLG_UNIQUESRVR flag
- description, 5-14
- ORAMTS_CONN_POOL_TIMEOUT registry parameter, 6-4
- ORAMTS_CP_TRACE_DIRECTORY registry parameter, 7-2
- ORAMTS_CP_TRACE_LEVEL registry parameter, 7-2
- ORAMTS_ENFLG_DEFAULT flag
- description, 5-17, 5-19
- ORAMTS_NET_CACHE_MAXFREE registry parameter, 6-4
- ORAMTS_NET_CACHE_TIMEOUT registry parameter, 6-4
- ORAMTS_ORADB registry parameter, 2-13
- ORAMTS_OSCREDS_MATCH_LEVEL registry parameter, 6-5
- ORAMTS_SUNAME registry parameter, 2-13
- ORAMTS_SUPWD registry parameter, 2-13
- oramtsadmin.sql script
- creating the Microsoft Transaction Server administrator user account, 3-6
- creating the PL/SQL package, 3-6
- oramts.dll file
- definition, 7-2
- OraMTSEnlCtxGet() function
- enlisting pooled or standard Oracle Call Interface connections, 5-20
- Oracle Call Interface function, 5-20
- OraMTSEnlCtxRel() function
- destroying a previously set up enlistment context, 5-22
- parameters, 5-22
- returning ORAMTSERR_NOERROR, 5-22
- syntax, 5-22
- ORAMTSERR_NOERROR
- returning upon acquiring a connection, 5-18, 5-20, 5-23
- returning upon obtaining a connection, 5-14
- returning upon releasing a connection, 5-16
- OraMTSJoinTxn() function, 5-10
- enlisting a nonpooled Oracle Call Interface connection, 5-23
- Oracle Call Interface function, 5-23
- parameters, 5-23
- returning ORAMTSERR_NOERROR upon acquiring a connection, 5-23
- syntax, 5-23
- OraMTSOCIErrGet() function, 5-25
- Oracle Call Interface function, 5-25
- parameters, 5-25
- retrieving the Oracle Call Interface error code, 5-25
- syntax, 5-25
- OraMTSSvcEnlist() function
- enlisting pooled or standard Oracle Call Interface connections, 5-18
- Oracle Call Interface function, 5-17
- ORAMTS_ENFLG_DEFAULT flag, 5-17, 5-19
- parameters, 5-17
- restrictions on use, 5-17
- returning ORAMTSERR_NOERROR upon acquiring a connection, 5-18
- syntax, 5-17
- OraMTSSvcEnlistEx() function
- differences with OraMTSSvcEnlist() function, 5-20
- Oracle Call Interface function, 5-19
- parameters, 5-19
- restrictions on use, 5-19
- returning ORAMTSERR_NOERROR upon acquiring a connection, 5-20
- syntax, 5-19
- OraMTSSvcGet() function
- Oracle Call Interface function, 5-13
- ORAMTS_CFLG_ALLDEFAULT flag, 5-13
- ORAMTS_CFLG_NOIMPLICIT flag, 5-14
- ORAMTS_CFLG_PRELIMAUTH flag, 5-14
- ORAMTS_CFLG_SYSDBALOGN flag, 5-14
- ORAMTS_CFLG_SYSOPRLOGN flag, 5-14
- ORAMTS_CFLG_UNIQUESRVR flag, 5-14
- overview, 5-9, 5-13
- parameters, 5-13
- responsibilities, 5-13
- returning a pooled connection, 5-14
- returning ORAMTSERR_NOERROR upon acquiring a connection, 5-14
- syntax, 5-13
- OraMTSSvcRel() function
- Oracle Call Interface function, 5-16
- overview, 5-9
- parameters, 5-16
- releasing a pooled connection, 5-16
- returning ORAMTSERR_NOERROR upon releasing a connection, 5-16
- syntax, 5-16
- OraMTSTransTest() function
- Oracle Call Interface function, 5-24
- parameters, 5-24
- syntax, 5-24
- ORAOCI registry parameter
- setting, 5-29
- OS_ROLES initialization parameter, 6-5
P
- passwords
- changing for mtssys username, 3-6
- performance
- improving, 6-2
- pooled connection
- releasing, 5-16
- privileges
- deleting privileges of an inactive Oracle Service for MTS user, 2-10
- of administrator user account, 3-6
- utl_oramts.sql script, 3-6
- PROCESSES initialization parameter
- changing the value, 6-8
- programming
- with Oracle Provider for OLE DB and Microsoft Transaction Server, 5-29
- programming methods
- optimizing to improve performance, 6-2
- prvtoramts.plb file, 3-4
- public procedures
- exposing, 3-7
- recover_automatic, 3-8
- show_indoubt, 3-7
- utl_oramts.forget_RMs, 3-9
R
- receipt table
- using with Microsoft application demo, 4-3
- recover_automatic
- public procedure, 3-8
- recovery
- of in-doubt transactions, 3-3
- registry
- modifying the Oracle Service for MTS database connection, 2-11
- modifying values for Oracle Fail Safe configurations, 3-11
- trace file settings, 7-2
- registry parameters
- modifying for Oracle Fail Safe, 3-11
- ORAMTS_CONN_POOL_TIMEOUT, 6-4
- ORAMTS_CP_TRACE_DIRECTORY, 7-2
- ORAMTS_CP_TRACE_LEVEL, 7-2
- ORAMTS_NET_CACHE_MAXFREE, 6-4
- ORAMTS_NET_CACHE_TIMEOUT, 6-4
- ORAMTS_ORADB, 2-13
- ORAMTS_OSCREDS_MATCH_LEVEL, 6-5
- ORAMTS_SUNAME, 2-13
- ORAMTS_SUPWD, 2-13
- Resource Manager (RM)
- responsibilities, 5-2, 5-4
- revokeuser.sql script
- running, 2-10
- RM. See Resource Manager (RM)
- roles
- deleting roles of an inactive Oracle Service for MTS user, 2-10
- of administrator user account, 3-6
S
- samples
- Microsoft application demo, 4-2, 4-7
- SELECT_CATALOG_ROLE role, 3-6
- service
- deleting, 2-6
- service handles, 5-13
- Service Pack 5.0 or greater
- correcting Windows NT Explorer crashes, 7-3
- installation requirements, 2-4
- SESSIONS initialization parameter
- changing the value, 6-8
- shared server configurations, 7-5
- show_indoubt
- public procedure, 3-7
- SNP processes
- starting, 3-4
- SQL*Plus
- installation requirements, 2-4
T
- three-tiered architecture, 1-2, 1-4, 5-2
- timeout parameter
- increasing for Microsoft Transaction Server, 6-6
- tnsnames.ora file
- ensuring that entries point to the correct database, 2-12
- setting for shared server configurations, 7-5
- trace files
- filename conventions, 7-2
- monitoring for successful recovery messages, 2-8
- Oracle MTS Recovery Service, 7-3
- oramts.dll, 7-2
- registry settings, 7-2
- using, 7-2
- transaction recovery
- JOB_QUEUE_PROCESSES initialization parameter, 3-5
- Oracle Fail Safe environment, 3-3
- overview, 3-3
- scheduling, 3-4
- starting SNP processes, 3-4
- troubleshooting, 3-10
- transactional applications
- on Windows 2000, A-2
- transactions
- increasing the transaction timeout parameter, 6-6
- overview of COM component integration, 5-2
- troubleshooting
- correcting Oracle Net changes that impact connection pooling, 7-4
- correcting Windows NT Explorer crashes, 7-3
- dropping the administrator user account, 7-8
- increasing the transaction timeout parameter, 6-6
- starting MS DTC, 6-9
- transaction recovery, 3-10
- using trace files, 7-2
- tuning
- changing the SESSIONS and PROCESSES init.ora parameters, 6-8
- improving performance, 6-2
- increasing the transaction timeout parameter, 6-6
- increasing the transaction timeout parameter on Windows 2000, A-3
- managing connection pooling, 6-3
- two-phase commit protocol, 7-7
U
- usernames
- using with Microsoft application demo, 4-7
- utl_oramts PL/SQL package
- exposing public procedures, 3-7
- utl_oramts.forget_RMs
- public procedure, 3-9
- utl_oramts.sql script, 3-4
- privileges and roles granted, 3-6
V
- vcacct.dll file, 4-2
- building, 4-6
- views
- oramts_2pc_pending, 3-9
- Visual C++
- using with the Microsoft application demo, 4-5
W
- Windows 2000
- differences with using Microsoft Transaction Server on Windows NT, A-2
- Microsoft application demo not included, 4-1
- Windows NT
- differences between using Microsoft Transaction Server on Windows 2000, A-2
- Windows NT Explorer
- correcting crashes, 7-3