PERFFILE - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
15.00
Language
English (United States)
Last Update
2018-09-25
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

PERFFILE

Purpose  

The PERFFILE parameter produces a log of Teradata ARC performance data as a source for job performance monitoring, analysis, and debugging.

Syntax  

PLOG is the user-specified name for the Performance file. This is a separate file from the archive file and will be located in either the working directory or the path that is specified. See “Usage Notes” on page 140 for an example.

Each line of the Performance file contains a two-character record type followed by the data provided for this type, as shown in the next table.

 

Syntax Element

Definition

BG <timestamp> <IOPARM>

Beginning of performance log

<IOPARM> is the list of parameters given in the IOPARM command-line option (if any).

EN <timestamp> <exitcode>

Indicates the end of the Teradata ARC job

<exitcode> is the final exit code returned by ARC.

ER <timestamp> <exitcode> <errorcode> <string>

Indicates a warning, error, or failure by Teradata ARC

<exitcode> is the severity of the error (4 for warning, 8 for error, 12 for failure, and 16 for internal error).

<errorcode> is the Teradata ARC or Teradata Database error code for the error.

<string> is the string output by Teradata ARC indicating the error.

LG <timestamp>
<logon-str>

Displays the logon time and the logon string given to Teradata ARC in the ARC script

OE <timestamp> <TS-end> <objtype> <name>

Indicates the end time for the named object

<TS-end> is the end time for the object.

<objtype> is the type of object (database-level, 'D', or table-level, 'T').

<name> is the name of the database (and table for table-level objects).

OS <timestamp> <objtype> <name>

Indicates the start time for the named object

<objtype> is the type of object (database-level, 'D', or table-level, 'T').

<name> is the name of the database (and table for table-level objects).

ST <timestamp> <statement>

Displays the currently executing statement (from the ARC script)

TB <TS-begin> <TS-build> <TS-end> <bytes> <name>

Indicates the output at the end of archiving or restoring each table

TS-begin is the time the table started.

TS-build is the time the build process started.

TS-end is the ending.

<bytes> is the number of bytes of data archived or restored.

<name> is the name of the database and table archived or restored.

VB <timestamp> <string>

Indicates that a verbose message is output by Teradata ARC

<string> is the message that is displayed.

Usage Notes  

In mainframe platforms (that is, z/OS), limit file names to eight characters.

The following example demonstrates using PERFFILE to create a Performance log file:

ARCMAIN PERFFILE=C:\baruser\ARC_Test_perf.txt

Contents of Performance log: C:\baruser\ARC_Test_perf.txt
 
BG 12/02/2008 16:37:43 
LG 12/02/2008 16:37:43 LOGON TDPID/dbc,;
ST 12/02/2008 16:37:46 
ST 12/02/2008 16:37:46 copy data tables
ST 12/02/2008 16:37:46  (DB1),
ST 12/02/2008 16:37:46 release lock,
ST 12/02/2008 16:37:46 file=ARCH1;
VB 12/02/2008 16:37:47 ARCHIVED AT  12-02-08 13:34:03
VB 12/02/2008 16:37:47 ARCHIVED FROM ALL AMP DOMAINS
VB 12/02/2008 16:37:47 UTILITY EVENT NUMBER IN ARCHIVE - 770
VB 12/02/2008 16:37:47 RELEASE:13.00.00.00; VERSION:13.00.00.00; 
OS 12/02/2008 16:37:47 D "DB1".""
ER 12/02/2008 16:37:47 4 3803 *** Warning 3803:Table 'tb1' already exists.
VB 12/02/2008 16:37:50 Starting table "tb1"
VB 12/02/2008 16:37:50 Table "tb1" is not a deferred object
TB 12/02/2008 16:37:50 12/02/2008 16:39:07 12/02/2008 16:39:07 436,208,086 "DB1"."tb1"
VB 12/02/2008 16:39:07 Clearing build flag for index 0.
OE 12/02/2008 16:37:47 12/02/2008 16:39:07 D "DB1".""
ST 12/02/2008 16:39:07 
ST 12/02/2008 16:39:07 logoff;
EN 12/02/2008 16:39:07 4