Skip to main content
NetApp Knowledge Base

CSNAPC-12469: [RFE] Request to add functionality for handling PDB-level incarnations in SCO

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Issue

  • SnapCenter plugin for Oracle Database (SCO) doesn't have a capability to handle PDB-level incarnation.
  • After a PDB point-in-time recovery (PITR), the PDB is opened with OPEN RESETLOGS, which creates a new PDB incarnation (V$PDB_INCARNATION), and any later PITR to an SCN or time on an earlier (now orphaned) PDB incarnation fails with RMAN-5019.

RMAN-03002: failure of recover command at <MM/DD/YYYY> <HH:MI:SS>
RMAN-05109: UNTIL SCN (<XXXXXXXX>) is orphan incarnation of Pluggable Database <DB_NAME>
  • SCO cannot recover from this automatically, and the user has no way to tell in advance which backups can still be used on SnapCenter GUI.

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.