Unknown error message 966.

Howdy! I ran a SQL script, where I created a raw table as select statement, did so using isql from a client server, and I got this weird message where it should have said table created: Unknown error message 966. Any clue as to what might have happened? Thanks in advance. Ramón DB Server: IDS 12.10.FC10AEE on CentOS 7 (Linux 3.10) DB Client: CentOS 7 (Linux 3.10) with ISQL 7.50.FC6 Pseudo-query: create raw table _my_tempas select distinct < columns, aggregate function and case statements > from table1 A, ( select * from other_db:o_table1 union select * from other_db:o_table2) B where <join><filters> <group by> <having date(expression) = today-1> ; ------------------------------ Ramón Rey ------------------------------ #Informix

First guess is the problem is the derived table tom the other machine. There was a question about similar last week Cheers Paul

I'm not sure that isql had support for RAW tables. When the statement was prepared isql didn't understand the statement type number that was returned as part of the sqlda structure that it needed to parse in order to know if it needed to display any data and what the returned data types were. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.

Hello @Art Kagel , On one hand, the table did get created and populated. On the other, I don't like weird errors when running in production. Would I be safe to assume that if I create a logged table, I wouldn't get the error? EDIT: I did remove the raw from the create table , and it still returns the same unknown error message 966. @Paul Watson , You mentioned the derived table from the other database... could it be that the create table doesn't like the derived table? Because I haven't seen this issue when doing a regular select or even a select into temp. Thanks! Ramón ------------------------------ Ramon Rey ------------------------------

The issue the other day was a -999 - the remote DB call was trying to use an aggregate AFAIR. Cheers Paul ------------------------------ Paul Watson Oninit LLC Cell +1 9133877529 ------------------------------

To exclude isql as a possible source, how would this go when running exact same statement from dbaccess (I guess it shouldn't make a difference that dbaccess probably is local to the database server while isql apparently is ran remotely.) Also: what exactly is "other_db"? Is this on same db server or a different one? ------------------------------ Andreas Legner ------------------------------

Or maybe isql doesn't recognize the derived table? Other than that I'm out of ideas. ------------------------------ Art S. Kagel, President and Principal Consultant ASK Database Management Corp. www.askdbmgt.com ------------------------------

Andreas, Yes, isql is being used in a remote host. I'll test it on the local host to the DB server with dbaccess and report back. And, it is another DB on the same DB server. R ------------------------------ Ramon Rey ------------------------------