Re: Keeping OML active message table under 50K messages (best practice) (378 Views)
Reply
Regular Advisor
hlutz
Posts: 84
Registered: ‎11-23-2011
Message 1 of 7 (390 Views)

Keeping OML active message table under 50K messages (best practice)

Hi,

 

   We ran into an issue while I was out for an extended period in which we could not login using the Java GUI to OML.  We'd get a message indicating that the connection attempt timed out.  It was happening to our primary and backup servers.  I pointed out the possibility of it being because of so many messages being loaded and support advised that wasnt the issue.  When I eventually deleted the active messages in the backup server and then the primary (after downloading the critical and major messages), I was able to log back in.

 

   I found out why the active table filled up so fast (2 nodes out of control) but in the meanwhile was wondering if anyone could advise on a best practice for keeping the active message table under 50K messages.  I know about alerts that will appear in the events browser but I'm looking for something we can cron that can run regularly.  Commands like opcack just do all and don't have date filtering.  Others, like opcactdwn, have date filtering but wont help in this scenario. 

 

Thanks in advance,

Heidi

Please use plain text.
Honored Contributor
Goran Koruga
Posts: 1,280
Registered: ‎12-05-2002
Message 2 of 7 (378 Views)

Re: Keeping OML active message table under 50K messages (best practice)

Hello.

 

'opcack' does have some date filtering - the following options are available:

 

time_from,   time_to,  last_time_from,  last_time_to

 

As an alternative, you could write your own tool for this.  There's a number of tools in the "/opt/OV/OpC/examples/progs" directory that you can use as a starting point. Ask here if you need help with some specific task.

 

Regards,

Goran

Please use plain text.
Valued Contributor
Iris Berr
Posts: 66
Registered: ‎08-04-1999
Message 3 of 7 (371 Views)

Re: Keeping OML active message table under 50K messages (best practice)

Hello there,

 

you could use opcackmsg to acknowledge some old messages.

 

We have implemented some scripts which run as cronjobs to do so. 

 

First figure out the messages (message-id's) you want to acknowlege via an sql-statement, based on message groups and local-receiving-time. 

Then pass these message-id's to the opcackmsg command.

 

We even have created an "AUTOACK" operator which we use with the command to see that the messages have been acknowledged by our scripts.

 

Hope this helps,

 

best regards,

 

   Iris

 

Please use plain text.
Regular Advisor
hlutz
Posts: 84
Registered: ‎11-23-2011
Message 4 of 7 (360 Views)

Re: Keeping OML active message table under 50K messages (best practice)

Thanks, Iris, for the feedback.  Very helpful.

Please use plain text.
Regular Advisor
hlutz
Posts: 84
Registered: ‎11-23-2011
Message 5 of 7 (359 Views)

Re: Keeping OML active message table under 50K messages (best practice)

Thanks, Goran.  I never noticed that examples dir before.  I looked at it now after your post. May be useful.   Also, I see that I need to use the -e option on opcack to invoke those filters.  I didn't pick up on that when reading the man page at first.

 

Thanks again,

Heidi

Please use plain text.
Occasional Advisor
Om  Prakash
Posts: 11
Registered: ‎11-27-2007
Message 6 of 7 (191 Views)

Re: Keeping OML active message table under 50K messages (best practice)

Hi Goran

 

Is it possible to share the script to acknowlede the message?

 

Regards

Om

Please use plain text.
Honored Contributor
Goran Koruga
Posts: 1,280
Registered: ‎12-05-2002
Message 7 of 7 (185 Views)

Re: Keeping OML active message table under 50K messages (best practice)

Hello.

 

Which script do you mean?

 

Regards,

    Goran

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation