Issue: Not able to add tables/views to the Schema in Warehouse Catalog
Error: ‘Error adding Table(s) to the schema. This key is already associated with an element of this collection’
Solution in MSTR 9:
1) Open ‘Architect’,
2) Right click the table <table name>
3) Add to the project
4) once its added, Right table in Left Pane and update structure
5) Save and close (it will ask for Update Schema, so do the same
6) Now open Warehouse Catalog
7) you can see the table/view added to schema
Senthil and I proudly announce that we have decided to merge Object Tracking Tool and Metadata Browser into a single application.
In the meanwhile, feel free to post your suggestions and requirements for this new tool.
Stay tuned 😉
After long gap posting ‘Object Tracking Tool’ with some updates.
1) The tool tested in system where I-Server is installed (not got a chance to test without I-Server)
2) Tested in XP,2003,Vista, 7
3) For those testing using Tutorial; the object ID for some objects may looks like same…but actually there is one number difference between each ID. Don’t assume that its repeating the same ID.
4) Any suggestions/Comments are welcome
Note: Soon the tool will be integrated with some other tool also.
Download the tool here.
Note: This application is provided “as is” and I disclaim all warranties, whether express or implied, with respect to all provided items, including all warranties of merchantability, fitness for a particular purpose, accuracy, systems integration, title, satisfactory quality and non-infringement. I do not warrant that use of the provided items or any portion thereof will be uninterrupted or error-free, or that the provided items or any portion thereof will meet any need or requirement of licensee.
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……
Please refer to the following technical notes for more details:
Both issues are corrected in MicroStrategy 9.0.0 Hotfix 3. Customers who are on 9.x are urged to upgrade to this latest Hotfix that is available on the MicroStrategy Download Site.
MicroStrategy 9.0.0 Hotfix 3
MicroStrategy 9.0.0 Hotfix 3 is now generally available on the MicroStrategy Download Site to licensed customers. This is a maintenance release for customers currently running the 9.0.x version of the software. This release contains new issue corrections, as well as all corrections provided in the earlier 9.0.0 Hotfix 1 and 9.0.0 Hotfix 2 releases. In particular, Hotfix 3 addresses the two critical issues that may affect the stability and folder accessibility of the MicroStrategy environment as described in the technical notes TN 31747 and TN 31658. The Readme is available in the MicroStrategy Knowledge Base.