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.

 

Teradata SQL Error and Failure Codes from Error 9651 To 9664

9651 End of partition encountered in row-column subsystem.
Explanation: Compressed value encountered for a container row but it’s AC bitis off.
Generated By: Row Column Subsystem
For Whom: Site support representative.
Notes: This error is returned by the row-column subsystem. It is only returned to the client when the error is not one of
the possible expected error codes in the calling routine.
Remedy: Contact your System Representative.

9652 End of partition encountered in row-column subsystem.
Explanation: Container row context is not initialized for sticking a value in it.
Generated By: Row Column Subsystem
For Whom: Site support representative.
Notes: This error is returned by the row-column subsystem. It is only returned to the client when the error is not one of
the possible expected error codes in the calling routine.
Remedy: Contact your System Representative.

9653 Insufficient free space in a container row for appending a column-partition value.
Explanation: This error indicates that there is insufficient free space available in a container row for sticking a columnpartition
value.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the
calling routine.
Remedy: Contact your Support Representative.

9654 Insufficient free space in a container row for appending a column-partition value.
Explanation: This error indicates that there is insufficient free space available in a container row for sticking a columnpartition
value.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the
calling routine.
Remedy: Contact your Support Representative.

9655 Insufficient free space in a container row for appending a column-partition value.
Explanation: This error indicates that there is insufficient free space available in a container row for sticking a columnpartition
value.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the
calling routine.
Remedy: Contact your Support Representative.

9656 Insufficient space available for the compression dictionary of a container row.
Explanation: This error occurs when there is insufficient buffer space for the compression dictionary of a container row
of a column-partitioned table.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the
calling routine.
Remedy: Contact your Support Representative.

9661 Column partition row counts do not match with other column partition row counts.
Explanation: Column partition row counts do not match with other column partition row counts.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9662 Transaction was recovered.
Explanation: An a redrive-enabled transaction with at least one completed request was recovered by system recovery.
Any uncompleted requests were rolled back, and the transaction remains open. This is an informational code that is handled
internally by the Dispatcher and should not be visible to the end user.
Generated By: AMP
For Whom: Internal only.
Remedy: No remedy is necessary. The transaction may proceed as normal.

9663 Hash ownership check failed on AMP %d for %DBID.%TVMID.
Explanation: This message indicates that the database attempted to insert a row on the wrong AMP.
Generated By: AMP
For Whom: Field Engineer or the concerned site support representative.
Notes: This is an internal error.
Remedy: Contact your Support Representative.

9664 An incorrectly formatted container is detected.
Explanation: An incorrectly formatted container is detected during a level 3 CheckTable of a column-partitioned table or
join index. The following are examples of incorrect settings in a container: 1. The container has autocompression enabled and the offset to the last set of autocompression bits is out-of-bounds of the length of the container. 2. The first presence byte of the container indicates autocompression is to be determined and also indicates the container is using autocompression
types of local value dictionary compression, run length compression, or both. 3. The offset to free space is out-ofbounds
of the length of the container.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

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

 

Teradata SQL Error and Failure Codes from Error 9624 To 9650

9624 Logical row for a specified RowID does not exist or is marked as deleted.
Explanation: A logical row was located but a column-partition value was not found for it or the logical row is marked as
deleted. This can occur if an access lock is being used and the logical row was deleted by another session or an insert or
update attempted by another session was rolled back.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the
calling routine.
Remedy: Contact your Support Representative.

9626 Null column-partition value encountered in the row-column subsystem.
Explanation: This error indicates all column values in the column-partition value are null.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the calling routine.
Remedy: Contact your Support Representative.

9628 Insufficient free space in a container row for appending a column-partition value.
Explanation: This error indicates that there is insufficient free space available in a container row for sticking a columnpartition
value.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the calling routine.
Remedy: Contact your Support Representative.

9629 Insufficient buffer space for appending a column-partition value to a container row.
Explanation: This error occurs when there is insufficient buffer space available (that is, buffer is full) for appending a new column-partition value to a container row.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned by the row-column subsystem. It is only returned to the client when the error is not one of
the possible expected error codes in the calling routine.
Remedy: Contact your Support Representative.

9630 Unable to compress null value for a container row.
Explanation: This error occurs when attempting to append a null column-partition value to a container row and autocompression
is not being used for this container row or, if auto-compression is being used for this container row, that the
auto-compression types for this container row do not allow for nulls.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the
calling routine.
Remedy: Contact your Support Representative.

9632 Container row cannot be compressed.
Explanation: This error occurs when no compression techniques are applicable to a container row.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the calling routine.
Remedy: Contact your Support Representative.

9634 Insufficient space available for the compression dictionary of a container row.
Explanation: This error occurs when there is insufficient buffer space for the compression dictionary of a container row
of a column-partitioned table.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the calling routine.
Remedy: Contact your Support Representative.

9650 End of partition encountered in row-column subsystem.
Explanation: A read past the end of a column-partitioned table row partition during search mode was encountered.
Generated By: Row Column Subsystem
For Whom: Site support representative.
Notes: This error is returned by the row-column subsystem. It is only returned to the client when the error is not one of
the possible expected error codes in the calling routine.
Remedy: Contact your System Representative.

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

 

Teradata SQL Error and Failure Codes from Error 9608 To 9623

9608 Logon processing failed in the Dispatcher due to insufficient resources.
Explanation: Session context(s) cleanup is pending in the Dispatcher while concurrent session threshold prevailed. This
may occur when all session contexts are already in use, although some are being cleaned-up and should become available
shortly.
Generated By: Dispatcher by way of Session Control.
For Whom: End user.
Remedy: Please try to logon again.

9613 A dynamic group resource leakage was detected.
Explanation: Dispatcher diagnostic code detected a dynamic group resource leakage. This means that one or more
dynamic groups that was acquired to process a request was not released at the conclusion of request processing.
Generated By: Dispatcher.
For Whom: System Support Representative.
Notes: Note that at this point, the request had been committed. A snapshot dump may also be conditionally generated as
part of handling this event.
Remedy: Save the request that caused the problem, and contact your support representative.

9614 A snapshot dump of a Dispatcher task was saved.
Explanation: A snapshot dump was saved in order to be able to further investigate a problem involving a particular Dispatcher
task.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Save the request that caused the problem, and contact your support representative.

9615 Request completed and response available.
Explanation: The request has completed and its response is available.
Generated By: Dispatcher.
For Whom: End User.
Notes: This error is sent in response to a host status request from the client. The host status request is sent after a database
or client restart.
Remedy: Return the response to the application.

9616 Request is being re-driven by the database.
Explanation: The request was active at the time of a database crash and the database is re-driving the request following
the crash.
Generated By: Dispatcher.
For Whom: End User.
Notes: This error is sent in response to a host status request from the client. The host status request is sent after a database or client restart.
Remedy: Return the response to the application.

9617 The session doesn’t have any requests.
Explanation: The session doesn’t have any requests. The client can re-drive its outstanding request (if any) or submit a
new request.
Generated By: Dispatcher.
For Whom: End User.
Notes: This error is sent in response to a host status request from the client. The host status request is sent after a database or client restart.
Remedy: Client can re-drive its outstanding request (if any) or submit a new request.

9618 Request is active on the database.
Explanation: The request is active on the database.
Generated By: Dispatcher.
For Whom: End User.
Notes: This error is sent in response to a host status request from the client. The host status request is sent after a database or client restart.
Remedy: Wait for the request to complete.

9619 A spool table leak was detected.
Explanation: Dispatcher diagnostic code detected a spool table leakage. This means that one or more spool tables that
was acquired to process a request was not released at the conclusion of request processing.
Generated By: Dispatcher.
For Whom: System Support Representative.
Notes: Note that at this point, the request had been committed. A snapshot dump may also be conditionally generated as
part of handling this event.
Remedy: Save the request that caused the problem, and contact your support representative.

9620 End of file encountered in the row-column subsystem.
Explanation: A read past the end of a column-partitioned table during search mode was encountered.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the calling routine.
Remedy: Contact your Support Representative.

9623 Internal error encountered in the row-column subsystem: %VSTR.
Explanation: An internal processing exception occurred while processing logical rows for a column-partitioned table.
The text provides more information about the error. This is an internal error.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Remedy: Contact your Support Representative.

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

 

Teradata SQL Error and Failure Codes from Error 9597 To 9607

9597 Select list must have at least one period column.
Explanation: If <normalize select option> is specified, at least one column in the select list must be of period data type.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9598 Invalid use of NORMALIZE clause.
Explanation: If <normalize select option> cannot be specified when WITH clause or TOP N operator also specified in
the query. Also reports the above error when recursive query specifies the <normalize select option>.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9599 Fastload is not allowed on a table when primary index is part of NORMALIZE ignore column
list.
Explanation: Fastload is not allowed on a normalized PI table when PI column is part of the ignore column list.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9600 Response buffer size is insufficient to hold records 32KB.
Explanation: This error occurs if FetchRowCount value is greater than number of rows that can be returned in a single
response buffer to the host. This occurs when the below conditions are true. 1) fetchrowcount value is greater than number
of rows that would fit in 32K and 2) user specifies a response buffer <= 32K but the actual data is > 32K.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Client application can reduce the fetchrowcount value and submit a CONTINUE request. (OR) For Host utilities
that cannot handle 64KB Row Size, they should not resend the request. (OR) For Host utilities that can handle 64KB
Row Size, enlarge the application’s response buffer size to at least the size (but no more than 64,256) returned in the Info
field of the ERROR parcel and submit a CONTINUE request containing a single RESP or KEEPRESP parcel that specifies
the new response buffer size.

9601 Response buffer size is insufficient to hold one record.
Explanation: This error occurs if FRC value is greater than minimum number of rows that can be returned in a single
response buffer to the host.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Client application can reduce the fetchrowcount value and submit a CONTINUE request. (OR) Enlarge the
application’s response buffer size to the size returned in the Info field of the ERROR parcel and submit a CONTINUE
request containing a single RESP or KEEPRESP parcel that specifies the new response buffer size.

9602 Response buffer size is insufficient to hold one record 64KB.
Explanation: This error occurs if FetchRowCount value is greater than number of rows that can be returned in a single
response buffer to the host. This occurs when the below conditions are true. 1) fetchrowcount value is greater than number of rows that would fit in
64K and 2) user specifies a response buffer <= 64K but the actual data is > 64K.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Client application can reduce the fetchrowcount value and submit a CONTINUE request. (OR) For Host utilities
that cannot handle 1MB response buffer, they should not resend the request. (OR) For Host utilities that can handle
1MB response buffer, the client should grow the buffer and send a ’Continue’ request with the required buffer size

9603 Response buffer size is insufficient to hold one record 1MB.
Explanation: This error occurs if FetchRowCount value is greater than number of rows that can be returned in a single
response buffer to the host.
This occurs when fetchrowcount value is greater than number of rows that would fit in 1MB response buffer.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Client application can reduce the fetchrowcount value and submit a CONTINUE request.

9604 The request contains invalid fetch row count value.
Explanation: This error occurs if the request contains invalid FetchRowCount value in FetchRowCount parcel. Consult
the Call-Level Interface Version 2 Manual for more information on valid request parcel sequences.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Host application should send a valid FetchRowCount value.

9605 FetchRowCount value ignored.
Explanation: This is a warning only, not an error. FetchRowCount is applicable only for the datarows, current request
did not return any datarows, so FetchRowCount value is ignored . Response buffer will accomodate as many rows as possible.
Generated By: OPT modules.
For Whom: End User.
Notes: The request is still processed despite the warning.
Remedy: This message is for information only.

9607 Not enough virtual memory to proceed with the query.
Explanation: This is a task or process level limit. In thread based model(WINDOWS, LINUX), this task may be a victim
due to high consumption of memory by other threads in the process. However, in process based model, process hits the
limit of virtual address space due to high cosumption of segments by the query.
Generated By: Dispatcher.
For Whom: End user, System Suport Representative.
Remedy: Save the request that caused the problem, and contact your support representative.

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

 

Teradata SQL Error and Failure Codes from Error 9585 To 9596

9585 A column must not be part of more than one derived period column definition.
Explanation: A column cannot be both begin column and end column of a derived period column definition.
Generated By: RES modules
For Whom: The end user.
Remedy: Correct the statement and resubmit.

9586 A column cannot be both the begin column and end column of a derived period column definition.
Explanation: A column can be either a begin column or an end column of a derived period column definition, but not
both.
Generated By: RES modules
For Whom: The end user.
Remedy: Correct the statement and resubmit.

9587 Invalid use of a derived period column.
Explanation: The derived period column is not allowed in any other statement other than period predicates.
Generated By: RES modules
For Whom: The end user.
Remedy: Correct the statement and resubmit.

9588 Column %VSTR is part of derived period column definition and cannot be dropped.
Explanation: The columns participating in the derived period column cannot be dropped using ALTER TABLE.
Generated By: OPD modules
For Whom: The end user.
Remedy: Remove the derived period column and resubmit.

9589 Session qualifier cannot be set when nontemporal application compatibility mode is disabled.
Explanation: Session qualifier cannot be set when nontemporal application compatibility mode is disabled.
Generated By: RES modules
For Whom: The end user.
Remedy: Do not set the session qualifier in nontemporal application compatibility mode is disabled.

9590 Nontemporal application compatibility mode changed to %VSTR.
Explanation: Nontemporal application compatibility mode is changed between the database restarts.
Generated By: CTX modules
For Whom: The end user.
Remedy: Nontemporal application compatibility mode is changed between the database restarts.
9591 Normalize column must be a period column.
Explanation: When a table is DDL normalized, then the <Normalize column> must be a period data type column or a
pseudo period column.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9592 NORMALIZE is not allowed on a transaction time column.
Explanation: When a table is DDL normalized, then the <Normalize column> must not be transaction time column.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9593 LOB columns must be part of normalize ignore columns list.
Explanation: When a table is DDL normalized, A LOB column if present in the table definition must be included in the
ignore column list.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9594 A table already has a normalize definition.
Explanation: A table can have only one normalize column, adding another normalize column reports a new error.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9595 NORMALIZE option definition not allowed.
Explanation: The <normalize option definition> cannot be specified on a target table for CREATE TABLE AS statement.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9596 Invalid use of normalize period column.
Explanation: For triggers, normalize period column specification in newrow or newtable is not allowed.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

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

 

Teradata SQL Error and Failure Codes from Error 9572 To 9584

9572 DBQL Mode out of range. %VSTR.
Explanation: The Mode specifies the manner in which DBQL collects CPU/IO resource usage data for this rule. It overrides
the system default selection specified by DBS Control general parameter “DBQL CPU/IO Collection”. The %VSTR is the variable string that provides the valid range, for example “Valid range is 0 to 3”.
Generated By: OPD
For Whom: END USER
Remedy: Reissue the Query Logging request with a mode value in the range specified.

9573 MODE not allowed on Begin/Replace Query Logging due to lack of Execute rights on DBC.DBQLModeMacro.
Explanation: The user did not have EXECUTE right on DBC.DBQLModeMacro which is required for specification of
MODE on the Begin/Replace Query Logging SQL statement.
Generated By: Parser/Syntaxer
For Whom: End User, System Administrator
Remedy: Eliminate the use of MODE or obtain the necessary right.

9574 The DBQL option %VSTR.
Explanation: The Begin/Replace Query Logging command option specified in the error text is not available because the
associated macro is missing.
Generated By: resolver
For Whom: End User.
Remedy: DBA should create the respective macro.

9577 Create/Replace failed because of incompatible “%VSTR”.
Explanation: The parameter style is not compatible with the function type or the language style.
Generated By: RES modules.
For Whom: User.
Remedy: Specify compatible parameter, function type, and language styles.

9578 Extended MultiLoad Protocol does not allow USI update on the target table.
Explanation: USI update is not allowed in Extended MultiLoad Protocol.
Generated By: OPH module.
For Whom: End User.
Remedy: Do not update USI or do not use Extended MultiLoad Protocol.

9579 Extended MultiLoad Protocol does not allow multiple DMLs on the same target table.
Explanation: Multiple DMLs are not allowed on the same target table in Extended MultiLoad Protocol. Note – an Upsert
is considered one DML.
Generated By: OPH module.
For Whom: End User.
Remedy: Do not submit multiple DMLs on the same target table or do not use Extended MultiLoad Protocol.
9580 Warning: Extended MultiLoad Protocol is to be used for the MultiLoad job.
Explanation: This warning code, when included in the Success/OKs parcel for the CHECK WORKLOAD END statement,
tells the Client application that the Extended MultiLoad Protocol is to be used for the current MultiLoad job. Without
this warning code, the traditional MultiLoad protocol is to be used instead.
Generated By: OPH module.
For Whom: Client Application.
Remedy: None.

9581 Warning: The work table %DBID.%TVMID specified in the MLOAD statement was not created for the MultiLoad job.
Explanation: This warning code, when included in the Success/OKs parcel for an MLOAD statement, tells the Client
application that the work table specified in the statement was not created for the current MultiLoad job. There can be multiple MLOAD statements for a job; each is generated for a specific target table. Only the work table specified in the first MLOAD statement will be used to create the NoPI staging table for the job when Extended MultiLoad Protocol is used.
This warning code tells the Client application that a work table was not created and therefore the Client application should not attempt to drop it at the end of the load.
Generated By: OPH module.
For Whom: Client Application.
Remedy: Do not drop the work table at the end of the load.

9582 The maximum number of sessions allowed for this MultiLoad job has reached.
Explanation: This error occurs when the maximum number of sessions allowed for a MultiLoad has reached. The
default limit is the number of AMPs in the system.
Generated By: TDWM module.
For Whom: Internal Message Only.
Remedy: This error exists only to instruct the utility program to stop attempting to log sessions onto the Teradata DBS.

9583 Warning: The NoPI staging table has been deleted due to restart with LOB.
Explanation: This warning code, when included in the Success/OK parcel for a BEGIN MLOAD statement, tells the Client
application that the NoPI staging table has been deleted and the Client application should unwind the import data to
the beginning. This happens when there is a restart during the acquisition phase and the target table has LOB column(s).
Restarting the acquisition phase requires dropping of duplicate data that are resent from the restart. This will be done by sort but there is no interface currently available to drop the associated LOB rows.
Generated By: AMP module.
For Whom: Client Application.
Remedy: Rewind the import data to the beginning.

9584 Invalid derived period column definition.
Explanation: The columns participating in the derived period column must be identical date time columns with identical
format.
Generated By: RES modules
For Whom: The end user.
Remedy: Correct the statement and resubmit.

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

 

Teradata SQL Error and Failure Codes from Error 9555 To 9570

9555 Single-column PARTITION Statistics are recollected. It is recommanded to collect multicolumn PARTITION Statistics.
Explanation: Modifying partitioning expression invalidates the PARTITION statistics. Single-column partition statistics
is automatically recollected. It is recommended to recollect multicolumn partition statistics.
Generated By: OPD modules.
For Whom: End User.
Notes: This warning is issued when modifying partitioning expression having multicolumn PARTITION statistics.
Remedy: Recollect the multicolumn PARTITION statistics.

9556 Collect SUMMARY statistics natively on the target table.
Explanation: SUMMARY statistics saves some physical attributes of the table. It is recommended to collect SUMMARY
statistics natively on the target table.
Generated By: OPD modules.
For Whom: End User.
Notes: This warning is issued when SUMMARY statistics are copied between the tables.
Remedy: Collect SUMMARY statistisc natively on the target table.

9557 Collect or refresh single and multicolumn PARTITION Statistics.
Explanation: Modifying the partitioning expression invalidates the PARTITION statistics. It is recommended to collect
or recollect single-column and multicolumn PARTITION statistics after modifying the partitioning expression.
Generated By: OPD modules.
For Whom: End User.
Notes: This warning is issued when modifying partitioning expression either when no statistics are available or when
when multicolumn PARTITION statistics are available.
Remedy: Collect or recollect single and multi column PARTITION statistics.

9558 Row Level Security operations are not supported on this system.
Explanation: The Row Level Security feature is disabled and user attempted to access an RLS table created before the
feature was disabled.
Generated By: RES module.
For Whom: End User.
Remedy: Do not resubmit the request.

9559 Temporal operations are not supported on a table without a primary index.
Explanation: Temporal operations on a table without a primary index can be done only when EnableNoPITemporal flag
in the cost profile is set to 1.
Generated By: resnamtb.c.
For Whom: User.
Remedy: Set EnableNoPITemporal flag in the cost profile to 1 and re-submit the statement.

9560 Collect SUMMARY, single and multicolumn PARTITION statistics natively on the target table.
Explanation: SUMMARY statistics saves some physical attributes of the table. Also, copying PARTITION statistics
between the tables having different partitioning expression invalidates them. It is recommended to collect SUMMARY and
PARTITION statistics natively on the target table.
Generated By: OPD modules.
For Whom: End User.
Notes: This warning is issued when copying SUMMARY, single and/or multicolumn PARTITION statistics with different
partitioning expression.
Remedy: Collect SUMMARY, single and multicolumn PARTITION statistics natively on the target table.

9561 Collect single and multicolumn PARTITION statistics natively on the target table.
Explanation: Single column and/or multicolumn PARTITION statisitcs that are copied between tables having different
partitioning expression are not valid. It is recommended to collect these statistics natively on the target table.
Generated By: OPD modules.
For Whom: End User.
Notes: This warning is issued when copying single and/or multicolumn PARTITION statistics between tables with different
partitioning expression.
Remedy: Collect single and multicolumn PARTIITON statistics natively on the target table.

9562 Internal error has occurred. Query will be retried with the following parser diagnostics enabled: %$Enum:0=,65535=,=364,2%d%$Enum:0=,65535=,=,366,2%d%$Enum:0=,65535=,=,368,2%d%$En
um:0=,65535=,=,370,2%d%$Enum:0=,65535=,=,372,2%d.%$Enum:0=,65535= Diag:374,2%d%$Enum:0=,65535= after DiagCount:376,2%d
Explanation: This error is similar to a 3610 error except that it will be retried with parser diagnostics enabled.
Generated By: CON and PAR modules.
For Whom: End User, and System Support Representative.

9563 Insufficient memory to construct the XML for this request.
Explanation: The request required too much memory to construct internal XML structures.
Generated By: DOM modules.
For Whom: End User.
Remedy: Increase the DBS Control Performance field DBQLXMLPlanMemLimit.

9570 A constraint defined in the table is invalid.
Explanation: This can happen when a constraint is dropped or recreated after a table defined with the constraint is
archived. When the archived table is restored, the referenced constraint’s internal id is not associated with an existing constraint in DBC.SecConstraints.
Generated By: RES module.
For Whom: End User.
Remedy: The restored table is inaccessible because of a dropped or recreated constraint. Identify the constraint that was
dropped or recreated after the archive was taken. Drop the constraint column and add back the constraint if it was recreated, then resubmit the request. For further help, contact your Support Representative.

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

 

Teradata SQL Error and Failure Codes from Error 9543 To 9554

9543 Database SYSLIB or function SYSLIB.GetTimeZoneDisplacement does not exist.)
Explanation: Database SYSLIB or UDF SYSLIB.GetTimeZoneDisplacement does not exist. System/user timezonestring
is in effect and this object was found missing while resolving the timezone string.
Generated By: conlopa
For Whom: End User
Remedy: DBA should run dipdem to regenerate these objects.

9544 The ExportDefinitionName cannot be longer than %VSTR characters.
Explanation: The ExportDefinitionName is longer than permitted.
Generated By: OPD modules.
For Whom: User.
Remedy: Correct the Teradata SQL statemenet by using a valid ExportDefinitionName and resubmit the request.

9545 The ExportDefinitionName value must be a character string.
Explanation: The ExportDefinitionName value must be a character string.
Generated By: OPD modules.
For Whom: User.
Remedy: Use a character string for the ExportDefinitionName value.

9546 AT TIME ZONE is not a valid compile option for this ’%VSTR’.
Explanation: AT TIME ZONE clause is not allowed for compile of pre-14.0 SPs or for this application category of external
stored procedure.
Generated By: PAR module.
For Whom: End User.
Remedy: For pre-14.0 SPs, retry the alter procedure without the AT TIME ZONE clause first to recompile in the current
Teradata release and then resubmit with AT TIME ZONE clause.

9547 %VSTR can only be qualified by SYSUDTLIB/TD_SYSFNLIB.
Explanation: When algorithmic compression clause is specified for a column, the compress/decompress UDFs cannot
be qualified by other than SYSUDTLIB/TD_SYSFNLIB.
Generated By: RES.
For Whom: End User.
Remedy: Use only SYSUDTLIB/TD_SYSFNLIB as qualifier for Compress/Decompress UDFs.

9548 Source rows did not include all constraint columns in the source table.
Explanation: A MERGE-INTO or INSERT-SELECT statement involved a view or derived table that did not include all
constraint columns in the source table.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

9550 There are no statistics defined for the table.
Explanation: There are no statistics defined for the source table referenced in a Create Table as .. with data and statistics statement.
Generated By: OPD modules.
For Whom: End User.
Notes: This warning is issued when the statistics are requested to be copied but no statistics are available on the source table.
Remedy: Resubmit the statement without the copy statistics option (WITH STATISTICS).

9551 A left open monitor resource was detected by parser when parsing a SQL request.
Explanation: The event message documents a left open monitor detected when parsing a request.
Generated By: PARSER .
For Whom: System Support Representative.
Remedy: Contact your support representative.

9552 statistics cache hit ratio is lower than the threshold set in dbs control internal field.
Explanation: Statistics cache hit ratio is lower than the threshold. Please consider increasing the number of segments in
the statisitics cache.
Generated By: opt module.
For Whom: System Support Representative.
Remedy: Increase the number of segments in the statisitics cache.

9553 Cannot create/replace UDF/UDT with the current character set.
Explanation: MBC UDFs/UDTs are currently existing on the system. Users must use a character set that can accomodate
all existing MBC UDFs/UDTs to create/replace this UDF/UDT.
Generated By: mgcudfids.c.
For Whom: User.
Remedy: Re-submit the statement with an appropriate character set.

9554 Warning: Invalid join index is found.
Explanation: A join index is invalid because a UDF/UDM it refers to has been dropped.
Generated By: OPT modules.
For Whom: The DBA and the System Support Representative.
Notes: This warning is issued when a join index is no longer valid due to non-existent UDFs/UDMs referenced by the
join index(es).
Remedy: Drop the invalid join index.

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

 

Teradata SQL Error and Failure Codes from Error 9500 To 9542

9500 A CDT Index error occured. %VSTR
Explanation: This error is reported if an error occured with a CDT index. See the individual error message for details.
Generated By: PAR module.
For Whom: End User.
Remedy: See individual text.

9514 Cannot Proceed with DBC Restore, DBC Logons are not enabled.
Explanation: During a Full DBC Restore operation, DBC Logons should be enabled as enabling all logons causes restart
when other users try to logon. So report an error if DBC Logons are not enabled before starting the DBC Restore and abort
the restore operation. DBC user has to enable the DBC logons and logoff the users other than DBC and should start the
DBC Restore again.
Generated By: OPT modules.
For Whom: End User.
Remedy: DBC user has to Disable the logons except DBC and logoff all the users other then DBC and start the Restore
process again. Also, DBC Logons should be kept enabled until DBC Restore is complted.

9531 Override Select Constraint privileges are required for this operation.
Explanation: Override Select Constraint privileges on both the target and save tables are required for altering the partitioned
primary index of a protected table.
Generated By: RES module.
For Whom: User.
Remedy: Obtain the required privileges before re-submitting the

9532 Target and save tables do not have identical security constraints.
Explanation: The table being altered is a protected table And the save table is not created with the same constraints
defined in the target table.
Generated By: RES module.
For Whom: End User.
Remedy: Re-create the save table with the constraints

9533 The revoke statement is illegal.
Explanation: The user is trying to revoke either a) an Override Constraint privilege on a table that is not protected, or b)
a RLS privilege from PUBLIC. RLS privileges cannot be granted to PUBLIC.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

9534 The NO RLS option is applicable to creating an error table for a protected table only.
Explanation: When the NO RLS clause is specified, an unprotected error table will be created for a protected data table.
It is illegal to specify the clause if the data table is not protected.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

9536 RANGE_N defines more than %VSTR result values.
Explanation: A RANGE_N function with INTEGER data type must not define more than 2147483647 result values
(including all the ranges, and the NO RANGE, UNKNOWN, and NO RANGE OR UNKNOWN options if specified). In
this case, the value for VSTR is “2147483647”.
A RANGE_N function with BIGINT data type must not define more than 9223372036854775807 result values (including all
the ranges, and the NO RANGE, UNKNOWN, and NO RANGE OR UNKNOWN options if specified). In this case, the
value for VSTR is “9223372036854775807”.
Generated By: OPT modules.
For Whom: End User.
Remedy: Examine the RANGE_N function invocation and verify that it is correct. Modify the arguments to the
RANGE_N such that maximum result value does not exceed the limit.

9540 The ExportDefinitionName ’%VSTR’ does not exist.
Explanation: The user referred to an ExportDefinitionName as %VSTR that does not exist in DBC.ExportWidth table.
Generated By: OPD modules.
For Whom: User.
Remedy: Correct the Teradata SQL statemenet by using a valid ExportDefinitionName and resubmit the request.

9541 Diagnostic REWRITEQRY that returns rewritten text is applied on this query.
Explanation: This is a warning message and not an error. This warning code means that the the query is rewritten and
the rewritten text is sent back.
Generated By: PAR modules.
For Whom: End user.
Remedy: Not an error. This message is for information only.

9542 A security constraint with the name “%VSTR” already exists.
Explanation: This error is displayed when the user tried to create an UDT which has the same name as an existing security
constraint.
Generated By: Resolver
For Whom: End User
Remedy: Examine the Teradata SQL statement and verify that the request is correct. Change the statement to specify a
different name and resubmit the request.

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

 
1 2 3 4 5 50