• In the recovery, the transaction records left in the LLR table are taken as completing transactions.The LLR library provides an XA switch to emulate XA operations and several uniform APIs for LLR server/TMS. Configure LLR library in the RM file under ${TUXDIR}/udataobj as follows:The Table 20‑1 shows the LLR library details:
Table 20‑1 LLR Library ${TUXDIR}/lib/libllroraesql.soIn general, the LLR XA switch variable is tuxllrsw_[name] and the LLR XA switch name is tuxllr_[name]. The related library name is libllr[name], where [name] consists of RM ID and implementation ID. For example, ora indicates Oracle database, and esql indicates embedded SQL.The Table 20‑2 shows the details.
Table 20‑2 OPENINFO Format TuxLLR is a specific optional field for Tuxedo LLR, which defines the LLR table name. If not defined, the default name is used.The LLR table is used to store the committing TLOG for transactions that involves LLR server. The default table name is TUXLLR_[DOMAINID]. If [DOMAINID] is empty, DOM is used. When you specify the LLR table name using TuxLLR, make sure different LLR tables are used for different tuxedo domains in a same non-XA resource; otherwise the recovery might work incorrectly.Specifies a multiplier of the basic SCANUNIT between LLR completed records lazy deletions. The value must be greater than 0. If this parameter is not specified, the default is set so that SCANUNIT * LLR_DELDELAY is approximately 30 seconds, however, if the SCANUNIT value is greater than 30 seconds, LLR_DELDELAY is set to 1 if not specified.Listing 20‑2 Configuring the RM FileListing 20‑3 Configuring UBBCONFIGListing 20‑4 Building LLR Servers and TMSUnexpected node crash (e.g. BB is lost) leaves the completed records in the LLR table that does not be purged in time. Each record needs on entry in the transaction table during Tuxedo recovery. The transaction table size in BB is specified by MAXGTT. If MAXGTT is not big enough to store these records, BBL fails to boot up when the node is restored. When that happens, increase the MAXGTT value and retry.It is recommended that specifying a sufficient LLR_DELSWAPSIZE to accommodate at least all completed LLR involved 2PC gtrids in a scan unit.
Note:
•
•
• According to the MRM group, the OPENINFO used by the LLR server must be specified in the GROUP section
•
• RM-Specific (specific to libllroraesql)The simulating XA switch tuxllrsw_oraesql does not support thread context. According to LLR involved MRM group, the other XA connections to Oracle database should not enable the property Threads in the OPENINFO. Otherwise the SQL jobs on LLR connection in the application server cannot work.