<div dir="auto">Thanks, Dale. I sort of got something going. Still mysterious sometimes :-)</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 27 Oct 2022, 18:26 Dale Henrichs, <<a href="mailto:dale.henrichs@gemtalksystems.com">dale.henrichs@gemtalksystems.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Otto,</div><div><br></div><div>I was hoping that someone else would be able to answer your question, since I don't know the answer off the top of my head :) Sooo, I think that this would be a good question for an HR ... <br></div><div><br></div><div>Dale<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 25, 2022 at 3:39 AM Otto Behrens via Glass <<a href="mailto:glass@lists.gemtalksystems.com" target="_blank" rel="noreferrer">glass@lists.gemtalksystems.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>When we do migrations in our GemStone 3.6.5 databases, we sometimes do some cleanup before we start migrating because we discovered some loose ends before the release. This creates dead objects; then we have to ensure that the dead objects are garbage collected because our migration process picks up any object that can be migrated.</div><div><br></div><div>This process takes the system offline and we can then stop any "user" level gems / topaz sessions. This helps to get migrations to run reliably through.</div><div><br></div><div>I am assuming the best way is to do a full markForCollection and reclaim before we start listing objects that should be migrated. Is this a reasonable approach? </div><div><br></div><div>We run SystemRepository reclaimAll after the markForCollection. We then try to wait for all dead objects to be collected, but dead objects are still in the repository. We use </div><div><br></div><div>SystemRepository findReferencePathToObject: (Object _objectForOop: xxx)</div><div><br></div><div>and then get</div><div><br></div><div>*** Scan completed *** (object is dead) Total time is 5 seconds<br></div><div><br></div><div>Is there a way to synchronously wait until the space used by dead objects has been reclaimed? (and the object would not be picked up by listInstances). This assumes that the only way to really know if an object has been removed is if the space has been reclaimed. Or is there another approach that will work?</div><div><br></div><div>Regards<br clear="all"><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><table style="color:rgb(0,0,0);font-family:Times;font-size:medium" width="600" cellspacing="0" cellpadding="0" border="0"><tbody><tr><td width="400" valign="bottom"><p style="margin:0px;padding:0px"><span style="font-size:18px;color:rgb(146,148,151);font-family:Calibri,sans-serif;font-weight:700">Otto Behrens</span><br></p><p style="font-size:18px;font-weight:700;color:rgb(146,148,151);font-family:Calibri,sans-serif;margin:0px;padding:0px"><span style="font-size:14px;font-weight:300;margin:0px;padding:0px">+27 82 809 2375</span></p></td><td width="200" valign="middle"><img src="https://www.finworks.biz/signature/finworks-signature-logo.png" alt="FINWorks" style="display:block;border:0px none;width:200px;height:38px;margin:0px;padding:0px" width="200" height="38"></td></tr></tbody></table><table style="color:rgb(0,0,0);font-family:Times;font-size:medium" width="600" cellspacing="0" cellpadding="0" border="0"><tbody><tr><td height="5"></td></tr></tbody></table><table style="color:rgb(0,0,0);font-family:Times;font-size:medium;border-bottom:1px solid rgb(200,28,36)" width="600" cellspacing="0" cellpadding="0" border="0"><tbody><tr><td height="15"></td></tr></tbody></table><table style="color:rgb(0,0,0);font-family:Times;font-size:medium" width="600" cellspacing="0" cellpadding="0" border="0"><tbody><tr><td height="20"></td></tr></tbody></table><table style="color:rgb(0,0,0);font-family:Times;font-size:medium" width="600" cellspacing="0" cellpadding="0" border="0"><tbody><tr><td style="display:inline-block" width="15" valign="top"><a href="http://za.linkedin.com/in/waltherbehrens" style="color:rgb(17,85,204)" target="_blank" rel="noreferrer"><img src="https://www.finworks.biz/signature/finworks-linkedin-logo.png" alt="FINWorks" style="display:inline-block;border:0px none;width:15px;height:15px;margin-top:1.5px;padding:0px" width="15" height="15"></a></td><td style="display:inline-block" width="250" valign="top"><a href="http://www.finworks.biz/" style="color:rgb(200,28,36);font-family:Calibri,sans-serif;margin-left:10px;margin-top:0px;padding-top:0px;font-size:11pt;display:inline-block" target="_blank" rel="noreferrer">www.finworks.biz</a></td></tr></tbody></table><table style="color:rgb(0,0,0);font-family:Times;font-size:medium" width="600" cellspacing="0" cellpadding="0" border="0"><tbody><tr><td height="10"></td></tr></tbody></table><table style="color:rgb(0,0,0);font-family:Times;font-size:medium" width="600" cellspacing="0" cellpadding="0" border="0"><tbody><tr><td><p style="font-size:10px;color:rgb(146,148,151);font-family:Calibri,sans-serif;text-align:justify">Disclaimer & Confidentiality Note: This email is intended solely for the use of the individual or entity named above as it may contain information that is confidential and privileged. If you are not the intended recipient, be advised that any dissemination, distribution or copying of this email is strictly prohibited. FINWorks cannot be held liable by any person other than the addressee in respect of any opinions, conclusions, advice or other information contained in this email.</p></td></tr></tbody></table></div></div></div></div></div></div></div>
_______________________________________________<br>
Glass mailing list<br>
<a href="mailto:Glass@lists.gemtalksystems.com" target="_blank" rel="noreferrer">Glass@lists.gemtalksystems.com</a><br>
<a href="https://lists.gemtalksystems.com/mailman/listinfo/glass" rel="noreferrer noreferrer" target="_blank">https://lists.gemtalksystems.com/mailman/listinfo/glass</a><br>
</blockquote></div>
</blockquote></div>