Teradata SQL Error and Failure Codes from Error 9572 To 9584

SQLServerF1_Header_Small

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.

 

Leave a Reply

Your email address will not be published. Required fields are marked *