Teradata SQL Error and Failure Codes from Error 5844 To 5855

5844 Corresponding columns of Set operators must have same type.
Explanation: Entry level ANSI requires corresponding column descriptors for UNION to to be identical.
Generated By: OptRet procedure
For Whom: User.
Remedy: If the script is to be fully ANSI compliant, change the indicated statement.

5845 Hexadecimal Graphic constants are not supported in ANSI.
Explanation: This form of graphic constant is not supported in ANSI.
Generated By: LEXER.
For Whom: User.
Remedy: If script is to be full ANSI compliant, change the indicated statement.

5847 The database ’%VSTR’ has tables & triggers in different databases.
Explanation: The above error is generated when a user submits a DELETE DATABASE command that contains :
1.Tables with triggers defined in some other database. 2.Triggers that has reference to a table in other database.
If the DELETE DATABASE were successfully executed, it would cause Orphan triggers for first case or would results in
bogus triggercount in tvm rows (second case).
In order to avoid above problems, 1.Prevent the deletion of any database whose table(s) has one or more triggers defined
on it and trigger’s database is not same as the database to be deleted.
2.Prevent the deletion of any database whose trigger(s) has a reference to table and table database is not same as the database
to be deleted. <- DR120132-gs185064-01
Generated By: RES, OPD modules(opddeldb)
For Whom: End User or Field Engineer or the concerned site support Representative.
Notes: Find all the triggers that are defined on the tables in the database being deleted by using the following command:
SELECT dbase.databasename , triggerstbl.triggername WHERE triggerstbl.SubjectDbId = <DBID>;
where <DBID> is the database id of the database being deleted. The database id of the “database being deleted” can be
obtained using the following command:
SELECT dbase.databaseid WHERE dbase.databasename = <DBName>;
where <DBName> is the database name of the database being deleted.
Remedy: Drop all triggers from the above list and then execute the DELETE DATABASE command

5848 Maximum recursion level of triggers has exceeded.
Explanation: Database triggers can be recursive. However, a limit has to be imposed on the number of maximum levels
of recursion. If a restriction is not imposed, there can be a resource crunch when user submitted an SQL that fired a chain of recursive triggers.
Generated By: RES modules.
For Whom: End user or Field Engineer or the concerned site support Representative.
Notes: The current maximum Recursion level is 12.
Remedy: None.

5849 INSTEAD OF triggers are not supported.
Explanation: According to the ANSI standards, the INSTEAD OF triggers are not allowed. Hence, these triggers are disabled in the new implementation.
Generated By: SYN, RES modules.
For Whom: End user or Field Engineer or the concerned site support Representative
Notes: The INSTEAD OF triggers were supported in the original implementation of Triggers from V2R3. But to ensure
that Triggers are ANSI complaint, the INSTEAD OF triggers are disabled from V2R5.1
Remedy: None.

5850 BEFORE statement triggers are not supported.
Explanation: In the ANSI trigger implementation of V2R5.1 , BEFORE Statement triggers are not allowed.
Generated By: SYN, RES modules.
For Whom: End user or Field Engineer or the concerned site support Representative.
Notes: The BEFORE Statement triggers were supported in the original implementation of triggers from V2R3. But to
ensure that triggers are ANSI complaint, the BEFORE Statement triggers are disallowed from V2R5.1
Remedy: To prevent this error message, the application must be modified to use some alternative to the BEFORE Statement
trigger. Most likely a BEFORE statement trigger can be replaced by an AFTER trigger.

5853 Cannot specify an account string with a user list
Explanation: A BEGIN QUERY LOGGING statement contains list of users and one or more account. You may specify
one user for each account string (or list) in a BEGIN statement, or a list of account strings with the ALL users option.
Generated By: opddbql.c
For Whom: End User.
Remedy: Change the BEGIN QUERY LOGGING statement to indicate one user with one or more accounts, or the keyword
ALL with one or more accounts. This may require several BEGIN QUERY LOGGING statements.

5854 The DBQL feature has not been installed.
Explanation: The DBA must run the DIPVIEW script to create the DBQLAccessMacro which is used to provide permission
to users to invoke the BEGIN/END QUERY LOGGING command.
Generated By: resolver
For Whom: End User.
Remedy: DBA should run DIP.

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