Re: SQL0204 -- *QUERY0000 not found???

Did you also load the hiper group and the database group?

Rob Berendt
-- 
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)




CWilt@xxxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/07/2004 01:54 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Fax to

Subject
SQL0204 -- *QUERY0000 not found???






I've got a query that uses 3 common-table expressions along with a 
subquery
in the where clause.

When I run it from STRSQL, I get an SQL0204 error:
Message ID . . . . . . :   SQL0204

 

Message . . . . :   *QUERY0000 in QTEMP type *FILE not found.

Cause . . . . . :   *QUERY0000 in QTEMP type *FILE was not found. If this 
is
an ALTER TABLE statement and the type is *N, a constraint was not found. 
If
this is not an ALTER TABLE statement and the type is *N, a function,
procedure, or trigger was not found.


When I run the query from QueryManager or Ops-Nav I get a slightly 
different
error:
Message ID . . . . . . :   SQL0204


Message . . . . :   *QUERY0000 in QTEMP type *MEM not found.

Cause . . . . . :   *QUERY0000 in QTEMP type *MEM was not found. If this 
is
an ALTER TABLE statement and the type is *N, a constraint was not found. 
If
this is not an ALTER TABLE statement and the type is *N, a function,
procedure, or trigger was not found.

The query runs if I get rid of the subquery.  However, the subquery is not
in error.  By itself it runs fine.

Just to make life more interesting, let me say that the query was running
fine on our old 830.  We moved to a new 810 this past weekend, also the
latest cume pack has been loaded.

Any thoughts?

Charles
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.