In MSTR 9, there is a new feature called Multisource where user can connect Multiple DB instance.

We used the same and due to new license model we are forced to change back to single DB instance. So we pointed all DB instance to same ODBC connection (logically its one DB connection)

Issue: Even though all DB instance pointing to same ODBC, MSTR considering that as multiple DB instance. So when user without Multisource license login to the MSTR and try to run any report, it throws an error saying that ‘this is requires multisource license’. Interesting thing is, the tables for that report are coming from single DB instance.

Solution: It’s become critical issue during SIT due to client’s license changes…blah….blah.

Took bit risk option and also that’s the only solution…Changing DB Instance for all attributes in Metadata tables. (Alternate option, edit all attributes and change the table pointing to single DB instance which is huge task – [400 attributes].

Did some analysis on MD tables, relationships, etc…I changed the all DB instance 32 bit ID to single DB instance 32 bit ID (need to be very careful while deleting the rows, changing the column values in the Metadata DB.

I’m still doing documentation on changing DB instance in Metadata directly and along with that planning to document or new tool for “‘find and replace object in any definition”.

If anyone come cross this kind of issues like ‘Object ID cannot be found’ and also issues like SCANMD, DOCTOR MD not able to resolve, Will try to help you to fix the same.

Soon will post the document and tool for the same……