Teradata Database Message 3296 - 3296 - Analytics Database - Teradata Vantage

Message

PM/PC command processing timed out.

Explanation

This error is designed to be a general timeout but non-fatal indicator during SET SESSION ACCOUNT, MONITOR SESSION or MONITOR SQL commands processing. For MONITOR SESSION timeout only: A snapshot dump is taken on the first timeout. There will be a wait time of 60 minutes for next snapshot dump. No snapshot dump will be taken if another Monitor Session timeout occurs within 60 minutes. For MONITOR SQL timeout only: The timeout wait interval is user specifiable in PMPC_TimeoutSec field in dbscontrol gdo. The default timeout interval is 60 seconds. Some values have special meaning: 0: Disables Monitor SQL timeout. Monitor SQL request will wait for the response forever. This error, 3296, is never returned. 60: The dispatcher worker task's state is checked externally and if the task is blocked to receive and process Monitor SQL request then this timeout error (3296) is returned immediately rather than waiting for 60 seconds. Note that Monitor SQL processing can still take longer than 60 seconds and 3296 may be returned if the Monitor SQL request has been delivered, but waiting for some shared resources within the target dispatcher worker task. 61: Same as 60, but only applies if Stored Procedure is running on the target session whereas 60 applies to all kinds of requests running on the target session. N: Any other values, 1 - 59 and 62 - 3600, will cause Monitor SQL request to time out and return 3296 after N seconds.

Generated By

CONTSK (by order of PFMCOTSK), SESPMAIN, PFMCOTSK or PFMUMAIN tasks

For Whom

End User.

Notes

None

Remedy

Just retry, or check the session itself.