VoteRequest - Teradata Director Program

Teradata® Director Program Reference - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Director Program
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-17
dita:mapPath
cki1641301536147.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
frc1470439950465
Product Category
Teradata Tools and Utilities

Purpose

Requests a vote in a Two-phase commit session.

Usage Notes

The vote request parcel can be sent alone, or in a message (at the end of a sequence of request and data parcels that define a Teradata SQL statement).

If the vote request is sent in the same message as a Teradata SQL statement, then the request follows the rules for a multi-statement request; that is, all statements succeed, or all fail.

If your program is using the Initiate with Protocol-Function with the vote protocol function, then the VoteRequest parcel is included after the request and data parcels.

The response is one of the following:
  • A Success parcel, indicating that the database voted Yes, and that the transaction is now in-doubt.
  • A Failure parcel, indicating either that the database has voted No and rolled the transaction back, or that the session is not in Two-phase commit mode. The error code in Failure parcel indicates why the database did not commit the transaction.

Parcel Data

Field information for the VoteRequest parcel is as follows:

Flavor Parcel Body Length Parcel Body Fields
115 64 Coordinator (32 bytes)
    RunUnitID (32 bytes)

Field Notes

  • The Coordinator field contains the text string name of the coordinator for the protocol.

    The string consists of a two-byte length, followed by a 30-byte name.

  • The RunUnitID field contains a text string identifier of the run unit currently active for the session.

    The string consists of a two-byte length, followed by a 30-byte name.