This is the scenario we are facing .
In our vortex scripts we generally name the db // <db= ..>
after we do some of the error processing before due to which some load is borne by testdb. But as this load goes out of control, when many users log in, the entire application fails.
We were thinking of having an automated process which could check the error log files of Vortex and based on the logs, (for eg .. one of the strategy would be checking for certain parameters like could not open locks ... and if many such errors are logged, then depending upon threshold run a shell script which has rmlocks command embedded in it)
Any idea how we can achieve it.
In our vortex scripts we generally name the db // <db= ..>
after we do some of the error processing before due to which some load is borne by testdb. But as this load goes out of control, when many users log in, the entire application fails.
We were thinking of having an automated process which could check the error log files of Vortex and based on the logs, (for eg .. one of the strategy would be checking for certain parameters like could not open locks ... and if many such errors are logged, then depending upon threshold run a shell script which has rmlocks command embedded in it)
Any idea how we can achieve it.