Update Impromptu 5 Catalog with Impromptu 6?

[gazolba]

Can I update a version 5 Impromptu Catalog with Impromptu Administrator Version 6 and have it still work with Impromptu version 5.
I looked in all my Cognos documentation for the answer to this but nothing was mentioned.

 

[griffindm]

You can open a prior version of an Impromptu report or catalog with a subsequent version in read-only mode, but if you upgrade the report or catalog you will be unable to open it later with the older version.

If working with two version of Impromptu, I always make reports and catalogs read-only in the O/S to avoid accidentally upgrading them.

Regards,

Dave Griffin


The Decision Support Group
Reporting Consulting with Cognos BI Tools
"Magic with Data"
Want good answers? Read FAQ20-2863 first!

http://www.decisionsupportgroup.com

 

[gazolba]

Do you know if its possible to add a column to a catalog without being connected to the data source?
We need to do this but we have no way to connect to the data source since its on another network and a database that we have no ODBC driver for. Even if we had the driver its incompatible with other drivers we have on our machines.

 

[NEAR]

Recently we upgraded a version 5 impromptu catalog to version 6. When using the version 6 catalog we got the following error:

DMS-E-GENERAL A general exception has occurred during operation ‘prepare request’.
DMS-E-RBI_TABLE, The table or view TMKLS_RPT_FACT was not found in the dictionary
DMS-E-RBI_FACT was not found in the dictionary

This error does not occur using the version 5 catalog.

The source database is DB2 running client version 7.

Any Ideas?

 

[DoubleD]

Have you verified your tables in the catalog? It seems there is a table or field that Version 6 is not recognizing. Could be a datatype issue.

Pain is stress leaving the body.

DoubleD

 

[NEAR]

No we haven't looked into verifying the tables.

It's very strange, when we first bring up a new version 6 report there are no tables available in the source pane. After a few tries they suddenly appear. Very Weird...

By the way everything works fine with Impromptu version 5 looking at the original version 5 catalog.

Could this be a DB2 client (driver) issue? I've never seen this before with migrations from other data sources such as sybase etc...