Teradata SQL Error and Failure Codes from Error 6779 To 6807

6779 File name not specified
Explanation: This error occurs when the file name is not specifed along with the tdlocaledef utility.
Generated By: tdlocaldef utility.
For Whom: End user.
Remedy: Specify filename and resubmit the request.

6780 Failure in accessing GDO
Explanation: This error occurs when the tdlocaldef utility fails to read or write from the GDO.
Generated By: tdlocaldef utility.
For Whom: End user.
Remedy: Ensure the GDOs have been created and resubmit the request.

6781 The stored procedure/PPI need to be re-compiled/re-validated.
Explanation: The error occurs when the stored procedure/PPI already exists and hdr.fmt is tdinum which need to be
initialized to tdinumparsecompat or tdinumparsei18n.
Generated By: TDI modules.
For Whom: End user.
Remedy: Existing stored procedures need to be re-compiled and PPIs need to be revalidated.

6800 UDT ’%TVMID’ supports NOT EQUAL/EQUAL ONLY comparitive operations.
Explanation: A UDT with EQUALS ONLY ordering is being used in a FULL comparison situation.
Generated By: Syntaxer/Resolver and Optimizer Modules
For Whom: End User
Remedy: Modify the definition of the UDT to incorporate the correct ordering functionality

6801 DISTINCT,INTERSECT, UNION, ORDER-BY Not Supported For UDT ’%TVMID’.
Explanation: UDT does not support the DISTINCT, INTERSECT, UNION, and/or ORDER BY
Generated By: Par/Opt Modules
For Whom: End User
Remedy: If UDT is Opaque Type, then author the pertinent map DBS support method.

6802 Improperly Formed UDT Tree Encountered.
Explanation: An incorrectly formed UDT sub-tree was encountered
Generated By: Par/Opt/Gnc Modules
For Whom: End User
Remedy: Internal Parsing Error. Save all relevant information and notify your support representative

6803 Invalid hardware architecture for procedure execution.
Explanation: The Teradata RDBMS server Hardware Architecture in which the CALL SQL is submitted is different than
the one in which the stored procedure was created. A stored procedure created using 32-bit compiler cannot be executed on64-bit compiler. This situation can occur if a stored procedure is restored to a different server having different Hardware architecture than the archive was created on.
Generated By: RES modules.
For Whom: End User
Remedy: Recreate the procedure on the new server hardware architecture and resubmit the request.

6804 Trigger on DBC tables is not allowed.
Explanation: Dictionary tables are updated outside of normal SQL, changes to them will not fire triggers.
Generated By: RES modules.
For Whom: End User.
Remedy: Don’t use trigger on DBC tables.

6805 Invalid reference to ACCLOGTBL in MLoad.
Explanation: Delete operation on ACCLOGTBL can not be performed from DELETE and IMPORT task of MLOAD if
access logging is enabled.
Generated By: OPH modules.
For Whom: End User
Remedy: To avoid this error, disable access logging and run the MLOAD job again.

6806 Constructor Functions Are Functional Representation of Constants and As Such They Must Not Contain Any Table References.
Explanation: This error occurs when a Constructor Function contains a Table Reference in its parameter list. A constructor function is a declaration of a UDT constant. Parameters are used to initialize the constant to some state. All Parameters to a Constructor Function must themselves be constants. Thus the parameters for a constructor function cannot contain any table references in its parameter list.
Generated By: OPT module.
For Whom: End User.
Notes: User SQL statement construction error.
Remedy: Type in Constructor Function Using only constants as parameters

6807 Invalid relational operation involving %VSTR. Cast them to the same UDT data type.
Explanation: This error occurs when a term of the form, “leftExpr RelationalOp rightExpr”, evaluates such that the left- Expr and rightExpr are not of compatible Udt data types. For two Udts to be compatible, they must be exactly equal, or there must exist a cast function which enables one Udt to be casted to the other Udts data type. Also, for early release, the casting must be explicitly typed in on the SQL input.
Generated By: OPT module. .
For Whom: End User.
Notes: User SQL statement formulation error
Remedy: Use exactly equal Udt data types for all relational operations, or supply explicit casts to insure that the relational operation is upon equal Udt data types.

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

 

SQL Server Errors or Failures from Error: 10723 to Error: 10742

SQLServerF1

You may receive various errors in SQL Server while working. Below are some of the SQL Server Errors from Error: 10723 to Error: 10742

Error: 10723, Severity: 15,
In a MERGE statement, a variable cannot be set to a column and expression in the same assignment in the SET clause of an UPDATE action. Assignments of the form ‘SET @variable = column = expression’ are not valid in the SET clause of an UPDATE action in a

Error: 10724, Severity: 15,
The FORCESEEK hint is not allowed for target tables of INSERT, UPDATE, or DELETE statements.

Error: 10725, Severity: 15,
Cannot use the VARYING option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement.

Error: 10726, Severity: 15,
User defined aggregates do not support default parameters.

Error: 10727, Severity: 15,
A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a JOIN or APPLY operator.

Error: 10728, Severity: 15,
A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed as the table source of a PIVOT or UNPIVOT operator.

Error: 10729, Severity: 15,
A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in a SELECT statement that is not the immediate source of rows for an INSERT statement.

Error: 10730, Severity: 15,
A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the FROM clause of an UPDATE or DELETE statement.

Error: 10731, Severity: 15,
A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed inside another nested INSERT, UPDATE, DELETE, or MERGE statement.

Error: 10732, Severity: 15,
A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a UNION, INTERSECT, or EXCEPT operator.

Error: 10733, Severity: 15,
A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the USING clause of a MERGE statement.

Error: 10734, Severity: 16,
Variable assignment is not allowed in a statement containing a top level UNION, INTERSECT or EXCEPT operator.

Error: 10735, Severity: 15,
Incorrect WHERE clause for filtered %S_MSG ‘%.*ls’ on table ‘%.*ls’.

Error: 10736, Severity: 15,
A full-text stoplist statement must be terminated by a semi-colon (;).

Error: 10737, Severity: 15,
In an ALTR TABLE REBUILD or ALTER INDEX REBUILD statement, when a partition is specified in a DATA_COMPRESSION clause, PARTITION=ALL must be specified. The PARTITION=ALL clause is used to reinforce that all partitions of the table or index will be rebuil

Error: 10738, Severity: 15,
The number of row value expressions in the INSERT statement exceeds the maximum allowed number of %d row values.

Error: 10739, Severity: 15,
The insert column list used in the MERGE statement cannot contain multi-part identifiers. Use single part identifiers instead.

Error: 10740, Severity: 15,
A search property list statement must end with a semicolon (;).

Error: 10741, Severity: 15,
A TOP can not be used in the same query or sub-query as a OFFSET.

Error: 10742, Severity: 15,
The offset specified in a OFFSET clause may not be negative.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 10104 to Error: 10126

SQLServerF1

 

Error: 10104, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it references a table using a CONTAINSTABLE or FREETEXTTABLE full-text function. Consider removing use of these functions or not indexing the view.
Error: 10105, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it uses the OPENXML rowset provider. Consider removing OPENXML or not indexing the view.
Error: 10106, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it references an internal system rowset provider. Consider not indexing this view.
Error: 10107, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it uses table variable “%.*ls”. Consider not indexing this view or removing the reference to the table variable.

Error: 10108, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it references a SQL Server internal table.
Error: 10109, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it references derived table “%.*ls” (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view.
Error: 10110, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it contains an OUTER APPLY. Consider not indexing the view, or removing OUTER APPLY.
Error: 10111, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it contains a join using an ODBC standard escape syntax. Consider using an ANSI join syntax instead.
Error: 10112, Severity: 16, Cannot create %S_MSG on view ‘%.*ls’ because it contains an INNER join that specifies a join hint. Consider removing the join hint.

Error: 10113, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it uses a LEFT, RIGHT, or FULL OUTER join, and no OUTER joins are allowed in indexed views. Consider using an INNER join instead.
Error: 10114, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it uses the PIVOT operator. Consider not indexing this view.
Error: 10115, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it uses the UNPIVOT operator. Consider not indexing this view.
Error: 10116, Severity: 16, Cannot create %S_MSG on view ‘%.*ls’ because it contains one or more UNION, INTERSECT, or EXCEPT operators. Consider creating a separate indexed view for each query that is an input to the UNION, INTERSECT, or EXCEPT operators of the original view.
Error: 10117, Severity: 16, Cannot create %S_MSG on view “%.*ls” because the view uses the “*” operator to select columns. Consider referencing columns by name instead.
Error: 10118, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it contains a GROUP BY ALL. Consider using a GROUP BY instead.
Error: 10119, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it contains a CUBE, ROLLUP, or GROUPING SETS operator. Consider not indexing this view.
Error: 10121, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it contains a HAVING clause. Consider removing the HAVING clause.
Error: 10124, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it references an internal SQL Server column.
Error: 10125, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it uses aggregate “%.*ls”. Consider eliminating the aggregate, not indexing the view, or using alternate aggregates. For example, for AVG substitute SUM and COUNT_BIG, or for COUNT, substitute COUNT_BIG.
Error: 10126, Severity: 16, Cannot create %S_MSG on view “%.*ls” because it uses aggregate “%.*ls” with the DISTINCT keyword. Consider not indexing this view or eliminating DISTINCT. Consider use of a GROUP BY or COUNT_BIG(*) view to simulate DISTINCT on grouping columns.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.