IBM Business Analytics

Hello all,

After a framework change, we get following error in our datamodule: XQE-PLN-0248 The column 'column_xxx' of 'table_xxx' could not be found in the model. Possibly caused by out-of-date query subject definition: 'table_xxx'

This happened when we changed in an existing query-item the underlying database column.

E.g query-item YYY used to point to database column 'aaa', which was changed to database column 'xxx' (from the same table).

The package itself doesn't have this problem. I can perfectly report on the changed query-item. When I make a new data-module based on the same package, it also works fine.

I tried to relink the source package but this doesn't change anything. The error keeps popping up. And a simple 'refresh' of the package in the datamodule seems not to be available.

Recreating the datamodule from scratch might be an option but not sure if all reports based on this datamodule might still work because the object identifier might not be the same anymore.

Has anyone experienced the same problem and managed to solve this?

We are using Cognos v11.2.2

Regards,

Danny Casteels

I came across this same issue today.  This was the only thing I found on Google that hit the same issue. So whilst an old question, I thought I would update this in case anyone has the same issue.  

In my case I had an FM package that I had bought into a DM module.  I updated the FM model to bring in a new column into an existing query. I published the updated FM package t o Cognos.

If I used the Data Module that contained the package I could see the new column within the packages query. However, using that column caused the issue seen posted above. 

XQE-PLN-0248 The column 'column_xxx' of 'table_xxx' could not be found in the model. Possibly caused by out-of-date query subject definition: 'table_xxx'

• A report based directly on the FM package has no issues with the new column.
• A new DM based on the FM package has no issues with the new column.
• Only the existing DM had an issue with the new column.

My instance of the issue was caused by the following.

1. Both the FM and DM were using tables from the same schema.
2. In the DM datasoures, there was the FM package and the schema.
3. The table in question was only modelled in FM.
4. Whilst the DM was not using the table, using the DM 'reload metadata' corrected the issue.
5. It looks like the DM was getting confused as it could see the tables in both the schema and the package 

Hello all,

After a framework change, we get following error in our datamodule: XQE-PLN-0248 The column 'column_xxx' of 'table_xxx' could not be found in the model. Possibly caused by out-of-date query subject definition: 'table_xxx'

This happened when we changed in an existing query-item the underlying database column.

E.g query-item YYY used to point to database column 'aaa', which was changed to database column 'xxx' (from the same table).

The package itself doesn't have this problem. I can perfectly report on the changed query-item. When I make a new data-module based on the same package, it also works fine.

I tried to relink the source package but this doesn't change anything. The error keeps popping up. And a simple 'refresh' of the package in the datamodule seems not to be available.

Recreating the datamodule from scratch might be an option but not sure if all reports based on this datamodule might still work because the object identifier might not be the same anymore.

Has anyone experienced the same problem and managed to solve this?

We are using Cognos v11.2.2

Regards,

Danny Casteels

What version are you using at this time?  We are on 12.0.3.  I expect it still exists but we will check it out in the new version as time permits. 

I came across this same issue today.  This was the only thing I found on Google that hit the same issue. So whilst an old question, I thought I would update this in case anyone has the same issue.  

In my case I had an FM package that I had bought into a DM module.  I updated the FM model to bring in a new column into an existing query. I published the updated FM package t o Cognos.

If I used the Data Module that contained the package I could see the new column within the packages query. However, using that column caused the issue seen posted above. 

XQE-PLN-0248 The column 'column_xxx' of 'table_xxx' could not be found in the model. Possibly caused by out-of-date query subject definition: 'table_xxx'

• A report based directly on the FM package has no issues with the new column.
• A new DM based on the FM package has no issues with the new column.
• Only the existing DM had an issue with the new column.

My instance of the issue was caused by the following.

1. Both the FM and DM were using tables from the same schema.
2. In the DM datasoures, there was the FM package and the schema.
3. The table in question was only modelled in FM.
4. Whilst the DM was not using the table, using the DM 'reload metadata' corrected the issue.
5. It looks like the DM was getting confused as it could see the tables in both the schema and the package 

Hello all,

After a framework change, we get following error in our datamodule: XQE-PLN-0248 The column 'column_xxx' of 'table_xxx' could not be found in the model. Possibly caused by out-of-date query subject definition: 'table_xxx'

This happened when we changed in an existing query-item the underlying database column.

E.g query-item YYY used to point to database column 'aaa', which was changed to database column 'xxx' (from the same table).

The package itself doesn't have this problem. I can perfectly report on the changed query-item. When I make a new data-module based on the same package, it also works fine.

I tried to relink the source package but this doesn't change anything. The error keeps popping up. And a simple 'refresh' of the package in the datamodule seems not to be available.

Recreating the datamodule from scratch might be an option but not sure if all reports based on this datamodule might still work because the object identifier might not be the same anymore.

Has anyone experienced the same problem and managed to solve this?

We are using Cognos v11.2.2

Regards,

Danny Casteels