Teradata SQL Error and Failure Codes from Error 6194 To 6605

SQLServerF1_Header_Small

6194 The fallback subtables from 9 to 16 must be available for online reconfig.
Explanation: This error occurs if the system has added or modified the existing clusters when running online reconfig.
Thus, during redistribution, backupid array doesn’t have enought room to store the subtable during online reconfig.
Generated By: RCOckfig and figccfg.
For Whom: End User.
Remedy: With is configuration it can not run online reconfig at all.

6195 %$DateTime Reconfig Aborted by User.
Explanation: This error occurs if user wants to Abort Reconfig.
Generated By: RCOAbort.
For Whom: End User.
Remedy: Start reconfig again after initializing new amps vprocs.

6196 Reconfig online deletion finished.
Explanation: This message is displayed when the reconfiguration process online deletion completes.
Generated By: RCORESUME.
For Whom: End User.
Remedy: None.

6197 Reconfig Abort is disabled.
Explanation: This error occurs if abort for reconfig is disabled for the system.
Generated By: RCOSvc.
For Whom: End User.
Remedy: Contact support representative.

6198 Neither Move, Modify nor Add AMP changes are allowed for existing clusters during online reconfig.
Explanation: This error occurs when any AMPs in an existing cluster are moved, modified, or added during online
reconfig.
Generated By: RCOSvc.
For Whom: End User.
Remedy: Check the Teradata Database Current and New configurations to ensure that no AMPs are to be moved, modified
or added to an existing cluster during online reconfig. If such changes are required to reach the desired new configuration,
run reconfig offline.

6199 Adding to or modifying an AMP in an existing cluster is not allowed during online reconfig.
Explanation: This error occurs when any AMPs in an existing cluster are added to or modified during online reconfig.
Generated By: RCOSvc.
For Whom: End User.
Remedy: Check the the Teradata Database Current and New configurations to ensure that no AMPs are added or modified
for any existing cluster during online reconfig. If such changes are required to reach the desired new configuration, run
reconfig offline.

6200 The Move AMP operation is not permitted during online reconfig.
Explanation: This error occurs if a reconfiguration specifies a Move AMP operation and reconfig is running online.
Generated By: RCOSvc.
For Whom: End User.
Remedy: Check the Current and New configurations to ensure that no AMPs are moved during online reconfig. If moving
some AMPs is necessary to create the desired new configuration, run reconfig offline.

6600 Memory use to keep track of transactions has been exhausted.
Explanation: In order to process an transactions a certain amount of heap memory is needed. This for transaction context
and change row storage.
Generated By: Replication Services Call Interface (RCI)
For Whom: RSG (Relay Services Gateway)
Remedy: It could be as a result of send change rows out of order to the call interface. The worst case scenario being never
seeing the first change row for a transaction. Send the change rows in order and make sure that none are missing.

6601 There was a parameter error in the procedure call
Explanation: One of the Parameters in the RCI call interface was wrong or inconsistent.
Generated By: Replication Services Call Interface (RCI)
For Whom: RSG (Relay Services Gateway)
Remedy: Fix the problem in the interface.

6602 The batch is busy, it cannot execute the request
Explanation: A RCI request asked that an operation be performed for a particular asynchronous batch that is currently
busy doing other things such as applying transactions.
Generated By: Replication Services Call Interface (RCI)
For Whom: RSG (Relay Services Gateway)

6603 An operation was requested on a batch that does not exist
Explanation: A RCI request asked for an operation on a asynchronous batch that does not exist. A Start Batch request
must always precede any other batch operation.
Generated By: rcibegintransaction module.
For Whom: RSG (Relay Services Gateway)

6604 A changed data row was received that whose contents are in error
Explanation: A changed data row had one on many possible problems: 1. Invalid transaction ID or one not known
about. 2. Invalid session/host number or one not known about. 3. A row sequence number that has already been seen. 4. A
length field that is zero.
Generated By: Replication Services Call Interface (RCI)
For Whom: RSG (Relay Services Gateway)

6605 A operation was attempted that made no sense given the current state
Explanation: This is primarily the result of requesting that an operation be performed the is not following the proper
protocol. Some examples are: 1. Clean batch that is not in correct state (crash state or or done). 2. Asking for a commit
sequence number for a batch not in crash state. 3. Sending change rows to a transaction that is not in the correct state. 4.Executing control messages out of sequence or inappropriately for a transaction and example would be requesting a
request abort for an asynchronous transaction.
Generated By: Replication Services Call Interface (RCI)
For Whom: RSG (Relay Services Gateway)

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