Teradata SQL Error and Failure Codes from Error 3608 To 3611
3608 Not enough values in a subquery.
Explanation: The user specified a subquery in a set conditional. The subquery specified fewer values than are specified
in the conditional.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the conditional and resubmit request.
3609 Excessively complex set conditional.
Explanation: Because too many conjunctions (that is, ORs) of set operations would have caused incorrect results, the
SELECT statement was not carried out.
Generated By: OPT modules.
For Whom: End User.
Remedy: Separate the operation into separate SELECT statements or rephrase the request.
3610 Internal error: Please do not resubmit the last request. SubCode, CrashCode: %VSTR
Explanation: Because of an internal problem, the PE has decided to take a Snapshot dump, and abort the given request.
This is done instead of restarting the system.
Generated By: CON and PAR modules.
For Whom: End User, and System Support Representative.
Notes: The variable portion of this message may contain up to three different pieces of information about the nature of
the failure: a) A subcode which can be used to identify the routine which flagged the error. This will be zero if this error was
originally flagged with an error code other than 3610, in which case examine b) the crashcode, which indicates the original
error number used to flag the error. If this is zero, it just means that the original error designation was 3610. c) The TSET
row ID, preceded by a string reading “Failing query available in TSETQueryText table with row identifier ”
This information will be included when TSET information has been successfully collected about the failed query. This information
can be forwarded to support representatives to assist in reproducing the failure.
TSETQueryText is a globally available system table that is created in DBC at system initialization (DIP) time. The row contains
the following fields: QueryID (an internally generated unique (within the database) integer identifier for the failing
ErrorCode (an integer showing the internally generated DBS error code, 3610 for the initial release),
QueryTime (a timestamp of when the query was inserted into TSETQueryText),
Handled (a boolean denoting if TSET has been executed for this query), and
QueryText (the text of the failing query which caused the 3610 error).
If a backtrace is available, find the function that called pardie. If this function is on the list below, the probable reason for the
internal problem is given. If the function is not on the list, it is probable that pardie itself has generated the ERRTEQIFPDIE
error. The numbering of the entries in this list corresponds to the SubCode given in the message text.
1: ctxlopa.c: conlopa 1) request number out of sequence
2: ctxpmpc.c: congtabt 1) confiabt returned bad outcome
3: ctxpmpc.c: consnabt 1) parameter AbtCtx equal to zero
4: ctxrbm.c: conrbm 1) request number out of sequence
5: ctxstop.c: SetAbortFlag 1) message class is not equal to SYSMSGDABCLASS, 2) message kind is not equal to DABCONABTRSPMSGKIND
6: ctxtsk.c: DoExeAbtOrBulkEnd 1) conftabt returned a zero value, 2) session is not properly quiesced, 3) there is a queued
request for a parsing session during an abort
7: ctxtsk.c: ProcessRestart 1) a session in the incoming list is not in the session context
8: gncalloc.c: gnccopyalloc 1) the parameter Start specifies an invalid pstep segment location
9: gncapply.c: Run_EvlMach_R 1) PPI row is being processed but the partition is 0
10: gnccond.c: gnccond 1) the two operands on the evl stack have different scales
11: gncgtspl.c: gncgtspl 1) spool list is exhausted and spool cannot be allocated
12: gncvtutl.c: gncvtid 1) cannot find a free spool number
13: gnsmtb.c: GenPPIDesc 1) unable to get the ParIndexSpec node for the Primary Index
14: mgcexprq.c: mgcexpallamp 1) parameter Expkind needs to be equal to EXPRERXMSG or to EXPFTHMSG
15: mgctabhd.c: CopyIndexID 1) unable to get address to Faked Index List, 2) unable to match DupID
16: mgcudfspl.c: ExpReqASF 1) unable to discard a segment
17: opdcheck.c: SetThemUp 1) parameter ModtabPtr->Kind is required to be equal to ParModTab or ParTabRef
18: opdct.c: DoPPI 1) LastPartNoPtr for ParRange equals NIL
19: opdct.c: opdct 1) unable to update original create table statement with partitioning expression because of unsuccessful
outcome from pardtree, 2) pardtree is unable to translate the ParCheckSpec tree into text
20: opdgrant.c: AddRight 1) an unknown Access right is being added
21: opdmodpi.c: DropUSI 1) initial node kind in StmtList is ParMVN
22: opdmodpi.c: getExtPartNo 1) field 5 of the table header is Null
23: opdmodpi.c: PartList2Cond 1) invalid node type passed as parameter
24: opd/opdmodpi.c: alterRange2Cond 1) invalid node type passed as parameter
25: opd/opdmodpi.c: splitRange 1) the number of partitions in the new range is greater than or equal to the number of partitions
in the old range, 2) unable to copy tree
26: opdmodpi.c: partList2DropList 1) invalid node kind passed as a parameter, 2) range node kind is not ParRange_NCond
27: opdmodpi.c: reworkDropList 1) getPartsToDrop returned NIL, 2) partList2Drop returned NIL
28: opdmodpi.c: makePartitionInclList 1) invalid node kind passed as a parameter
29: opdmodpi.c: makePartSpool 1) invalid node kind passed as a parameter
30: opdmodpi.c: editAsgnList 1) invalid node kind passed as a parameter
31: opdmodpi.c: ModPICols 1) NIL pointer passed as parameter
32: opdmodpi.c: ModPIUnique 1) NIL pointer passed as parameter
33: opdmodpi.c: ModPIName 1) NIL pointer passed as parameter
34: opdmodpi.c: makeImplicitConstraint 1) pardtree is unable to convert the checkCond tree to text
35: opdmodpi.c: Range_NAllInclusive 1) invalid node kind passed as a parameter
36: opdmodpi.c: ModPartExpr 1) last partition number pointer is NIL
37: opdmodpi.c: MultiOptionAnalysis 1) primary index specification pointer is NIL
38: opdmodpi.c: opdmodpi 1) primary index pointer is NIL
39: opdrevalpi.c: GetSpool1AsgnList 1) spool assign list pointer is NIL40: opdrevalpi.c GetDestSpoolAsgnList 1) destination spool assign list pointer is NIL
41: opdrevalpi.c: opdrevalpi 1) revalidate primary index pointer is NIL
42: opdrevok.c AddRight 1) unexpected access right
43: optcommon.c: OptGetFids 1) attempt to write beyond the bounds of the Fids array
44: optdump.c:misc: LockPmaGdo 1) unexpected error while placing a lock on the gdo, 2) unable to allocate memory, 3)
unable to read the gdo
45: optdump.c:misc: LockVconGdo 1) unexpected error while placing a lock on the gdo, 2) unable to allocate memory, 3)
unable to read the gdo
46: optdump.c:misc: LockTctrlGdo 1) unexpected error while placing a lock on the gdo, 2) unable to allocate memory, 3)
unable to read the gdo
47: optdump.c:misc: LockCtrlGdo 1) unexpected error while placing a lock on the gdo, 2) unable to allocate memory, 3)
unable to read the gdo
48: optindex.c: MergeQryConfig 1) unable to locate the TableInQry level info pointer
49: optindex.c: FindConflict 1) unable to local the TableInQry level info pointer
50: optinss.c: CheckGeog 1) unable to find source table
51: opuppi.c: opuppi123 1) node kind is not ParData
52: parcapt.c: CaptureIndexTable 1) unable to find the IndexInfo entry using the tableid
53: parcnvu.c: parcnvu 1) unable to discard a segment
54: pardie.c: pardie 1) error while inside a logmark
55: pardrivr.c: Process_MultiTsrMsg 1) unable to open file to write the multitsr messages 2) unable to open file to write the
original MDS request text
56: parexpl.c: Scan 1) unable to obtain the total number of partitions for the table, 2) unexpected partition list kind
57: parnodeinit.c: getgdoptr 1) unable to obtain pointer to resident gdo, 2) resident gdo is empty
58: parnodeinit.c: Nodeinit_PE 1) PE is in PROCHOLD status but tpastate is SYSLOGON, 2) unable to obtain tosvpr index,
3) PE node map failed sanity check
59: parnodeinit.c: parnodecascinit 1) unable to compute the root PE for this node
60: parrcfindentry.c: FindEntry 1) unexpected kind of parcel in the request
61: resname.c: Add_AltAuthorization 1) node kind is required to be either ParCollStat or ParDropStat, 2) authorization list
62: resname.c: SCAN 1) node kind is required to be either ParUDF or ParCast
63: resri.c: resri 1) unexpected statement kind
64: opdudtddl.c: UdtCastPdtFields 1) The DataDesPtr parameter is NULL, or is not of Kind ParDataDesc
65: opdudtddl.c: InsertUdtCast 1) The CastPtr is NULL or contains a NULL ptr
66: opdudtddl.c: opdudtcrcast 1) The first statement in the statement list parameter is NULL, 2) The statement kind is neither
Create nor Replace Cast, 3) No Cast Ptr was found, 4) No Source Ptr, Target Ptr, or Cast Routine Ptr was found in the
Cast node, 5) No Cast Routine TabRef Ptr was found, 6) The CastRoutine Kind is neither ParUDF nor ParUdtLocal, 7) The
DB Ref Ptr could not be assigned
67: opdudtddl.c: opdudtdropcast 1) The DropCast node did not contain a Cast Ptr, 2) The Cast Node had neither a Source
nor a Target Pointer, 3) A DB Ref could not be set up
68: opdudtddl.c: opdudthelpcast 1) This stub function was called 69: opdudtddl.c: opdudtcrorder 1) The statement in the statement list was not of type ParUdtCrOrder or ParUdtReplaceOrder,
2) OrderPtr was NULL, 3) The Order node contained a NULL ptr, 3) the Order Routine is of type ParUDF but no
TabRef was associated with it, 4) the OrderFormChar was not equivalent to EQUALS or FULL 5) the OrderCategoryChar
was notequivalent to MAP or RELATIVE, 6) The OrderRoutine kind was not ParUDF or ParUdtLocal
70: opdudtddl.c: opdudtdroporder 1) The statement list was empty, 2) The DropOrder node had a NULL UdtPtr
71: opdudtddl.c: opdudtcrtrans 1) The statement kind is not ParUdtCrTrans or ParUdtReplaceTrans, 2) From-
SQLPtr/ToSQLPtr is of Kind ParUDF, but does not contain either UDFNamePtr or UDFSpecificNamePtr **DR97993-
72: opdudtddl.c: opdudtdroptrans 1) The statement list was empty, 2) The DropTrans node had a NULL Trans Ptr, 3) the
Trans node contained a NULL ptr, 4) The TransGrp node had a null TransGrpNamePtr
73: resudthelpshow.c: GetPreDef 1) Control returned unexpectedly to the routine after calling ReleaseAllFlSpec
74: resudthelpshow.c: resudthelptrans the TypeKind of the UdtSpecPtr was not MgcInternal, MgcDistinct, or MgcStructured
75: resudthelpshow.c: resudthelpcast 1) this stub function was called inappropriately, 2) a name was longer than SYSMAXNAME
76: resnamtb.c: CheckPPIPartExpr 1) PPICheckSpecPtr was NULL, 2) the black Partition By Expression was NULL
77: resname2.c: ResolvePrivList: 1) Kind was not ParTabRef or ParDBRef, 2) The ParNot was not previously converted, 3)
The TVMPtr passed in through the LINK was NULL
78: resname2.c: Handle_UdtCast 1) The tree node kind was not ParUdtCrCast, ParUdtReplaceCast, or ParUdtDropCast, 2)
The CastPtr was NULL 3) The Source, Target, or CastRoutine pointer was NULL, 4) The pointer to the CastRoutine Kind
was NULL, 5) a non-specific User-Defined Method was specified in the DDL, but the associated User-Defined Type was not
specified, 6) neither a User-Defined Function Name or User-Defined Function Specific Name pointer was defined, 7) No
Table Reference node was found for the Source or Target
79: resname2.c: Handle_UdtDropOrdering 1) The tree node has a NULL UDT pointer
80: resname2.c: Handle_UdtOrdering 1) The tree node kind was not ParUdtCrOrder, ParUdtReplaceOrder or ParUdtDropOrder,
2) the pointer to the Order node was NULL, 3) One of the expected subnode pointers of the Order node was NULL,
4) the UDFKind pointer in the OrderRoutine node was NULL, 5) A non-specific User-Defined Method is specified in the
DDL, but no associated type is specified, 6) the Order Routine node is of type ParUDF, but neither a UDFNamePtr or UDFSpecificNamePtr
is in the ParUDF node
81: resname2.c: Handle_UdtDropTransform 1) the tree node has a null TransPtr, 2) the Trans node has a NULL UdtPtr or
NULL TransGrpPtr, 3) the TransGrpNamePtr was NULL
82: resname2: Handle_UdtTransform 1) the tree node is not of kind ParUdtCrTrans, ParUdtReplaceTrans, or ParUdtDrop-
Trans, 2) a NULL TransPtr was found, 3) either UdtPtr or TransGrpPtr was NULL in the Trans node, 4) no FromKind
pointer was found in a From node, 5) no ToKind pointer was found in a To node, 6) a non-specific User-Defined Method
was specified in the DDL but no associated User-Defined Type was specified, 7) the From node contained neither a UDF
Name pointer nor a UDF Specific Name pointer, 8) the To node contained neither a UDF Name pointer nor a UDF Specific
83: opdcredb.c: Do_Dbase 1)Variable PWUpperLower has an illegal value (ex. MIXEDCASEPWDNOTALLOWED)
84: opdmoddb.c: Do_Dbase 1)Variable PWUpperLower has an illegal value (ex. MIXEDCASEPWDNOTALLOWED)
85: resname2.c: Handle_JARs 1) ExtRefPtr of ParInstJar, ParRplcJar must never be NULL 2) DBRefPtr of ParInstJar.JarPtr,
ParRplcJar.JarPtr must never be NULL 3) UpdateFromUsingRow: return value of GetUsingData must always be a ParTree
of Kind ParData 4) Repr.kind of ParData tree returned from GetUsingData may only be EVLCHARFIX or EVLCHARVAR
86: resname.c: BuildValueString function for array constructor 1) encountered a type for which there is no handling coded 101: parerr: The error-handling routine parerr() was sent the ERRTEQIFPDIE code, which it passes on to pardie(). Many,
but not all of these errors come from gncapply() or optdump(). The stack backtrace in the event log will provide more detailon where the initial error detection occurred.
Remedy: Save a test case, and contact your support representative for an analysis of the dump.
If the TSET row ID is available, Support should recreate the conditions prevailing when the query was submitted using the TSET information, and duplicate the problem, enabling eventual resolution.
3611 A crash dump could not be saved.
Explanation: A Teradata crash dump could not be saved in a table. The error that occurred while trying to save the crash
dump is displayed with this entry.
Generated By: SEM modules.
For Whom: The DBA and the System Support Representative.
Notes: The dump area is not cleared if it cannot be saved.
If the reason the crash dump cannot be saved is “2644: No more room in the database”, the save will be tried again in one
hour. Clear out old crash dumps, or give the database more PERMANENT space.
Remedy: The remedy depends on the reason listed with this error. Make sure DIP has been run on this system.
Above are list of Teradata Errors or Failure Codes from Error 3608 To 3611 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.
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.