nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deleting Edition

System

What is the best way to delete the old editions. The TeamSite has 19 branches and each branch has 20+ editions in it. We are running TeamSite 5.5.2 on Solaris 8.

Thanks - ST

Find more posts tagged with

Comments

Migrateduser

Well, simplest way would just be to have the administrator or master for the branch log in and delete any un-needed editions. However, 20+ per branch does not sound like that much. You might want to archive the edition off to tape or some other restorable media (it would not get the EA's, but at least any content would be saved).

Maybe if you gave some idea as to why you are deleting editions or any other requirements that you may have we could give more ideas.

tvaughan

If you write a script to automatically delete old editions, make sure you put some "wait" commands in between each call to the iwrmed command.

If you flood the TeamSite server with a whole bunch of edition delete commands at once, you can kill your TS server and cause backing store corruptions (happened to me on TS 5.0.1). I'd recommend waiting for 60 seconds between each iwrmed and just letting your script run all night.

Tom

Adam Stoller

edition deletion in 5.5.2 is much more atomic than it was in previous versions of TeamSite - a wait of 1 second (if at all) is probably all that would be needed.

--fish
(Interwoven Senior Technical Consultant)

james1

fish

I believe that edition deletion is a background batch job. So, if you invoke "iwrmed", then control is immediately returned, but the operation will continue to run inside iwserver until it completes, which could take much more than 1 second.

-- James

--
James H Koh
Interwoven Engineering

tvaughan

Hmm. . . . I remember that in TS 4.5 and 5.0 you could "watch" iwrmed work by running "iwstat" over and over again and see the process work its way through the backing store.

I just blew away an EDITION on my 5.5 installation that contained a week's worth of changes on a several gig branch, and it was gone before I could type "i - w - s - t - a - t"

Maybe engineering souped up the process and/or made it less stressful on the TS server.

Tom

james1

OK, then maybe fish is right, and all you need is a 1-second wait. Sorry to inject confusion into the thread!

-- James

--
James H Koh
Interwoven Engineering

Migrateduser

Yes, edition/branch deletion time was part of the target performance improvements with TS5.5.2. This along with lots of other improvements to the backing store in TS5.5.x.

Bryan_K

This script by Smitty has been working well for us. Automatically deletes editions in specified branches if the branch exceeds the specified limit. We also modified his script to read the branch and edition limit from an Oracle DB that we keep website/TeamSite information stored in.

http://devnet.interwoven.com/forums/cgi-bin/showflat.pl?Cat=&Board=PRODUCTS_TEAMSITE&Number=5799&page=&view=&sb=&o=&vc=1

disco

James,

Glad you injected the confusoin. I couldn't figure out why TeamSite went all wonky after I ran a script to delete a bunch of editions. The thread has cleared it up a little for me. I am running 552. After deleting about 15 editions, TeamSite was unresponsive, then it froze the backing store without much explanation, we bounced it, and now its back to normal but it took a while for the edition deletion to complete. (even after the bounce, iwstat had two lines referencing edition cleanup). I would continue to advise caution when deleting a number of editions.

Runtime.JPG

SheetLayout.JPG