f



DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command.

Hello

we got a script automatically generated to populate a table that
belongs to a partition table, then while executing we get this error
message:

"DB21034E  The command was processed as an SQL statement because it
was not a valid Command Line Processor command.  During SQL processing
it returned:
12-14-2004 17:45:55 SQL0204N  "TABLE_NAME" is an undefined name. 
SQLSTATE=42704"
I dont know if this is permission related? or something else, I have
not used db2 in 3 years, any help would be great!!!
Thank you so much 
Maria
0
evoradba
12/16/2004 2:55:46 AM
comp.databases.ibm-db2 12448 articles. 3 followers. arunrocks (9) is leader. Post Follow

1 Replies
5518 Views

Similar Articles

[PageSpeed] 29

Maria wrote:
> Hello
> 
> we got a script automatically generated to populate a table that
> belongs to a partition table, then while executing we get this error
> message:
> 
> "DB21034E  The command was processed as an SQL statement because it
> was not a valid Command Line Processor command.  During SQL processing
> it returned:
> 12-14-2004 17:45:55 SQL0204N  "TABLE_NAME" is an undefined name. 
> SQLSTATE=42704"
> I dont know if this is permission related? or something else, I have
> not used db2 in 3 years, any help would be great!!!
> Thank you so much 
> Maria
Maria,

Can you post the SQL statement?
One possibility would be that the table was created non-upper-cased.
E.g. CREATE TABLE "Table_Name"(C1 INT);
then you need to select:
SELECT * FROM "Table_Name" instead of
SELECT * FROM Table_Name
another option could be that the CURRENT SCHEMA is not set properly.
SCHEMA is SQL's equivalent to a working directory. So being in the wrong 
schema will cause DB2 not to find the table.

Cheers
Serge
0
Serge
12/16/2004 3:43:47 AM
Reply: