Messages Having Operational Impact - Teradata Director Program

Teradata® Director Program Reference - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Director Program
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-17
dita:mapPath
cki1641301536147.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
frc1470439950465
Product Category
Teradata Tools and Utilities
While many TDP messages are informational and require no actions, several reflect conditions that can adversely impact TDP so might warrant some corrective action. Operational procedures or automated operations software should consider such messages.
  • Since the types and quantity of processing performed by TDP can vary widely, its use of virtual storage also varies. TDP separates its use of virtual storage into various sizes of cells, with the number of cells of each size selected when TDP initializes. If all cells of a particular size are exhausted, some aspect of TDP will either dynamically allocate a new cell or wait for other TDP processing to release a cell of that size. If dynamically obtained the cell will be freed when its use is complete. Either action can affect performance so is indicated by the following message:

    TDP0021 **WARNING** 100% OF nnnnn BYTE CELLS ARE IN USE

    The shortage can be addressed by using the TDP ADD CELLS command to increase the number of cells of that size. Using z/OS, a second type of some size cells, known collectively as XMS cells, exist for use in communicating with application address spaces. Should a shortage of these cells occur, that request or response is delayed until other processing frees an XMS cell of the required size. Such delays are indicated by one of the following messages:

    TDP0201 **WARNING** 100% OF INITIAL XMS CELLS ARE IN USE

    TDP0202 **WARNING** 100% OF ADDITIONAL XMS CELLS ARE IN USE

    The first indicates that one of the three sizes of XMS cells is unavailable; the second indicates that the largest of the three is unavailable. The shortage can be addressed by using the TDP ADD XMSCELLS command to increase the number of cells of that size.

  • Communication with the database can be interrupted if an individual CP or NP fails to respond, or if the database crashes or is manually restarted. Since each CP and NP is independent of the others, each will produce an appropriate message if communication using it is lost:

    TDP2202 "cpname" IS WAITING FOR COMMUNICATION TO BE ESTABLISHED

    TDP3511 "npname" IS WAITING FOR COMMUNICATION TO BE ESTABLISHED

    The loss of only some CPs or NPs can affect requests that are active on that CP or NP but otherwise only reduces performance. If all CPs and NPs fail, the following message results:

    TDP1700 COMMUNICATION LOST WITH THE TERADATA DATABASE

    Periodically (as specified by the TDP CONFIG COMMLOST MSG INTERVAL command) if communication has not been re-established, the following reminder occurs:

    TDP1701 MINUTES SINCE TERADATA DATABASE COMMUNICATION LOST: min

    The time taken by the database to complete its restart varies, but the more time that elapses the more likely that a more serious database problem exists. When the database does complete its restart and any CP or NP begins processing, the following message is produced:

    TDP1702 TERADATA DATABASE COMMUNICATION HAS BEEN RE-ESTABLISHED

    This does not imply that every CP or NP is functional, only that at least one is. The failure of an SP forces a database restart and if the SP remains down after the restart, TDP will switch sessions on the down SP to other SPs. If there is insufficient session capacity then the following message results:

    TDP1706 INSUFFICIENT SP CAPACITY FOR EXISTING SESSIONS

    No new sessions are permitted until all existing sessions are switched to functional SPs. The following message indicates that this has been accomplished and new sessions are again permitted:

    TDP1708 SUFFICIENT SP CAPACITY FOR EXISTING SESSIONS

    It is also possible that unrelated to a database restart, a CP or NP problem might be detected. A physical permanent I/O error is indicated by:

    TDP2203 "cpname" UNUSABLE -- PERMANENT I/O ERROR

    TDP3407 "npname" UNUSABLE -- PERMANENT I/O ERROR

    while a logical failure of the internal communication protocol is indicated by one of the four following messages:

    TDP2207 "cpname" UNUSABLE -- TERADATA DATABASE PROTOCOL-VIOLATION

    TDP3600 "npname" TERADATA SERVER ENCAPSULATION-VIOLATION: TU(xx), ERROR , INFO(xxxxxxxx)

    TDP2208 "cpname" UNUSABLE -- CLIENT PROTOCOL-VIOLATION

    TDP3601 "npname" CLIENT ENCAPSULATION-VIOLATION: TU(xx), ERROR

  • In addition to explicit events, TDP can detect implicit communication problems. If an internal request sent to recover from a loss of communication with the database is judged to be taking excessive time and another functional CP exists, the following message is issued and the request is resent using another CP:

    TDP1788 "cpname" ASSUMED TO HAVE HUNG ON THE CHANNEL

    If a number (as indicated by the DISPLAY CONFIG XP DETAIL command) of consecutive requests have been sent without any responses received, the CP or NP is judged to be unresponsive. One of the following messages is issued and subsequent requests are sent using any functional CP or NP until this one begins responding. Requests already sent are unaffected and will remain outstanding until their responses are received.

    TDP2211 "cpname" HAS BEEN QUIESCED: UNRESPONSIVE

    TDP3412 "npname" HAS BEEN QUIESCED: UNRESPONSIVE

    TDP2212 "cpname" HAS BEEN QUIESCED: UNRESPONSIVE

    TDP3413 "npname" HAS BEEN QUIESCED: UNRESPONSIVE

    The TDP2212 or TDP3413 message will be held on the operator console until either manually deleted, the CP or NP is again responsive, the CP or NP is STOPped, or TDP ends. This is the preferred message because it is held on the z/OS console for the duration of the problem. The TDP2211 or TDP3412 message, which is not held on the console, is issued only if internal TDP conditions prevent the preferred message.

    If either a response is eventually received, the CONFIG XP MAXNORSP command raises the limit, or a database restart occurs, use of the CP or NP is resumed after the following message is issued:

    TDP2213 "cpname" IS NO LONGER QUIESCED: reason

    TDP3414 "npname" IS NO LONGER QUIESCED: reason

  • The database can reject an attempt to establish a session because the database system userid is unknown or the supplied password is invalid. Such a security violation is indicated by:

    TDP0907 type VIOLATION FOR JOB: jobname, SESSION: number

    If a TDP logon exit rejects the session it issues the following message:

    TDP0908 messagetext

  • Exceeding certain internal TDP limits might impact message processing. If TDP is unable to retain the system's identity for an action message the system cannot be told to delete it. This situation is indicated by:

    TDP0376 UNABLE TO RETAIN OPERATOR MESSAGE IDENTITIES, CODE(code)

    If TDP cannot retain the system's identity of the source of a TDP command the response cannot be routed back to it. This situation is indicated by one of the following messages:

    TDP0312 UNABLE TO RETAIN ORIGINATING CONSOLE INFORMATION

    TDP0203 UNABLE TO RETAIN ORIGINATING CONSOLE INFORMATION