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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ODBC Error (DB2) Unsuccessful Execution

Status
Not open for further replies.

eileenr27

Technical User
Jul 2, 2004
9
US
I'm using Crystal Reports 7.0

I'm getting the following ODBC error after making a couple of changes to a report that was working before I made the changes.

CHANGES: a have four groups. I changed the first group to a different field. Then, I added a database to the report so I could add a description for the new group. I inserted the description field in the report.

SYMPTOMS: the report runs for about 10 minutes and then I get the following error:
=============================================
ODBD error; [StarQuest] [StarSQL ODBC Driver] [DB2] UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C90084, TYPE OF RESOURCE 00000230, AND RESOURCE NAME.
=============================================

Whenever I've gotten this error in the past it had to do with the permissions for the userid that I was using. We generally no longer get this error because we created a userid with all permissions except the ability to write to the database.

Does anyone know what else could be causing the error?
 
Perhaps the generic user doesn't have permission for the new table?

Could be related to the type of field in the table that you added (what you call a database).

-k

 
I tested to see if I could access the table I added by creating a new report and it displayed the data just fine.

Not sure what your trying to tell me with the second suggestion though. Please draw me a picture.
 
The fact that the message occurred after you added the new table is the real clue here. This often happens (not just with DB2) if you connect to the new table's database in a different way than the original tables were connected to i.e. Crystal doesn't like a mix of different connection types. Try verifying the database through Crystal, or converting the database driver (Database, Convert Database Driver) so that all tables are connected to using the same method.

Peter Shirley
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top