Teradata SQL Error and Failure Codes from Error 8257 To 8271

SQLServerF1_Header_Small

8257 Improperly formatted directed request. Improperly formatted directed request.
Explanation: The above errors (8241-8257) are generated if a directed request is improperly formatted or inconsistent.
The different error code values just allow support to isolate the source of the problem more quickly.
Generated By: Various AMP Procedures.
For Whom: Support Representative/System Administrator.
Remedy: Contact software support and explain the scenario.

8258 Orphan dictionary row discarded for database %DBID in table DBC.%TVMID.
Explanation: This warning is generated during a recovery operation if an ’orphan’ data row is found for DBC.TVFields,
DBC.Indexes, DBC.TextTbl or DBC.Association for which there is no corresponding data row in DBC.TVM. In this situation
the data row will be discarded and recovery will continue uninterrupted.
Generated By: Hut Insert Row procedure DoRowInsert
For Whom: End User
Remedy: This is a warning message. No response is required from the user.

8259 Invalid table access.
Explanation: This error is generated if a user attempts to access a table object using an Archive/Recovery operation for
which the user does not have appropriate access rights.
Generated By: Hut Control Segment procedure HcsAcCk2
For Whom: Software internal code.
Remedy: This error is for internal purposes and will not be returned to the user under the current implementation.

8260 The header row of the table which is used for restoring archive in old release is missing.
Explanation: To restore the system table which has been restructured from previous release, DBS relies on knowing the
old definition of that table. Unfortunately, this table is absence in the current system.
Generated By: HUTINR and HUTRDB Amp procedures.
For Whom: Support Representative.
Remedy: Determine which history table(s) is missing and re-create them.
Note: These history tables were created in SYSINIT time or from the migration script.

8261 Checksum error in the restore data block.
Explanation: HUTRBLK received from client caused checksum error.
Generated By: HUTRDB
For Whom: End User
Remedy: Check the connection and resubmit the job.

8263 A character string inserted into dictionary field DBC.%TVMID.%FLDID would not convert to
Unicode due to untranslatable characters.
Explanation: While performing a cross major release restore/copy, the DBS detects a dictionary column containing character(
s) which don’t convert to Unicode. The column will be temporarily assigned the following string containing a hexa decimal character literal of the first 30 bytes in the source string (from the old source table) causing the error: ’?? –
Conversion Error of: [hex_character_literal]’
Generated By: HUT routines
For Whom: End User
Remedy: User will need to replace bad data with good value by recreating the database object encountering the error.

8267 Operation not allowed: %DBID.%TVMID is in DSA restore pending state. ARC cannot build it
explicitly.
Explanation: The specified table is in DSA restore pending state, ARC cannot build it. It only builds tables that are in ARC restore pending state.”
Generated By: HUTBLD Amp procedure
For Whom: End user
Remedy: Restore the table.

8268 Error exists when converting Graphic.
Explanation: To perform a cross major release restore/copy on a table contains graphic data. The graphic data will be
converted into new internal form. DBS detects conversion error and the bad data will be given system assigned error
graphic character.
Generated By: HUTRDB
For Whom: End User
Remedy: Replace the bad data with good data.

8269 Rehashing is required.
Explanation: To perform a same hash function restore or copy operation, DBS determines rehashing will be required.
The example will be the primary key of a table was changed.
Generated By: HUTRDB
For Whom: ASF2/ARC

8270 Trigger Dictionary Row discarded during copy.
Explanation: This warning is generated during a copy operation if a trigger data row is found. In this situation the data
row will be discarded and copy will continue uninterrupted.
Generated By: Hut Insert Row procedure DoRowInsert
For Whom: ASF2/ARC

8271 Operation cannot be completed on the table. The operation needs to be restarted from the
beginning.
Explanation: Internal error happened during an ARC operation. For example when trying to rollback online archive, the
online archive subtable was not in the proper format. This can happen when the database is restarted while a non-unique
secondary index is being sorted during the build phase.
Generated By: HUTBLD Amp procedure
For Whom: End user
Remedy: The operation needs to be restarted from the beginning. If the user is attempting a build operation, the table
should be restored/copied from the beginning. The table is probably not in a state where it can be built properly.

Above are list of Teradata Errors or Failure Codes from Error 8257 To 8271 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 *