Translator not found error with Teiid 7.1 CR

[chesse]

Hello everyone,

I successfully deployed a VDB with a small View Model (containing 3 Tables) with Teiid 7.0. I was able to establish a connection to the vdb and to get data out of it.

I wanted to try out the new ODBC feature in 7.1 but after updating to Teiid 7.1 the JBoss AS log says that "oracle" Translator couldn't be found. Even though it says that all the Translators have been added.

I've tried several installations and I confirmed that the *.jars on the server and on my client are the Teiid 7.1.CR ones.

log entries:

"[org.teiid.RUNTIME] (main) Teiid translator "oracle" has been added."

"[org.teiid.RUNTIME] (HDScanner) For myVDB.1 VDB, Translator "oracle" not found."

"[org.teiid.RUNTIME] (HDScanner) myVDB.1 status has been changed to inactive. Check the required translators and data sources!"

Can you please help me out?

Thank you,

Carmon Hesse

[rareddy]

Carmon,

This seems odd. I do not see any issues with the details provided.

Can you attach your VDB as it may provide some insight into the issue?

Thanks

Ramesh..

[chesse]

Thank you Ramesh for the fast respond,

I have attached the vdb. I know there are some warnings but it worked using Teiid 7.0.

Note, I have been using Teiid Designer 7.0 to create the vdb, does that matter?

Stacktrace is the following if I try to connect via DTP (using 7.1.CR teiid jar):

Could not connect to eprs.
   Error creating SQL Model Connection connection to eprs. (Error: Remote  org.teiid.client.security.LogonException: VDB "eprs" version "latest"  is not active.)
   Remote org.teiid.client.security.LogonException: VDB "eprs" version "latest" is not active.
   Error creating JDBC Connection connection to eprs. (Error: Remote  org.teiid.client.security.LogonException: VDB "eprs" version "latest" is  not active.)
   Remote org.teiid.client.security.LogonException: VDB "eprs" version "latest" is not active.

Thank you again for your time,

Carmon

[rareddy]

The above error is known regression in the CR1, which since has been fixed. This bug is considering any warnings in the VDB as errors and not letting the VDB to deploy in active state. In 7.1.0-CR2 (will possibly release today) this will not be an issue.

To workaround,

• either fix all the warnings in the Designer and rebuild the VDB and deploy.
• or open the VDB file, and edit "META-INF/vdb.xml" fie, and remove the entries corresponding to the warnings and save. Then re-deploy.

as per the "translator" not found, I do not see any reason that would be failing. Are you still seeing this issue?

Thanks.

Ramesh..

[chesse]

Hello Ramesh,

I used the second option of the workaround and it is working now. Finally I can go and try out the new ODBC feature.

As for the Translator not found error. It seems this issue isn't occuring anymore.

Thank you for helping me out Ramesh.

Carmon

[rareddy]

Carmon,

7.1.0-CR2 released, which does not have the warnings issue any more. So that next time you rebuild the the VDB you do not need to do the manual removal of the warnings.

I am curious to know to how the ODBC feature works out for you, as this is just added to the 7.1 release.

Thanks.

Ramesh..

[chesse]

Hello Ramesh,

I updated everything to 7.1.0-CR2 and the deployed vdbs are working fine.

Regarding the ODBC feature, I'm trying to use QlikView to connect via the postgreSQL odbc driver but I receive the following error message listed below. On the client side it says unexpected protocol character =' .

2010-08-16 13:05:59,967 ERROR [org.teiid.TRANSPORT] (New I/O server worker #1-1) Unhandled exception, closing client instance
java.io.StreamCorruptedException: Unsupported version: 0
    at org.teiid.netty.handler.codec.serialization.CompactObjectInputStream.readStreamHeader(CompactObjectInputStream.java:57)
    at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)
    at org.teiid.netty.handler.codec.serialization.CompactObjectInputStream.<init>(CompactObjectInputStream.java:48)
    at org.teiid.transport.ObjectDecoder.decode(ObjectDecoder.java:128)
    at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:282)
    at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:214)
    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
    at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:340)
    at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:272)
    at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:192)
    at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
    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:619)

Thanks,

Carmon

[rareddy]

Carmon,

This exception did not give away much details. Are there any more exceptions on server? May be you can turn on debug logging on server it may give insight on what went wrong.

Are you running QlikView  on windows? Can you check with any other ODBC access, like Excel and see if you are seeing the same error. I want to rule out, if this may be due to Teiid's inability to satisfy some metadata call by the QlikView program.

Thanks.

Ramesh..

[chesse]

Hello Ramesh,

I enabled DEBUG logging on the server but the error information is still the same.

I'm running QlikView on Windows and I now tried to connect via Excel to Teiid using postgresql drivers but received the same error message.

I installed a postgresql server to test if my driver installation was correct and the connection tests were all successful.

I added a screenshot from the error message I get on client side.

Thanks,

Carmon

[rareddy]

Carmon,

The ports for JDBC and ODBC are separate. Looks like you are accessing Teiid through JDBC port. The default for this 31000. For ODBC, the default port is 35432. So in your DSN the port must be set to 35432. Also note that, the default port of Postgres is 5432, which not same for Teiid. You can find ODBC documentation in "Client Developers Guide". Check in the "teiid-docs" directory in the kit.

Thanks

Ramesh..

[chesse]

Hello Ramesh,

Thanks for the help! It's working now

Greetings,

Carmon