Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • Which database files does SnapCenter for Oracle create Snapshots on ?
      https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Which_database_files_does_SnapCenter_for_Oracle_create_Snapshots_on
      Oracle database table space files are the primary snapshot target on ONTAP volumes for backups, this snapshot gets a _1 name extension. Oracle archive log backups, are the secondary target for Snapsho...Oracle database table space files are the primary snapshot target on ONTAP volumes for backups, this snapshot gets a _1 name extension. Oracle archive log backups, are the secondary target for Snapshot backups with _0 extension on the snapshot name, except when (Active) DataGuard is used This means that control files, temp files and, for Data Guard (active) standby databases, the archive logs, can all be on local storage.
    • SAP HANA backup archive logs are not getting cleaned at all, disregarding the retention policy in SnapCenter
      https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SAP_HANA_backup_archive_logs_are_not_getting_cleaned_at_all_disregarding_the_retention_policy_in_SnapCenter
      Applies to SnapCenter Plug-in for SAP HANA (SCHANA) 4.x Issue SCHANA snapshot backups age the Snapshots according to the retention setting, but the HANA archive logs are not deleted within that retent...Applies to SnapCenter Plug-in for SAP HANA (SCHANA) 4.x Issue SCHANA snapshot backups age the Snapshots according to the retention setting, but the HANA archive logs are not deleted within that retention.
    • SnapCenter for Oracle asks for archive logs on cloning and cannot recover automatically
      https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_for_Oracle_asks_for_archive_logs_on_cloning_and_cannot_recover_automatically
      Applies to SnapCenter Plug-in for Oracle (SCO) Issue When cloning using Until Cancel, Point In Time (PIT) or SCN, SCO will fail to recover the database with errors: ORA-00308: cannot open archived log...Applies to SnapCenter Plug-in for Oracle (SCO) Issue When cloning using Until Cancel, Point In Time (PIT) or SCN, SCO will fail to recover the database with errors: ORA-00308: cannot open archived log '/u02/archivelogs/ORASID/arch1_123_456789012.arc' ORA-01195: online backup of file 1 needs more recovery to be consistent
    • During archive log pruning with SMO, RMAN complains that the Oracle Version is mismatched
      https://kb.netapp.com/Legacy/SnapManager/Archive_log_pruning_with_RMAN_complains_that_the_Oracle_Version_is_mismatched
      SnapManager for Oracle (SMO) for Windows 3.4.x SnapManager for SAP (SMSAP) for Windows 3.4.x After upgrading a database from (e.g.) Oracle 12.1 to Oracle 12.2, during the Archive Log Pruning SnapManag...SnapManager for Oracle (SMO) for Windows 3.4.x SnapManager for SAP (SMSAP) for Windows 3.4.x After upgrading a database from (e.g.) Oracle 12.1 to Oracle 12.2, during the Archive Log Pruning SnapManager job, the following error sometimes (*) occurs: RMAN-06429: TARGET database is not compatible with this version of RMAN RMAN-06618: RMAN client and database release mismatch; indicated database release is 12.2.0.1