Rob

Because the error lists your user name as the library, this suggests that you are using SQL naming. In that naming, an unqualified reference to a table uses the user name (authorization ID is the term, I think) as the "library list" - not the *LIBL.

So you have a couple choices - in SQL naming you would put the true library (schema ) in front of the table name, separated with a period.

Or change the connection to use SYS naming - then unqualified table names use the *LIBL. You still might need to qualify the table name, if the library is not in your library list. Then the separator is a forward slash. In more recent releases, I think the period is a valid separator for SYS naming, but don't quote me today!!

I forget where in the connection settings to make the change - I think it's one of the tabs on the right.

Vern

On 10/9/2015 12:33 PM, Rob wrote:
Hey gang,

Again... thanks for all of the advise and help so far... you guys are great.

I am really feeling like a newbie in the eyes of the Atlanta group who built this software.

I was in Navigator trying to run some SQL to take a peak into the data to see what was being stored in the tables.

I send the team a message explaining I was getting errors.

> select count( * ) from KWCBASE

SQL State: 42704
Vendor Code: -204
Message: [SQL0204] --TABLENAME-- in --USERNAME-- type *FILE not found. Cause . . . . . : --TABLENAME-- in --USERNAME-- type *FILE was not found. If the member name is *ALL, the table is not partitioned. If this is an ALTER TABLE statement and the type is *N, a constraint or partition was not found. If this is not an ALTER TABLE statement and the type is *N, a function, procedure, trigger or sequence object was not found. If a function was not found,--TABLENAME-- is the service program that contains the function. The function will not be found unless the external name and usage name match exactly. Examine the job log for a message that gives more details on which function name is being searched for and the name that did not match. Recovery . . . : Change the name and try the request again. If the object is a node group, ensure that the DB2 Multisystem product is installed on your system and create a nodegroup with the CRTNODGRP CL command. If an external function was not found, be sure that the case of the EXTERNAL NAME on the CREATE FUNCTION statement exactly matches the case of the name exported by the service program.

Processing ended because the highlighted statement did not complete successfully


The reply:
The SQL state code that got returned in the first attempt, 08S01, is a communications link failure, if I remember correctly. Usually, those kind of errors are caused by network or firewall settings or issues. The second attempt that returned SQL state code 42704 means that the resource being accessed does not exist. Looking at the rest of the log for that entry it looks like you where trying to access KWCBASE in library RCOUCH. I know with the navigator SQL and just db2 in general if you do not specify the library it uses your user profile as the library name. You should be able to set the library to KWDB108 or qualify the table, i.e. KWDB108/KWCBASE, to run queries against it.

So how does one select the database...

This is what I did in the Navigator:

Opened Connection

Connection->Databases->OnlyObjectedListed->Schemas->DBFILE

then in the bottom right section I chose "Run an SQL script"

I have also tried:

Connection->Databases->OnlyObjectedListed->Schemas->DBFILE->All Objects

then in the bottom right section I chose "Run an SQL script"

again... "No Joy!"

I am googling... but no answer found yet...

Thank You,
Rob


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.