15.00 - Return Codes - Teradata Database

Teradata Database Utilities

Product
Teradata Database
Release Number
15.00
Content Type
Configuration
Publication ID
B035-1102-015K
Language
English (United States)
Last Update
2018-09-25

Return Codes

Dul issues return codes to report processing success or failure:

 

On …

dul and dultape support return codes via …

Linux

shell commands ($?).

A return code of “0” indicates that processing was successful; a nonzero return code indicates that processing failed. In order of severity, dul return codes are 02, 04, 08, and 12. These codes are defined as shown below:

  • 02  -  Special warning
  • 04  -  Warning
  • 08  -  User error
  • 12  -  Severe internal error
  • A 02 code is returned if you attempt a Teradata Database operation without logging onto the system.

    The following table shows messages resulting in dul Return Code 04.

     

    Return Code

    Error Code

    Description

    04

    3747

    No startup string defined for this user.

    04

    3803

    Table “%VSTR” already exists.

    04

    3804

    View “%VSTR” already exists.

    04

    3805

    Macro “%VSTR” already exists.

    The following table shows messages resulting in dul Return Code 08.

     

    Return Code

    Error Code

    Description

    08

    2538

    A disk read error occurred in the tables area.

    08

    2541

    End of Hash Code range reached.

    08

    2631

    Transaction ABORTED due to %VSTR.

    08

    2632

    All AMPs own sessions for this Fast/MultiLoad.

    08

    2639

    Too many simultaneous transactions.

    08

    2641

    %DBID.%TVMID was restructured. Resubmit.

    08

    2644

    No more room in database %DBID.

    08

    2654

    Operation not allowed: %DBID.%TVMID is being Restored.

    08

    2805

    Maximum row length exceeded in %TVMID.

    08

    2809

    Invalid recovery sequence detected.

    08

    2815

    Apparent invalid restart of a restore.

    08

    2818

    Invalid lock to dump table without after-image journaling.

    08

    2825

    No record of the last request was found after Teradata Database restart.

    08

    2826

    Request completed but all output was lost due to Teradata Database restart.

    08

    2827

    Request was aborted by user or due to command error.

    08

    2828

    Request was rolled back during system recovery.

    08

    2830

    Unique secondary index must be dropped before restoring table.

    08

    2835

    A unique index has been invalidated; resubmit request.

    08

    2837

    Table being FastLoaded; no data dumped.

    08

    2838

    Table is unhashed; no data dumped.

    08

    2840

    Data rows discarded due to inconsistent hash codes.

    08

    2843

    No more room in the database.

    08

    2866

    Table was Recovery Aborted; no data dumped.

    08

    2868

    This permanent journal table is damaged; no data dumped.

    08

    2920

    Delete journal and AMP down without dual.

    08

    2921

    No saved subtable for journal %DBID.%TVMID.

    08

    2926

    No more room in %DBID.%TVMID.

    08

    3001

    Session is already logged on.

    08

    3111

    The dispatcher has timed out the transaction.

    08

    3116

    Response buffer size is insufficient to hold one record.

    08

    3119

    Continue request submitted but no response to return.

    08

    3120

    The request is aborted because of a Teradata Database recovery.

    08

    3523

    %FSTR does not have %VSTR access to %DBID.%TVMID.

    08

    3524

    %FSTR does not have %VSTR access to database %DBID.

    08

    3566

    Teradata Database does not have a PERMANENT journal.

    08

    3596

    RESTORE Teradata Database invalid if table, view, or macro exists outside of Teradata Database.

    08

    3598

    Concurrent change conflict on Teradata Database. Please try again.

    08

    3603

    Concurrent change conflict on table. Please try again.

    08

    3613

    Dump/Restore, no hashed nonfallback tables found.

    08

    3656

    Journal table specified no longer exists.

    08

    3658

    ROLLBACK/ROLLFORWARD table specifications are invalid.

    08

    3705

    Teradata Database/SQL request is longer than the Simulator maximum.

    08

    3737

    Name is longer than 30 characters.

    08

    3802

    Database “%VSTR” does not exist.

    08

    3807

    Table/view “%VSTR” does not exist.

    The following table shows messages resulting in dul Return Code 12.

     

    Return Code

    Error Code

    Description

    12

    CLI0001

    Parameter list invalid or missing.

    12

    CLI0002

    Invalid number of parameters received.

    12

    CLI0003

    Error validating HSIRCB.

    12

    CLI0004

    Error validating HSICB.

    12

    CLI0005

    Error validating HSISPB.

    12

    CLI0006

    Invalid destination HSICB detected.

    12

    CLI0007

    Invalid destination RCB detected.

    12

    CLI0008

    DBCFRC unable to free RCB/HSICB control blocks because they are not contiguous in storage.

    12

    CLI0009

    Invalid DBCAREA pointer or id.

    12

    CLI0010

    ECB already waiting.

    12

    CLI0530

    Character Set Name or Code unknown.

    12

    2123

    A segment could not be read successfully.

    12

    2971

    The AMP Lock table has overflowed.

    12

    2972

    No table header exists for table.

    For details on error messages, see Messages.