A.4 Configuring Database-Specific Software

To use the DB XA Module with the Oracle OCI Access Module:

• Run the xaview.sql script on your database server.

• Ensure that all users of XA connections have SELECT rights for database view DBA_PENDING_TRANSACTIONS.

To use the DB XA Module with the Sybase CT Access Module:

• Enable the distributed Transaction Management feature using the following command:

sp_configure `enable DTM', 1

• Grant to each user of the XA functionality the role dtm_tm_role:

sp_role "grant", dtm_tm_role, <user_name>

• Create an XA configuration file.

The Sybase XA configuration file contains one entry per LRM. The entry associates the LRM with a physical Adaptive Server name, and assigns pre-connection Client-Library capabilities and properties to the LRM. The simplest form of XA configuration file looks like this:

; Comment line as first line of file REQUIRED!
;
; Test XA configuration file
;
; "lrm" - names the logical connection as seen by the app 
;         and the TM.
; "server" - names the physical server as found in the 
;         interfaces files
; "capabilties" - lists pre-connection capabilties to be set 
;         (optional)
; "properties" - lists pre-connection properties to be set 
          (optional)
;

[all]
  logfile=/nfs/homes/user/xa_log
  traceflags=xa
        properties=CS_MAX_CONNECT=5

[xa]
  lrm=mylrm
  server=SYBASE120

[xa]
  lrm=lrmtest
  server=SYBASE125

There are many more properties that could be set in the XA configuration file. For detailed information about the structure of the XA configuration file, please refer to the XA Interface Integration Guide for CICS, Encina and Tuxedo.

• Create environment variable XACONFIGFILE, which points to the XA configuration file.

setenv XACONFIGFILE /usr/u/sybase/xaconfig1.txt

---

NOTE -- The DB XA Module supports XA functionality for Sybase 12.0 and above.

---

To use the DB XA Module with the DB2 CLI Access Module:

1. Set the TP_MON_NAME database manager configuration parameter to indicate the TPM being used.

2. If the TPM being used does not support holding cursors across transactions, do the following:

• Open the DB2 client initialization file db2cli.ini in the DB2 installation directory. If the file does not have a section named for the database alias to be used for XA connections, create one.

• Set the CURSORHOLD property equal to zero, as seen below.
  
  [DBAlias1]
  CURSORHOLD=0

Make sure to leave a blank line at the end of the db2cli.ini file.

© Copyright Rogue Wave Software, Inc. All Rights Reserved.
Rogue Wave and SourcePro are registered trademarks of Rogue Wave Software, Inc. in the United States and other countries. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.