problem when change in datatype/data length

[umag]

Hi
I have a catalog which was prepared sometime back but recently there are changes in database and some field lengths were changed and some datatypes were changed and my reports starts complaining. when I went into tables and verified them, those specific columns were invalid. how to deal with this situation. I am sure there is a way to deal the situation but seems I am missing some clue here.

thanks in advance

 

[Prasad678]

Hi,
I don't think there is a solution for this. U have to once again add the tables or the columns of the tables.

If u find any solution do post it.

Prasad.

 

[Recce]

I agree with Prasad. You will have to replace the tables or columns in the catalog with the latest ones before it will work. :->

 

[umag]

Thanks for the response prasad/recce.

I have that database column changed from varchar to number and is in almost all the tables of the catalog so have to prepare/change all the reports again. wondering people might come across this problem with some different experiance. wanted to know how different people dealt with this situation. please post your opinions...

 

[astra1]

Hi,

If you are talking about the changes in the Data Type and the length, then i think there is a solution. Please follow the following procedure:

1. Go to Catalog -> Tables
2. Remove the table and attach it again
3. press ok. it will take you to join Window
4. Check Joins (It should be OK)
5. Go to Catalog -> Folder and check the new table structure

Open the report and see.

Happy viewing

Vish

 

[umag]

Nope Vish
New reports you will be creating afterwards will be fine but the old reports which have used that fields of the table will complain saying that data item couldn't find if you follow the said procedure

Thanks

 

[CognosProfessional]

I believe Vish is partially correct. However, there is more to it.

REPORT: You then must open the report and cancel the error, then for each data item that uses that item that it cannot find, you have to replace that one with the new one.

I have done this because I did not want to re-build all my reports when data types have changed. All I had to do was delete the data item in the reports where needed and replace the item with the new one. It is tricky, but it worked. You keep doing this until no errors are left. If it is a big report, Yes, it will take a while.

CATALOG: The verification of tables don't always verify(for some odd reason), when you re-add each item to the tables in the catalog, but the reports work fine, and numbers tie.

Maybe certain versions don't act similar, this was version 6.

CP
CP

 

[umag]

Thanks CP
I know this and did the same thing for couple of reports in the past but this time it is hitting me big time as almost that changed column is in every table and almost all reports got effected. Looking for someone who has fixed more deligently than this. Changing one by column in the report till it is ok is my last resort anyways.

Thanks