Each row in the RCEvent table contains multiple columns. Some of these columns are the same for all rows and others are optional, depending on the type of event being recorded. The following table describes fields in the RCEvent table.
| Field | Description |
|---|---|
| Standard Fields | |
| Event Number | A unique integer value assigned by the Teradata Database to each recorded event Teradata Archive/Recovery Utility assigns event numbers in ascending order. For example, events that occur earlier in time have smaller numbers. The event number (not the date and time stamp) is the most accurate way to determine the chronology of events. |
| Date and Time | The value of the Teradata Database time-of-day clock when the event is recorded Earlier events can have later time stamps than later events. Therefore, do not use this value to determine the chronology of checkpoint events. Instead, use event numbers. |
| User Name | Logon ID for the user who initiated the event |
| Event Type | A text string identifying the event The event types are:
|
| Database Name | The name of the database affected by the activity If multiple databases are affected, a row is recorded for each database. |
| Object Type | A single character that defines the type of object involved The character values and their meanings are:
|
| Object Identifier | A four byte field containing either a database ID or the uniqueness portion of a table identifier This field further defines the object involved in the event. These fields are derived from the DBASE and TVM dictionary tables and are maintained by the Teradata Database. |
| All-AMPs Flag | The value “A” means the following:
|
| Restart Count | If the event is restarted and the online AMP configuration has changed, this column increases by one. If the event was completed without a configuration change, this field contains a zero. |
| Operation in Progress | This field contains a Y when the Teradata ARC operation specified is not complete. Operations that terminate abnormally and are not restarted are left with Y. When the specified Teradata ARC operation completes, this field contains an N. |
| Optional Fields | |
| Dataset Name | The client file name specified for an archive or recovery activity |
| Table Name | The table name specified for an archive or recovery activity Contains one row for each table affected unless all tables are affected If all rows are affected, BTEQ shows a question mark. This indicates a NULL field. |
| Checkpoint Name | The label given to the checkpoint |
| Linking Event Number | The number assigned to some other event that influenced the current event The termination point for a rollback is a linking event number. |
| Journal Used | A single character indicating which journal table the event used:
|
| Journal Saved | Y or N to indicate that the CHECKPOINT statement did (or did not) contain the SAVE option |
| Index Present | Y or N to indicate whether the archive included the index option |
| Dup Archive Set | Y or N to indicate if this is a duplicate file created by an archive request If two files are created by a single archive request, two event rows are generated. One has the flag set to Y to indicate that it is a duplicate. The other has a value of N to indicate that it is the primary copy. |
| Lock Mode | A single character to identify the HUT lock that is applied by an archive operation:
|
The RCEventtable also has other fields not listed in the table, which are reserved for future use.