Tables not coming when creating a FM package in dynamic query mode

[vipulag]

Hi All,

I have copied the jar files into the appropriate location in Cognos installation and then created a datasource of Type OLEDB with JDBC Connection selected and it is testing successful in both compatible and dynamic mode. When, I am trying to create a model and checks the dynamic query mode checkbox, then, post selecting the datasource created above, I am not able to see tables for that database.

Is there something that I am missing or something I am doing wrong.

[MFGF]

Does your database signon have privileges to see the tables?

MF.

[vipulag]

The signon has privileges to the tables as when I uncheck dynamic query mode, I am able to view the tables in all the schemas for the database. There is one more thing: I have four schemas in my database and am able to see the tables for two of the schemas.

[MMcBride]

I have seen an issue similar to what you are reporting with DQM

I also run 32 Bit mode to support CQM and DQM.

We created a DQM FM model and added 4 tables (Very basic star Schema) so I thought this would be a perfect test for us to mess around with DQM.
Everything worked ok, but when we added a 5th table we could not add it to the model, nothing we did - even recreating the Datasource would bring in the 5th table.
We ended up creating a brand new model and the table came in ok - but redoing an entire model to update a table was not acceptable.
We also tried to updated a table - added a column - once again nothing we did would update the model correctly...

I finally pulled the model built it in CQM and published the Package as DQM and so far everything is still working (6 months in)

So now the only time I start a model in DQM is when I am mapping TM1 sources, otherwise I use CQM and publish the packages as DQM.

My Data Source was IBM DB2, My Cognos server is AIX

[Sugs]

Hello, out of interest are you on 10.1 or 10.2? I have read a few comments about users having issues like this in 10.1 and IBM have suggested upgrading to 10.2 to fix them.     

[pumccg]

There's a new Capability called "Import Relational Metadata" and unless the FWM modellers are included in it they won't be able to import DQM metadata into a DQM FWM model, even if all other permissions seem ok. To enable a FWM person to actually see and import metadata into a DQM model they must be added to this new capability with Execute and Traverse permissions. By default, for some strange reason, only Report Administrators are there with these permissions, so unless a FWM person is also one of these they can't import DQM metadata. In 10.2 this is now executed on the Cognos dispatcher box by the new Relational Metadata Service, and then fed to the FWM box.

Note that this new Capability also applies when using the new Dynamic Cubes Designer tool.