Hello all,

I am just starting to set up the Resource Govenor and need a little help creating a rule. I am looking for it to kill the report request/agent if it runs over a certain amount of time.

I have installed RMAT 7.6.3 and there appears to be a section for global rules that has parameters for CPU time and elapsed time (in seconds). So I set the elapsted time to 900 seconds (15 minutes) to test because I have a report that runs for 20-30 minutes and I wanted to see if it would kill it. So I started the report and at the 15 minute mark, it did not stop it.

Am I not understanding how this works properly? Or do I need to create a custom rule to do this?

Any help is greatly appreciated.

Thanks,

This message has been edited. Last edited by: MO Admin,

It has been a really really long time since I've used this, so ... grain of salt and all that.

Your understanding of what should happen is correct.

Check to ensure that the rule is not running under advise mode. If I remember correctly, when you build a rule, the rule is not implemented as stated, rather it advises you via a message in the HTML response object when a rule has been broken. Once you remove the advise attribute on the rule, then it is suppose to work as documented.

This particular rule is listed un the the Rule Parameters section of RMAT. It is called DEFAULT, the state is set to ON and is uneditable. There is also a seperate section of 'Build Rules', but it appers to be specific to a table or source being picked. I want this rule to be global.

I can create a new rule under 'Rule Parameters' where I can edit the state, but the only options are ON and OFF...no ADVISE.

I may just need to open a ticket with support. It seems like there are very few people on the forum that have experience with RMAT.

Thank you for your suggestion and time.

Ok, I am less tired now. I made a mistake with my last post. RMAT is suppose to stop actions preemptively based on past learned knowledge. It is suppose to predict when a query will take too long, and not allow it to run at all.

If you wish to stop a query that is taking too long, you need to define that in the data service. From the configuration page of the server console, open the data services. Edit the default service (or what ever one you want) and change the connection_limit to 900. That should do what you are looking for.

Awesome. That is what I needed. I guess I don't really need Resource Govenor at all.

Thank you very much.