Teradata SQL Error and Failure Codes from Error 7495 To 7506

7495 “%S”.”%S” was skipped due to error %d. Run SCANDISK.
Explanation: This message indicates that the CheckTable utility could not check the table due to data corruption.
Generated By: CheckTable
For Whom: End user or Field Engineer or the concerned site support representative.
Notes: While checking a table, if the CheckTable utility faces some data corruption problems, then the table check is
skipped. The message identifies the error code of the problem that caused the error along with the database name and the
table name.
Remedy: Run SCANDISK after CheckTable utility has completed checking the remaining tables.

7496 CheckTable utility aborted while checking table %04XH %04XH due to unexpected error %d.
Explanation: This message indicates that the CheckTable utility is aborted due to unexpected problems.
Generated By: CheckTable
For Whom: End user or Field Engineer or the concerned site support representative.
Notes: When the CheckTable utility faces some unexpected event, like SEGV, Floating Point Exception, or some illegal
operation, then the utility is aborted. The message identifies the error code of the problem which caused the error along
with the table that was being processed at the time.
Remedy: Restart CheckTable Utility and if the problem persists contact support personnel.

7497 The primary index values in the UPSERT statement hash the same, but are mismatched.
Explanation: The user specified different primary index values for the UPDATE and the INSERT parts of an UPSERT
statement. The values used have the same rowhash, but are not the same. The same primary index values must be used in
both parts of an UPSERT statement.
Generated By: StpUpd
For Whom: End User
Remedy: Correct the UPSERT statement and resubmit.

7498 The primary index values in the UPSERT statement match but other fields do not.
Explanation: The user specified non matching values for fields other than the primary index of an UPSERT statement.
The values used must be the same for both the UPDATE and INSERT parts of an UPSERT statement.
Generated By: StpUpd
For Whom: End User
Remedy: Correct the UPSERT statement and resubmit.

7500 Right truncation of string data for UDF/XSP/UDM %DBID.%TVMID.
Explanation: A UDF/XSP/UDM running in an ANSI mode session cannot pass a string to the function that would
result in the truncation of significant characters. The specified length of the parameter on the create determines the maximum
length string the function will accept.
Generated By: EVL modules.
For Whom: End user or UDF/XSP/UDM developer.
Remedy: Either redesign the UDF/XSP/UDM to accept longer strings or make sure the input string length does not
exceed the maximum string length defined by the UDF/XSP/UDM.

7502 A system trap was caused by UDF/XSP/UDM %DBID.%TVMID for %VSTR
Explanation: The UDF/XSP/UDM caused a system trap for the reason indicated.
Generated By: AMP subsystem.
For Whom: UDF/XSP/UDM Developer.
Notes: The error string will contain the system trap information plus trace back information where possible.
Remedy: The developer of the UDF/XSP/UDM has to look at the UDF/XSP/UDM and fix the bugs.

7503 The UDF server failed to execute UDF/XSP/UDM %DBID.%TVMID
Explanation: The specified UDF/XSP/UDM caused the server task that is used to execute a UDF/XSP/UDM in protected
mode to fail. The error was severe enough to prevent the UDF server from reporting any proper error information
Generated By: AMP subsystem.
For Whom: UDF/XSP/UDM developer.
Remedy: The developer of the UDF/XSP/UDM has to look at the function and fix the bugs. Try bypassing some suspect
code. Try trace output.

7504 in UDF/XSP/UDM %DBID.%TVMID: SQLSTATE %VSTR
Explanation: This is a UDF/XSP/UDM generated error. The meaning depends on the UDF as defined by the developer.
Generated By: AMP subsystem.
For Whom: UDF/XSP/UDM user.
Notes: The variable string will contain the SQLSTATE code followed by an optional text string supplied by the
UDF/XSP/UDM.
Remedy: Look up the documentation for the UDF/XSP/UDM and take the necessary action to use the function in the
correct context.

7505 in UDF/XSP/UDM %DBID.%TVMID: SQLSTATE %VSTR
Explanation: This is a UDF/XSP/UDM generated warning. The meaning depends on the UDF/XSP/UDM as defined
by the developer. Since this is only a warning the request is not terminated.
Generated By: AMP subsystem.
For Whom: UDF/XSP/UDM user.
Notes: The variable string will contain the SQLSTATE code followed by an optional text string supplied by the
UDF/XSP/UDM.
Remedy: Look up the documentation for the UDF/XSP/UDM and take the necessary action to use the function in the
correct context.

7506 The library for UDF/XSP/UDM %DBID.%TVMID could not be found
Explanation: All UDFs/XSPs/UDMs are linked in a dynamic linked library or in a package which must exist on all
nodes on the database system. The library for this UDF/XSP/UDM could not be found on at least one node.
Generated By: AMP subsystem.
For Whom: DBA.
Remedy: If the UDF/XSP/UDM is in a package make sure the package has not been deleted or propagated to all nodes.
If the UDF/XSP/UDM is in a library then it has been deleted on some node. To generate a new library compile the
UDF/XSP/UDM via the ALTER FUNCTION/PROCEDURE statement using the COMPILE option. This create a new
UDF/XSP/UDM library.
If the UDF/XSP/UDM is called or executed in protected mode, make sure on each node the library and all the dependency
libraries exist and were given the correct file permission. Check the system log for error 7820 for more specific information.

Above are list of Teradata Errors or Failure Codes from Error 7495 To 7506 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.

When it comes to troubleshooting, the more you know the better troubleshooter you are (in my option). Sometimes knowing more actually gets in the way. We repeatedly get calls where customers couldn’t connect to AlwaysOn Listener on Azure because of the misconfiguration of the subnet mask for the listener IP. They receive this error “A...

We just released SQL Nexus 5.5.0.1 on codeplex. In addition to numerous ‘rules’ that catch issues that can potentially impact your SQL Server performance, we added quite a few reports. Some of the reports are displayed below. The following three were born out of troubleshooting experience. “Top 20 Active CPU Intensive Queries”: When troubleshooting CPU...

A user called in for help because he wasn’t able to drop a user from a database. The error message is below Msg 15136, Level 16, State 1, Line 2The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot be dropped. From the error, the...

There are multiple levels of throttling with Azure. You can get throttled at disk level, storage account level or VM/host level. These types of throttling can manifest into something that may not be that obvious. Recently we received a call from customer who was backing up databases from Azure VM to Azure blob storage. The...

Lately, we had a customer who contacted us for a performance issue where their server performed much worse in SQL Server 2016 following upgrade. To show us as an example, he even captured a video. In the video, he showed that the session that was compiling the query had multiple threads waiting on LATCH_EX of...

With so many users new to Azure, Sometimes an issue appears more complex than it really is. If you back up your databases to Azure blob storage but your company uses proxy servers for internet access, you will need to configure backuptoURL.exe.config per SQL Server Backup to URL Best Practices and Troubleshooting. We...

If you created an SQL Server VM via azure portal, there will be a section called “SQL Server Configuration” which was introduced via blog “Introducing a simplified configuration experience for SQL Server in Azure Virtual Machines”. Here is a screenshot of that setting. It allows you to configure various things like auto backup, patching or...

If you need to open up your SQL Server on an Azure VM to public internet access, you need to look no further than this document Connect to a SQL Server Virtual Machine on Azure (Resource Manager). It has very detailed step-by-step instructions. On a very high level, here are steps In your VM, create...

Recently we got a customer who called in and wanted to know why he received NULL for query_plan when querying sys.dm_exec_query_plan. This customer referenced a blog from https://dzone.com/articles/dmexecqueryplan-returning-null. In that scenario, you will get NULL for query_plan if there are any statements involving temp tables that have not been executed for the first time. For...