[JBoss JIRA] (TEIID-3188) ORA-01702: a view is not appropriate here
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3188?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3188.
---------------------------------
> ORA-01702: a view is not appropriate here
> -----------------------------------------
>
> Key: TEIID-3188
> URL: https://issues.jboss.org/browse/TEIID-3188
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 7.4
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> When importing tables/views from Oracle, importing keys/indexes fails. Workaround is to disable importing of either views or indexes. I think the issue is that Oracle views cannot have indexes/primary-keys, so the fix would be to not call getIndexInfo() on views.
> {code}
> <property name="importer.tableTypes" value="TABLE,VIEW"/>
> <property name="importer.importKeys" value="true"/>
> {code}
> {code}
> 23:03:42,170 CONFIG [oracle.jdbc.driver] (teiid-async-threads - 4) 593E0A4C SQL: analyze table FOO.MY_VIEW compute statistics: java.lang.Throwable: No Error
> at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1592)
> at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:2618)
> at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:2547)
> at oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:1073)
> at oracle.jdbc.OracleDatabaseMetaData.getIndexInfo(OracleDatabaseMetaData.java:9365)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.getIndexes(JDBCMetdataProcessor.java:553)
> at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:135)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:309)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:57)
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) [teiid-engine-8.9.0.Alpha2-SNAPSHOT.jar:8.9.0.Alpha2-SNAPSHOT]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.9.0.Alpha2-SNAPSHOT.jar:8.9.0.Alpha2-SNAPSHOT]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.9.0.Alpha2-SNAPSHOT.jar:8.9.0.Alpha2-SNAPSHOT]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.9.0.Alpha2-SNAPSHOT.jar:8.9.0.Alpha2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
> {code}
> 23:03:42,173 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB Foo.1 model "foo" metadata failed to load. Reason:TEIID11010 java.sql.SQLSyntaxErrorException: ORA-01702: a view is not appropriate here
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (TEIID-2223) Compiled Groovy cannot deploy a dynamic VDB, using AdminShell methods, that is recognized as ACTIVE by the Groovy script
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2223.
---------------------------------
> Compiled Groovy cannot deploy a dynamic VDB, using AdminShell methods, that is recognized as ACTIVE by the Groovy script
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2223
> URL: https://issues.jboss.org/browse/TEIID-2223
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 7.7.2
> Reporter: Paul Nittel
> Assignee: Johnathon Lee
> Priority: Optional
> Fix For: Open To Community
>
> Attachments: CrummyWeather.groovy, ShortWeatherNoTest.groovy, weather-vdb.xml
>
>
> This is a weird case. If I deploy a dynamic VDB from a compiled Groovy script, it is not seen as ACTIVE by the script. The server log shows it is active.
> If I use a non-compiled Groovy script, it all works fine.
> To add to the intrigue, if the compiled script periodically polls to see if the VDB is active, and I go to the Virtual Databases display in RHQ, the script magically sees the VDB as ACTIVE.
> I'm attaching the materials used in this test.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months