Teradata SQL Error and Failure Codes from Error 9665 To 9678

9665 VPROC %d:AutoTempComp can no longer
uncompress database %s (%04X %04X). Uncompressing
will leave this database with less than %d%% (as defined by
DBSControl tunable UncompressReservedSpace) of its allocated
space available. Depending on other activities against database
%s further uncompression may occur in the future.
Explanation: TBBLC background task stops uncompressing database, if free space is lower than UncompressReserved-
Space threshold
Generated By: AMP
For Whom: End user or Field Engineer or the concerned site support representative.
Remedy: Free some space in database or adjust the DBSControl’s UncompressReservedSpace tunable to lower value

9666 DBQL AWT DPS cache overflow, %s.
Explanation: The AMP DBQL Performance Statistics (DPS) cache cannot grow above the current DBS Control
“DBQL_AWTDPS_CacheMaximum” limit. DBQL capture of AMP request and step data is impacted and the QryLog
DBQLStatus field (DBQLogTbl) will reflect that.
Generated By: AMP Worker Task (awtdps module).
For Whom: System administrator & Site support representative.
Notes: This message is only logged once per AMP, however If you increase the limit this message will occur if the new
limit is reached.
Remedy: Determine whether this condition represents an error to report to the site support representative. If the limit
should be raised to accommodate more DBQL data collection, increase the internal field
’DBQL_AWTDPS_CacheMaximum’ value in DBS Control.

9672 Fastload is not allowed on a normalized table with no primary index.
Explanation: Fastload is not allowed on a normalized NOPI table.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9673 Normalize specification was not copied.
Explanation: This is only a warning to let the user know that Normalize specification will not be copied to the table
being created. This is the case where a table name was specified in the Create Table As/Like statement with column names
defined in the Create Table clause. For example,
CREATE TABLE Table1 (field_1, field_2) Table2 WITH [NO] DATA; Normaliz specification on Table2 (if exist) will not be copied to Table1.
Generated By: Resolver.
For Whom: End User.
Remedy: The message is for information only.

9674 Multiple Normalize clauses are defined.
Explanation: Multiple Normalize clauses are defined.
Generated By: SYN module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9675 Extended MultiLoad Protocol does not allow target table in a Replication group.
Explanation: Replication is not allowed with the Extended MultiLoad Protocol.
Generated By: OPH module.
For Whom: End User.
Remedy: Do not use MultiLoad.

9676 MERGE-INTO DELETE does not allow target table in a Replication group.
Explanation: Replication is not allowed with MERGE-INTO DELETE.
Generated By: GNS module.
For Whom: End User.
Remedy: Do not submit MERGE-INTO DELETE with target table in a Replication group.

9677 BEGIN QUERY CAPTURE already in progress into %VSTR query capture database.
Explanation: There is already an active BEGIN QUERY CAPTURE session in progress on a different Query Capture
Database whose name is contained in %VSTR. BEGIN QUERY CAPTURE can be enabled only on one Query Capture Database
at a time for a user.
Generated By: parser.
For Whom: User.
Remedy: To enable BEGIN QUERY CAPTURE on the new Query Capture Database, the existing BEGIN QUERY CAPTURE
session should be ENDED. If not, the BEGIN QUERY CAPTURE session currently in progress will remain active.

9678 The UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING specification is not
supported for FIRST_VALUE/LAST_VALUE.
Explanation: The FIRST_VALUE/LAST_VALUE functions do not support the UNBOUNDED PRECEDING AND
UNBOUNDED FOLLOWING specification.
Generated By: Opt modules
For Whom: End User.
Remedy: Resubmit the request with a valid ROWS expression.

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