If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Error when trying to save DM catalog

Started by Tim86, 26 Feb 2013 10:18:42 AM

Previous topic - Next topic

Tim86

This morning I have been getting this error when I try to save my catalog in Data Manager (version 8.3.81.20).  But if I close it and re-open it, I can make some changes in the catalog and save it successfully again.  Then a little while later, I start to get the same error again when I try to save.  Here is the error:

   'CheckCatalog' returned with 1 message
   1. ERROR
   DM-DBM-0400 UDA driver reported the following on connection ALIAS_070DADE8:
   UDA-SQL-0564 [Microsoft OLE DB Provider for SQL Server]Connection failure (SQLSTATE=08S01, SQLERRORCODE=0)

Then when I close Data Manager, I also get this additional error:

   'GetItemHandleCount' returned with 1 message
   1. ERROR
   DM-HDL-0100 The handle is null or not valid

and another box also pops up with this:
   Run-time error '5'
   Invalid procedure call or argument

Also, another error I keep seeing at the end of job logs (even though they are successful):
   DM-DBM-0400 UDA driver reported the following on connection DataMartDB:
   UDA-SQL-0403 There are active transactions associated with the specified database.

I don't know if that last error is related to the others or not...but thought it might be useful information.

Please help!  This is going to cause major headaches in my development work, because I'll have to be saving too often to avoid losing my work.

MFGF

Oh yikes! That doesn't sound healthy at all! It sounds like your catalog tables are corrupted somehow.

I would create a catalog backup as soon as possible if I were you (File > Backup Catalog). Create a new, empty database to host your catalog, point Data Manager at this (File > New Catalog) then once it has initialised and opened as empty in the Designer, restore your catalog backup into it.

Good luck!

MF.
Meep!

Tim86

Thanks for the reply.  The next day the problem went away, and I didn't have any issues for several days.  Then today it showed its ugly head again on a completely different catalog.  I closed it, re-opened it, made my changes again, and it saved without a problem.  It doesn't seem like a corrupted catalog issue, since it has happened on two different catalogs and doesn't persist when I close/re-open.

MFGF

I'm not sure 8.3 is even in support these days. It's probably worth upgrading to a newer release if you can.

Cheers!

MF.
Meep!