2009 Apr 28 10:28 AM
Hi,
Our organization would like to start using SCOV ( Coverage Analyzer ) on our Production system. From owr understanding, when the main switch is turned on, there are several jobs sheduled that compile all programs. This step should be very expensive in terms of system resources and when it is done on Production system - it could be crutual. My question: is there any way to make this step easier in terms of performance overhead? Maybe to run it on each Application Server seperately?
In general I would like to know if anyone has experience running SCOV on production system. Is there any effect on performance except the first compilcation step?
Thanks in advance,
Anna Lifshits-Agmon
Hi,
Our organization would like to start using SCOV ( Coverage Analyzer ) on our Production system. From owr understanding, when the main switch is turned on, there are several jobs sheduled that compile all programs. This step should be very expensive in terms of system resources and when it is done on Production system - it could be crutual. My question: is there any way to make this step easier in terms of performance overhead? Maybe to run it on each Application Server seperately?
In general I would like to know if anyone has experience running SCOV on production system. Is there any effect on performance except the first compilcation step?
Thanks in advance,
Anna Lifshits-Agmon
2009 Apr 29 8:04 AM
Hi,
Its better to run SCOV in the Quality system. You can refresh the qualoity system with all production data and then run SCOV on QA system.
2009 May 14 2:15 PM
you might want to take a look at OSS note 626215. We recently ran this overnight in our development system and it fell over, running out of tablespace in certain areas. Next time we ran it, we used the note, extended the necessary tablespaces and made sure we kept an eye on it. It took a day to run in our development system as it generates every program on the system. We've not yet tried it on Production.