ORA-00932: inconsistent datatypes: expected NUMBER got LONG

hm — Mon, 26 Dec 2005 06:17:35 GMT

I am running alfresco on Oracle 10G XE (Express/Free Edition). I am able to log into the application and create spaces etc.In the Oracle web client when I look at the data in the 'node_properties' table I see the following message instead of the data:report errorRA-00932: inconsistent datatypes: e

Re: ORA-00932: inconsistent datatypes: expected NUMBER got LONG

derek — Wed, 04 Jan 2006 15:35:48 GMT

Hi,

I am not sure what you mean by "Java Null". Null values are allowed in the columns and we use them liberally.

The fact that one client fails while the other succeeds suggests to me that the failing client is executing an illegal query.

Long datatype has some restrictions , one of them is ;
LONG columns cannot be used in WHERE, GROUP BY, ORDER BY, or CONNECT BY clauses or with the DISTINCT operator in SELECT statements

from http://datawarehouse.ittoolbox.com/groups/technical-functional/oracle-db-l/760953.

At any rate, as long as you are able to perform queries using SQLPLUS, it should be fine. The schema has already had to be modified specifically to handle Oracle restrictions that get applied to column types. As we don't ever select specific values from the LONG BINARY column, it is probably just the Oracle web client doing a DISTINCT or something. Try SQLPLUS with


SQL> select distinct ( serializable_value) from node_properties;
select distinct ( serializable_value) from node_properties
                  *
ERROR at line 1:
ORA-00997: illegal use of LONG datatype
‍‍‍‍‍‍‍

Regards

topic ORA-00932: inconsistent datatypes: expected NUMBER got LONG in Alfresco Archive

ORA-00932: inconsistent datatypes: expected NUMBER got LONG

Re: ORA-00932: inconsistent datatypes: expected NUMBER got LONG