VERBOSE - 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

VERBOSE

Purpose  

The VERBOSE parameter directs Teradata ARC progress status information to the standard output device (for example, SYSPRINT for IBM platforms). The amount of status information sent is determined by the level specified in the parameter.

Syntax  

where

 

Syntax Element

Definition

n

Level of program status information sent to the standard output device, where n represents 2 or 3

VERBOSE without an n value provides the lowest level of status information.

The amount of process status information sent to standard output increases with a higher n value.

Usage Notes  

Progress status report is displayed on a standard output device. On the IBM mainframe platform, the progress status is sent to the SYSPRINT DD with other regular Teradata ARC output lines.

VERBOSE provides three levels of progress status (1 through 3):

  • Level 1is specified as:
  • VERBOSE, VERB or VB
  • Levels 2 through 3 are specified as:
  • Level 2 - VERBOSE2, VERB2 or VB2
    Level 3 - VERBOSE3, VERB3 or VB3

    While VERBOSE level 1 is designed for normal operation, the other two levels are for diagnosis and debugging. The performance of Teradata ARC is affected when these higher VERBOSE levels are used, especially if a low CHECKPOINT value is specified.

    The output of VERBOSE is preceded by three dashes (---) for easy identification and filtering by other utilities.

    For ARCHIVE and RESTORE/COPY operations, the amount of data processed in the data phase is displayed at each checkpoint. Teradata ARC internally takes checkpoints for every n number of data blocks processed for restart purposes. Therefore, it is possible to control the frequency of display of status information when VERBOSE is specified by the CHECKPOINT parameter setting. See “CHECKPOINT” on page 109.

    For the RESTORE/COPY operations, each build request is displayed in addition to the data processed before the request is sent to the Teradata Database. However, the client has no control of the actual build execution. Therefore, after the request is sent, Teradata ARC waits for the completion of the build request.

    Specify NOVERBOSE to disable the VERBOSE parameter. The default is NOVERBOSE.

    Example  

    Following is sample output that results from specifying VERBOSE level 1.

    Note: The organization and contents of informational progress report lines changes without notice with new releases of Teradata ARC. Therefore, do not develop scripts or programs that exactly copy this example.

    04/29/97 10:40:38    ****   ****    ****    DATABASE COMPUTER
    04/29/97 10:40:38    *   *  *   *  *
    04/29/97 10:40:38    *   *  ****   *        PROGRAM: ARCMAIN
    04/29/97 10:40:38    *   *  *   *  *        RELEASE: 06.01.00
    04/29/97 10:40:38     ****   ****    **** BUILD: 9702-16 (Apr 25 1997)
    04/29/97 10:40:38
    04/29/97 10:40:38  RUNTIME PARAMETERS SPECIFIED:
    04/29/97 10:40:38  verbose checkpoint=5
    04/29/97 10:40:38
    04/29/97 10:40:40  PARAMETERS IN USE:
    04/29/97 10:40:40
    04/29/97 10:40:40  SESSIONS 4
    04/29/97 10:40:40  VERBOSE LEVEL 1
    04/29/97 10:40:40  									CHECKPOINT FREQUENCY CHANGED TO 5
    04/29/97 10:40:40
    04/29/97 10:40:41  CHARACTER SET IN USE: EBCDIC
    04/29/97 10:40:41  LOGON TDRU/JCK,
    04/29/97 10:40:42  LOGGED ON    2 SESSIONS
    04/29/97 10:40:42  STATEMENT COMPLETED
    04/29/97 10:40:42
    04/29/97 10:40:42  ARCHIVE data tables (jck),
    04/29/97 10:40:42       release lock,
    04/29/97 10:40:42       file=archive;
    04/29/97 10:40:43  LOGGED ON    4 SESSIONS
    04/29/97 10:40:44  UTILITY EVENT NUMBER  - 79
    04/29/97 10:40:44
    04/29/97 10:40:44  ARCHIVING DATABASE "JCK"
    04/29/97 10:40:54 ---  Starting table "ACCESSRIGHTS"
    04/29/97 10:40:56 ---  CHKPT:  129,510 bytes,   2,184 rows      received
    04/29/97 10:40:57 ---  CHKPT:  183,200 bytes,   3,094 rows      received
    04/29/97 10:40:58 ---  CHKPT:  322,971 bytes,   5,463 rows      received
    04/29/97 10:40:59 ---  CHKPT:  436,310 bytes,   7,384 rows      received
    04/29/97 10:41:00 ---  CHKPT:  526,226 bytes,   8,908 rows      received
    04/29/97 10:41:01 ---  CHKPT:  634,845 bytes,  10,749 rows      received
    04/29/97 10:41:01  TABLE "ACCESSRIGHTS" - 669,242 BYTES,       11,332 ROWS ARCHIVED
    04/29/97 10:41:01 ---  Starting table "ACCOUNTS"
    04/29/97 10:41:02 ---  CHKPT:    1,228 bytes, 17 rows received
    04/29/97 10:41:02 ---  CHKPT:    1,228 bytes, 17 rows received
    04/29/97 10:41:04 ---  CHKPT:    1,734 bytes, 28 rows received
    04/29/97 10:41:11 ---  CHKPT:    2,608 bytes, 47 rows received
    04/29/97 10:41:11  TABLE "ACCOUNTS" -   2,930 BYTES, 54 ROWS      ARCHIVED
    04/29/97 10:41:11 ---  Starting table "DBASE"
    04/29/97 10:41:12 ---  CHKPT:    4,751 bytes, 13 rows received
    04/29/97 10:41:13 ---  CHKPT:    7,711 bytes, 23 rows received
    04/29/97 10:41:14 ---  CHKPT:   14,599 bytes, 47 rows received
    04/29/97 10:41:14  TABLE "DBASE" -  17,556 BYTES, 57 ROWS      ARCHIVED
    04/29/97 10:41:14  "JCK" - LOCK RELEASED
    04/29/97 10:41:14  DUMP COMPLETED
    04/29/97 10:41:14  STATEMENT COMPLETED
    04/29/97 10:41:14
    04/29/97 10:41:14
    04/29/97 10:41:14
    04/29/97 10:41:14 RESTORE DATA TABLES JCK),release lock,      file=archive;
    04/29/97 10:41:15 ---  ARCHIVED AT    04-29-97 10:40:43
    04/29/97 10:41:15 ---  ARCHIVED FROM  ALL AMP DOMAINS
    04/29/97 10:41:15 ---  UTILITY EVENT NUMBER IN ARCHIVE  - 79
    04/29/97 10:41:16  UTILITY EVENT NUMBER  - 80
    04/29/97 10:41:22  STARTING TO RESTORE DATABASE "JCK"
    04/29/97 10:41:26  DICTIONARY RESTORE COMPLETED
    04/29/97 10:41:29 ---  Starting table "ACCESSRIGHTS"
    04/29/97 10:41:30 ---  CHKPT: 145,204 bytes,   2,450 rows sent
    04/29/97 10:41:30 ---  CHKPT: 145,204 bytes,   2,450 rows sent
    04/29/97 10:41:30 ---  CHKPT: 215,414 bytes,   3,640 rows sent
    04/29/97 10:41:31 ---  CHKPT: 325,449 bytes,   5,505 rows sent
    04/29/97 10:41:31 ---  CHKPT: 448,582 bytes,   7,592 rows sent
    04/29/97 10:41:32 ---  CHKPT: 558,440 bytes,   9,454 rows sent
    04/29/97 10:41:32 ---  CHKPT: 667,059 bytes,  11,295 rows sent
    04/29/97 10:41:32 ---  Building fallback subtable for index 0.
    04/29/97 10:41:32 ---  Clearing build flag for index 0.
    04/29/97 10:41:33 ---  Building index subtable for index 4.
    04/29/97 10:41:33 ---  Clearing build flag for index 4.
    04/29/97 10:41:34 ---  Building index subtable for index 8.
    04/29/97 10:41:34 ---  Clearing build flag for index 8.
    04/29/97 10:41:34  "ACCESSRIGHTS" - 669,242 BYTES, 11,332 ROWS      RESTORED
    04/29/97 10:41:34 ---  Starting table "ACCOUNTS"
    04/29/97 10:41:35 ---  CHKPT:   1,320 bytes, 19 rows sent
    04/29/97 10:41:35 ---  CHKPT:   2,010 bytes, 34 rows sent
    04/29/97 10:41:35 ---  CHKPT:   2,838 bytes, 52 rows sent
    04/29/97 10:41:35 ---  Building fallback subtable for index 0.
    04/29/97 10:41:36 ---  Clearing build flag for index 0.
    04/29/97 10:41:36  "ACCOUNTS" -   2,930 BYTES, 54 ROWS RESTORED
    04/29/97 10:41:59 ---  Starting table "DBASE"
    04/29/97 10:42:00 ---  CHKPT:   5,325 bytes, 15 rows sent
    04/29/97 10:42:00 ---  CHKPT:   9,146 bytes, 28 rows sent
    04/29/97 10:42:00 ---  CHKPT:  15,834 bytes, 51 rows sent
    04/29/97 10:42:00 ---  CHKPT:  15,834 bytes, 51 rows sent
    04/29/97 10:42:00 ---  Building fallback subtable for index 0.
    04/29/97 10:42:01 ---  Clearing build flag for index 0.
    04/29/97 10:42:01 ---  Building index subtable for index 4.
    04/29/97 10:42:02 ---  Building fallback subtable for index 4.
    04/29/97 10:42:02 ---  Clearing build flag for index 4.
    04/29/97 10:42:02  "DBASE" -  17,556 BYTES, 57 ROWS RESTORED
    04/29/97 10:42:03  "JCK" - LOCK RELEASED
    04/29/97 10:42:03
    04/29/97 10:42:03  STATEMENT COMPLETED
    04/29/97 10:42:03
    04/29/97 10:42:03
    04/29/97 10:42:03
    04/29/97 10:42:03  LOGOFF;
    04/29/97 10:42:03  LOGGED OFF   6 SESSIONS
    04/29/97 10:42:03  STATEMENT COMPLETED
    04/29/97 10:42:03
    04/29/97 10:42:03
    04/29/97 10:42:03  UTILITY TERMINATED