Archives of the TeradataForum

Message Posted: Mon, 12 Sep 2005 @ 18:02:15 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Xinyu,

As you are aware that volatile table is only valid during a session you populated it if you have preserve rows on commit as part of your create table statement.

If there is any interruption then the data in those volatile tables are gone. Your BTEQ is probably set to retry after network disconnect or DBS restart. The message is generic one to tell you that the insert..select statement is no longer valid after the interruption. Please resubmit everything including statement that populate the ND and OD volatile tables.

The second one is a tricky one. You have two SQL statements string together by putting the semicolon of first statement as beginning of second statement. This only works in BTEQ environment. The error was simple. Your update statement and insert statement probably try to update the same record and with the way your syntax was in BTEQ. The system try to process both at the same time and violated something. Separate the two statement may into their own statement as following will probably help you prevent this type of message:

     update A
     set .........
     ;
     Insert into B
     select ........
     from wt_i;

Otherwise, your update statement is updating a row with multiple answer set from your select statement. Take the select portion of the update statement and group by the column you are going to use to set new value and include a having count(*) > 1 statement in the where condition to see whether your data you are using to update the table A has multiple data.

Hope this helps,

Samuel Chu

	<Prev	Next>		<<First	<Prev	Next>	Last>>