Teradata SQL Error and Failure Codes from Error 7537 To 7552

SQLServerF1_Header_Small

7537 %DBID.%TVMID has a type of partitioning not supported in the current release.
Explanation: This code is used internally to indicate to ARCMAIN that a table being restored or copied must be
skipped. The specified table on an archive was defined in a later release with a form of partitioning not supported in the
current release to which the archive is being restored or copied.
Generated By: Restore and copy.
For Whom: ARCMAIN.
Notes: Internal use only.
Remedy: None.

7544 Cannot logon utility session.
Explanation: The error is reported in the following cases :
1. The configuration has more PEs than AMPs. And an utility session is already logged on the same AMP.
2. Or, some internal sanity checks have failed, resulting in failure to logon the utility session.
Generated By: UtaDvTsk.
For Whom: End User. Site support representative.
Remedy: If the configuration has more PEs than AMPs, change the configuration to have more AMPs than PEs.
In case 2, contact the Global Support Center.

7545 Numbering for Identity Column %TVMID.%FLDID is over its limit.
Explanation: A system-generated number for an identity column has exceeded its limit set by the column’s MAXVALUE/
MINVALUE parameter or, if not specified, by the default limit of the identity column’s data type.
Generated By: EXP module.
For Whom: End User.
Remedy: If the data type of the identity column is smaller than DECIMAL(18,0) or NUMERIC(18,0) create a new table
with a larger data type for the identity column.

7546 Unable to discard UDT memory segments for this process.
Explanation: The system was not able to discard the memory segments from the UDT Scratch Memory Pool. A call to
segdiscard() failed.
Generated By: UDT subsystem, after execution of EVL interpretive machine.
For Whom: DBA.
Remedy: Re-create the segment in error.
7547 Target row updated by multiple source rows.
Explanation: In present system we do not support to update the target row with multiple source rows. Before implementing
Merge Update the join updates were processed in two steps, Merge Delete and Merge Insert. Since, we used to
delete all the rows, we end up generating the duplicate rows to insert. In that scenario, we return a different error. This type
of Merge Updates (Join Updates) are not allowed.
For tables T1(a1,b1,c1), T2(a2,b2,c2), consider the update
update t1 from t2 set c1=c2 where a1=b2 and b2 < 10;
If there are more than one row satisfying this condition, we are not sure which row needs to be used for this update. In this scenario, we return this error message.
Note that with the introduction of the UDT indexing feature we also return this error when an update operation is performed
on a table with a hash index if:
a) the hash index is defined in one or more columns and one of the column is a structured udt column. b) the ordering function
defined for the structured udt column returns null.
Generated By: AMP subsystem
For Whom: User
Remedy: See that source rows are unique before updating.
If the update operation is performed on a table with a hash index and the hash index includes a structured udt column, verify that the ordering function does not return null.

7548 %VSTR
Explanation: An error was generated during processing of UDT data. Exact UDT error code and corresponding message
are given within VSTR.
Generated By: UDT subsystem.
For Whom: UDT Developer, End User.
Remedy: Take appropriate action based on the value of VSTR.

7550 Hash join operation is aborted due to non availability of segments.
Explanation: This error is reported when concurrent hash join operations are executed in parallel. As per design hash
join consumes few hundred segments, but when a number of hash joins are executed at the same time results in consumption
of all 64K segments(SEGSDB) allocated for a Vproc.
Generated By: AMP Software(STPHJIN).
For Whom: End User, Site support representative.
Remedy: If the site encounters this too often, disable hash join flag in dbscontrol gdo.

7551 An EVL LOB instruction has a bad parameter (%VSTR).
Explanation: One of the EVL LOB instructions was passed a bad parameter or an illegal combination of parameters.
Generated By: The Interpretive Instruction Processor.
For Whom: Site support representative.
Notes: The EVL interpreter detected a bad parameter or an illegal combination of parameters in a LOB instruction.
Remedy: Try to resubmit the request. If unsuccessful, contact the Global Support Center.

7552 Unable to create UDT Instance %VSTR – Check message log for possible 7820 errors in library synchronization.
Explanation: An error was generated while trying to create a UDT instance from UDT Type Identifier.
Generated By: UDT Instance sub-system.
For Whom: Syntaxer/Resolver/Optimizer/GNC-EVL and Amp sub-systems.
Remedy: The UDT developer should make sure the Constructor Function is returning a valid Instance pointer.

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