Teradata SQL Error and Failure Codes from Error 7553 To 7562

SQLServerF1_Header_Small

7553 Unable to obtain a External Routine Address for a UDF/UDM.
Explanation: An error was generated while trying to obtain a External Routine entry point address.
Generated By: DLL Management sub-system.
For Whom: UDT Instance and EVL sub-systems.
Remedy: The UDT developer should make sure the External Name of the routine is exported from the user DLL library.

7554 Invalid %VSTR argument to LOB access function in UDF/XSP/UDM %DBID.%TVMID.
Explanation: The UDF/XSP/UDM passed an invalid argument to a LOB access function.
Generated By: UDF/XSP/UDM LOB access functions.
For Whom: UDF/XSP/UDM developer.
Remedy: Correct the error in the UDF/XSP/UDM code.

7555 Context cannot be allocated in UDF/XSP/UDM %DBID.%TVMID.
Explanation: The UDF/XSP/UDM attempted to open a large object for reading, but the maximum number of read contexts
were already open.
Generated By: FNC_LobOpen
For Whom: UDF/XSP/UDM developer
Remedy: The UDF/XSP/UDM must close (by calling FNC_LobClose) at least one outstanding large object read context
before opening another one.

7556 Illegal LOB access function call in UDF/XSP/UDM %DBID.%TVMID.
Explanation: The UDF/XSP/UDM attepted to call a large object access function, but the UDF/XSP/UDM does not have
either a large object parameter or a large object return value.
Generated By: UDF/XSP/UDM LOB access functions
For Whom: UDF/XSP/UDM developer
Remedy: Modify the UDF/XSP/UDM. In order to use any of the LOB access functions, it must be defined to have at
least one large object type argument or return value.

7557 Maximum number of locators exceeded in UDF/XSP/UDM %DBID.%TVMID.
Explanation: The UDF/XSP/UDM has exceeded the maximum number of locators that may allocated by the
FNC_LobRef2Loc function. This may be caused by a logic error in the UDF resulting in the execution of an unbounded
loop.
Generated By: FNC_LobRef2Loc
For Whom: UDF/XSP/UDM developer
Notes: The maximum number of locators that may be allocated in one UDF/XSP/UDM execution is 2000.
Remedy: Modify the UDF/XSP/UDM.

7558 Result indicator value not valid for UDF/XSP/UDM %DBID.%TVMID.
Explanation: The result indicator value must be set to -1 to indicate a NULL return result or to 0 to indicate that a valid
result is present. Upon return from the UDF/XSP/UDM some other value was found.
Generated By: AMP subsystem.
For Whom: Developer
Remedy: The remedy is to debug the UDF/XSP/UDM and set the correct result indicator value.

7559 Memory (via malloc call) not freed before exiting UDF/XSP/UDM %DBID.%TVMID.
Explanation: The UDF/XSP/UDM executes some C “malloc” calls and did not have the appropriate “free” calls to
release all of the allocated memory before exiting the UDF/XSP/UDM. The database system does not allow this because
this will cause memory leaks which would require an eventual restart of the database.
Generated By: AMP subsystem.
For Whom: Developer
Remedy: The remedy is to debug the UDF/XSP/UDM and make sure all allocated memory is freed before exiting the
UDF/XSP/UDM.

7560 Illegal call to FNC_LobAppend in UDF/XSP/UDM %DBID.%TVMID.
Explanation: Either the UDF/XSP/UDM does not have a large object return value, or it is an aggregate function that is
not executing the final phase. In either case, the UDF/XSP/UDM is not allowed to call FNC_LobAppend.
Generated By: FNC_LobAppend
For Whom: UDF/XSP/UDM developer
Remedy: Modify the UDF/XSP/UDM.

7561 Internal error from fast scan data dictionary ctbsctidf.
Explanation: This error is flagged if Checktable encountered an error during fast scan data dictionary (ctbsctidf).
Generated By: CheckTable.
For Whom: Internal.
Notes: This is an internal error to inform Checktable to rescan data dictionary using normal scan flow for errors reporting.
Remedy: None needed.

7562 Invalid operation on table %FSTR.
Explanation: This error message is reported when the user attempts to perform an update operation on a table which
has been invalidated. This error can also be reported if a single table retrieve is being executed without specifying the
READ OVERRIDE locking modifier.
Generated By: SUT modules.
For Whom: End User.
Remedy: Validate the table on which update operation has to be performed by executing a DELETE ALL operation on it
or by dropping and creating it again. In case a single table retrieve operation is being performed, then specify the READ
OVERRIDE locking modifier. The table can also be used after restoring it from backup.

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