It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×1,305

question asked: Mar 20 '12, 12:01 p.m.
question was seen: 4,394 times
last updated: Jun 26 '13, 8:32 a.m.

Related questions

RAMDB Size Management

0
Kim Lee (1●1●1) | asked Mar 20 '12, 12:01 p.m.
Is there a best practice for managing RAMDB tables?

Certain tables in our Oracle RAMDB are large and growing larger: REPOSITORY_ITEM_STATES
WORKITEMS_SNAPSHOT_WRKTM_CHNGS

Can someone explain what these table do? Is there a method to purge these tables?

Thanks!
Comments
Isaias Zaral commented Jun 24 '13, 5:29 a.m.

We have the same problem with this HUGE table: REPOSITORY_ITEM_STATES.

we posted here our question:
https://jazz.net/forum/questions/115997/repository_item_states-grows-too-quickly

if somebody can tell us which records tables must be deleted together with with one, we are thankful.

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Rich Kulp (3.6k●3●8) | answered Mar 20 '12, 1:49 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi,

Those aren't RAM tables, those are RTC tables. RTC records all activity and every time an asset is updated activity is recorded in RTC. So it will continue to grow. RTC doesn't have a purge capability. What they are actually recording is internal to RTC. I don't know what form it is.

What kind of size problems are you seeing? MB or GB's?
Comments
Isaias Zaral commented Jun 24 '13, 6:24 a.m.

100GB. The table, just with nightly builds now are growing more than a million per month.

Gili Mendel commented Jun 26 '13, 8:32 a.m.
JAZZ DEVELOPER

How many policies are running on your lifecycle/how often?

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.