[
https://issues.jboss.org/browse/TEIID-2875?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2875:
---------------------------------------
Ramesh, how are you able to determine that this is happening when an index is loaded?
importApproximateIndexes is not new, and you should rarely need to set it to false. If
false, then you are telling the db to use non-statistical methods to determine any
applicable row counts for the index info - which could turn out to be quite expensive or
in this case seems to be causing a privilege issue.
The simplest fix here is to determine if you need the RATE table. If not then you can add
an exclusion for it.
To resolve this in general, as Ramesh is getting, we need to know when we're
referencing this column (during index import, key import, etc.) which could be determined
by shutting off individual imports or from the full stack trace. And we would need to see
why it's not appearing in the primary table metadata.
Metadata failed to load. No column found
----------------------------------------
Key: TEIID-2875
URL:
https://issues.jboss.org/browse/TEIID-2875
Project: Teiid
Issue Type: Bug
Affects Versions: 8.6
Environment: Windows server 2003, Windows 7.
Reporter: SHI HONG CHIN
Assignee: Steven Hawkins
Attachments: JakkerData-vdb.xml
Affected database: Oracle
The following error displayed when Teiid loading a dynamic VDB:
10:21:41,458 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB
JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column
found with name "RATE"."CHARGE_NAME"
10:23:29,994 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB
JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column
found with name "RATE"."CHARGE_NAME"
I am not the one who design the database. But, I cannot find any table with above
mentioned column name in Oracle database. So, I am not sure whether the above mentioned
column name is a hidden column or not.
This bug does not exist in version 8.5.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira