Archives of the TeradataForum

Message Posted: Tue, 19 Dec 2006 @ 13:47:27 GMT

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

This is documented somewhere - I'm sure I've seen it. Basically Teradata is looking in the current database (db2) and your default database (db1). In this case, it finds your table in both databases and doesn't know which one to use so you get the ambiguous message.

Having said that, I'm not able to replicate the error on V2R6.1 - so maybe there is something more to it, but I have seen the error before and that is why it is occurring.

The best bet is to fully qualify table names so you know what you are getting.

Glenn Mc

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