[teiid-issues] [JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

Steven Hawkins (JIRA) issues at jboss.org
Thu Sep 8 08:57:00 EDT 2016


    [ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290570#comment-13290570 ] 

Steven Hawkins commented on TEIID-4427:
---------------------------------------

The DDL I'm showing is specifically the Teiid DDL - how are you creating the metadata for the oracle materialized table target?  Translator import, Designer, DDL?  With the Teiid Oracle import NUMBER(10) will be represented by bigdecimal by default.  If the useIntegralTypes import option is used, NUMBER(10) would be represented by a long.  Either way it wouldn't match the expectation of the view.  I'm still trying to understand how this would have worked in 8.11, but not 9.

> Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal
> -----------------------------------------------------------------------------------------
>
>                 Key: TEIID-4427
>                 URL: https://issues.jboss.org/browse/TEIID-4427
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 9.0
>            Reporter: Mark Tawk
>            Assignee: Steven Hawkins
>            Priority: Critical
>             Fix For: 9.1, 9.0.4
>
>
> After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on Oracle server.
> when fetching an Oracle materialized view that contains a column using date function like : "Month" or "Year" or "TIMESTAMPDIFF", we are getting the error : Expected integer, but was bigdecimal.
> If we go back to Teiid 8.11.3, the same materialized views fetch without any problem.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the teiid-issues mailing list