Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DBS-E-RBI_Column, Error Number -239

Status
Not open for further replies.

Adriantee

MIS
May 9, 2003
2
MY
Hi there,

I'm really new to Cognos-Impromptu.

This Impromptu report created based on Impromptu 5.0, connection thru the CAT should be fine, but once I input the selection into the prompt up screen and click ok. It's gave the following error:-

Error number -239:

DMS-E-GENERAL, A general exception has occurred during operation 'prepare request'.
DMS-E-RBI_COLUMN, Column c6 was not found.
DMS-E-RBI_COLUMN, Column c7 was not found.
DMS-E-RBI_COLUMN, Column c37 was not found.
DMS-E-RBI_COLUMN, Column c36 was not found.
DMS-E-RBI_COLUMN, Column c27 was not found.
DMS-E-RBI_COLUMN, Column c35 was not found.
DMS-E-RBI_COLUMN, Column c34 was not found.
DMS-E-RBI_COLUMN, Column c33 was not found.
DMS-E-RBI_COLUMN, Column c32 was not found.
DMS-E-RBI_COLUMN, Column c31 was not found.
DMS-E-RBI_COLUMN, Column c30 was not found.
DMS-E-RBI_COLUMN, Column c29 was not found.
DMS-E-RBI_COLUMN, Column c28 was not found.
DMS-E-RBI_COLUMN, Column c27 was not found.
DMS-E-RBI_COLUMN, Column c38 was not found.
DMS-E-RBI_COLUMN, Column c26 was not found.
DMS-E-RBI_COLUMN, Column c25 was not found.
DMS-E-RBI_COLUMN, Column c16 was not found.
DMS-E-RBI_COLUMN, Column c1 was not found.
DMS-E-RBI_COLUMN, Column c2 was not found.
DMS-E-RBI_COLUMN, Column c3 was not found.
DMS-E-RBI_COLUMN, Column c4 was not found.
DMS-E-RBI_COLUMN, Column c5 was not found.
DMS-E-RBI_COLUMN, Column c6 was not found.

Plaftform:
Impromptu 5.0
Windows 2000 Professional/Server
SQL Server 2000

Please help!!

Any input will be very much appreciated. Thanks.

Adriantee
 
Adrian,
the message indicates that there is a difference between what Impromptu "expects" to find at the DB according to the catalogue and what it can find once it connects.
If you save the report as an IQD or SQL type, you can determine what fields and tables Impromptu is expecting to see for each of the columns your report references.
The difference can result from changes in the version of Cognos, in the catalogue, in the DB connection method and changes in the DB (content and format) itself.

Your helpdesk/database administrator/IT dept. should be able to assist in determining where the error results and how to fix it. As a start point; does anyone else run this report and are they experiencing the same problem? That might isolate the problem to your PC and local set-up.
Bear in mind, as many people on this forum will testify, it's not unusual for a DB administrator to change the DB and 'forget' to tell users!
HTH,
lex
 
Hi Drlex,

Thanks for your input.

Basically, the Impromptu Report was running fine in my client's office. I'm trying to extract the report and troubleshoot on the information.

Initially, by having one copy of the report within my company, which gave the error messages once I run it. Then, I copied the CAT and the report from my client's office, again it's gave me the same error.

Can anyone forsee what went wrong? Perhaps, give me some hint where to begin with?

Thanks in Advance!

Adriantee
 
Adriantee,

Are the database tables under the same schema name as at the client's office? Impromptu using SQL Server is fairly finicky about this. If this is the problem, you may have to adjust the schema. If you have access to the Cognos knowledgebase, try looking up 'schema leveling'.

Regards,

Dave Griffin


The Decision Support Group
Reporting Consulting with Cognos BI Tools
"Magic with Data"
[pc2]
Want good answers? Read FAQ20-2863 first!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top