Now days we have lots of installation and our installation is totally done via Script (Something like Autodomain) and lots of objects become orphan so I hve to restore it from group scan....
So any solution on that and why it become Orphan... ????
How are you finding orphans? When database is online? Don't do that!
First put database offline (stop database service), perform cache rebuild, then scan for orphans, then put database online.
Make sure your EEPC database is excluded from AV Scans, and set SBADMIN.exe as a low-risk process.
We ran into an issue a few months ago when moving machine objects between machine groups where the objects would disappear. When we did a group scan, it would "find" all these orphans, but everyonce in a while we would get a message that the group scan could update an attribute. The only objects that were "recovered" were any that were processed since the last error. Long story short, our EEPC database was getting overloaded, and timing out due to AV scannning. We made the changes above and everything works fine, even with the database server service running.
orphans occur when a group update is aborted - either because it timed out, or because the task doing it got interupted (like a network outage, or someone closed the application without waiting for it to finish.
You can minimize them by making sure your DB server is up to the job, by extending the timeouts, and by making sure people don't close EEM etc without letting it finish.
It's not an error state, it's a failsafe to ensure the objects remain, even if they are not connected to a group.
Actually much better explanation and recommendations about "dbcfg.ini" parameters you will find in:
Well, I downloaded the 5.2.4 packages recently, but this guide is not included in the documents folders, neither in EEM nor in the EEPC archive ...
Do you have a download link for this guide ?
I have posted that link multiple times....Message was edited by: peter_eepc on 3/15/10 10:29:23 AM EDT