ATS and RIS Text File Contents

The information about failed replicated transactions that are shown in ATS and RIS text files is listed in rows that are prefaced by information labels.

The first three characters in each line of the ATS and RIS file describe the type of information for the line, as the following table defines. The first four labels apply to both ATS and RIS files. The last three labels apply to only RIS files.

Table 1. Information labels
Label	Name	Description
TXH	Transaction heading	This line contains information from the transaction header, including the sending server ID and the commit time, the receiving server ID and the received time, and any Enterprise Replication, SQL, or ISAM error information for the transaction.
RRH	Replicated row heading	This line contains header information from the replicated rows, including the row number within the transaction, the group ID, the replicate ID (same as replicate group ID if replicate is not part of any replicate group), the database, owner, table name, and the database operation.
RRS	Replicated row shadow columns	This line contains shadow column information from replicated rows, including the source server ID and the time when the row was updated on the source server. This line is printed only if the replicate is defined with a conflict-resolution rule.
RRD	Replicated row data	This line contains the list of replicated columns in the same order as in the SELECT statement in the cdr define replicate command. Each column is separated by a pipe character ( \| ) and displayed in ASCII format. When the spooling program encounters severe errors (for example: cannot retrieve the replicate ID for the replicated row; unable to determine the replicated column type, size, or length), it displays this row data in hexadecimal format. The spooling program also displays the row data in hexadecimal format if a row includes replicated UDT columns.
LRH	Local-row header	RIS only. Indicates if the local row is found in the delete table and not in the target table
LRS	Local-row shadow columns	RIS only. Contains the server ID and the time when the row was updated on the target server This line is printed only if the replicate is defined with a conflict resolution rule.
LRD	Local-row data	RIS only. Contains the list of replicated columns extracted from the local row and displayed in the same order as the replicated row data. Similar to the replicated row data, each column is separated by a ‘\|' and written in ASCII format. When the spooling program encounters severe errors (for example: cannot retrieve the replicate ID for the replicated row; unable to determine the replicated column type, size, or length) or the table includes UDT columns (whether defined for replication or not), it displays the replicated row data in hexadecimal format. In this case, the local row data is not spooled.

Changed Column Information

If you define a replicate to only replicate columns that changed, the RRD entry in the ATS and RIS file shows a ? for the value of any columns that are not available. For example:

RRD 427|amsterdam|?|?|?|?|?|?|?|?|?|?|?

For more information, see Replicate only changed columns.

BLOB and CLOB Information

If a replicate includes one or more BLOB or CLOB columns, the RRD entry in the ATS and RIS file displays the smart large object metadata (the in-row descriptor of the data), not the smart large object itself, in hexadecimal format.

BYTE and TEXT Information

When the information recorded in the ATS or RIS file includes BYTE or TEXT data, the replicated row data (RRD) information is reported, as the following examples show.

Example 1

<1200, TEXT, PB 877(necromsv) 840338515(00/08/17 20:21:55)>

In this example:

1200 is the size of the data.
TEXT is the data type (it is either BYTE or TEXT).
PB is the storage type (PB when the BYTE or TEXT is stored in the tblspace, BB for blobspace storage).
The next two fields are the server identifier and the time stamp for the column if the conflict-resolution rule is defined for this replicate and the column is stored in a tblspace.

<500 (NoChange), TEXT, PB 877(necromsv) 840338478(00/08/17 20:21:18)>

Example 2

In this example, 500 (NoChange) indicates that the TEXT data has a size of 500, but the data is not changed on the source server. Therefore, the data is not sent from the source server.

Example 3

<(Keep local blob),75400, BYTE, PB 877(necromsv) 840338515(00/08/17 20:21:55)>”)

In this example, (Keep local blob) indicates that the replicated data for this column is not applied on the target table, but instead the local BYTE data was kept. This usually happens when time stamp conflict resolution is defined and the local column has a time stamp greater than the replicated column.

UDT Information

If a replicate includes one or more UDT columns, the RRD entry in the ATS and RIS files displays the row data in delimited format as usual, except the string <skipped> is put in place of UDT column values. For example, the following row shows information about a table with columns of type INTEGER, UDT, CHAR(10), and UDT:

RRD 334|<skipped>|amsterdam|<skipped>

TimeSeries information

If a replicate includes a TimeSeries column, an RTS row displays the time series instance ID and the timestamp of the element. If the failed replicated transaction includes a TimeSeries routine that affects a range of elements, both the starting and ending timestamps are shown. The following example shows three failed replication transactions that include a TimeSeries column:

TXH Source ID:100 / Name:g_delhi / CommitTime:12-01-27 12:27:39 
TXH Target ID:200 / Name:g_bombay / ReceiveTime:12-01-27 12:27:39
----------
RRH Row:1 / Replicate Id: 6553638 / Table: test@tstr1.tpk / DbOp:TSInsert
RRH CDR:2 (ERROR DESCRIPTION) / SQL:0 / ISAM:0
RTS  Instance id=100, Timestamp=12-01-27 12:27:39

RRH Row:2 / Replicate Id: 6553638 / Table: test@tstr1.tpk / DbOp:TSDelete 
RRH CDR:2 (ERROR DESCRIPTION) / SQL:0 / ISAM:0
RTS  Instance id=100, Timestamp=12-01-27 12:27:39

RRH Row:2 / Replicate Id: 6553638 / Table: test@tstr1.tpk / DbOp:TSDelRange
RRH CDR:2 (ERROR DESCRIPTION) / SQL:0 / ISAM:0
RTS  Instance id=100, Begin Timestamp=12-01-27 12:27:39, End Timestamp=12-01-27 12:27:39
==========
TXH Transaction committed
TXH Total number of rows in transaction:1