I get to quote my immortal prose:
"In Cognos Analytics 11.1.6 .... in addition to [the] existing column dependency functionality, new automatically generated column dependency groups will be created in your modules, supplementing your existing manually-modelled column dependency.

These automatically generated column dependency groups are based on the columns of the primary key of a data base table. If the source table contains a primary key and the query subject has not had column dependency defined in it, then they are generated in the query subject.


https://community.ibm.com/community/user/businessanalytics/blogs/ian-henderson1/2020/04/30/migration-of-cognos-query-engine-primary-key-query

Accordingly, my supposition is that your table has a primary key defined for it.

You state that no column dependency exists. When you select the table and choose view column dependency from the context menu, what do you see?


Just to confirm,

1. You upgraded to 11.1.6
2. Everything with your module was fine.
3. You deleted a table.
4. You started to get errors.

or

1. You upgraded to 11.1.6
2. You started to get validation errors.

or

1. You upgraded to 11.1.6
2. Everything with your module was fine.
3. You deleted a column
4. You started to get errors.

or

Some other set of circumstances which you would need to describe.  It is possible that you have omitted actions which you performed because you think that they might not be relevant.


The error you mention complains that a column dependency group is using a column as its key but the column does not exist.   The first thing you need to do is investigate the areas around the thing being complained about.

Does the column exist?

Has the table been altered in the data base?

Did you modify the query subject?

Does the column dependency accurately reflect the primary key?

Is there anything special or unusual about the primary key?

Has your actions changed the count of validation errors? 

Other questions could spring to mind once I have confirmed the circumstances in which you encountered the problem.

Just as a rule of thumb, when you are trying to troubleshoot a problem you need to be conscious of the possible consequences of actions. Subsequently, actions should not be entered into unless and until you have understood the problem and understood what any proposed action will do. This is especially the case for possibly destructive actions.

Hope that helps.

Error: MSR-VRF-1106 The table "TABLE NAME" has an invalid column dependency that references key column "COLUMS NAME" which is missing.

Any Suggestions ? 

Thank you for such a detailed answer!

what happened :

We upgraded to 11.1.6

About a month ago I built a new Data Module

The initial table was replaced and the old table had to be removed  

A day after the table was removed suddenly many error messages  all  have same error just referring to different fields in the table

Q: Does the column exist? A: Not anymore

Has the table been altered in the database?

Q: Did you modify the query subject? A: No

Q: Does the column dependency accurately reflect the primary key? I Can not see any column dependency, perhaps I am not looking in the correct place ? However I can not find any place to find if a column dependency exits?

Q: Is there anything special or unusual about the primary key? I do not see anything unusual,  however perhaps I am looking on the wrong location

Q: Has your actions changed the count of validation errors? A: No

Q: Other questions could spring to mind once I have confirmed the circumstances in which you encountered the problem.

I get to quote my immortal prose:
"In Cognos Analytics 11.1.6 .... in addition to [the] existing column dependency functionality, new automatically generated column dependency groups will be created in your modules, supplementing your existing manually-modelled column dependency.

These automatically generated column dependency groups are based on the columns of the primary key of a data base table. If the source table contains a primary key and the query subject has not had column dependency defined in it, then they are generated in the query subject.


https://community.ibm.com/community/user/businessanalytics/blogs/ian-henderson1/2020/04/30/migration-of-cognos-query-engine-primary-key-query

Accordingly, my supposition is that your table has a primary key defined for it.

You state that no column dependency exists. When you select the table and choose view column dependency from the context menu, what do you see?


Just to confirm,

1. You upgraded to 11.1.6
2. Everything with your module was fine.
3. You deleted a table.
4. You started to get errors.

or

1. You upgraded to 11.1.6
2. You started to get validation errors.

or

1. You upgraded to 11.1.6
2. Everything with your module was fine.
3. You deleted a column
4. You started to get errors.

or

Some other set of circumstances which you would need to describe.  It is possible that you have omitted actions which you performed because you think that they might not be relevant.


The error you mention complains that a column dependency group is using a column as its key but the column does not exist.   The first thing you need to do is investigate the areas around the thing being complained about.

Does the column exist?

Has the table been altered in the data base?

Did you modify the query subject?

Does the column dependency accurately reflect the primary key?

Is there anything special or unusual about the primary key?

Has your actions changed the count of validation errors? 

Other questions could spring to mind once I have confirmed the circumstances in which you encountered the problem.

Just as a rule of thumb, when you are trying to troubleshoot a problem you need to be conscious of the possible consequences of actions. Subsequently, actions should not be entered into unless and until you have understood the problem and understood what any proposed action will do. This is especially the case for possibly destructive actions.

Hope that helps.

Error: MSR-VRF-1106 The table "TABLE NAME" has an invalid column dependency that references key column "COLUMS NAME" which is missing.

Any Suggestions ? 

To view the column dependency diagram, select the table and choose view column dependency from the context menu.

Just to confirm, after you changed the table in the data base did you reload the metadata in the schema?  My supposition is that you didn't.  I think that's a usability issue of some sort; the schema metadata workflow very much assumes that the metadata will be stable.  

My hypothesis is this:  as we know, when you upgrade to 11.1.6 or higher from a release prior to that, the schema metadata has added to it the primary key information in the form of column dependency. In your case this was based on your old table.  Validation can't find stuff in the rest of the metadata which is contained in the column dependency and you end up in the pickle which you have ended up in.

Create a new data module and import the table.  Verify both that the errors occur and that the column dependency refers to columns which no longer exist in the table. This will test my hypothesis.

If that is the case, then it might be a simple-ish (unless you have data security defined) matter of reloading the metadata of the schema and then re-adding the table to the module. (you would not need to delete it from the module I think.)

Thank you for such a detailed answer!

what happened :

We upgraded to 11.1.6

About a month ago I built a new Data Module

The initial table was replaced and the old table had to be removed  

A day after the table was removed suddenly many error messages  all  have same error just referring to different fields in the table

Q: Does the column exist? A: Not anymore

Has the table been altered in the database?

Q: Did you modify the query subject? A: No

Q: Does the column dependency accurately reflect the primary key? I Can not see any column dependency, perhaps I am not looking in the correct place ? However I can not find any place to find if a column dependency exits?

Q: Is there anything special or unusual about the primary key? I do not see anything unusual,  however perhaps I am looking on the wrong location

Q: Has your actions changed the count of validation errors? A: No

Q: Other questions could spring to mind once I have confirmed the circumstances in which you encountered the problem.

I get to quote my immortal prose:
"In Cognos Analytics 11.1.6 .... in addition to [the] existing column dependency functionality, new automatically generated column dependency groups will be created in your modules, supplementing your existing manually-modelled column dependency.

These automatically generated column dependency groups are based on the columns of the primary key of a data base table. If the source table contains a primary key and the query subject has not had column dependency defined in it, then they are generated in the query subject.


https://community.ibm.com/community/user/businessanalytics/blogs/ian-henderson1/2020/04/30/migration-of-cognos-query-engine-primary-key-query

Accordingly, my supposition is that your table has a primary key defined for it.

You state that no column dependency exists. When you select the table and choose view column dependency from the context menu, what do you see?


Just to confirm,

1. You upgraded to 11.1.6
2. Everything with your module was fine.
3. You deleted a table.
4. You started to get errors.

or

1. You upgraded to 11.1.6
2. You started to get validation errors.

or

1. You upgraded to 11.1.6
2. Everything with your module was fine.
3. You deleted a column
4. You started to get errors.

or

Some other set of circumstances which you would need to describe.  It is possible that you have omitted actions which you performed because you think that they might not be relevant.


The error you mention complains that a column dependency group is using a column as its key but the column does not exist.   The first thing you need to do is investigate the areas around the thing being complained about.

Does the column exist?

Has the table been altered in the data base?

Did you modify the query subject?

Does the column dependency accurately reflect the primary key?

Is there anything special or unusual about the primary key?

Has your actions changed the count of validation errors? 

Other questions could spring to mind once I have confirmed the circumstances in which you encountered the problem.

Just as a rule of thumb, when you are trying to troubleshoot a problem you need to be conscious of the possible consequences of actions. Subsequently, actions should not be entered into unless and until you have understood the problem and understood what any proposed action will do. This is especially the case for possibly destructive actions.

Hope that helps.

Error: MSR-VRF-1106 The table "TABLE NAME" has an invalid column dependency that references key column "COLUMS NAME" which is missing.

Any Suggestions ?