Teradata SQL Error and Failure Codes from Error 2958 To 2968

2958 Processor is looping in TOS initialization.
Explanation: A processor is hung in TOS (the startup task was not started or the global TN2 was not set busy).
Generated By: SSSMain.
For Whom: End User. Site support representative.
Notes: This is normally caused by a processor being halted during the startup sequence by the debugger, by an invalid
version record, or by malfunctioning hardware.
Remedy: If none of these is the cause, leave the processor off-line and start up the remainder of the system.

2959 Cannot install CharSet: With International Hash Function
Explanation: The CharSet is one of the special MBCS character sets defined in the system table DBC.Translation. This
error means that an attempt was made to install a CharSet on a DBC with the International Hash Function.
Generated By: SSSMain (System startup)
For Whom: DBA Site support representative
Notes: When this error occurs during normal system startup, the error message logged on the console will identify the
name of the CharSet.
Remedy: Remove the International Hash Function from the DBC.

2960 Invalid sequence of startup messages.
Explanation: There is an error in the sequence of startup messages received by a processor.
Generated By: SSSMain.
For Whom: Site support representative.
Notes: This is an internal error that should never occur.
Remedy: Contact your Support Representative.

2961 Processor must remain off-line.
Explanation: The processor must remain off-line and not participate in the configuration.
Generated By: SSSMain.
For Whom: Internal.
Notes: This is an internal error to inform other software procedures that the processor is in an off-line state.
Remedy: None needed.

2962 Configuration is not operational.
Explanation: The current configuration is not operational because a cluster has more than one AMP unavailable.
Generated By: SSSMain.
For Whom: Internal.
Notes: This is an internal error to inform other software procedures that the processor is in an off-line state.
Remedy: None needed.

2963 Processor has changed types.
Explanation: A processor already in the configuration has changed its type (from PE to AMP, or vice versa).
Generated By: SSSMain.
For Whom: End User. Site support representative.
Notes: Either the Configuration utility was given wrong information regarding the type of processor in that processor
slot, or the correct board type has been removed and a different type of board has been inserted into that slot.
Remedy: Change the board in the processor slot. Then, if necessary, correctly define the board type for this slot using the
Configuration and Reconfiguration utilities.

2964 Duplicate processor cabinet ids.
Explanation: There are duplicate processor ids in the configuration.
Generated By: SSSMain.
For Whom: End User. Site support representative.
Notes: Two processor cabinets have the same setting in their cabinet identifiers.
Remedy: Change the identifier on one cabinet.

2966 Invalid configuration map version.
Explanation: The two version numbers in the configuration map are not equal.
Generated By: SSSConfg.
For Whom: Site support representative.
Notes: The configuration map has somehow been overwritten.
Remedy: Restore the configuration map from a backup copy in /var/ns/bkup.

2967 Invalid configuration map.
Explanation: The configuration map returned from one or more nodes during startup is not valid.
Generated By: SSSMain
For Whom: Site support representative.
Notes: The configuration map has either an invalid version, length, etc..
Remedy: None. DBS startup will select the best config map available.

2968 Release call issued for blocked transaction.
Explanation: A lock release call was issued for a task that was blocked waiting for a lock.
Generated By: LokRelse.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

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