Error Adding column to package

[kc9400]

I'm trying to add a column to the SQL in a package but when I do so it says the column was not found.

If I search through the tables and check all the items available it is available.

Am I missing something simple?

Thanks

[kc9400]

Ok, right after I posted this I found a solution.

http://www-01.ibm.com/support/docview.wss?uid=swg21342606


I used:

2. - Not recommended because the metadata has to be retrieved every time:
In Framework Manager, from the menu "Project", select "Edit Governors ..." and ensure that "Allow enhanced model portability at Run Time" is checked. (Activating this setting can have a negative impact on the performance)




What would be the major drawbacks of doing this?

[bdbits]

From the FM help (copied below), I gather it is going to cause extra hits to the database. Did the "preferred" option from your linked article not work? I would use that approach anyway, personally.


Allow Enhanced Model Portability at Run Time
This governor is selected upon initial upgrade of a Cognos ReportNet 1.x model. It prevents rigid enforcement of data types so that an IBM Cognos model can function as a ReportNet 1.x model until you update the data types in the metadata. After you have verified that the model has been upgraded successfully, clear this governor.

Other than for initial upgrade, there are limited uses for this governor. For example, you have created a model for use with a data source and you want to run it against a different data source. The new data source must be structurally similar to the original data source, and the database schema must be the same between the two data sources. If you select this governor, IBM Cognos BI retrieves metadata from the data source and caches it instead of using the metadata already cached in the model. When you have completed modifying and testing the model against the new data source, clear this governor.

[bus_pass_man]

Is there any particular reason why you're writing SQL?   You do know that will cause unnecessary metadata callbacks.   (plus the problem you're encountering).   

The query that you've written will get generated automatically in the business layer etc. if the objects in your projection list are included in a query (either by being in a model query subject or being selected and tested).   

[Michael75]

Just one thing to add to the excellent replies already given.

I'm pretty sure I once had the same problem as kc9400. I checked "Allow enhanced model portability at Run Time", imported my column, then unchecked this option and republished. This avoids taking a performance hit.

[kc9400]

Hi, thanks for the replies.

Yeah I did the same as yourself Michael. Allowing it, publishing, then disabling it so that seems to have done the trick. It was the quickest fix at the time so I went with that option.

After I looked a little further it was only one report out of the 300 odd that I manage which it had any effect on.

bus_pass: A lot of the packages that have been built use SQL and I've yet to get round to sorting them all out. Unfortunately the system was running for a couple of years before I started.