Teradata SQL Error and Failure Codes from Error 5703 To 5713

SQLServerF1_Header_Small

5703 QCD schema or data modified.
Explanation: The QCD schema or data has been modified externally
Generated By: MGC routines.
For Whom: End-User
Remedy: Restore the QCD Schema This error appears when the QCD fetch routines expects a row to be there and it is not
found.

5704 Cannot BEGIN QUERY LOGGING due to existing rule. Use REPLACE QUERY LOGGING ew options ON %VSTR to replace.
Explanation: There is a row in the DBQLRuleTbl for this application or user/account. To change attributes, the DBQL
rule must be ENDED and another BEGIN issued. If the BEGIN contained a list of users, accounts or applications, this message
only indicates that one of the list has a rule. Use SELECT * FROM DBQLRULES to determine if others on the list
already have a rule in place.
Generated By: opddbql.c
For Whom: End User.
Remedy: REPLACE QUERY LOGGING <new options> ON <user/account/applname> or (END QUERY LOGGING for
user/account/applname, issue a new BEGIN QUERY LOGGING command).

5707 DBQL limits must be between 0 and 32,767.
Explanation: For Summary and Threshold limits, the specified values must be greater than zero and less than 32767.
Generated By: opddbql.c
For Whom: End User.
Remedy: Specify a value in the correct range.

5708 Table header size exceeds limit.
Explanation: The table header contains information about each column, the compress values associated with COMPRESS
columns, and the partitioning expressions, if any. The table header size has exceeded the maximum permissible
limit.
Generated By: gnsmtb,gnsct
For Whom: End User
Remedy: Decrease the number of columns, the number of compress columns or the size of compress columns with non-
NULL values and/or simplify the partitioning expressions, if any, and then resubmit the request.

5709 Default value List is too long.
Explanation: Alter table query caused Default value list to exceed the maximum permissible limit.(64K) Default value
list is used by stpmtb and sutmtb functions.
Generated By: GNS module (gnsmtb)
For Whom: End User
Remedy: Decrease number of Default value columns and re-submit alter table query or split alter table query into multiple
alter table queries and re-submit it.

5710 Journal Row Length for Alter Table is too long.
Explanation: Alter table query generates TJ row of Kind RcvTModTblKind row. It consists of Field5 and Default value
list. This row size exceeded 64K.
Generated By: GNS module (gnsmtb)
For Whom: End User
Remedy: Decrease number of Compress columns or Default value columns and re-submit alter table query. If this error
occured because of more Default values, split the alter table query into multiple alter table queries and re-submit the
request.

5711 PARTITION BY is not allowed.
Explanation: A partitioned primary index is not allowed to be specified for a compressed join index, join index with
ORDER BY or hash index.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the partitioned
primary index rules and resubmit the request.

5712 UNIQUE is not allowed.
Explanation: For a CREATE TABLE statement, a partitioned primary index is not allowed to be unique unless all the
partitioning columns are included in the set of primary index columns. For an ALTER TABLE statement, UNIQUE may
only be specified if the primary index for the table is already unique, there is a unique secondary index on the same set of columns as the primary index, or the table is empty. In addition, a partitioned primary index may only be specified as UNIQUE if all the partitioning columns are included in the set of primary index columns and altering the primary index columns of a unique primary index to not include all the partitioning columns is only allowed if NOT UNIQUE is specified.
If the primary index is altered to be unique and there is a unique secondary index on the same set of columns as the primary index, the unique secondary index is dropped since it is no longer needed.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Notes: Use a unique secondary index to define the columns as unique if not all the partitioning columns are included in
the set of primary index columns.
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the partitioned
primary index rules and resubmit the request. **DR62813-bessc**

5713 UNIQUE secondary index is not allowed.
Explanation: For a CREATE TABLE statement, a unique secondary index on the same set of columns as the primary
index columns must not be specified when the primary index is partitioned and the set of primary index columns includes
all the partitioning columns. For an ALTER TABLE statement, a unique secondary index on the same set of columns as the
primary index columns must not exist for the table when the resulting primary index is partitioned and the set of primary index columns includes all the partitioning columns and resulting primary index is not specified to be unique.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Notes: For a CREATE TABLE statement, the primary index should be created as UNIQUE instead of including a unique
secondary index. For an ALTER TABLE statement, the altered primary index should be specified as UNIQUE (the ALTER
TABLE statement automatically drops the unique secondary index). Alternatively, a unique secondary index may be created on the table in a separate CREATE INDEX statement after the CREATE TABLE or ALTER TABLE statement; this
allows a table to be subsequently altered to have a unique primary index.
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the partitioned primary index rules and resubmit the request.

Above are list of Teradata Errors or Failure Codes from Error 5703 To 5713 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *