Highlighted
Absent Member.
Absent Member.
2637 views

Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

Hi, my environment:

Hp TRIM 7.1.1828 Win 7, MS Office 2010 ,Server 2008R2

 

What to do when Scheduled Event Triggers are accumulating at the rate faster than they are processed?
E.g. hourly, we create 1200 events and they are being processed at approx 50 per hour.
Based on this, we never going to decrease the load.

When there is not so many events accumulated, the rate is faster...Now, it looks like that there is no solution .. 400.000 event triggers are there now and constantly increasing.

The re-start of the server does not help.

Any advice on this? It is kind of urgent.

 

Is this issue exist/fixed in HP TRIM 7.3.2.5511?

Thanks

 

 

0 Likes
20 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

This was improved in later versions of 7.2.x, and in 7.3.x. KM1420410

 

Also, there is an excellent knowledge document regarding this, KM765264.

 

I have removed all the existing events and manually recalculated specific schedules before, but it is time consuming to identify what needs to be recalculated.

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

Thanks,

so there is no solution for my problem with the events?

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

What's actually happening with TRIM? Is someone performing a large migration, or moving classifications around?

 

These events are kicked off because record objects are being created or moving within the system. If the rate at which they are being generated has ramped up, that indicates abnormal activity.

 

If a large number of records are being imported, then it is worth simply turning off the event processing for these triggers for the duration of the import.

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

Yes, large data migration. I recevied a few suggestions what to do "next time" but not how to fix the current issue .

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

Has the large data migration already finished? If that's what triggered the large backlog of events, perhaps if you're patient the system will eventually start catching up. It's the speed at which the database engine can process the fairly complex queries that determines how quickly they process. Perhaps ask your DBA if there's any way they can throw extra resources at it until the backlog's processed?

 

There are ways to intervene and remove the backlog from the queue, with a view to re-processing them manually (as outlined in the knowledge document mentioned in an earlier post), so if you're particularly impatient you may wish to log a support case with HP Support asking for assistance.

 

One of the good things about scheduled event triggers is they're the sort of thing that only ought to be up to date when the records people decide to do some scheduled disposal activities. Sometimes this is quite infrequently (e.g. annually) so you may want to speak with them.

 

The other thing you always need to monitor is whether people are putting a large number of contents into containers (300+ is considered large). The TRIM documentation recommends not containing more than 300 documents in any one container, and the automated part rules feature is provided to allow you to configure TRIM to avoid this. Perhaps some of the imported records fall into this category, so it may not be the sheer volume of them that's the cause.

 

Here’s a script your DBA can run to identify containers in your database with more than 300 contents:

 

select b.title,
            b.fullrecordid,
            count(a.uri) as #Documents
from TSRECORD a, TSRECORD b
where a.rccontaineruri=b.uri
group by b.title,
            b.fullrecordid         
having (count(*) > 300)
order by 3 desc

Neil

Note: Any posts I make on this forum are my own personal opinion, and unless stated otherwise do not constitute a formal commitment on behalf of Micro Focus.

(Please state the version of CM you're using in all posts.)

MySupport: https://softwaresupport.softwaregrp.com/

If you find this post useful, please use the and/or buttons below.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

Hi,

the data migration is not finished and also much more data migratrion is about to start.

Events are still building up.

Somebody suggested that more resources could be added...Not sure how that will reduce the number of events... They are already there.

I sugested the removal of the known events and adding them later...when safe...

 

The tool is implemented to monitor TRIM files with more than 999 records and there are a few hundreds of these...some old and some still active ( documents are added daily).

 

Is this really a "catch 22" situation?

 

Local HP rep was contacted as well...

Will let you know how this will be solved (next week I hope).

Thanks

 

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

Complete your import, clear up folders with more than 300-400 items (new parts), purge all of the entries for Scheduled Event Triggers, and then recalculate triggers.

 

Your build is just a problematic build (as with all 7.1.x) with regard to SET's. 

---------
Erik
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

It is not so easy to create new parts as some business applications using the same file for the last 3-4 years...

 

Not sure how to purge all entries for triggers (only related to my import?) ...

 

Then, new imports will do the same thing? Create so many event triggers ....

 

Regards

 

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

I use a utility that does all this automatically, because it is a big problem. If you don't parse out the folders with lots of content then the issue will keep coming up each time you add a single document to that massive folder.
---------
Erik
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

 

800.000 events and raising.

 

2 questions:

1. A test was done: The corporate file where the records are migrating to is wihout the retention schedules, so how many triggers events are created per, let say 1,000 records. The answer is = 2,000 events. The migration was done not through the main central server, but through some other one.

 

The question is: Are these events, although processed by the other server, ever end up with the main central server or not at all, e.g. these 1000 records imported that created 2,000 events through the other server were processed by that server and nothing eventswise was added to the main server? We are trying to use the other server without influencing the main server, e.g. not to add these events on the 800,000 events to become 802,000 events...

 

2. Would a drastic rebuild of a main (central) server help processing the outstanding events?... (We are staying for now on the same TRIM Version, but that new server has 12 time better CPU and memory power)

 

New version of TRIM will be implemented in January 2014, but we can not wait for so long with these events problems

 

Thanks

 

 

 

 

 

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Scheduled Event Triggers issue - Big problem, 7.1.1828 - Urgent

1.  That is expected.

2. Possibly.  The issue is more in the configuration of your record types, retention schedules, and triggers.  Throwing more resources may help, but if you don't solve the underlying problem then it's not going to go away.

 

Use this link for more information:  http://support.openview.hp.com/selfsolve/document/KM765264?searchIdentifier=31e035dc%3a13f88a33b01%3a393b&resultType=document&documentURL=KM765264&resultsURL=%2fselfsolve%2fdocuments&allowReturn=true&searchString=trigger&searchKey=2013-06-29+05%3a41%3a46

---------
Erik
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.