VoteRequest - Call-Level Interface Version 2

VoteRequest

Purpose

Requests a vote in a 2PC session.

Usage Notes

Two-phase commit is available only for Teradata Database for UNIX version 2 release 2 (or later), and for Teradata DBS for TOS version 1 release 5 (or later).

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 Teradata Database voted Yes, and that the transaction is now in‑doubt.

A Failure parcel, indicating either that the Teradata Database has voted No and rolled the transaction back, or that the session is not in 2PC mode. The error code in Failure parcel indicates why the Teradata Database did not commit the transaction

Parcel Data

The following information applies to the VoteRequest parcel.

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.