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; } } }

Purge/Clean event subsytem tables.

dazzlad

Hi All,

We enabled the event subsytem configured to use Oracle.

After two days we have over 500,000 rows in our 'messages' table.

Does anyone know of any configuration or process to manage the size of these tables and purge rows from time to time in order that the amount of diskspace used is not so high?

We are running TS 6.5 SP2 on Solaris.

Thanks.

Find more posts tagged with

Comments

motlnt

Hi All,

We enabled the event subsytem configured to use Oracle.

After two days we have over 500,000 rows in our 'messages' table.

Does anyone know of any configuration or process to manage the size of these tables and purge rows from time to time in order that the amount of diskspace used is not so high?

We are running TS 6.5 SP2 on Solaris.

Thanks.

Never came across any such configuration for eventsubsystem.
not sure if this has to be set up on database level where there can be some auto-purging mechanism.

==============================
Interwoven certified consultant
TS 6.7.1 on RedHat Linux

dazzlad

I've opened a support case with Interwoven.

Will post the outcome here when I get a response....

KoenDeSmet

Same thing over here : 500.000 rows too after a while.
Eventsubsystem doesn't startup anymore.

You've gotten some answer from Iwov people concerning this ?

Kind regards,

De Smet Koen - Belgacom ,Belgium

fbuno

we have the same issue on SQL. did you get an answer from IWOV?

ukscottallen

We had same issue with TS672, Oracle 9;

We encountered many records in events DB tables and Teamsite would no longer start up due to this;
select count(*) from messages
507044
select count(*) from message_handles
504881

Solution was to purge these records and reduce expiry time from 4 days to 2 days, explained in response below from Interwoven;

The issue is actually because of the following:

The event subsystem database will take up some initial space to list all the subscribers and topics but a table space of about 1.5 GB should be sufficient. Once messages are processed, they are deleted. Normally, there is no data left over in the event subsystem tables after an event. Thus as far as the event subsystem is concerned, it does not grow as long as all the subscribers are connected and listening.

If problems arise due to some subscribers not listening, the db can grow enormously due to subscriber error messages. In this case, you may want to clear the db

So after removing the records from the message handler and messages tables in the database the issue got resolved for us.

If you don't use TS reporting, Search, Indexing or Datadeploy DAS services, then you can turn off the EventSubSystem. (In this case, there is no chance of growing the DB since there are no messages to be processed)

Scott: With regards to this setting can be changed in /httpd/webapps/eventsubsystem/WEB-INF/iw_bridge_cfg.xml it is already defaulted to expiryTimeInDays = "4">, so Im unsure why old messages were not automatically deleted anyways? Could there be a bug during the function to Removed expired messages? I have now changed this to 2 days.

I am not sure why this setting hasn’t delete the messages which are not older than 4 days. Since you have changed it to 2 days now, please notice if the tables grows or not and let us know if you face any issues