Skip to main content
NetApp Knowledge Base

SnapManager for Oracle or SAP backup completion time is taking too long

  1. Last updated
  2. Save as PDF
Views:
219
Visibility:
Public
Votes:
0
Category:
snapmanager-for-oracle
Specialty:
legacy
Last Updated:

Applies to

  • SnapManager for Oracle 3.4.x
  • Snapmanager for SAP 3.4.x

Issue

SnapManager for Oracle or SAP backup completion time is taking longer than expected, where SMSAP is also creating large BR*Backup Log files.

The following error may be displayed:

N archived log files do not exist in the active file system. These archived log files will not be included in the backup.

Missing files N

Query returned M distinct files

Optionally, many lines containing an error similar to the following can exist in the logs:

Archived log file /Database Name/ARCHIVELOG/Date/Log sequence number does not exist in the active file system.

Note: N stands for number of archived log files missed from active file system and M stands for total number of archived log files found in the backup.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.