There are a few things you can do that will help if you are extremely low on resources and reduce the memory usage. This is applicable for Version 7.0
- Make sure you are using the latest Dbvisit standby. There is a major performance improvement using version 7.0.10 and later. It is recommended to use the latest version available (7.0.14 at time of writing).
- Do not use the Dbvisit GUI or the GUI scheduler. You can run Dbvisit via the Unix Cron schedule. You can then shutdown the GUI (
dbvserverd) saving that memory/cpu.
- If you are using version 7 of Standby, you can possibly disable Dbvnet and just use SSH. Set the
DBVNETport to null / empty value. Make sure an SSH port is set in the DDC file. Also the oracle Unix account must be able to SSH between the primary/standby servers without passwords.
COMPARE_CHECKSUM = Nin the primary DDC files. The change will be applied to standby DDC on next run.
RUN_INSPECT=Nin the primary DDC files. The change will be applied to standby DDC on next run. But please note if you do this the internal repository will not have historical information for reporting. If you do not use this feature, then setting this value will help.
- You can possibly run Dbvisit on only one of the nodes, but then you must use the
RAC_TAKEOVER_FORCE=Yoption in the DDC.
We suggest to try out first five options , Few more tuning options have been provided in the below link.
Donna Zehl May 14, 2014 02:26