Hi,
One possible scenario is when a session has an unfinished transaction. This is when a user has issued a BEGIN TRANSACTION is Teradata transaction mode, or is working in ANSI transaction mode. Until the transaction is finished, the session holds the locks. If it is waiting for the next command to be entered by user, it can be in the IDLE state.
Regards,
Vlad.
Hi,
One possible scenario is when a session has an unfinished transaction. This is when a user has issued a BEGIN TRANSACTION is Teradata transaction mode, or is working in ANSI transaction mode. Until the transaction is finished, the session holds the locks. If it is waiting for the next command to be entered by user, it can be in the IDLE state.
Regards,
Vlad.