Storm season is back, bringing with it the potential for significant weather events. If you have clients in areas prone to infrastructure disruption, visit the Disaster Recovery Resources guide for preparedness information. Datto recommends performing proactive disaster recovery testing to mitigate potential downtime. See our articles about the importance of disaster recovery testing and Preparing For A Cloud Virtualization Test: Policies, Procedures, And Partner Responsibilities to learn more. For live updates, follow @datto on Twitter.

Oracle Databases: Oracle VSS Memory Leak

Follow

Topic

This article discusses issues that may be found when using ShadowSnap's VSS backups as well as Oracle's Intellisnap backup engine.

Environment

  • ShadowSnap Agent
  • Oracle Intellisnap 11

Overview

As discussed in this article via IntelliSnap, there is a known issue with the Oracle VSS writer in Oracle 11:

"There is a known issue with Oracle VSS Writer memory leak (metalink ID 1358570.1). Hence, if Oravssw.exe consumes more memory, restart the service."

Workaround

This issue primarily manifests with Oracle 11, although other versions may be affected. Our findings have shown that the memory leak can eventually make its way into the pagefile of a device and cause a server to run out of memory, hindering all server operations. Restarting the service is a known fix. If you'd like less VSS processes to be occurring, you can configure backups for the impacted server to use the STC Backup Engine, but the issue may still persist in the Oracle VSS writer.

Should this issue persist, contact Oracle support for further assistance.


Was this article helpful?

1 out of 1 found this helpful

You must sign in before voting on this article.

Calling all Partners! We want to hear your feedback! Please participate in this quick survey and help us build a better, more-relevant Knowledge Base!

Want to talk about it? Head on over to our Community Forum!