Teradata SQL Error and Failure Codes from Error 3032 To 3042

SQLServerF1_Header_Small

3032 User password has expired.
Explanation: If this is a warning, then the user has successfully logged on with an expired password. The only command
that will be accepted in this session is the one to assign a new password.
If this is an error, then the same user is logging on or has logged on to the DBC from another session.
Generated By: Session Control.
For Whom: End User.
Notes: This warning, or error, is returned when the current date is greater than or equal to the password change date plus
the security defaults password expiration interval or immediately after a user has been created or immediately after the 5.0
dictionary conversion utility has been run.
Remedy: Change your password with the DBC/SQL statement: MODIFY USER <username> AS PASSWORD =
<name>.

3033 Invalid partition with expired password.
Explanation: The user has logged on with an expired password and is executing a utility or program which does not
have the ability to change the users password.
Generated By: Session Control.
For Whom: End User.
Notes: This requirement exists because the only command which can be entered after an expired password logon is the
DBC/SQL statement: MODIFY USER <username> AS PASSWORD = <name>.
Remedy: Use a utility such as BTEQ or ITEQ to change the users password and then the utility or program may be executed.

3034 User Id is locked from further logon attempts.
Explanation: The number of logon attempts with an invalid password on the user ID has exceeded the site defined maximum
logon attempts.
Generated By: Session Control.
For Whom: End User.
Notes: A user Id which has becomed locked will remain so until either a system time limit (site defined) has expired or
the system administrator unlocks the user Id. The Id can be unlocked by submitting the following DBCSQL statement:
MODIFY USER user-name AS RELEASE PASSWORD LOCK;
Remedy: Check with your system administrator.

3035 DBC.Sessiontbl is corrupted, session cannot be recovered.
Explanation: During system recovery, session logged on prior to the restart is restored from the DBC.SessionTbl. The
session control detects a BAD row and it cannot restore the session to it original state. The session control forces to delete
the row from the DBC.SessionTbl.
Generated By: Session Control.
For Whom: Support Representative.
Notes: This error is returned by an internal consistency check.
Remedy: Relogon the session.

3036 The logged on user name is longer then 30 bytes.
Explanation: The request was made to return the logged on user name in 30 bytes or less. The error is returned because
the name is longer than 30 bytes.
Generated By: SesLogon.
For Whom: Support Representative.
Remedy: Enable the Extended Object Name facility in the client sofware.

3037 A role, profile, or authentication string is too long.
Explanation: An attemp was made to log on using a string which is longer than expected. The strings which could be too
long include:
audit trail identifier authentication user identifier, authentication mechanism object identifier, authentication mechanism
data, profile name, role name
Generated By: SesLogon.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

3040 Session was not found in the session lock cache.
Explanation: A session lock service request is received for a session entry which is not found in the session lock cache.
Generated By: Session Lock Server.
For Whom: Support Representative.
Notes: This error is returned by an internal consistency check. This error causes an error message to be returned to the
host.
Remedy: Save the dump and contact your Support Representative.

3041 A lock waiter for a switch session was found.
Explanation: A ’remove entry’ request is received from SesTsk2 (when it completed a session switch) for an entry in the
session lock cache which has a waiter waiting for the lock to be released.
Generated By: Session Lock Server.
For Whom: Support Representative.
Notes: This error is returned by an internal consistency check.
Remedy: Save the dump and contact your Support Representative.

3042 At least one session lock is not released.
Explanation: This error is returned by a session lock service routine when an ’unlock entry’ request has not been successfully
carried out.
Generated By: Session Lock Server.
For Whom: Support Representative.
Notes: This error is returned by an internal consistency check.
Remedy: Save the dump and contact your Support Representative.

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