New Data Sources in FM

[ghostraider]

Hi All, I have an existing model and i am trying to add new query subjects to it. I am importing metadata from the data source and this data source is already created in Cognos Connection. But when i add new query subjects by importing metadata new data sources are showing up in framework. I don't have them in Cognos Connection. For example i have a data source named 'LIB' in Framework and when i add a query subject its creating another data source 'LIB1' and when i test it, it succeeds. These new data sources are getting created in FM directly and if i add more than two subjects like this some of my existing subjects are getting hidden in the Project Viewer list. They are not deleted but just hidden because i can see them in the explorer view. As i mentioned before this is only happening for new subjects which are created using data source and not for model query subjects. Please let me know if anyone has faced something like this.

Thank you for your time.

[ghostraider]

Ok, i have done some further testing and i see this is happening when i have my production database in the content manager. When i change it to test everything seems to work well. Recently, there was some upgrade work done on the Prod Database, does it have to do anything with it? Please let me know.

Thanks

[blom0344]

Yes, Cognos introduces a new datasource by default , adding a suffix 1 to the datasource name.
You can very easily correct this by editing the sql of the imported objects:

select * from [datasource1].[sometable]

to

select * from [datasource].[sometable]

After correction simply delete datasource1 from the framework..

[ghostraider]

Hi Blom0344, thank you very much for your response. But i also see some query subjects suddenly disappear from the list even though i can see them in the explorer. This happens when i create a new query subject. Any ideas about this issue? Please let me know.

Thank You once again.

[blom0344]

'disappear from the list' ?
If they are still visible in explorer, then they must be available in the framework somewhere.
Did try for a search action in the namespace concerned?