CMS objects that are orphaned in the Input FRS

Question

Post Author: [email protected]
CA Forum: Administration
Is there a tool / way to comb through the CMS objects and clean up CMS objects that do not have a file that exists in the Input FRS?
Not sure how we ended up with these orphaned objects, product of migration i guess.

Answer 1

Post Author: jsanzone
CA Forum: Administration
Jason,
I'm not sure what the case would be if you were to allow these orphans to linger around, as best as I can tell there are no inherent problems.  However, as good administrators we sometimes feel best when things are neat, tidy, and all accounted for.  In answer to your question, I do not know of any tool per se, other than using the artificats that Bus Objects leaves us with to "check things out" and to also use other resources as we see fit.  The best I can imagine in getting to the data you seek is as follows:
-  use the Query Builder tool (/businessobjects/enterprise115/WebTools/websamples/query/query.aspx"&gt;https://<server>/businessobjects/enterprise115/WebTools/websamples/query/query.aspx?
- in the "enter your SQL code here" box, type: select si_files,si_name from ci_infoobjects where si_obtype=260 (then click on "Submit Query")
- you will get a screenful of info back in your browser, and this is where the "tricky" part starts.  If you're working in a unix (or unix-flavored) environment (or have "grep", "cut" and "paste" for windows), you can highlight all the text that is returned, then copy to a text file.  Using grep, you can grep on "SI_FILES SI_PATH" | cut -c24- and output to another text file.  Then you can grep on "SI_FILE1" |cut -c10- and output to another text file.  Then finally, paste -d"/" <file1text> <file2text> (this puts the two parts together with a slash between thus resembling a file name.  The next task is to go the place where your filestore is at (if you've not moved it from the original installation, then most likely at "C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\FileStore").  From here you'll have to obtain a pathname/filename list of all your "*.wid" files (in unix this is easy, however, in Windows/DOS, you might try zipping everything to a PKZip file, then "test" the file and copy/paste the output from it to another text file.  Once you have the two text files in front of you then you can use a variety of tools to "match things up" (i.e. import to Access as two tables and use inner join/outer join techniques, etc, etc).
In my particular case, the query builder is telling me that I have 894 objects, however, doing an Explorer search I get 880 objects, so I have 14 orphans in CMS.  I'm not sure how this happens either and I'm not sure how I'd go about removing these puppies from CMS either, but I guess if I took the above steps, I'd know exactly which IDs in CMS were out of whack.
Good luck.