Teradata SQL Error and Failure Codes from Error 9543 To 9554

SQLServerF1_Header_Small

9543 Database SYSLIB or function SYSLIB.GetTimeZoneDisplacement does not exist.)
Explanation: Database SYSLIB or UDF SYSLIB.GetTimeZoneDisplacement does not exist. System/user timezonestring
is in effect and this object was found missing while resolving the timezone string.
Generated By: conlopa
For Whom: End User
Remedy: DBA should run dipdem to regenerate these objects.

9544 The ExportDefinitionName cannot be longer than %VSTR characters.
Explanation: The ExportDefinitionName is longer than permitted.
Generated By: OPD modules.
For Whom: User.
Remedy: Correct the Teradata SQL statemenet by using a valid ExportDefinitionName and resubmit the request.

9545 The ExportDefinitionName value must be a character string.
Explanation: The ExportDefinitionName value must be a character string.
Generated By: OPD modules.
For Whom: User.
Remedy: Use a character string for the ExportDefinitionName value.

9546 AT TIME ZONE is not a valid compile option for this ’%VSTR’.
Explanation: AT TIME ZONE clause is not allowed for compile of pre-14.0 SPs or for this application category of external
stored procedure.
Generated By: PAR module.
For Whom: End User.
Remedy: For pre-14.0 SPs, retry the alter procedure without the AT TIME ZONE clause first to recompile in the current
Teradata release and then resubmit with AT TIME ZONE clause.

9547 %VSTR can only be qualified by SYSUDTLIB/TD_SYSFNLIB.
Explanation: When algorithmic compression clause is specified for a column, the compress/decompress UDFs cannot
be qualified by other than SYSUDTLIB/TD_SYSFNLIB.
Generated By: RES.
For Whom: End User.
Remedy: Use only SYSUDTLIB/TD_SYSFNLIB as qualifier for Compress/Decompress UDFs.

9548 Source rows did not include all constraint columns in the source table.
Explanation: A MERGE-INTO or INSERT-SELECT statement involved a view or derived table that did not include all
constraint columns in the source table.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

9550 There are no statistics defined for the table.
Explanation: There are no statistics defined for the source table referenced in a Create Table as .. with data and statistics statement.
Generated By: OPD modules.
For Whom: End User.
Notes: This warning is issued when the statistics are requested to be copied but no statistics are available on the source table.
Remedy: Resubmit the statement without the copy statistics option (WITH STATISTICS).

9551 A left open monitor resource was detected by parser when parsing a SQL request.
Explanation: The event message documents a left open monitor detected when parsing a request.
Generated By: PARSER .
For Whom: System Support Representative.
Remedy: Contact your support representative.

9552 statistics cache hit ratio is lower than the threshold set in dbs control internal field.
Explanation: Statistics cache hit ratio is lower than the threshold. Please consider increasing the number of segments in
the statisitics cache.
Generated By: opt module.
For Whom: System Support Representative.
Remedy: Increase the number of segments in the statisitics cache.

9553 Cannot create/replace UDF/UDT with the current character set.
Explanation: MBC UDFs/UDTs are currently existing on the system. Users must use a character set that can accomodate
all existing MBC UDFs/UDTs to create/replace this UDF/UDT.
Generated By: mgcudfids.c.
For Whom: User.
Remedy: Re-submit the statement with an appropriate character set.

9554 Warning: Invalid join index is found.
Explanation: A join index is invalid because a UDF/UDM it refers to has been dropped.
Generated By: OPT modules.
For Whom: The DBA and the System Support Representative.
Notes: This warning is issued when a join index is no longer valid due to non-existent UDFs/UDMs referenced by the
join index(es).
Remedy: Drop the invalid join index.

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