​We had an issue where the SQL column xyz was removed from the database, but the COGNOS model referenced column xyz. Clients were getting the error XQE-PLN-0012 The column 'xyz' could not be found in the model. We ran a SQL script to add back the missing column. After rerunning the erroneous report some clients saw the fix right away, some had to log off COGNOS and back on, some had to restart the service/server. 

On my test machine I logged on and back on, tried Chrome instead of IE, delete all history, delete all internet temporary files, then finally just restarted the server in frustration.

What is the proper way, with the least amount of disruption, to force the model to recognize a database change?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

#CognosAnalyticswithWatson

FM Models will need to be updated and the package refreshed for the database change to be included.

------------------------------
NORBERT Bracke
IBM
------------------------------

Original Message:
Sent: Fri May 01, 2020 12:38 PM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​We had an issue where the SQL column xyz was removed from the database, but the COGNOS model referenced column xyz. Clients were getting the error XQE-PLN-0012 The column 'xyz' could not be found in the model. We ran a SQL script to add back the missing column. After rerunning the erroneous report some clients saw the fix right away, some had to log off COGNOS and back on, some had to restart the service/server. 

On my test machine I logged on and back on, tried Chrome instead of IE, delete all history, delete all internet temporary files, then finally just restarted the server in frustration.

What is the proper way, with the least amount of disruption, to force the model to recognize a database change?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

#CognosAnalyticswithWatson

The column xyz was already in the FM model. That is why we got the ​error "XQE-PLN-0012 The column 'xyz' could not be found in the model". I know the error is worded strangely. But xyz is in the model, but was not in the database. So we add column xyz to the database. But now we are having a hard time getting Cognos to recognize xyz. If we do a custom SQL query "select xyz from table1" it returns values. But even if a new report is created and the model that references xyz the error is still thrown. Log off, delete all internet objects, use a different browser, set use local cache to NO, and the model still says that xyz does not exist in the database. Certainly there is something that we can do other than restart Cognos. (although I am not even sure that will do it. I restarted my development server to get the model to recognize the database change.)

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

Original Message:
Sent: Fri May 01, 2020 12:38 PM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​We had an issue where the SQL column xyz was removed from the database, but the COGNOS model referenced column xyz. Clients were getting the error XQE-PLN-0012 The column 'xyz' could not be found in the model. We ran a SQL script to add back the missing column. After rerunning the erroneous report some clients saw the fix right away, some had to log off COGNOS and back on, some had to restart the service/server. 

On my test machine I logged on and back on, tried Chrome instead of IE, delete all history, delete all internet temporary files, then finally just restarted the server in frustration.

What is the proper way, with the least amount of disruption, to force the model to recognize a database change?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

#CognosAnalyticswithWatson

Have you tested the query subject in FM?

------------------------------
NORBERT Bracke
IBM
------------------------------

Original Message:
Sent: Mon May 04, 2020 08:20 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

The column xyz was already in the FM model. That is why we got the ​error "XQE-PLN-0012 The column 'xyz' could not be found in the model". I know the error is worded strangely. But xyz is in the model, but was not in the database. So we add column xyz to the database. But now we are having a hard time getting Cognos to recognize xyz. If we do a custom SQL query "select xyz from table1" it returns values. But even if a new report is created and the model that references xyz the error is still thrown. Log off, delete all internet objects, use a different browser, set use local cache to NO, and the model still says that xyz does not exist in the database. Certainly there is something that we can do other than restart Cognos. (although I am not even sure that will do it. I restarted my development server to get the model to recognize the database change.)

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Fri May 01, 2020 12:38 PM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​We had an issue where the SQL column xyz was removed from the database, but the COGNOS model referenced column xyz. Clients were getting the error XQE-PLN-0012 The column 'xyz' could not be found in the model. We ran a SQL script to add back the missing column. After rerunning the erroneous report some clients saw the fix right away, some had to log off COGNOS and back on, some had to restart the service/server. 

On my test machine I logged on and back on, tried Chrome instead of IE, delete all history, delete all internet temporary files, then finally just restarted the server in frustration.

What is the proper way, with the least amount of disruption, to force the model to recognize a database change?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

#CognosAnalyticswithWatson

​I am not an FM person but I looked in the model.xml at the actual query and it references column xyz. Once I restarted my development server the report worked. Also we support many Cognos instances. Client care is telling me that for some clients that after running the sql script to add the xyz column they just log off and back on Cognos and the report now works. BUt for others it is not so easy. Thinking of what can I restart (besides cognos or the server) or clear to get this database change to work with Cognos.

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

Original Message:
Sent: Mon May 04, 2020 08:27 AM
From: NORBERT Bracke
Subject: How to force the model to recognize a database change

Have you tested the query subject in FM?

------------------------------
NORBERT Bracke
IBM

Original Message:
Sent: Mon May 04, 2020 08:20 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

The column xyz was already in the FM model. That is why we got the ​error "XQE-PLN-0012 The column 'xyz' could not be found in the model". I know the error is worded strangely. But xyz is in the model, but was not in the database. So we add column xyz to the database. But now we are having a hard time getting Cognos to recognize xyz. If we do a custom SQL query "select xyz from table1" it returns values. But even if a new report is created and the model that references xyz the error is still thrown. Log off, delete all internet objects, use a different browser, set use local cache to NO, and the model still says that xyz does not exist in the database. Certainly there is something that we can do other than restart Cognos. (although I am not even sure that will do it. I restarted my development server to get the model to recognize the database change.)

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Fri May 01, 2020 12:38 PM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​We had an issue where the SQL column xyz was removed from the database, but the COGNOS model referenced column xyz. Clients were getting the error XQE-PLN-0012 The column 'xyz' could not be found in the model. We ran a SQL script to add back the missing column. After rerunning the erroneous report some clients saw the fix right away, some had to log off COGNOS and back on, some had to restart the service/server. 

On my test machine I logged on and back on, tried Chrome instead of IE, delete all history, delete all internet temporary files, then finally just restarted the server in frustration.

What is the proper way, with the least amount of disruption, to force the model to recognize a database change?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

#CognosAnalyticswithWatson

So … does anyone know how to force Cognos FM packages / models to​ recognize a database change? Getting a report error due to a missing column on the database, but the error on the database has been correct. But the reports are still giving the error - even new reports. The error clears if we restart Cognos. So is there something that we can clear or restart that will clear the error but not be as disruptive as restarting the Cognos service?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

Original Message:
Sent: Mon May 04, 2020 08:45 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​I am not an FM person but I looked in the model.xml at the actual query and it references column xyz. Once I restarted my development server the report worked. Also we support many Cognos instances. Client care is telling me that for some clients that after running the sql script to add the xyz column they just log off and back on Cognos and the report now works. BUt for others it is not so easy. Thinking of what can I restart (besides cognos or the server) or clear to get this database change to work with Cognos.

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Mon May 04, 2020 08:27 AM
From: NORBERT Bracke
Subject: How to force the model to recognize a database change

Have you tested the query subject in FM?

------------------------------
NORBERT Bracke
IBM

Original Message:
Sent: Mon May 04, 2020 08:20 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

The column xyz was already in the FM model. That is why we got the ​error "XQE-PLN-0012 The column 'xyz' could not be found in the model". I know the error is worded strangely. But xyz is in the model, but was not in the database. So we add column xyz to the database. But now we are having a hard time getting Cognos to recognize xyz. If we do a custom SQL query "select xyz from table1" it returns values. But even if a new report is created and the model that references xyz the error is still thrown. Log off, delete all internet objects, use a different browser, set use local cache to NO, and the model still says that xyz does not exist in the database. Certainly there is something that we can do other than restart Cognos. (although I am not even sure that will do it. I restarted my development server to get the model to recognize the database change.)

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Fri May 01, 2020 12:38 PM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​We had an issue where the SQL column xyz was removed from the database, but the COGNOS model referenced column xyz. Clients were getting the error XQE-PLN-0012 The column 'xyz' could not be found in the model. We ran a SQL script to add back the missing column. After rerunning the erroneous report some clients saw the fix right away, some had to log off COGNOS and back on, some had to restart the service/server. 

On my test machine I logged on and back on, tried Chrome instead of IE, delete all history, delete all internet temporary files, then finally just restarted the server in frustration.

What is the proper way, with the least amount of disruption, to force the model to recognize a database change?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

#CognosAnalyticswithWatson

Have you tried to repoint the package from RS from the Properties i.e Replace Package and check if the report spec validates fine.
Sometimes you will need to open the report in RS in order for it validate against the package
Thanks

------------------------------
Sanjay Chakravarty
------------------------------

Original Message:
Sent: Wed May 06, 2020 09:31 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

So … does anyone know how to force Cognos FM packages / models to​ recognize a database change? Getting a report error due to a missing column on the database, but the error on the database has been correct. But the reports are still giving the error - even new reports. The error clears if we restart Cognos. So is there something that we can clear or restart that will clear the error but not be as disruptive as restarting the Cognos service?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Mon May 04, 2020 08:45 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​I am not an FM person but I looked in the model.xml at the actual query and it references column xyz. Once I restarted my development server the report worked. Also we support many Cognos instances. Client care is telling me that for some clients that after running the sql script to add the xyz column they just log off and back on Cognos and the report now works. BUt for others it is not so easy. Thinking of what can I restart (besides cognos or the server) or clear to get this database change to work with Cognos.

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Mon May 04, 2020 08:27 AM
From: NORBERT Bracke
Subject: How to force the model to recognize a database change

Have you tested the query subject in FM?

------------------------------
NORBERT Bracke
IBM

Original Message:
Sent: Mon May 04, 2020 08:20 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

The column xyz was already in the FM model. That is why we got the ​error "XQE-PLN-0012 The column 'xyz' could not be found in the model". I know the error is worded strangely. But xyz is in the model, but was not in the database. So we add column xyz to the database. But now we are having a hard time getting Cognos to recognize xyz. If we do a custom SQL query "select xyz from table1" it returns values. But even if a new report is created and the model that references xyz the error is still thrown. Log off, delete all internet objects, use a different browser, set use local cache to NO, and the model still says that xyz does not exist in the database. Certainly there is something that we can do other than restart Cognos. (although I am not even sure that will do it. I restarted my development server to get the model to recognize the database change.)

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Fri May 01, 2020 12:38 PM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​We had an issue where the SQL column xyz was removed from the database, but the COGNOS model referenced column xyz. Clients were getting the error XQE-PLN-0012 The column 'xyz' could not be found in the model. We ran a SQL script to add back the missing column. After rerunning the erroneous report some clients saw the fix right away, some had to log off COGNOS and back on, some had to restart the service/server. 

On my test machine I logged on and back on, tried Chrome instead of IE, delete all history, delete all internet temporary files, then finally just restarted the server in frustration.

What is the proper way, with the least amount of disruption, to force the model to recognize a database change?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

#CognosAnalyticswithWatson

​@Sanjay Chakravarty - after making the database change even a new report still throws the old error. So I don't think repointing the package back and forth would help.
​

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

Original Message:
Sent: Wed May 06, 2020 09:55 AM
From: Sanjay Chakravarty
Subject: How to force the model to recognize a database change

Have you tried to repoint the package from RS from the Properties i.e Replace Package and check if the report spec validates fine.
Sometimes you will need to open the report in RS in order for it validate against the package
Thanks

------------------------------
Sanjay Chakravarty

Original Message:
Sent: Wed May 06, 2020 09:31 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

So … does anyone know how to force Cognos FM packages / models to​ recognize a database change? Getting a report error due to a missing column on the database, but the error on the database has been correct. But the reports are still giving the error - even new reports. The error clears if we restart Cognos. So is there something that we can clear or restart that will clear the error but not be as disruptive as restarting the Cognos service?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Mon May 04, 2020 08:45 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​I am not an FM person but I looked in the model.xml at the actual query and it references column xyz. Once I restarted my development server the report worked. Also we support many Cognos instances. Client care is telling me that for some clients that after running the sql script to add the xyz column they just log off and back on Cognos and the report now works. BUt for others it is not so easy. Thinking of what can I restart (besides cognos or the server) or clear to get this database change to work with Cognos.

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Mon May 04, 2020 08:27 AM
From: NORBERT Bracke
Subject: How to force the model to recognize a database change

Have you tested the query subject in FM?

------------------------------
NORBERT Bracke
IBM

Original Message:
Sent: Mon May 04, 2020 08:20 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

The column xyz was already in the FM model. That is why we got the ​error "XQE-PLN-0012 The column 'xyz' could not be found in the model". I know the error is worded strangely. But xyz is in the model, but was not in the database. So we add column xyz to the database. But now we are having a hard time getting Cognos to recognize xyz. If we do a custom SQL query "select xyz from table1" it returns values. But even if a new report is created and the model that references xyz the error is still thrown. Log off, delete all internet objects, use a different browser, set use local cache to NO, and the model still says that xyz does not exist in the database. Certainly there is something that we can do other than restart Cognos. (although I am not even sure that will do it. I restarted my development server to get the model to recognize the database change.)

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Fri May 01, 2020 12:38 PM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​We had an issue where the SQL column xyz was removed from the database, but the COGNOS model referenced column xyz. Clients were getting the error XQE-PLN-0012 The column 'xyz' could not be found in the model. We ran a SQL script to add back the missing column. After rerunning the erroneous report some clients saw the fix right away, some had to log off COGNOS and back on, some had to restart the service/server. 

On my test machine I logged on and back on, tried Chrome instead of IE, delete all history, delete all internet temporary files, then finally just restarted the server in frustration.

What is the proper way, with the least amount of disruption, to force the model to recognize a database change?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

#CognosAnalyticswithWatson

​@Sanjay Chakravarty - after the database change, even a new report still throws the error. So I do not think that repointing the package would help.​

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

Original Message:
Sent: Wed May 06, 2020 09:55 AM
From: Sanjay Chakravarty
Subject: How to force the model to recognize a database change

Have you tried to repoint the package from RS from the Properties i.e Replace Package and check if the report spec validates fine.
Sometimes you will need to open the report in RS in order for it validate against the package
Thanks

------------------------------
Sanjay Chakravarty

Original Message:
Sent: Wed May 06, 2020 09:31 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

So … does anyone know how to force Cognos FM packages / models to​ recognize a database change? Getting a report error due to a missing column on the database, but the error on the database has been correct. But the reports are still giving the error - even new reports. The error clears if we restart Cognos. So is there something that we can clear or restart that will clear the error but not be as disruptive as restarting the Cognos service?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Mon May 04, 2020 08:45 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​I am not an FM person but I looked in the model.xml at the actual query and it references column xyz. Once I restarted my development server the report worked. Also we support many Cognos instances. Client care is telling me that for some clients that after running the sql script to add the xyz column they just log off and back on Cognos and the report now works. BUt for others it is not so easy. Thinking of what can I restart (besides cognos or the server) or clear to get this database change to work with Cognos.

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Mon May 04, 2020 08:27 AM
From: NORBERT Bracke
Subject: How to force the model to recognize a database change

Have you tested the query subject in FM?

------------------------------
NORBERT Bracke
IBM

Original Message:
Sent: Mon May 04, 2020 08:20 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

The column xyz was already in the FM model. That is why we got the ​error "XQE-PLN-0012 The column 'xyz' could not be found in the model". I know the error is worded strangely. But xyz is in the model, but was not in the database. So we add column xyz to the database. But now we are having a hard time getting Cognos to recognize xyz. If we do a custom SQL query "select xyz from table1" it returns values. But even if a new report is created and the model that references xyz the error is still thrown. Log off, delete all internet objects, use a different browser, set use local cache to NO, and the model still says that xyz does not exist in the database. Certainly there is something that we can do other than restart Cognos. (although I am not even sure that will do it. I restarted my development server to get the model to recognize the database change.)

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Fri May 01, 2020 12:38 PM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​We had an issue where the SQL column xyz was removed from the database, but the COGNOS model referenced column xyz. Clients were getting the error XQE-PLN-0012 The column 'xyz' could not be found in the model. We ran a SQL script to add back the missing column. After rerunning the erroneous report some clients saw the fix right away, some had to log off COGNOS and back on, some had to restart the service/server. 

On my test machine I logged on and back on, tried Chrome instead of IE, delete all history, delete all internet temporary files, then finally just restarted the server in frustration.

What is the proper way, with the least amount of disruption, to force the model to recognize a database change?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

#CognosAnalyticswithWatson

Try deleting the RTM models
located on app servers in <install>/data/cqe/RTModels

------------------------------
NORBERT Bracke
IBM
------------------------------

Original Message:
Sent: Wed May 06, 2020 09:31 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

So … does anyone know how to force Cognos FM packages / models to​ recognize a database change? Getting a report error due to a missing column on the database, but the error on the database has been correct. But the reports are still giving the error - even new reports. The error clears if we restart Cognos. So is there something that we can clear or restart that will clear the error but not be as disruptive as restarting the Cognos service?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Mon May 04, 2020 08:45 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​I am not an FM person but I looked in the model.xml at the actual query and it references column xyz. Once I restarted my development server the report worked. Also we support many Cognos instances. Client care is telling me that for some clients that after running the sql script to add the xyz column they just log off and back on Cognos and the report now works. BUt for others it is not so easy. Thinking of what can I restart (besides cognos or the server) or clear to get this database change to work with Cognos.

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Mon May 04, 2020 08:27 AM
From: NORBERT Bracke
Subject: How to force the model to recognize a database change

Have you tested the query subject in FM?

------------------------------
NORBERT Bracke
IBM

Original Message:
Sent: Mon May 04, 2020 08:20 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

The column xyz was already in the FM model. That is why we got the ​error "XQE-PLN-0012 The column 'xyz' could not be found in the model". I know the error is worded strangely. But xyz is in the model, but was not in the database. So we add column xyz to the database. But now we are having a hard time getting Cognos to recognize xyz. If we do a custom SQL query "select xyz from table1" it returns values. But even if a new report is created and the model that references xyz the error is still thrown. Log off, delete all internet objects, use a different browser, set use local cache to NO, and the model still says that xyz does not exist in the database. Certainly there is something that we can do other than restart Cognos. (although I am not even sure that will do it. I restarted my development server to get the model to recognize the database change.)

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Fri May 01, 2020 12:38 PM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​We had an issue where the SQL column xyz was removed from the database, but the COGNOS model referenced column xyz. Clients were getting the error XQE-PLN-0012 The column 'xyz' could not be found in the model. We ran a SQL script to add back the missing column. After rerunning the erroneous report some clients saw the fix right away, some had to log off COGNOS and back on, some had to restart the service/server. 

On my test machine I logged on and back on, tried Chrome instead of IE, delete all history, delete all internet temporary files, then finally just restarted the server in frustration.

What is the proper way, with the least amount of disruption, to force the model to recognize a database change?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

#CognosAnalyticswithWatson

@NORBERT Bracke - I will try that. We use DQM and read that they do not use RTModels but use

ibm\cognos\Bankxx\data\mfw4j\PMCs. Wonder though if the current pmc or rtmodels that are in use would be locked by the system. I also started thinking about maybe redeploying the package. That might work. And then a coworker said to clear the cache by taking these steps https://www.ibm.com/support/knowledgecenter/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.ug_cra.doc/t_asg_clear_qs_cache.html

unfortunately I cannot take any of these three steps to see which one might work as the issue has been solved on my development machine. but I will let client care know and see what they say works.

​​

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

Original Message:
Sent: Thu May 07, 2020 06:55 AM
From: NORBERT Bracke
Subject: How to force the model to recognize a database change

Try deleting the RTM models
located on app servers in <install>/data/cqe/RTModels

------------------------------
NORBERT Bracke
IBM

Original Message:
Sent: Wed May 06, 2020 09:31 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

So … does anyone know how to force Cognos FM packages / models to​ recognize a database change? Getting a report error due to a missing column on the database, but the error on the database has been correct. But the reports are still giving the error - even new reports. The error clears if we restart Cognos. So is there something that we can clear or restart that will clear the error but not be as disruptive as restarting the Cognos service?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Mon May 04, 2020 08:45 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​I am not an FM person but I looked in the model.xml at the actual query and it references column xyz. Once I restarted my development server the report worked. Also we support many Cognos instances. Client care is telling me that for some clients that after running the sql script to add the xyz column they just log off and back on Cognos and the report now works. BUt for others it is not so easy. Thinking of what can I restart (besides cognos or the server) or clear to get this database change to work with Cognos.

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Mon May 04, 2020 08:27 AM
From: NORBERT Bracke
Subject: How to force the model to recognize a database change

Have you tested the query subject in FM?

------------------------------
NORBERT Bracke
IBM

Original Message:
Sent: Mon May 04, 2020 08:20 AM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

The column xyz was already in the FM model. That is why we got the ​error "XQE-PLN-0012 The column 'xyz' could not be found in the model". I know the error is worded strangely. But xyz is in the model, but was not in the database. So we add column xyz to the database. But now we are having a hard time getting Cognos to recognize xyz. If we do a custom SQL query "select xyz from table1" it returns values. But even if a new report is created and the model that references xyz the error is still thrown. Log off, delete all internet objects, use a different browser, set use local cache to NO, and the model still says that xyz does not exist in the database. Certainly there is something that we can do other than restart Cognos. (although I am not even sure that will do it. I restarted my development server to get the model to recognize the database change.)

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS

Original Message:
Sent: Fri May 01, 2020 12:38 PM
From: brenda grossnickle
Subject: How to force the model to recognize a database change

​We had an issue where the SQL column xyz was removed from the database, but the COGNOS model referenced column xyz. Clients were getting the error XQE-PLN-0012 The column 'xyz' could not be found in the model. We ran a SQL script to add back the missing column. After rerunning the erroneous report some clients saw the fix right away, some had to log off COGNOS and back on, some had to restart the service/server. 

On my test machine I logged on and back on, tried Chrome instead of IE, delete all history, delete all internet temporary files, then finally just restarted the server in frustration.

What is the proper way, with the least amount of disruption, to force the model to recognize a database change?

------------------------------
brenda grossnickle
BI Programmer Analyst
FIS
------------------------------

#CognosAnalyticswithWatson