Teradata SQL Error and Failure Codes from Error 9017 To 9102

SQLServerF1_Header_Small

9017 RepGroup row discarded during restore.
Explanation: This warning is generated during a restore operation if a DBC.RepGroup row is found in the archive file.
In this situation the row will be discarded and restore will continue uninterrupted.
Generated By: This warning code is generated by HUTRDB Amp procedure.
For Whom: End User.
Remedy: Informational.

9018 Restore/Copy detected invalid Algorithmic Compression/Decompression UDF: %FSTR
%VSTR.
Explanation: This error is generated if the system determines that the Algorithmic Compression/Decompression UDF
specified in the table archive does not match the current system info. VSTR will give the name of the UDF.
Generated By: HUT
For Whom: Support Representative/System Administrator.
Remedy: Contact software support and explain the scenario. Most likely the UDF does not exist on the target system.
Table in the archive is not usable and will not be restored unless the original UDF definition can be created.

9019 Restore/Copy detected invalid Server Table Operator: %FSTR %VSTR.
Explanation: This error is generated if the system determines that the Table Operator specified in the table archive does
not match the current system info. VSTR will give the name of the table operator.
Generated By: HUT
For Whom: Support Representative/System Administrator.
Remedy: Contact software support and explain the scenario. Most likely the table operator does not exist on the target
system. Server in the archive is not usable and will not be restored unless the original table operator definition can be created.

9020 Restored/Copied data table’s security may be compromised because a security constraint is
inconsistent between the backup and disk.
Explanation: The restore or copy of an RLS protected table or a database containing an RLS protected table detected an
inconsistency between the last alter timestamp of a security constraint defined in the table and the associated entry in
DBC.SecConstraints.
Generated By: Restore data block host utility step (hutrdb)
For Whom: End User
Remedy: Double-check the constraints defined in the table. If a constraint was altered to add new constraint valuename:
value pairs, security remains intact. If an existing constraint valuename:value pair was altered, then security of the
table could be compromised.

9021 Restore/Copy table stopped because user does not have the required privilege for the
operation.
Explanation: The restore/copy table request for the restore or copy of an RLS protected table was stopped because the
user does not have the required Override Dump Constraint or Override Restore Constraint privilege.
Generated By: HUT subsystem
For Whom: End User
Remedy: Do not re-submit the request.

9022 Can not archive, Database %DBID has UDF/UDM/XSP %TVMID in restore pending state.
Explanation: This message indicates that while the database has any UDF/XSP in TabRestore state the user can not
archive the database.
Generated By: HUT
For Whom: End user or Field Engineer or the concerned site support representative.
Remedy: Wait for restore to finish on all the UDF/XSP and then try archivng the database.

9023 Permanent journal for table was deactivated.
Explanation: BAR software does not backup nor restore permanent journal.
Generated By: BAR.
For Whom: End user.
Remedy: Manually activate permanent journal with ALTER TABLE for the desired table after restore job finishes.

9100 Unique index violation; errors logged in %TVMID where ETC_dbql_qid = %FSTR.
Explanation: This error is returned when a MERGE-INTO or INSERT-SELECT statement that specified LOGGING of
errors other than USI violations detects a USI error during index maintenance. To retrieve error rows logged for this
request, query the error table with the following search condition displayed at the end of the error message:
where ETC_dbql_qid = <Query Id>
Generated By: AMP Steps.
For Whom: End User.
Remedy: Analyse the logged errors and, if necessary, correct the source rows that caused the errors and re-load the corrected
rows.

9101 Referencing violation; errors logged in %TVMID where ETC_dbql_qid = %FSTR.
Explanation: This error is returned when a MERGE-INTO or INSERT-SELECT statement that specified LOGGING of
errors other than RI violations detects an RI error during index maintenance. To retrieve error rows logged for this request,
query the error table with the following search condition displayed at the end of the error message:
where ETC_dbql_qid = <Query Id>
Generated By: AMP Steps.
For Whom: End user.
Remedy: Analyse the logged errors and, if necessary, correct the source rows that caused the errors and re-load the corrected
rows.

9102 Invalid CAST. %VSTR
Explanation: An error was generated during Period Data Type CAST. The exact message is given within VSTR. a) For an
explicit CAST function or implicit cast, Source character value cast as PERIOD must conform to the format of the target.
b) For an explicit CAST function or implicit cast of a character value as PERIOD, the character value must represent a
period that has a precision less than or equal to the target type’s precision.
c) For an explicit CAST function or implicit cast, the result beginning bound must be less than the result ending bound in
its UTC form. This can occur for a TIME or TIMESTAMP value cast as PERIOD(TIME), a PERIOD(TIMESTAMP) value cast
as PERIOD(DATE) or PERIOD(TIME), or a CHARACTER or VARCHAR value cast as a Period data type.
d) For a source PERIOD(TIMESTAMP) value cast as PERIOD(TIME), the source value must have the same date for both the
beginning and ending bounds.
e) In order to cast a Period value as DATE, TIME, or TIMESTAMP, the Period value must have a duration of one granule of
the Period value’s data type.
f) For a cast of a DATE value as PERIOD(DATE) the result ending bound must not exceed the maximum allowed DATE
value.
g) For a cast of a TIME value as PERIOD(TIMESTAMP), the result ending bound must not exceed the maximum allowed
TIMESTAMP value. For a cast of a TIME value as PERIOD(TIME), the result ending bound must be greater than the result
beginning bound.
h) For a cast of a TIMESTAMP value as PERIOD(DATE) or PERIOD(TIMESTAMP), the result ending bound must not
exceed the maximum allowed value for the targets element type. For a cast of a TIME value as PERIOD(TIME), the result
ending bound must be greater than the beginning bound. DR121843-sb230132-01 ->> i) During data conversion internally
if the period values are converted from UTC to local value and vice versa and results in an out of range then the period
value is out of range at the local time zone. <<- DR121843-sb230132-01
Generated By: Period CAST function.
For Whom: End User.
Remedy: Correct the source value and re-submit.

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