Teradata SQL Error and Failure Codes from Error 5544 To 5552

SQLServerF1_Header_Small

5544 The OPTCOST GDO is uninitialized.
Explanation: An attempt was made to SET costs on for SYSTEM.
Generated By: OPT modules.
For Whom: Internal only.
Remedy: This operation is OK. It tells Optcostul.c to allocate – initialize the OPTCOST GDO, and should not be returned
to the user. If it is that probably means the OPTCOST GDO has been corrupted in which case the Global Support Center
should be contacted.

5545 The TLE feature has not been enabled.
Explanation: The user attempted to set the optimizer costs, but the Target Level Emulation feature has not been enabled.
Generated By: OPT modules.
For Whom: End User.
Remedy: Enable the TLE feature by running DIPPATCH or DIPSYSFE and setting the Target Level Emulation flag in the
DBSControl utility to true.

5546 Sampleid cannot be nested inside Ordered Analytical and AGGREGATE Functions.
Explanation: The Sampleid cannot be nested inside the Ordered Analytical and the Aggregate Functions
Generated By: PAR Module
For Whom: END USER
Remedy: Remove Sampleid nested within the Ordered Analytical and Aggregate Function

5547 Internal Error: %VSTR.
Explanation: There was an internal error during the compilation or creation of the stored procedure and the request was
aborted. Following messages can appear for VSTR in the error message. 1) Message : Unknown handler type encountered
during C code generation. While reading the parse tree during the C code generation phase unknown handler type is
encountered. The generated CL command line has exceeded the maximum length limit of 255 characters. This error is specific
to W2K environment only. YY_FATAL_ERROR occurred in tsp Lexer. This is Lexer internal error. The request string
submitted to CheckLiteral routine is empty. tpi-data directory, under which TDSP temporary directory resides does not
exist on the test machine. On Linux this directory is available under the path: /var/opt/teradata/tdtemp
fwrite/_write call has either failed to write the SPL text to the temporary file or incorrect number of bytes are written to the
temporary file. The stat/_stat system call failed to retrieve the size of the file. This error occurs when fread fails to read the
SPL Text. This error occurs when fread fails to read the object code. mt.exe is required for successful compilation of a Stored
procedure. This error occurs when mt.exe is not present in VC/bin directory.
Generated By: TSP modules OPU modules. TSP modules. TSP modules. TSP/OPU/OPD modules. TSP/OPU/OPD
modules. TSP/OPU/OPD modules. TSP/OPU/OPD modules. TSP/OPU/OPD modules. TSP modules.
For Whom: End User and System Support Representative. End User and System Support Representative. End User and
System Support Representative. End User and System Support Representative. End User and System Support Representative.
End User and System Support Representative. End User and System Support Representative. End User and System
Support Representative. End User and System Support Representative. End User and System Support Representative.
Remedy: Retry the test case and contact the support representative, if the problem persists.
2) Message : Length of compile command exceeded maximum limit. Retry the test case and contact the support representative, if the problem persists.
3) Message : Lexer error. Retry the test case and contact the support representative, if the problem persists.
4) Message : Request string is empty. Retry the test case and contact the support representative, if the problem persists.
5) Message : /tpi-data does not exist on the test machine. Contact the system administrator for support.
6) Message : Problem writing the SPL text into temporary file Retry the test case and contact the support representative, if the problem persists.
7) Message : Failed to get the file size. Retry the test case and contact the support representative, if the problem persists.
8) Message : SPL text file is in inconsistent state. Retry the test case and contact the support representative, if the problem persists.
9) Message : Object code file is in inconsistent state. Retry the test case and contact the support representative, if the problem
persists.
10) Message : Can not find mt.exe Retry the test case and contact the support representative, if the problem
persists.

5548 Stored Procedure Compiled with Errors/Warnings.
Explanation: The SPL text of the stored procedure contains compilation errors/warnings. This error is returned when
the error code 5526 is not present in the dbc.errormsgs. This error can also be reported in case only warnings have occurred during the compilation of stored procedures and the error code 5527 is missing in the dbc.errormsgs table. Stored procedure is not created/replaced when this code is reported.
Generated By: Parser (SPL Compiler).
For Whom: Field Engineer
Remedy: The DBC.ErrorMsgs must contain the entry corresponding to error code 5526 and 5527.

5550 Comment string is longer than permitted.
Explanation: The comment string cannot be longer than 255 characters.
Generated By: Parser (opd).
For Whom: END USER
Remedy: Use a shorter comment string.

5551 The compress value is longer than permitted.
Explanation: The compress value cannot be longer than 255 characters.
Generated By: Parser (opu and opd).
For Whom: END USER
Remedy: Use a shorter compress value.

5552 The default value is longer than permitted.
Explanation: The default value cannot be longer than 255 characters.
Generated By: Parser (opu and opd).
For Whom: END USER
Remedy: Use a shorter default value.

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