Direct Discovery Oracle Error (Table doesn't exist

[#1]

using sql select, my sql runs just fine.  switching over to direct discovery I am getting oracle errors from the database that the table doesn't exist.  Any ideas what i'm doing wrong?  I'm using an OLEDB connection.

sql select

acct_system_portf_no,

sec_source_id,

portfolio_type,

base_ccy,

portfolio_name,

update_date

FROM fidb.portfolio_universe;

DIRECT QUERY

dimension

acct_system_portf_no,

sec_source_id,

portfolio_type,

base_ccy

measure

portfolio_name

detail

update_date

FROM fidb.portfolio_universe;

error:

ErrorSource: OraOLEDB, ErrorMsg: ORA-00942: table or view does not exist

DIRECT QUERY

dimension

acct_system_portf_no,

sec_source_id,

portfolio_type,

base_ccy,

portfolio_name,

update_date

FROM fidb.portfolio_universe

DirectTable << INL43F7 0 lines fetched

"fidb"."portfolio_universe".acct_system_portf_no (fetching)

[fernando_tonial]

Hi, please check this limitations.

• Oracle database tables with LONG datatype columns are not supported.
• Big integers in scientific notation, outside range [-9007199254740990, 9007199254740991], can cause rounding errors and undefined behavior.

Best Regards.

Tonial.

[#3]

Neither of those are issues in this particular query/table unfortunately

[#4]

I was able to trace the sql queries being generated by QV.  How do I remove the " (double quotes) from the query creation?

SELECT DISTINCT "acct_system_portf_no" FROM "portfolio_universe"

[maxgro · Accepted solution]

change your sql to uppercase: columns to uppercase, tables to uppercase

I tried direct discovery with my oracle db and I have the same problem (doubel quotes added to the query)

Changed all to uppercase and it works.

You can try with an Oracle tool as sqlplus

select sysdate from dual

select sysdate from "DUAL"

select sysdate from "dual"

first and seconds work

last one doesn't

[#6]

Brilliant! Thank you so much.  I've spent days banging my head against the wall.