Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORA-00932: inconsistent datatypes: expected - got BLOB

AquaNX4Feb 27 2018 — edited Feb 27 2018

Hello:

Oracle 11GR2 XE

APEX 5.0

An error occurred on one of my application pages that is somewhat baffling.  This application (and page) has been in production for 3 years with no hiccups whatsoever.  Everyday, 30 users access this application and in particular, a specific page within the application.  This morning, 2 specific users were getting the below error when trying to access that particular page.  NO other users, including my development team and I were experiencing this error: 

Logging exception:

Sqlerrm: ORA-00932: inconsistent datatypes: expected - got BLOB

Backtrace: ORA-06512: at "SYS.DBMS_SYS_SQL", line 1249

ORA-06512: at "SYS.WWV_DBMS_SQL", line 464

ORA-06512: at "SYS.WWV_DBMS_SQL", line 475

ORA-06512: at "APEX_050000.WWV_FLOW_DYNAMIC_EXEC", line 416

I had at-least 20 other users come to my office to see if they had the same issues and they did not.  At first, I thought it was some quirky browser error (blame the browser syndrome), so I had the same 2 users come to my office and logon the application, and they experienced the same error.  A view of the page debug shows the above error.  There is only one classic report on the page.

Here is the kicker:

This is the query:

SELECT sor.ID                     AS sor_id         ,

        sor.REQ_DATE                     AS date_of_request,

        TO_CHAR(sor.REQ_DATE, 'HH24:MI') AS time_of_request,

        ae.LAST_NAME

        || ', '

        || ae.FIRST_NAME AS requestor  ,

        ae.phone                       ,

        sor.BUILDING                   ,

        sor.ROOM_NUM                         AS room_number    ,

        sor.REQ_DESC                         AS sor_description,

        cat.LU_DESC                          AS req_category   ,

        pri.LU_DESC                          AS req_priority   ,

        stat.LU_DESC                         AS req_status     ,

        sor.REQ_ASS                          AS assigned_to    ,

        sor.NOTES                            AS sor_notes      ,

        sor.REQ_CLOSED                       AS date_closed    ,

        date_diff3((sor.req_date),(sysdate)) AS time_elapsed   ,

        SOR.ATTACH_DATA                      AS ATTACHMENT     ,

        sor.attach_filename

FROM SOR_TRACKER sor

LEFT JOIN ACTIVE_EMP ae

ON sor.REQ = ae.EMP_ID

LEFT JOIN LU_SOR_CAT cat

ON sor.REQ_CAT = cat.LU_ID

LEFT JOIN LU_SOR_PRI pri

ON sor.REQ_PRI = pri.LU_ID

LEFT JOIN LU_SOR_STAT stat

ON sor.REQ_STAT   = stat.LU_ID

WHERE stat.lu_id <> 2

ORDER BY 16,

        2 DESC    ,

        6

I removed the order by and it worked!  WTH?!

What would cause the above error for 2 specific users and no one else, and why would the order by cause this error?

Thanks,

Aqua

This post has been answered by Anton Scheffer on Feb 27 2018
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 27 2018
Added on Feb 27 2018
8 comments
5,645 views