Orphan backout member in the package

[kimchheng heng]

Hi everyone, 
I would like to ask a question. Have anyone encounter issues with orphaned backout member before? 

The place I am working for have old packages and it already committed or deleted but the backout members(.member name) still existed. It does not automatically delete. 

Regards 

[Richard Rozentals]

Hi,

You're luck it's only one. Some companies have hundreds of these members.

As I remember one of the ways this can happen is when a package is reset after execution. Then different elements/versions are processed. 

Backout members do have footprints that can be viewed by option 1  DISPLAY then option 2  FOOTPRINT. 

Yes these member can only be deleted manually. I recommend that you first backup the file. Check the footprint before deleting to make sure it's not current backout member.

 

------------------------------
Richard Rozentals

Endevor Support
Broadcom
------------------------------

[Felicity Vaughan]

Yes, that's what I had to do. We had a lot of orphaned backout members and we backed them up and then deleted them. Hope that works for you.

[kimchheng heng]

Thank for your recommendation, it seems like the only options now is to backup then manual delete them.

[kimchheng heng]

Thank for your answer. Unfortunately, there are more than 4k elements to be deleted that why I would like to know if there is any better way to do it rather than manually delete.

[Richard Rozentals]

Hi,

Commit all the packages you can. This will lessen the load of the members you don't delete.

------------------------------
Richard Rozentals

Endevor Support
Broadcom
------------------------------

[kimchheng heng]

we have to keep the package for at least 30 days, there are schedule job to commit the packages that are older than 30 days. But the orphan members are from package that are already commit or deleted and most of that package are old.