Teradata Database Errors

Teradata Database Errors starting with: errors 60*

Errors starting with: errors 60*

change error category

errors 60*

Teradata error 6000 A programming fault has occurred.

Teradata error 6001 The Status field of an AMP descriptor contains invalid value.

Teradata error 6002 Command has syntax error.

Teradata error 6003 Configuration Map is not properly initialized.

Teradata error 6004 No AMPs are in the configuration map.

Teradata error 6005 No PEs are in the configuration map.

Teradata error 6006 Cluster size must not be greater than 8.

Teradata error 6007 All clusters must be size 2 to 8.

Teradata error 6008 Some AMPs are not in any cluster.

Teradata error 6009 Vproc number is duplicate.

Teradata error 6010 Some AMPs with a higher Vproc number have not been deleted

Teradata error 6011 Vproc Number is invalid.

Teradata error 6012 Cluster number is invalid.

Teradata error 6013 Vproc Number is not defined in the Physical Configuration.

Teradata error 6014 For a COP, host number must match a LAN HGID in the Physical Configuration.

Teradata error 6015 The host number is invalid.

Teradata error 6016 Host Type is invalid.

Teradata error 6017 Host Number is duplicate.

Teradata error 6018 The host number is not found in the configuration map.

Teradata error 6019 The Vproc number is not found in the configuration map.

Teradata error 6020 The Vproc Number specified is not that of an AMP Vproc.

Teradata error 6021 The Vproc Number specified is not that of an PE Vproc.

Teradata error 6022 The AMP Vproc Number specified is moved to the wrong AMP.

Teradata error 6023 Configuration type should be either Current or New.

Teradata error 6024 Configuration map is inconsistent.

Teradata error 6025 Some hosts are not connected to any PE.

Teradata error 6026 Some hosts are connected to more than 512 PEs.

Teradata error 6027 Some PEs are not connected to any host.

Teradata error 6028 Addition, Deletion, and Moving of AMPs are mutually exclusive.

Teradata error 6029 Cluster Numbers are not consecutive.

Teradata error 6030 The move AMP command was not entered for all AMPs that are to be moved.

Teradata error 6032 Warning: The number of Amps in a cluster is less than one-half of the Default Cluster value

Teradata error 6033 The Default Cluster size results in a cluster with one Amp.

Teradata error 6034 Incompatible operation with the Vproc type in current config map.

Teradata error 6035 Warning: The Default Cluster size results in a cluster with multiple Amps on the same Clique.

Teradata error 6036 The range is invalid.

Teradata error 6037 Listing configuration map option should be either Long or Short.

Teradata error 6038 The total AMP virtual processors count exceeded.

Teradata error 6039 The total PE virtual processors count exceeded.

Teradata error 6051 Cluster number is not found in the configuration map.

Teradata error 6052 Number of Vprocs moving from is not equal to number of Vprocs moving to.

Teradata error 6053 Unable to rebuild reference index, needs to be rebuilt.

Teradata error 6056 Moved AMPs must follow added AMPs

Teradata error 6058 Reconfig stopped, active online archive table(s) found.

More informatoin

Teradata error TPT2813 Error: Failed to create the Job variable

Teradata error Sufficient permission was not available.

Teradata error TDP9001E ttt LOGOFF FAILED, CODE=ccc, ASID=aaaa. JOB=jjjjjjj. ssssssss.pppppppp

Teradata error TDP2202 cpname IS WAITING FOR COMMUNICATION TO BE ESTABLISHED

Teradata error TPT13107 Error %d retrieving DML statement for DML group: %d

Teradata error 3412 The respond parcel flavor specified is invalid.

Teradata error 3 – 4 Messages

Teradata error TPT2534 Error: CheckPoint finished unsuccessfully

Teradata error TDP1305 COMMUNICATION LOSS DETECTED ON DEVICE devnum

Teradata error TDP2995 TRDTXMSC: INSUFFICIENT BUFFERS PROVIDED



Teradata Database Errors