Category Upgrade Items function

Message from Joe Vocioni <Joe.Vocioni@gov.ab.ca> via eLink

Message from Joe Vocioni <Joe.Vocioni@gov.ab.ca> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">Category Upgrade Items function

Good day,

I have a couple questions and I apologize for posting in two different forums, however I wasn’t sure where it belonged.

We’re using LL 9.7 with an Oracle DB. Our current back-up process is “hot” back-ups while LL services are still running. I have gone through OT’s Oracle best practices and realize that there is a sync up utility. However, our client leans more towards a “cold” back-up strategy which means LL services should be brought down.

· What are the best practices back-up processes when you can't restart LL services because upgrade items process is running?

· Is there a config setting that says if no db response wait X amount of time?

· Additionally for the LAPI community, has anyone created a wrapper using LAPI around this process to make it behave differently? For example, how I explained above – wait X amount of time before continuing to run.

Any thoughts or suggestions are appreciated,

Joe

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

Find more posts tagged with

Comments

Appu_Nair

In answer to the's"What are the best practices back-up processes when you can't restart LL services because upgrade items process is running?"When you hit the upgrade items behind the scenes livelink takes the logic nad creates a "cached node crawler " object.This object constantly checks and updates the life of the nodecrawler object(almost when you see 5 items processed).I forget the exact life of the object but it is more than 24 hrs.So if you stop the livelink service,immediately on the update screen that is meta refreshing you will see a "Server Did Not Respond" message.After you re-start the service after your backup process if you refresh the subscreen livelink takes it from that point onwards.Alternatively you can bump up the num items from the "5" to say about "100" to speed up things.When I was an administrator I used to run my internet explorer windows on the admin server box so that even if I had started a major category upgarde on the weekend I would come monday morning and refresh( F5)the SDNR screen and get the upgrade complete.(Take this with a pinch of salt since I have not kept up with sys administration after 9.5 so if you can test this scenario on a dev server that will be good,also you should be able to get the cacheid in the llcache table to see how long livelink gives it time to live,also what I am tlking about is the "upgrade items" in the category functions menu)Alternatively you can just go and upgrade the items from the main folders and make a note of it and that does the same thing and abviously you know whaich folders you have upgraded.