Catalog Upgrade Problem

[NEAR]

When running a report from Impromptu version 7.1.3 I get the following error:

Error number -239:

DMS-E-GENERAL, A general exception has occurred during operation 'prepare request with options'.
DMS-E-RBI_TABLE, The table or view VMKCUR_CO was not found in the dictionary.

We are running reports from a DB2 database that was running previously from Impromptu version 5 reports without any problems. No changes were made within the database. However several upgrades have been made to database drivers and we think there may be a binding issue but we're not sure. The catalogs seem to migrate without a problem.

Any help would be greatly appreciated!

 

[GJParker]

Is the VMKCUR_CO table in the upgraded catalog ? catalog Menu -> Tables -> Catalog tables

If not there then add the table and create the required links, if it is there verify the table and see if errors occur.

HTH

Gary Parker
MIS Data Analyst
Manchester, England

 

[drlex]

In addition to what Gary has written, you might just check thread401-5362510 which details how to update a table and maintain both the existing joins and reports that use the table.
lex

soi la, soi carre

 

[griffindm]

I think lex means thread401-536251.

Dave Griffin


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

http://www.decisionsupportgroup.com

 

[drlex]

I do indeed dave, darn that sticky 0 key and the inability to edit a post!

soi la, soi carre

 

[NEAR]

Thanks for the prompt reply!

When verifing the catalog tables cognos simply displays a red X over the database. No error messages are displayed or logged. Interestingly, some of the reports are returning result sets. However, most are not. It's really weird, but sometimes nothing is displayed in the tables frame while at other times tables display. It's as if database is trying to bind to the application but for some reason it's not able to. Very weird! I've never seen anything like this before...

 

[NEAR]

By the way...No changes have been made to the database. Nothing has been renamed and/or dropped. When we start from scratch to build a new catalog it takes a very long time to bind. Once it seems this has completed, the same errors occur when building a new report using the new cat.

 

[NEAR]

I'm beginning to think this is more related to a database driver issue...??

 

[drlex]

Can you take the problem outside the Cognos environment: use tools supplied with the drivers to test the DB connection?

soi la, soi carre

 

[NEAR]

Yes. This works fine. The DBA's have said that the data needs to bind with the application the first time through. I've been told that this only needs to happen once. From that time forward the database should be available to anyone currently using the same database driver version. I'm being told that the current driver may have some bugs that could cause it not to bind through some applications. I'm skeptical...

I've never seen this before. Normally this is transparent to the admin migrating a catalog to another version. I’ve done migrations before with Sybase and never experienced this sort of problem except when database changes have occurred. That's obvious and usually only required and update to the table elements. Dropped columns can cause the same errors we’re seeing here. However no changes have been made to the database currently in use. Weird!

 

[NEAR]

Resolved. The issue was resolved simply by running a FixPac against the DB2 driver. This allowed Impromptu to bind the data.