Action Move extremely slow - almost impossible to perform

Action Move and Multiple Move generally result in hours wait when successful. In most cases I just give up after a few hours. I suspect this is due to our LLCACHE table size, currently 50000 rows. I've also noticed a concurrent proliferation of llclient processes that would generally slow down the overall platform performance and even impede at times users access.Could anybody kindy refer me to the relevant documentation? Would it be fine if I just delete the table?Thank youBettina

Find more posts tagged with

Comments

eLink User

Message from Nair, Krishnankutty via eLinkOn 9.5 sp1 we identified the problem with a dtreeancestors table kind of problemwith a call backPlease check whether you are having this issue as well.The problem waswith the recommender module.We had it uninstalled and the problem wentaway.I am assuming that this call back has since been corrected in asubsequent version with a patch.The time line I am talking is around Apr 2006. -----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com] Sent: Wednesday, April 25, 2007 12:05 PMTo: eLink RecipientSubject: Action Move extremely slow - almost impossible to performAction Move extremely slow - almost impossible to perform Posted byMastroianni, Bettina on 04/25/2007 01:04 PMAction Move and Multiple Move generally result in hours wait whensuccessful. In most cases I just give up after a few hours. I suspect this is due to our LLCACHE table size, currently 50000 rows. I've also noticed a concurrent proliferation of llclient processes thatwould generally slow down the overall platform performance and evenimpede at times users access.Could anybody kindy refer me to the relevant documentation? Would it be fine if I just delete the table?Thank youBettina[To reply to this thread, use your normal E-mail reply function.]============================================================Discussion: Development Discussionhttps://knowledge.opentext.com/knowledge/llisapi.dll/open/786303Livelink Server:https://knowledge.opentext.com/knowledge/llisapi.dllTo Unsubscribe from this Discussion, send an e-mail tounsubscribe.development@elinkkc.opentext.com.-----------------------------------------*Please note my E-Mail Address has changed. Please update yourcontact list*Anadarko Confidentiality Notice: This electronic transmission and any attached documents or otherwritings are intended only for the person or entity to which it isaddressed and may contain information that is privileged,confidential or otherwise protected from disclosure. If you havereceived this communication in error, please immediately notifysender by return e-mail and destroy the communication. Anydisclosure, copying, distribution or the taking of any actionconcerning the contents of this communication or any attachments byanyone other than the named recipient is strictly prohibited.

Bettina_Mastroianni

llclients or llcache table with too many rows?I'm also running still the 9.2, not even SP1 and we're planning to migrate to the 9.6 late this year.I'm not clear what the dtreeancestors table is and what callback you're mentioning. Can I have more details?ThanksBettina

eLink User

Message from Nair, Krishnankutty via eLinkLike I said in my post when you do a move it was painfullyslow.so I putbuilder in debug and was able to find out that a recommender callbackobject was giving the proble.we reported this to ot with screenshots,logs,capi connect logs etc and they advised us toUninstall it.I am sure it has been fixed.The dtree ancestors table Iguess is made by OT to simulate a tree walk easier.This couldnot be your problem as I think 9.2 did not have therecommender module perhaps.My $.).02 will beput connect logs and sendit for ot's analysis -----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com] Sent: Thursday, April 26, 2007 5:56 AMTo: eLink RecipientSubject: What exactly did you come across?What exactly did you come across?Posted by Mastroianni, Bettina on 04/26/2007 06:35 AMllclients or llcache table with too many rows?I'm also running still the 9.2, not even SP1 and we're planning tomigrate to the 9.6 late this year.I'm not clear what the dtreeancestors table is and what callback you'rementioning. Can I have more details?ThanksBettina[To reply to this thread, use your normal E-mail reply function.]============================================================Topic: Action Move extremely slow - almost impossible to performhttps://knowledge.opentext.com/knowledge/llisapi.dll/open/12292739Discussion: Development Discussionhttps://knowledge.opentext.com/knowledge/llisapi.dll/open/786303Livelink Server:https://knowledge.opentext.com/knowledge/llisapi.dllTo Unsubscribe from this Discussion, send an e-mail tounsubscribe.development@elinkkc.opentext.com.-----------------------------------------*Please note my E-Mail Address has changed. Please update yourcontact list*Anadarko Confidentiality Notice: This electronic transmission and any attached documents or otherwritings are intended only for the person or entity to which it isaddressed and may contain information that is privileged,confidential or otherwise protected from disclosure. If you havereceived this communication in error, please immediately notifysender by return e-mail and destroy the communication. Anydisclosure, copying, distribution or the taking of any actionconcerning the contents of this communication or any attachments byanyone other than the named recipient is strictly prohibited.

Bettina_Mastroianni

The dtreeancestors table is not in my schema, so can't be a problem.In LL 9.2 recommender is a core module that gave us other problem but there is no evidence it affects the move.What I can see are lots of llclient processes and llcache full.Thanks anywayBettina

Chris_Jones

The dtreeancestors table was introduced with 9.5. In very large installations your dtree ancestors table is very large the update statements take a very long to complete with move and delete. In our instance we have 14 million rows in the dtreeancestors table. This may prevent us from going into production with 9.5. You can disable recommender but there are some consequence.s If you have search results to show common locations, common authors ect. these values will not be updated with current information. Disabling recommender would also prevent you from implementing My Home and if you own communities of practice the majority of the features on the communities front page will not be updated (new blogs, whats new etc.) I have heard this is corrected in 9.7 but I have not scene this yet.Another note while upgrading to 9.5 part of the upgrade will take a very long time to complete that is the section when recommender is updated because the process is building the dtreeancestors table.Thank you,Chris

Atiya_Sultana

Hi Appu,

We are running on Livelink 9.7.0, IIS 6.0 and SQL Server 2005 and have Recommender installed. Do you think Recommender is still a problem even with this version? If yes, do I need to completely uninstall or just disabling the Recommender Agent will do?

This is related to the bulk move issue I raised in another thread.

Many Thanks,

Atiya.