An IAL built on a view with TIMESTAMP-typed columns (e.g. from a SYS-owned view like DBA_SCHEDULER_JOBS, granted to a read-only integration user) runs fine when queried directly, but fails with 'Cannot convert JDBC type -101 to PlsqlType' when accessed through a Quick Report or the SQL Query Tool.

All FAQ questions / Data migration

Answer

TIMESTAMP-typed columns are the likely cause — the IAL/Quick Report data-access layer doesn't reliably handle the TIMESTAMP JDBC type (-101) that some views expose. Either drop the TIMESTAMP columns from the IAL's SELECT entirely, or explicitly convert them to a supported type before selecting (e.g. to_char(your_timestamp_column, 'YYYY-MM-DD HH24:MI:SS')) — converting to a formatted string avoids the JDBC type-conversion error while still keeping the date/time information available in the IAL's output.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Data migration questions