Teradata SQL Error and Failure Codes from Error 7893 To 7904

SQLServerF1_Header_Small

7893 Object %VSTR does not exist in Glop_Set table.
Explanation: The error message is generated if glop set name does not exist in DBCExtension.Glop_Set table.
Generated By: Glop SPs
For Whom: End User.
Remedy: Correct the Set_Name parameter and resubmit the request.

7894 %VSTR glop does not exist in GLOP set.
Explanation: The error message is generated if Type_g glop does not exist in glop set.
Generated By: Glop SPs
For Whom: End User.
Remedy: Correct the Type_g parameter and resubmit the request.

7895 User %VSTR must be the creator or owner of the glop set %FSTR.
Explanation: The error message is generated if the current user is not the creator or owner of the glop set.
Generated By: Glop SPs
For Whom: End User.
Remedy: Correct the request and resubmit.

7896 GLOP parameter %VSTR value invalid in table input mode.
Explanation: The error message is generated if Set_Name or Type_g parameter value in table input mode is invalid.
Generated By: Glop SPs
For Whom: End User.
Remedy: Correct the parameter value and resubmit the request.

7897 No rows found in %VSTR.
Explanation: The error message is generated if there are no rows in the table given in table input mode.
Generated By: Glop SPs
For Whom: End User.
Remedy: Make sure there are rows in table and resubmit the request.

7898 Data must exist for a read only GLOP.
Explanation: The error message is generated if NULL data is passed for ’R/W’ or ’M’ glops and Length is supplied as -1.
Generated By: Glop SPs
For Whom: End User.
Remedy: Correct the parameter value and resubmit the request.

7899 Circular Dependencies are not allowed.
Explanation: The error message is generated if calling Glop_Change SP resulted in circular dependency in a glop set.
Generated By: Glop SPs
For Whom: End User.
Remedy: Make sure that Glop_Change SP call does not result in circular dependency and resubmit the request.

7900 Cost profile name not in data dictionary.
Explanation: Cost profile name used to access OCES data dictionary tables is not in the database
Generated By: OCES cost profile access routines
For Whom: System Administrator
Remedy: Correct source of the missing name or create a profile with that name.

7901 Cost profile Id value not in data dictionary.
Explanation: Cost profile Id. number used to access OCES data dictionary tables is not in the database
Generated By: OCES cost profile access routines
For Whom: System Administrator
Remedy: Correct source of missing Id. value or create a profile with that Id.

7902 Internal error: Cost profile type name not in data dictionary.
Explanation: Cost profile type name used to access OCES data dictionary tables is not in the database
Generated By: Not currently used
For Whom: Internal
Remedy: Diagnose how invalid profile type name value was established. If incorrect in data dictionary, then fix it there
and in any scripts that may have generated it.

7903 Internal error: Cost profile type Id. not in data dictionary.
Explanation: Cost profile type Id. used to access OCES data dictionary tables is not in the database
Generated By: OCES management routines
For Whom: Internal
Remedy: Diagnose how invalid profile type id value was established. If incorrect in data dictionary, then fix it there and in any scripts that may have generated it.

7904 Internal error: OCES startup error.
Explanation: OCES start-of-day initialization error
Generated By: Not currently used
For Whom: Internal
Remedy: Save relevant information and the dump, and contact your support representative

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