Teiid Designer can't create a Teiid Execution Plan for a DB2 source model

[rob.t]

I am getting the error:

org.teiid.jdbc.TeiidSQLException: TEIID30498 Capabilities for (Source Model) were not available. The command could not be planned properly.

I used the import tool to load a DB2 table into a source model from a remote host. I know the  JDBC driver works because I can query the table with no problems in the Database Development view, but when I try to run a preview or view the execution plan, I get the above error, even though the source model correctly visualizes the table.

Can anyone help me?

[rareddy]

Rob,

Can you see if there are other errors in server log? I guess for some reason the metadata between the Designer and Server got out of sync, you can also try cleaning out by restarting both Designer and Server and removing any "preview" artifacts.

Ramesh..

[blue666man]

Ramesh,

I encountered the same issue.  A SQLServer 2012 source model that has a stored procedure.  We created a virtual proc for it, and then used the virtual proc as the source for a base table that has a primary key and access pattern defined.  Worked fine locally on a Windows 7 box, but results in the following on the RHEL server:

23:44:14,917 WARN  [org.teiid.PROCESSOR] (http-/0.0.0.0:8680-1) IbeJtimVKGzS TEIID30020 Processing exception for request IbeJtimVKGzS.0 'TEIID30498 Capabilities for <my View Model> were not avaialable.  The command could not be planned properly.'. Originally QueryPlannerException PlanToProcessConverter.java:319. Enable more detailed logging to see the entire stacktrace.

23:44:14,925 WARN  [org.teiid.ODATA] (http-/0.0.0.0:8680-1) null TEIID16012 Could not produce a sucessful OData response.  Returning status ServerErrorException with message TEIID30498 Capabilities for <my View Model> were not avaialable.  The command could not be planned properly..

This is at DEBUG log level; no other log messages pertaining to the error appear; including a stacktrace, but I can retry with an ALL.  We're using a 8.5 nightly build:

http://github.com/teiid/teiid/commit/30989522b71902d84febb9b7f5eafe964e229c0d

Any ideas?

Thanks,

John

[shawkins]

The exception that you are seeing is produced late in planning after the original exception should have been logged at a debug level (from CachedFinder).  Are the logs against your view model?  That would be odd as we should not be checking capabilities there.

[rob.t]

It looks like I was mistaken about the driver, it looks like the root of the problem is the DB2 License not working correctly with JBoss, My team was able to fix it by deploying the DB2 driver jars as a module.

[blue666man]

I also resolved my issue; totally different in my case as it's SQLServer:  the JNDI data source was not correct.