TDP1788 "cpname" ASSUMED TO HAVE HUNG ON THE CHANNEL
While recovering from loss of communication with a CP, a Configuration Request was judged to be taking excessive time. The request is retried using a different CP.
Since neither the channel architecture nor the Teradata Channel Interface define response time requirements, it is possible that no problem exists. However, if after TDP and the Teradata Database successfully synchronize, the indicated CP remains down, then it had violated the channel architecture by not terminating an active channel command when the CP went down, by not rejecting a channel command after the CP went down, or by both.
Contact Customer Support personnel to report the erroneous Teradata Database CP.