Teradata SQL Error and Failure Codes from Error 5533 To 5543

SQLServerF1_Header_Small

5533 Too many MULTITSR Parcels.
Explanation: The submitted Stored Procedure is too large to handle.
Generated By: Pardrivr.
For Whom: End User
Remedy: Reduce the size of the Stored procedure and submit the request.

5534 SPOptions Parcel information is invalid.
Explanation: Print Option was not ’P’ or ’N’. SPL text Option was not 1 or 0.
Generated By: Pardrivr.
For Whom: System Support Representative.
Remedy: Correct the program and resubmit the request.

5535 No SPL source text available for stored procedure “%VSTR”.
Explanation: SPL Text is not available in SPTable for the stored procedure specified to display it.
Generated By: RES modules.
For Whom: End User
Remedy: Correct the SQL and resubmit the request.

5536 Bad table definition for SystemFE.%VSTR.
Explanation: The user is attempting to use the Target Level Emulation feature, but for some reason the DDL has been
changed from its initial definition. The appropriate fields expected by this feature no longer exist in either SystemFE. opt_cost_table or SystemFE.opt_ras_table.
Generated By: OPT modules.
For Whom: End User.
Remedy: Drop the appropriate SystemFE table and run DIPSYSFE to recreate the table with the correct definition. If after this the same error still occurs, please contact the Global Support Center.

5537 Internal error while cleaning up Request Level Cost Segment.
Explanation: This is an internal error with the Target Level Emulation Feature.
Generated By: OPT modules.
For Whom: Internal
Remedy: Please save the traceback and any pertinent information that would help an analyst reproduce the problem,
and contact the Global Support Center.

5538 Internal error while cleaning up Session Level Cost Segment.
Explanation: This is an internal error with the Target Level Emulation Feature.
Generated By: OPT modules.
For Whom: Internal
Remedy: Please save the traceback and any pertinent information that would help an analyst reproduce the problem,
and contact the Global Support Center.

5539 Internal error while cleaning up IFP Level Cost Segment.
Explanation: This is an internal error with the Target Level Emulation Feature.
Generated By: OPT modules.
For Whom: Internal
Remedy: Please save the traceback and any pertinent information that would help an analyst reproduce the problem,
and contact the Global Support Center.

5540 Target name “%VSTR” not found.
Explanation: The user attempted to set the optimizer costs to a target system name which has not been loaded to SystemFE.
opt_cost_table.
Generated By: OPT modules.
For Whom: End User.
Remedy: Fix the target system name specified or update the SYSTEMFE.OPT_COST_TABLE with dumped costs from
the desired system.

5541 Local instance of temporary table ’%VSTR’ does not exist in current session.
Explanation: The user referenced the local instance of a temporary table which does not exist in current session.
Generated By: RES modules.
For Whom: End User.
Remedy: Resubmit request after local instance of temporary table has been created.

5542 Only Select, Insert, Delete or Update statements can be captured.
Explanation: The DUMP EXPLAIN, INSERT EXPLAIN, and EXPLAIN IN XML commands can be done only on
SELECT, INSERT, UPDATE or DELETE statements.
Generated By: Parser
For Whom: End User.
Remedy: Do not submit DUMP EXPLAIN, INSERT EXPLAIN, or EXPLAIN IN XML commands on requests other than
SELECT, INSERT, UPDATE or DELETE statements.

5543 There were NO costs enabled to turn off.
Explanation: An attempt was made to SET COSTS {NOT | TPA} ON FOR LEVEL, but NO costs were found to be
enabled at the specified level.
Generated By: OPT modules.
For Whom: End User.
Remedy: This error is a warning. The only remedy is to SET COSTS ON FOR {SESSION | IFP | SYSTEM} before turning
costs off.

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