If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Adding New columns to a Query Subject from DB2 tables

Started by Sugs, 13 Nov 2013 06:26:26 AM

Previous topic - Next topic

Sugs

Hello,

Whenever I try to update a query subject bringing through some new columns from the datasource they don't come through automatically. I have tried editing the definition, removing the sql and dragging the table back in from the source and editing the sql to no avail. The only way I can get around this is to run the Metadata wizard again which brings everything through fine but then it needs remodelling and joining to others tables etc. which is a pain. Has anyone else experienced this or have a better solution?       

cognostechie

Click on the Query subject, from the 'Tools' menu select 'Update Object'

Sugs

Thanks for the response but tried that - still doesn't update. The only way I can get it to update is to bring it through again via the meta data wizard. :-[

Sugs

I think I've sussed it. The model was set to Dynamic Query mode and I think that there must be some kind of caching (or something) going on preventing updates. I changed it to Compatible and hey presto all the query subjects updated automatically then back to Dynamic and alls good.
Rather than guess at this if anyone knows technically what is going on that would be useful. 

   

cognostechie

My best bet is that this is one of those 10.2.x issues. More than 70 issues have already been declared.

bdbits

It may be a bug, and if you are on 10.2.x you may want to update to 10.2.1.1 (the latest fixpack). There were a large number of fixes, but at the moment I do not have the luxury to go search to see if this particular issue was listed.

Alternatively, you could open a support ticket with Cognos and see what they have to say about it.

MMcBride

It is a bug - at least for Cognos 10.1.1 FP2 - IBM Assured me this is fixed in 10.2...