Teradata Database Errors

Teradata Database Errors starting with: errors 79*

Errors starting with: errors 79*

change error category

errors 79*

Teradata error 7900 Cost profile name not in data dictionary.

Teradata error 7901 Cost profile Id value not in data dictionary.

Teradata error 7902 Internal error: Cost profile type name not in data dictionary.

Teradata error 7903 Internal error: Cost profile type Id. not in data dictionary.

Teradata error 7904 Internal error: OCES startup error.

Teradata error 7905 Internal error: OCES session initialization error.

Teradata error 7906 Internal error: OCES fatal error.

Teradata error 7907 Spool tables contained %VSTR rows with compressed values.

Teradata error 7908 Cost profile name in user profile was not found; ignored.

Teradata error 7934 Assertion failed at %VSTR.

Teradata error 7947 Only create/replace procedure allowed.

Teradata error 7948 A significant part of the password submitted contains a restricted word.

Teradata error 7960 Role(s) cannot be revoked from user DBC.

Teradata error 7961 A triggered stored procedure can not contain BT, ET or COMMIT statements.

Teradata error 7962 Java XSP and UDF is disabled because %VSTR.

Teradata error 7963 The statement is not eligible to return a result set.

Teradata error 7965 JAR file %VSTR either is corrupted, has invalid format, or uses absolute paths for its

Teradata error 7967 %VSTR is not a Jar.

Teradata error 7968 The recipient of the result set does not support dynamic result sets.

Teradata error 7969 Invalid external name string option specified for Java XSP/UDF ’%FSTR’ because %VSTR.

Teradata error 7970 Create/Replace Java XSP/UDF passed an unacceptable signature. Correct the signature.

Teradata error 7971 Jar %VSTR already exists

Teradata error 7972 Jar %VSTR does not exist.

Teradata error 7973 Invalid locspec option specified for JAR file %VSTR.

Teradata error 7974 The privilege is not applicable to a Jar.

Teradata error 7975 Can not execute XSP/UDF %VSTR. Java Language is not supported on the system.

Teradata error 7976 Can not execute XSP/UDF %VSTR. Java Language is not supported on the system hardware

Teradata error 7978 Can not execute XSP/UDF %VSTR. Java Language is not supported for non-protected

Teradata error 7980 A JAVA method in the specified Jar which matches that in the EXTERNAL NAME clause was

Teradata error 7981 Reference to JAR %VSTR is not allowed in this context.

Teradata error 7982 %VSTR operation is not allowed on a JAR.

Teradata error 7983 XSP %VSTR does not exist in the SQLJ database.

Teradata error 7984 Maximum number of Java XSPs/UDFs referencing one Jar has been exceeded.

Teradata error 7985 Diagnostic BYPASS ACCESSRIGHTS not allowed if multiple users logged on.

Teradata error 7986 Diagnostic BYPASS ACCESSRIGHTS not allowed if logons are enabled.

Teradata error 7987 Internal Error: Assertion violated in Optimizer

Teradata error 7988 Internal Info: Assertion violated in Optimizer

Teradata error 7989 Invalid operand for the %VSTR operator. The operand must have a Period data type that is

Teradata error 7990 Invalid operands for the %VSTR operator. The operands must have comparable Period data

Teradata error 7991 Invalid Period argument. Passing an argument corresponding to a parameter with lower

Teradata error 7992 Invalid input data for period. The beginning bound must be less than the ending bound.

Teradata error 7993 Invalid input data for period. The input data precision must not be greater than the described

Teradata error 7994 Invalid Period arithmetic operation. One of the operands must be an Interval type.

More informatoin

Teradata error TPT2930 Error: text buffer is NULL

Teradata error 3762 Lock object must be TABLE in FOR CHECKSUM locking modifier.

Teradata error 9620 End of file encountered in the row-column subsystem.

Teradata error SIGNAL/RESIGNAL statement.

Teradata error TDP0308 COMMAND AUTHORITY FOR: ..., IS: ....

Teradata error 218 EM_BREAK Break was hit.

Teradata error TPT2932 Error: %s near line %d (text was ’%s’)

Teradata error 31 Invalid Supplemental Format Information

Teradata error TPT3590 Error: in PERIOD datatype. Length specified must be a value between 0-6.

Teradata error 6191 Changing PE(s) is only allowed during offline reconfig.



Teradata Database Errors