|
Archives of the TeradataForumMessage Posted: Mon, 12 Sep 2005 @ 09:32:41 GMT
Hi, The below is the description of the two error codes: I am not sure about the 1st about DBS restart, but I hope that second error code descrition will help you. 1. 2825 No record of the last request was found after DBC restart. Explanation: No record of the last request sent was found on the Teradata DBS after restart. The request may or may not have been rolled back. The user must determine if the request completed or not. Generated By: System Recovery. For Whom: End User. Notes: This error is sent in response to a host status request from the TDP after a Teradata DBS restart. Remedy: Resubmit the last request if it did not complete. Remedy: Resubmit the transaction. 2. 7547 Target row updated by multiple source rows. Explanation: In present system we do not support to update the target row with multiple source rows. Before implementing Merge Update the join updates were processed in two steps, Merge Delete and Merge Insert. Since, we used to delete all the rows, we end up generating the duplicate rows to insert. In that scenario, we return a different error. This type of Merge Updates (Join Updates) are not allowed. For tables T1(a1,b1,c1), T2(a2,b2,c2), consider the update update t1 from t2 set c1=c2 where a1=b2 and b2 10; If there are more than one row satisfying this condition, we are not sure which row needs to be used for this update. In this scenario, we return this error message. Generated By: AMP subsystem For Whom: User Remedy: See that source rows are unique before updating. Vinod
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||