Teradata Database is unaware of a TDP crash. In-progress requests continue, and responses are still available. When the TDP is restarted, it sends a cold client start, which causes Teradata Database to log off all sessions and roll back any uncommitted work. If the Two-phase commit protocol is being used and there is a TDP crash, any in-doubt sessions will remain active and must be resolved by the coordinator.