Skip Headers
Oracle® Services for Microsoft Transaction Server Developer's Guide
10
g
Release 2 (10.2) for Microsoft Windows
Part Number B14320-01
Home
Book List
Contents
Master Index
Contact Us
Previous
View PDF
Index
A
C
D
E
F
G
I
J
M
N
O
P
R
S
T
U
V
W
A
account table
using with Microsoft application demo,
4.1.1
administrator username
dropping,
7.7
Microsoft Transaction Server,
3.3.2
C
Component Object Model (COM)
marking components as transactional,
1.2
programming with Oracle Call Interface and Microsoft Transaction Server,
5.3
registering in a Microsoft Transaction Server environment,
5.2.1
running in a Microsoft Transaction Server
coordinated transaction,
5.2.2
running in an MS DTC-coordinated transaction,
5.2.3
using with Microsoft Oracle ODBC Driver,
5.4.3
using with the Oracle ODBC Driver and Microsoft Transaction Server,
5.4.2
computer on which Microsoft Transaction Server is installed
installation requirements,
2.1.1
computer on which Oracle Database is installed
installation requirements,
2.1.2
configuration requirements
modifying for Oracle Fail Safe,
3.5
on client computer,
3.1
on computer on which Microsoft Transaction Server is installed,
3.1
on computer on which Oracle Database is installed,
3.1
connection
managing connection pooling,
6.2
connection attribute
setting with ODBC,
5.4.1
connection pooling
client side registry parameters,
6.2
emptying connection pools,
7.3
managing connections,
6.2
obtaining service handles,
5.3.3
releasing connections,
5.3.4
using OraMTSSvcGet() function,
5.3.3
CREATE SESSION role,
3.3.2
D
Data Manipulation Language (DML)
using in shared server configurations,
7.4
database job-queue processes
starting,
3.3.1
DBMS_JOBS package,
3.3.2
DBMS_TRANSACTION package,
3.3.2
DCOM.
See
Distributed Component Object Model (DCOM)
demos
Microsoft application,
4.3
Microsoft application demo,
4.1
running the Microsoft application demo,
4.1.3
running the omtssamp.sql script,
4.1.2
using the mtsdemousr username,
4.1.2
using Visual C++,
4.1.3
verifying Microsoft application demo installation,
4.1.3
verifying the Oracle Database includes the proper tables,
4.1.2
differences with OraMTSJoinTxn() function,
5.3.6
Distributed Component Object Model (DCOM),
1.1
distributed transactions
in-doubt,
7.6
support for serializable isolation level,
1.1.1
DML.
See
Data Manipulation Language (DML)
E
Enterprise Services,
1.1.2
F
FORCE_ANY_TRANSACTION privilege,
3.3.2
G
getting started
with Microsoft Transaction Server and an Oracle Database,
1.3
I
in-doubt transactions
JOB_QUEUE_PROCESSES initialization parameter,
3.3.1
resolving,
3.2
scheduling automatic recovery,
3.3
starting database job-queue processes,
3.3.1
viewing,
3.4
initialization parameters
JOB_QUEUE_PROCESSES,
3.3.1
PROCESSES,
6.4
SESSIONS,
6.4
installation
of Oracle MTS Recovery Service,
2.1
installation requirements
for computer on which Microsoft Transaction Server is installed,
2.1.1
for computer on which Oracle Database is installed,
2.1.2
for computer running Oracle Fail Safe,
2.1
Microsoft Transaction Server,
2.1
,
2.1.1.2
Oracle Net Manager,
2.1.1.1
Oracle Net Services for the client,
2.1.1.1
Oracle Net Services for the server,
2.1.2.1
Oracle Objects for OLE,
2.1.1.1
Oracle ODBC Driver,
2.1.1.1
Oracle Services for Microsoft Transaction Server,
2.1.1.1
required RAM,
2.1
Service Pack 5.0 or greater,
2.1.1.2
SQL*Plus,
2.1.1.1
,
2.1.2.1
J
JOB_QUEUE_PROCESSES initialization parameter,
3.3.1
M
Microsoft application demo
overview of database contents,
4.1.1
running,
4.1.3
running the omtssamp.sql script,
4.1.2
using Microsoft Developer Studio,
4.1.3
using Oracle Call Interface,
4.1
using Oracle Provider for OLE DB,
4.3
using the mtsdemousr username,
4.1.2
using the Oracle ODBC Driver,
4.2
using Visual C++,
4.1.3
verifying installation,
4.1.3
verifying the Oracle Database includes the proper tables,
4.1.2
Microsoft Developer Studio
using with the Microsoft application demo,
4.1.3
Microsoft Distributed Transaction Coordinator (DTC),
1.1.2
Microsoft Distributed Transaction Coordinator (MS DTC)
COM components running in an MS DTC-coordinated transaction,
5.2.3
in a cluster,
3.5
starting,
6.5
using with Oracle Service for MTS,
2.1
Microsoft Transaction Server
benefits,
1.1
changing the administrator username,
3.3.2
COM components running in a transaction,
5.2.2
components running in an MS DTC-coordinated transaction,
5.2.3
creating the administrator user account,
3.3.2
definition,
1.1
getting started with an Oracle Database,
1.3
installation requirements,
2.1
,
2.1.1.2
integration with an Oracle Database,
1.2
programming with Microsoft Oracle ODBC Driver,
5.4
programming with Oracle Call Interface,
5.3
programming with Oracle ODBC Driver,
5.4
registering COM components,
5.2.1
scheduling transaction recovery,
3.3
starting MS DTC,
6.5
upgrade from a previous installation,
2.2
using Oracle Call Interface with the Microsoft application demo,
4.1
using with Microsoft Oracle ODBC Driver,
5.4.3
using with the Oracle ODBC Driver,
5.4.2
Microsoft Transaction Server demos
using Oracle Provider for OLE DB with the Microsoft application demo,
4.3
using the Oracle ODBC Driver with the Microsoft application demo,
4.2
migration.
See
upgrade
mtsdemo username,
4.1.1
using the account and receipt tables,
4.1.1
using with Microsoft application demo,
4.1.1
mtsdemousr username
using the Microsoft application demo,
4.1.2
MTSSamples.dsn file
using with the Oracle ODBC Driver,
5.4.2
mtssys username
changing the password,
3.3.2
default administrator user account,
3.3.2
mtxstop.exe file
running,
7.3
N
net service name
changes that impact connection pool,
7.3
changes that impact connection pooling,
7.3
.NET, Enterprise Services,
1.1.2
nonpooled Oracle Call Interface connection
OraMTSJoinTxn function,
5.3.9
O
OCI_THREADED flag
passing,
5.3
OCIInitialize function
calling,
5.3
ODBC.
See
Open Database Connectivity (ODBC)
omtssamp.sql script,
4.1.2
,
5.4.3
Open Database Connectivity (ODBC)
configuring Microsoft Oracle ODBC Driver with Microsoft Transaction Server,
5.4.3
configuring the Oracle ODBC Driver with Microsoft Transaction Server,
5.4.2
Oracle ODBC Driver installation requirements,
2.1.1.1
programming with Microsoft Transaction Server,
5.4
setting the connection attribute,
5.4.1
using Microsoft Oracle ODBC Driver with Microsoft Transaction Server,
5.4.3
using the MTSSamples.dsn file with the Oracle ODBC Driver,
5.4.2
using the Oracle ODBC Driver with Microsoft Transaction Server,
5.4.2
using the Oracle ODBC Driver with the Microsoft application demo,
4.2
using the SQL_ATTR_ENLIST_IN_DTC parameter,
5.4.1
using the SQLSetConnectAttr function,
5.4.1
Oracle Call Interface (OCI),
4.1
enlisting an MS DTC-coordinated transaction,
5.3.5
obtaining pooled or standard Oracle Call Interface connections,
5.3.5
obtaining pooled Oracle Call Interface connections,
5.3.3
OraMTSEnlCtxGet() function,
5.3.7
OraMTSEnlCtxGet() function parameters,
5.3.7
OraMTSJoinTxn() function,
5.3.9
OraMTSOCIErrGet() function,
5.3.11
OraMTSOCIErrGet() function parameters,
5.3.11
OraMTSSvcEnlist() function,
5.3.5
OraMTSSvcEnlist() function parameters,
5.3.5
OraMTSSvcGet() function,
5.3.3
OraMTSSvcGet() function parameters,
5.3.3
OraMTSSvcRel() function,
5.3.4
programming with Microsoft Transaction Server,
5.3
releasing pooled Oracle Call Interface connections,
5.3.4
Oracle Database
changing init.ora file parameter settings,
6.4
integration with Microsoft Transaction server,
1.2
Oracle Fail Safe
installation requirements,
2.1
modifying registry parameters,
3.5
Oracle MTS Recovery Service
installation,
2.1
resolving in-doubt transactions,
3.2
trace file output,
7.1
Oracle Net Manager
installation requirements,
2.1.1.1
Oracle Net Services for the client
installation requirements,
2.1.1.1
Oracle Net Services for the server
installation requirements,
2.1.2.1
Oracle Objects for OLE (OO4O)
installation requirements,
2.1.1.1
Oracle Provider for OLE DB
using with the Microsoft application demo,
4.3
Oracle Service for MTS
deleting,
2.2.1
deleting roles and privileges of inactive users,
2.3
modifying Oracle Service for MTS in the registry,
2.4
preparing to delete,
2.2.1
using with MS DTC,
2.1
Oracle Services for Microsoft Transaction,
3.1
Oracle Services for Microsoft Transaction Server
installation requirements,
2.1.1.1
oramts_2pc_pending
views,
3.3.2.4
ORAMTS_CFLG_ALLDEFAULT flag
description,
5.3.3
ORAMTS_CFLG_SYSDBALOGN flag
description,
5.3.3
using,
5.3.3
ORAMTS_CFLG_SYSOPRLOGN flag
description,
5.3.3
using,
5.3.3
ORAMTS_CONN_POOL_TIMEOUT registry parameter,
6.2.1
ORAMTS_ENFLG_DEFAULT flag
description,
5.3.5
,
5.3.6
ORAMTS_NET_CACHE_MAXFREE registry parameter,
6.2.1
ORAMTS_NET_CACHE_TIMEOUT registry parameter,
6.2.1
,
6.2.1
ORAMTS_OCI_OBJ_MODE registry parameter,
2.4.1
ORAMTS_ORADB registry parameter,
2.4.1
ORAMTS_OSCREDS_MATCH_LEVEL registry parameter,
6.2.1
ORAMTS_SUNAME registry parameter,
2.4.1
ORAMTS_SUPWD registry parameter,
2.4.1
oramtsadmin.sql script
creating the Microsoft Transaction Server administrator user account,
3.3.2
creating the PL/SQL package,
3.3.2
oramts.dll file
definition,
7.1
OraMTSEnlCtxGet() function
Oracle Call Interface function,
5.3.7
OraMTSEnlCtxRel() function
destroying a previously set up enlistment context,
5.3.8
parameters,
5.3.8
returning ORAMTSERR_NOERROR,
5.3.8
syntax,
5.3.8
ORAMTSERR_ILLEGAL_OPER
returning upon acquiring a connection,
5.3.6
ORAMTSERR_ILLEGAL_OPER returning upon acquiring a connection,
5.3.6
ORAMTSERR_NOERROR
returning upon acquiring a connection,
5.3.5
,
5.3.9
returning upon obtaining a connection,
5.3.3
returning upon releasing a connection,
5.3.4
OraMTSJoinTxn() function
enlisting a nonpooled Oracle Call Interface connection,
5.3.9
Oracle Call Interface function,
5.3.9
returning ORAMTSERR_NOERROR upon acquiring a connection,
5.3.9
syntax,
5.3.9
OraMTSOCIErrGet() function
parameters,
5.3.11
retrieving the Oracle Call Interface error code,
5.3.11
syntax,
5.3.11
OraMTSSvcEnlist() function
enlisting pooled or standard Oracle Call Interface connections,
5.3.5
Oracle Call Interface function,
5.3.5
ORAMTS_ENFLG_DEFAULT flag,
5.3.5
,
5.3.6
parameters,
5.3.5
restrictions on use,
5.3.5
returning ORAMTSERR_NOERROR upon acquiring a connection,
5.3.5
syntax,
5.3.5
OraMTSSvcEnlistEx() function
restrictions on use,
5.3.6
returning ORAMTSERR_ILLEGAL_OPER upon acquiring a connection,
5.3.6
syntax,
5.3.6
OraMTSSvcGet() function
Oracle Call Interface function,
5.3.3
ORAMTS_CFLG_ALLDEFAULT flag,
5.3.3
ORAMTS_CFLG_SYSDBALOGN flag,
5.3.3
ORAMTS_CFLG_SYSOPRLOGN flag,
5.3.3
overview,
5.3
parameters,
5.3.3
responsibilities,
5.3.3
returning a pooled connection,
5.3.3
returning ORAMTSERR_NOERROR upon acquiring a connection,
5.3.3
syntax,
5.3.3
OraMTSSvcRel() function
Oracle Call Interface function,
5.3.4
overview,
5.3
releasing a pooled connection,
5.3.4
returning ORAMTSERR_NOERROR upon releasing a connection,
5.3.4
syntax,
5.3.4
OraMTSTransTest() function
syntax,
5.3.10
ORAOCI registry parameter
setting,
5.4.3
P
packages
DBMS_JOBS,
3.3.2
DBMS_TRANSACTION,
3.3.2
passwords
changing for mtssys username,
3.3.2
pooled connection
releasing,
5.3.4
privileges
deleting privileges of an inactive Oracle Service for MTS user,
2.3
FORCE_ANY_TRANSACTION,
3.3.2
of administrator user account,
3.3.2
utl_oramts.sql script,
3.3.2
PROCESSES initialization parameter
changing the value,
6.4
programming methods
optimizing to improve performance,
6.1
prvtoramts.plb file,
3.3
public procedures
exposing,
3.3.2
recover_automatic,
3.3.2.2
show_indoubt,
3.3.2.1
utl_oramts.forget_RMs,
3.3.2.3
R
Real Application Clusters,
1.1.2
receipt table
using with Microsoft,
4.1.1
recover_automatic
public procedure,
3.3.2.2
recovery
of in-doubt transactions,
3.2
registry
modifying the Oracle Service for MTS database connection,
2.4
modifying values for Oracle Fail Safe configurations,
3.5
trace file settings,
7.1
registry parameters
modifying for Oracle Fail Safe,
3.5
ORAMTS_CONN_POOL_TIMEOUT,
6.2.1
ORAMTS_NET_CACHE_MAXFREE,
6.2.1
ORAMTS_NET_CACHE_TIMEOUT,
6.2.1
,
6.2.1
ORAMTS_OCI_OBJ_MODE,
2.4.1
ORAMTS_ORADB,
2.4.1
ORAMTS_OSCREDS_MATCH_LEVEL,
6.2.1
ORAMTS_SUNAME,
2.4.1
ORAMTS_SUPWD,
2.4.1
revokeuser.sql script
running,
2.3
roles
CREATE SESSION,
3.3.2
deleting roles of an inactive Oracle Service for MTS user,
2.3
of administrator user account,
3.3.2
SELECT_CATALOG_ROLE,
3.3.2
S
samples
Microsoft application demo,
4.1
SELECT_CATALOG_ROLE role,
3.3.2
serializable transactions,
1.1.1
service
deleting,
2.2.1
service handles,
5.3.3
Service Pack 5.0 or greater
correcting Windows NT Explorer crashes,
7.2
installation requirements,
2.1.1.2
SESSIONS initialization parameter
changing the value,
6.4
shared server configurations,
7.4
show_indoubt
public procedure,
3.3.2.1
SQL*Plus
installation requirements,
2.1.1.1
,
2.1.2.1
T
three-tiered architecture,
1.1
tnsnames.ora file
ensuring that entries point to the correct database,
2.4
setting for shared server configurations,
7.4
trace files
filename conventions,
7.1
monitoring for successful recovery messages,
2.2.1.4
Oracle MTS Recovery Service,
7.1
oramts.dll,
7.1
registry settings,
7.1
using,
7.1
transaction recovery
JOB_QUEUE_PROCESSES initialization parameter,
3.3.1
Oracle Fail Safe environment,
3.2
overview,
3.2
scheduling,
3.3
starting database job-queue processes,
3.3.1
troubleshooting,
3.4
transactions
ensuring consistency across data resources,
1.1.2
troubleshooting
correcting Oracle Net changes that impact connection pooling,
7.3
correcting Windows Explorer crashes,
7.2
dropping the administrator user account,
7.7
starting MS DTC,
6.5
transaction recovery,
3.4
using trace files,
7.1
tuning
change,
6.4
managing connection pooling,
6.2
two-phase commit protocol,
7.6
U
upgrade
from a previous Oracle Services for Microsoft Transaction Server installation,
2.2
requirements,
2.2
usernames
using with Microsoft application demo,
4.1.3
utl_oramts PL/SQL package
exposing public procedures,
3.3.2
utl_oramts.forget_RMs
public procedure,
3.3.2.3
utl_oramts.sql script,
3.3
privileges and roles granted,
3.3.2
V
vcacct.dll file,
4.1
building,
4.1.3
views
oramts_2pc_pending,
3.3.2.4
Visual C++
using with the Microsoft application demo,
4.1.3
W
Windows 2000
Microsoft application demo not included,
4
Windows Explorer
correcting crashes,
7.2
Scripting on this page enhances content navigation, but does not change the content in any way.