Here's a possibility... DB2 uses schemas to group database objects. Since I don't see any reference to ADMINISTRATOR.TBLDONE in your query, you may be having a problem because you haven't qualified your table name with a schema reference (schema.table). DB2 would then look at the default schema (ADMINISTRATOR, in your case?) where TBLDONE does not exist.
On 5/4/07, Bruce Sorge <[EMAIL PROTECTED]> wrote: > > I ran the select statement and even took out the join, and I get the same > message. I will have to look into it further I guess. > > Bruce > > On 5/4/07, Jochem van Dieten <[EMAIL PROTECTED]> wrote: > > > > Bruce Sorge wrote: > > > DB21034E The command was processed as an SQL statement because it was > > not a > > > valid Command Line Processor command. During SQL processing it > > returned: > > > SQL0204N "ADMINISTRATOR.TBLDONE" is an undefined > name. SQLSTATE=42704 > > > > > > SQL0204N "ADMINISTRATOR.TBLDONE" is an undefined name. > > > > > > the table does exist and is under the schema ADMINISTRATOR. > > > > Does the select without the insert work? What if you alias the tables? > Do > > you really need the full outer join? > > > > Jochem > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/SQL/message.cfm/messageid:2840 Subscription: http://www.houseoffusion.com/groups/SQL/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.6
