[teiid-issues] [JBoss JIRA] Commented: (TEIID-1559) Dynamic VDB deployed in inactive state on Oracle11g

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Wed Apr 20 10:24:33 EDT 2011


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

Steven Hawkins commented on TEIID-1559:
---------------------------------------

There are several issues here:

1. the initial import was erroring due to a duplicate table being created in Teiid.
The resolution is to use the full schema name.

2. the import from oracle appears to never return.
As the reference warns, the default importer settings crawl all available metadata.  So one resolution is to limit what you are importing, see the reference for importer.schemaPattern

The other question would be, suppose we do want to import all of the metadata, is it taking too long?  That could be harder to determine.  The import code is rather straightforward.  We are just asking DatabaseMetadata for tables/columns limited by the given patterns.  I would have you try the first option - limit the metadata your importing and see if you get an appropriate load time.

> Dynamic VDB deployed in inactive state on Oracle11g
> ---------------------------------------------------
>
>                 Key: TEIID-1559
>                 URL: https://issues.jboss.org/browse/TEIID-1559
>             Project: Teiid
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 7.1.1
>         Environment: Oracle 11g R2, driver version: 11.2.0.1.0
> Teiid 7.1.1 in SOA-P 5.1
>            Reporter: Boris Belovic
>            Assignee: Steven Hawkins
>         Attachments: mytext-ds.xml, myvdb-vdb.xml, oracle-ds.xml
>
>
> Dynamic VDB is deployed in inactive state on SOA-P 5.1 server configured with Oracle 11g R2 database. First I deploy both datasources required by VDB and then dynamic VDB itself. But the VDB remains in inactive state, despite all datasources referred by this VDB are in place (= deployed correctly). Few seconds after deployment of VDB I got this exception from the server.
> 08:42:24,335 INFO  [RUNTIME] VDB "myvdb-1" - "Employees" model metadata is currently being loaded. Start Time: 4/19/11 8:42 AM
> 08:42:24,355 INFO  [PROCESSOR] Clearing prepared plan cache
> 08:42:24,358 INFO  [RUNTIME] VDB "myvdb.1[Employees[oracle-connector/oracle/java:DefaultDS], TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state.
> 08:42:50,307 WARN  [RunnableTaskWrapper] Unhandled throwable for runnable: org.teiid.deployers.VDBDeployer$1 at 13bf30c
> java.lang.AssertionError: Duplicate Table APEX_ACTIVITY_LOG
> 	at org.teiid.metadata.Schema.addTable(Schema.java:42)
> 	at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:82)
> 	at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:195)
> 	at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:110)
> 	at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:268)
> 	at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:80)
> 	at org.teiid.dqp.internal.datamgr.ConnectorManager.getMetadata(ConnectorManager.java:125)
> 	at org.teiid.deployers.VDBDeployer.loadMetadata(VDBDeployer.java:310)
> 	at org.teiid.deployers.VDBDeployer.access$000(VDBDeployer.java:59)
> 	at org.teiid.deployers.VDBDeployer$1.run(VDBDeployer.java:293)
> 	at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)
> I also tried deploying this VDB on MySQL 5.1 and PostgreSQL 8.3 and the VDB was deployed without any problems or exceptions.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the teiid-issues mailing list