Table of Contents
- Title and Copyright Information
- Preface
-
Part I Overview of Backup and Recovery
-
1
Introduction to Backup and Recovery
- 1.1 Purpose of Backup and Recovery
- 1.2 Oracle Backup and Recovery Solutions
- 1.3 Comparison of Oracle Backup Techniques
- 1.4 About Oracle Flashback Technology
- 1.5 About Data Recovery Advisor
- 1.6 RMAN and Oracle Enterprise Manager Cloud Control
- 1.7 About Zero Data Loss Recovery Appliance
- 1.8 Backup and Recovery Documentation Roadmap
-
2
Getting Started with RMAN
- 2.1 Overview of the RMAN Environment
- 2.2 Starting RMAN and Connecting to a Database: Quick Start
- 2.3 Showing the Default RMAN Configuration
-
2.4
Backing Up a Database: Quick Start
- 2.4.1 About Typical RMAN Backup Options
- 2.4.2 Backing Up a Database in ARCHIVELOG Mode
- 2.4.3 Backing Up a Database in NOARCHIVELOG Mode
- 2.4.4 Making Incremental Backups: Quick Start
- 2.4.5 Making Incrementally Updated Backups
- 2.4.6 Validating Database Files and Backups: Quick Start
- 2.4.7 Scripting RMAN Operations
- 2.5 Reporting on RMAN Operations: Quick Start
- 2.6 Maintaining RMAN Backups
- 2.7 Diagnosing and Repairing Failures with Data Recovery Advisor: Quick Start
- 2.8 Rewinding a Database with Flashback Database: Quick Start
- 2.9 Restoring and Recovering Database Files: Quick Start
-
1
Introduction to Backup and Recovery
-
Part II Starting and Configuring RMAN and Flashback Database
-
3
Recovery Manager Architecture
- 3.1 About the RMAN Environment
- 3.2 About RMAN Command-Line Client
- 3.3 About RMAN Channels
- 3.4 About the RMAN Repository
- 3.5 About Media Management Using RMAN
- 3.6 About the Fast Recovery Area
- 3.7 About RMAN in a Data Guard Environment
- 3.8 About RMAN in a Recovery Appliance Environment
-
4
Starting and Interacting with the RMAN Client
- 4.1 Starting and Exiting RMAN
-
4.2
Making Database Connections with RMAN
- 4.2.1 About RMAN Database Connection Types
- 4.2.2 About Authentication for RMAN Database Connections
- 4.2.3 Methods of Making RMAN Database Connections
- 4.2.4 About Performing Operations on CDBs and PDBs
- 4.2.5 Connecting as Target to the Root
- 4.2.6 Connecting as Target to a PDB
- 4.2.7 Connecting RMAN to an Auxiliary Database
- 4.2.8 Making RMAN Database Connections Within Command Files
- 4.3 Diagnosing RMAN Connection Problems
- 4.4 Entering RMAN Commands
- 4.5 Setting Globalization Support Environment Variables for RMAN
- 4.6 Specifying the Location of RMAN Output
- 4.7 Checking RMAN Syntax
- 4.8 Using the RMAN Pipe Interface
-
5
Configuring the RMAN Environment
- 5.1 About Configuring the Environment for RMAN Backups
- 5.2 Showing and Clearing Persistent RMAN Configurations
- 5.3 Configuring the Default Device for Backups: Disk or SBT
- 5.4 Configuring the Default Type for Backups: Backup Sets or Copies
- 5.5 Configuring Channels
- 5.6 Configuring Control File and Server Parameter File Autobackups
-
5.7
Configuring RMAN to Make Backups to a Media Manager
- 5.7.1 Prerequisites for Using a Media Manager with RMAN
- 5.7.2 Determining the Location of the Media Management Library
- 5.7.3 Configuring Media Management Software for RMAN Backups
- 5.7.4 Testing Whether the Media Manager Library Is Integrated Correctly
- 5.7.5 Configuring SBT Channels for Use with a Media Manager
- 5.8 Configuring RMAN to Make Backups to Recovery Appliance
- 5.9 Configuring Locations for Control Files and Redo Logs
- 5.10 Configuring the Fast Recovery Area
- 5.11 Configuring the Backup Retention Policy
- 5.12 Backup Optimization and the CONFIGURE command
- 5.13 Configuring an Archived Redo Log Deletion Policy
- 5.14 Configuring RMAN in a Data Guard Environment
-
6
Configuring the RMAN Environment: Advanced Topics
- 6.1 Configuring Advanced Channel Options
- 6.2 Configuring Advanced Backup Options
- 6.3 Configuring Auxiliary Instance Data File Names
- 6.4 Configuring the Snapshot Control File Location
- 6.5 Configuring RMAN for Use with a Shared Server
- 6.6 Enabling Lost Write Detection
- 6.7 Enabling Shadow Lost Write Protection
-
7
Using Flashback Database and Restore Points
- 7.1 Overview of Flashback Database, Restore Points and Guaranteed Restore Points
- 7.2 About Logging for Flashback Database and Guaranteed Restore Points
- 7.3 Prerequisites for Flashback Database and Restore Points
- 7.4 Using Normal and Guaranteed Restore Points
- 7.5 Using Flashback Database
-
3
Recovery Manager Architecture
-
Part III Backing Up and Archiving Data
-
8
RMAN Backup Concepts
- 8.1 About Consistent and Inconsistent RMAN Backups
- 8.2 About Online Backups and Backup Mode
-
8.3
About Backup Sets
- 8.3.1 About Backup Sets and Backup Pieces
- 8.3.2 About RMAN Block Compression for Backup Sets
- 8.3.3 About Binary Compression for RMAN Backup Sets
- 8.3.4 About RMAN Backup Undo Optimization
- 8.3.5 About Encryption for RMAN Backup Sets
- 8.3.6 About File Names for RMAN Backup Pieces
- 8.3.7 About Number and Size of RMAN Backup Pieces
- 8.3.8 About Number and Size of RMAN Backup Sets
- 8.3.9 About Multiplexed RMAN Backup Sets
- 8.3.10 About RMAN Proxy Copies
- 8.4 About RMAN Image Copies
- 8.5 About Sparse Backups
- 8.6 About Preplugin Backups
- 8.7 About Multiple Copies of RMAN Backups
- 8.8 About RMAN Control File and Server Parameter File Autobackups
- 8.9 About RMAN Incremental Backups
- 8.10 About Backup Retention Policies
-
9
Backing Up the Database
- 9.1 Overview of RMAN Backups
-
9.2
Specifying Backup Output Options
- 9.2.1 Specifying the Device Type for an RMAN Backup
- 9.2.2 Specifying Backup Set or Copy for an RMAN Backup to Disk
- 9.2.3 Specifying a Format for RMAN Backups
- 9.2.4 Specifying Tags for an RMAN Backup
- 9.2.5 Making Compressed Backups
- 9.2.6 Specifying Multisection Incremental Backups
- 9.2.7 Making Multisection Backups Using Image Copies
-
9.3
Backing Up Database Files with RMAN
- 9.3.1 Backing Up a Whole CDB
- 9.3.2 Backing Up the Root with RMAN
- 9.3.3 Backing Up the Root with Oracle Enterprise Manager Cloud Control
- 9.3.4 Backing Up PDBs with RMAN
- 9.3.5 Backing Up PDBs with Oracle Enterprise Manager Cloud Control
- 9.3.6 Backing Up Tablespaces and Data Files with RMAN
- 9.3.7 Backing Up Tablespaces and Data Files in a PDB
- 9.3.8 Backing Up Control Files with RMAN
- 9.3.9 Backing Up Server Parameter Files with RMAN
- 9.3.10 Backing Up a Database in NOARCHIVELOG Mode
- 9.3.11 Creating a Preplugin Backup of the Whole Database
- 9.3.12 Creating Preplugin Backups of PDBs Using RMAN
- 9.4 Backing Up Application Containers
- 9.5 Backing Up Sparse Databases with RMAN
- 9.6 Backing Up Archived Redo Logs with RMAN
-
9.7
Making and Updating RMAN Incremental Backups
- 9.7.1 Purpose of RMAN Incremental Backups
- 9.7.2 Planning an Incremental Backup Strategy
- 9.7.3 Making Incremental Backups
- 9.7.4 Incrementally Updating Backups
- 9.7.5 Creating a Base Backup of New Data Files
- 9.7.6 Using Block Change Tracking to Improve Incremental Backup Performance
- 9.8 Making Database Backups for Long-Term Storage
- 9.9 Backing Up RMAN Backups
-
10
Backing Up the Database: Advanced Topics
- 10.1 Limiting the Size of RMAN Backup Sets
- 10.2 Using Backup Optimization to Skip Files
- 10.3 Skipping Offline, Read-Only, and Inaccessible Files
- 10.4 Duplexing Backup Sets
- 10.5 Making Split Mirror Backups with RMAN
- 10.6 Encrypting RMAN Backups
- 10.7 Restarting RMAN Backups
- 10.8 Managing Backup Windows
-
8
RMAN Backup Concepts
-
Part IV Managing RMAN Backups
-
11
Reporting on RMAN Operations
- 11.1 Overview of RMAN Reporting
- 11.2 Listing Backups and Recovery-Related Objects
- 11.3 Reporting on Backups and Database Schema
- 11.4 Using V$ Views to Query Backup Metadata
- 11.5 Querying Recovery Catalog Views
-
12
Maintaining RMAN Backups and Repository Records
- 12.1 Overview of RMAN Backup and Repository Maintenance
- 12.2 Maintaining the Control File Repository
-
12.3
Maintaining the Fast Recovery Area
- 12.3.1 Deletion Rules for the Fast Recovery Area
- 12.3.2 Monitoring Fast Recovery Area Space Usage
- 12.3.3 Managing Space for Flashback Logs in the Fast Recovery Area
- 12.3.4 Responding to a Full Fast Recovery Area
- 12.3.5 Changing the Fast Recovery Area to a New Location
- 12.3.6 Disabling the Fast Recovery Area
- 12.3.7 Responding to an Instance Crash During File Creation
- 12.4 Updating the RMAN Repository
-
12.5
Deleting RMAN Backups and Archived Redo Logs
- 12.5.1 Overview of Deleting RMAN Backups
- 12.5.2 Deleting All Backups and Copies
- 12.5.3 Deleting Specified Backups and Copies
- 12.5.4 Deleting Expired RMAN Backups and Copies
- 12.5.5 Deleting Obsolete RMAN Backups Based on Retention Policies
- 12.5.6 Deleting Backups of Dropped PDBs
- 12.5.7 Deleting Preplugin Backups
- 12.6 Dropping a Database
-
13
Managing a Recovery Catalog
- 13.1 Overview of the RMAN Recovery Catalog
- 13.2 Creating a Recovery Catalog
- 13.3 Registering a Database in the Recovery Catalog
- 13.4 Cataloging Backups in the Recovery Catalog
-
13.5
Creating and Managing Virtual Private Catalogs
- 13.5.1 Overview of Virtual Private Catalogs
- 13.5.2 About Using the VPD Model for Virtual Private Catalogs
- 13.5.3 Creating Virtual Private Catalogs
- 13.5.4 Registering a Database with a Virtual Private Catalog
- 13.5.5 Revoking Privileges from a Virtual Private Catalog Owner
- 13.5.6 Upgrading Virtual Private Catalogs
- 13.6 Protecting the Recovery Catalog
-
13.7
Managing Stored Scripts
- 13.7.1 About Stored Scripts
- 13.7.2 Creating Stored Scripts
- 13.7.3 Replacing Stored Scripts
- 13.7.4 Executing Stored Scripts
- 13.7.5 Creating and Executing Dynamic Stored Scripts
- 13.7.6 Printing Stored Scripts
- 13.7.7 Listing Stored Script Names
- 13.7.8 Deleting Stored Scripts
- 13.7.9 Executing a Stored Script at RMAN Startup
-
13.8
Maintaining a Recovery Catalog
- 13.8.1 About Recovery Catalog Maintenance
- 13.8.2 Resynchronizing the Recovery Catalog
- 13.8.3 Updating the Recovery Catalog After Changing a DB_UNIQUE_NAME
- 13.8.4 Unregistering a Target Database from the Recovery Catalog
- 13.8.5 Resetting the Database Incarnation in the Recovery Catalog
- 13.8.6 Upgrading the Recovery Catalog
- 13.8.7 Importing and Moving a Recovery Catalog
- 13.9 Dropping a Recovery Catalog
-
11
Reporting on RMAN Operations
-
Part V Diagnosing and Responding to Failures
- 14 RMAN Data Repair Concepts
-
15
Diagnosing and Repairing Failures with Data Recovery Advisor
-
15.1
Overview of Data Recovery Advisor
- 15.1.1 Purpose of Data Recovery Advisor
- 15.1.2 Basic Concepts of Data Recovery Advisor
- 15.2 Basic Steps of Diagnosing and Repairing Failures
- 15.3 Listing Failures
- 15.4 Checking for Block Corruptions by Validating the Database
- 15.5 Determining Repair Options
- 15.6 Repairing Failures
- 15.7 Changing Failure Status and Priority
-
15.1
Overview of Data Recovery Advisor
- 16 Validating Database Files and Backups
-
17
Performing Complete Database Recovery
- 17.1 Overview of Complete Database Recovery
-
17.2
Preparing for Complete Database Recovery
- 17.2.1 Identifying the Database Files to Restore or Recover
- 17.2.2 Determining the DBID of the Database
- 17.2.3 Previewing Backups Used in Restore Operations
- 17.2.4 Validating Backups Before Restoring Them
- 17.2.5 Restoring Archived Redo Logs Needed for Recovery
- 17.2.6 Providing the Password Required to Decrypt Encrypted Backups
-
17.3
Performing Complete Database Recovery
- 17.3.1 About Complete Database Recovery
- 17.3.2 Performing Complete Recovery of a Whole CDB
- 17.3.3 Performing Complete Recovery of the Root
- 17.3.4 Performing Complete Recovery of a Tablespace in a CDB
- 17.3.5 Performing Complete Recovery of PDBs with RMAN
- 17.3.6 Performing Complete Recovery of PDBs with Cloud Control
- 17.3.7 Performing Complete Recovery of Tablespaces or Data Files in a PDB with RMAN
- 17.3.8 Performing Complete Recovery of Tablespaces in a PDB with Cloud Control
- 17.3.9 Performing Complete Recovery After Switching to a Copy
- 17.4 Performing Complete Recovery Using Preplugin Backups
- 17.5 Performing Complete Recovery of Application Containers
- 17.6 Performing Complete Recovery of Sparse Databases with RMAN
-
18
Performing Flashback and Database Point-in-Time Recovery
- 18.1 Overview of Oracle Flashback Technology and Database Point-in-Time Recovery
- 18.2 Rewinding a Table with Flashback Table
- 18.3 Rewinding a DROP TABLE Operation with Flashback Drop
- 18.4 Rewinding a Database with Flashback Database
- 18.5 Performing Database Point-in-Time Recovery
- 18.6 Performing Point-in-Time Recovery of Application PDBs
- 18.7 Performing Point-in-Time Recovery of Sparse Databases
- 18.8 Flashback and Database Point-in-Time Recovery Scenarios
- 19 Performing Block Media Recovery
-
20
Performing RMAN Recovery: Advanced Scenarios
- 20.1 Recovering a NOARCHIVELOG Database with Incremental Backups
- 20.2 Restoring the Server Parameter File
- 20.3 Performing Recovery with a Backup Control File
- 20.4 Performing Disaster Recovery
- 20.5 Restoring a Database on a New Host
- 20.6 Restoring Backups Created Using Older Versions of RMAN
- 20.7 Restoring and Recovering Files Over the Network
-
21
Performing RMAN Tablespace Point-in-Time Recovery (TSPITR)
- 21.1 Overview of RMAN TSPITR
- 21.2 TSPITR Restrictions, Special Cases, and Limitations
- 21.3 Planning and Preparing for TSPITR
- 21.4 Performing Fully Automated RMAN TSPITR
-
21.5
Overriding Defaults for RMAN TSPITR with an RMAN-Managed Auxiliary Database
- 21.5.1 Renaming TSPITR Recovery Set Data Files with SET NEWNAME
- 21.5.2 Naming TSPITR Auxiliary Set Data Files
- 21.5.3 Using Image Copies for Faster RMAN TSPITR Performance
- 21.5.4 Customizing Initialization Parameters for the Automatic Auxiliary Database in TSPITR
- 21.6 Performing RMAN TSPITR Using Your Own Auxiliary Database
- 21.7 Troubleshooting RMAN TSPITR
-
22
Recovering Tables and Table Partitions
-
22.1
Overview of Recovering Tables and Table Partitions
- 22.1.1 Purpose of Recovering Tables and Table Partitions from RMAN Backups
- 22.1.2 Basic Concepts of Recovering Tables and Table Partitions from RMAN Backups
-
22.1.3
Guidelines for Recovering Tables and Table
Partitions
- 22.1.3.1 Specify the Location of Auxiliary Database Files Created During Table Recovery
- 22.1.3.2 Specify the Name and Location of the Data Pump Export Dump File
- 22.1.3.3 Decide Whether to Import Recovered Tables and Table Partitions into the Target Database
- 22.1.3.4 Rename the Recovered Tables and Table Partitions
- 22.1.3.5 Recover Tables and Partitions Into a New Schema
- 22.1.4 Limitations of Recovering Tables and Table Partitions from RMAN Backups
- 22.2 Preparing to Recover Tables and Table Partitions
- 22.3 Recovering Tables and Table Partitions
- 22.4 Recovering Tables and Table Partitions in PDBs
- 22.5 Examples: Recovering Tables and Table Partitions From RMAN Backups
-
22.1
Overview of Recovering Tables and Table Partitions
-
Part VI Tuning and Troubleshooting
-
23
Tuning RMAN Performance
- 23.1 Purpose of RMAN Performance Tuning
- 23.2 Basic Concepts of RMAN Performance Tuning
- 23.3 Using V$ Views to Diagnose RMAN Performance Problems
- 23.4 Tuning RMAN Backup Performance
-
24
Troubleshooting RMAN Operations
- 24.1 Interpreting RMAN Message Output
- 24.2 Using V$ Views for RMAN Troubleshooting
- 24.3 Testing the Media Management API
- 24.4 Terminating an RMAN Command
-
23
Tuning RMAN Performance
-
Part VII Transferring Data with RMAN
-
25
Duplicating Databases
-
25.1
Overview of RMAN Database Duplication
- 25.1.1 Purpose of Database Duplication
- 25.1.2 Basic Concepts of Database Duplication
-
25.1.3
Types of Database Duplication
- 25.1.3.1 Overview of Backup-Based Duplication
- 25.1.3.2 Techniques for Performing Backup-Based Duplication
- 25.1.3.3 Overview of Active Database Duplication
- 25.1.3.4 Techniques for Performing Active Database Duplication
- 25.1.3.5 Factors that Determine Whether Backup Sets or Image Copies Are Used for Active Database Duplication
- 25.1.4 How RMAN Duplicates a Database
- 25.1.5 Contents of a Duplicate Database
- 25.1.6 About the Destination Host for Database Duplication
- 25.1.7 About Duplicate Database File Names
- 25.1.8 About Duplicating a Database to a Past Point-in-Time
- 25.1.9 Prerequisites for Duplicating a Database
- 25.2 Planning to Duplicate a Database
-
25.3
Preparing to Duplicate Databases
- 25.3.1 Configuring RMAN Channels for Use in Duplication
- 25.3.2 Making Backups Accessible to the Duplicate Instance
-
25.3.3
Preparing the Auxiliary Instance
- 25.3.3.1 Creating Directories for the Duplicate Database
- 25.3.3.2 Creating an Initialization Parameter File for the Auxiliary Instance
- 25.3.3.3 Creating a Password File for the Auxiliary Instance
- 25.3.3.4 Establishing Oracle Net Connectivity Between the Source Database and Auxiliary Instance
- 25.3.3.5 Starting the Auxiliary Instance
- 25.3.3.6 Making the Oracle Keystore Available to the Destination Host
- 25.3.4 Placing the Source Database in a Proper State
- 25.3.5 Starting RMAN and Connecting to Databases
- 25.3.6 Using the DUPLICATE Command to Duplicate Databases
- 25.4 Duplicating Databases
- 25.5 Duplicating Databases to Oracle Cloud
- 25.6 Duplicating an Oracle Cloud Database as an On-premise Database
- 25.7 Restarting DUPLICATE After a Failure
-
25.8
Examples: Duplicating Databases
- 25.8.1 Example: Duplicating a Database to a Remote ASM Host by Using Active Database Duplication with Backup Sets
- 25.8.2 Example: Duplicating a Database to a Remote Host by Using Active Database Duplication with Image Copies
- 25.8.3 Example: Duplicating a Database to a Remote Host by Using Backup-based Duplication without a Target Connection or Recovery Catalog
- 25.8.4 Example: Duplicating a Database to a Remote Host by Using Backup-Based Duplication with a Recovery Catalog
- 25.8.5 Example: Duplicating a Database to a Remote Host by Using Backup-based Duplication with a Target Connection
- 25.8.6 Example: Duplicating a Database to the Local Host by Using Active Database Duplication
- 25.8.7 Example: Duplicating PDBs to a New CDB by Using Active Database Duplication
- 25.8.8 Example: Duplicating a PDB to an Existing CDB by Using Active Duplication
- 25.8.9 Example: Performing Backup-based Duplication by Using Encrypted Backups
- 25.9 Example: Script to Duplicate a Database Using Backup-based Duplication
-
25.1
Overview of RMAN Database Duplication
-
26
Duplicating Databases: Advanced Topics
-
26.1
Specifying Alternative Names for Duplicate Database Files
- 26.1.1 Specifying Non-OMF or Non-ASM Alternative Names for Duplicate Database Files
-
26.1.2
Specifying OMF or ASM Alternative Names for Duplicate Database Files
- 26.1.2.1 Settings and Restrictions for OMF Initialization Parameters
- 26.1.2.2 Setting Initialization Parameters for ASM
- 26.1.2.3 Examples: Duplicating Databases to ASM
- 26.1.2.4 Using the SET NEWNAME Command to Create OMF or ASM Files
- 26.1.2.5 Using the DB_FILE_NAME_CONVERT Parameter to Generate Names for Non-OMF or ASM Data Files
- 26.1.2.6 Using the LOG_FILE_NAME_CONVERT Parameter to Generate Names for Non-OMF or ASM Log Files
- 26.2 Making Disk Backups Accessible Without Shared Disk
-
26.1
Specifying Alternative Names for Duplicate Database Files
-
27
Creating Transportable Tablespace Sets
- 27.1 Overview of Creating Transportable Tablespace Sets
- 27.2 Customizing Initialization Parameters for the Auxiliary Instance
- 27.3 Creating a Transportable Tablespace Set
- 27.4 Troubleshooting the Creation of Transportable Tablespace Sets
- 27.5 Transportable Tablespace Set Scenarios
-
28
Transporting Data Across Platforms
- 28.1 About Cross-Platform Data Transport
- 28.2 Overview of Cross-Platform Data Transport Using Image Copies
- 28.3 Performing Cross-Platform Tablespace Conversion with Image Copies
- 28.4 Performing Cross-Platform Data File Conversion with Image Copies
- 28.5 Performing Cross-Platform Database Conversion with Image Copies
-
28.6
Overview of Cross-Platform Data Transport Using Backup Sets
- 28.6.1 Basic Terms Used in Cross-Platform Data Transport Using Backup Sets
- 28.6.2 High-Level Steps to Transport Data Across Platforms Using Backup Sets
- 28.6.3 Scenarios in Which RMAN Automatically Creates a Cross-Platform Backup of the Database
-
28.6.4
Guidelines for Cross-Platform Data Transport
Using Backup Sets
- 28.6.4.1 About Backing Up Data on the Source Database for Cross-Platform Data Transport
- 28.6.4.2 About the Data Pump Export Dump File Used for Cross-Platform Tablespace Transport
- 28.6.4.3 About Restoring Data on the Destination Host During Cross-Platform Data Transport
- 28.6.4.4 About Selecting Objects to Be Restored from Cross-Platform Backups
- 28.6.4.5 About Names and Locations for Restored Objects on the Destination Database
- 28.6.4.6 About Importing the Data Pump Export Dump File Created During Cross-Platform Tablespace Transport
- 28.7 Performing Cross-Platform Database Transport with Backup Sets
-
28.8
Performing Cross-Platform Transport of
Tablespaces Using Backup Sets
- 28.8.1 Performing Cross-Platform Transport of Read-Only Tablespaces Using Backup Sets
-
28.8.2
Performing Cross-Platform Transport of Tablespaces Using Inconsistent Backups
- 28.8.2.1 Overview of Cross-Platform Transport of Tablespaces Using Inconsistent Backups
- 28.8.2.2 Requirements for Applying Cross-Platform Incremental Backups to the Restored Data Files
- 28.8.2.3 Steps to Transport Inconsistent Tablespaces to a Different Platform
- 28.8.2.4 Example: Performing Cross-Platform Inconsistent Tablespace Transport Using Backup Sets
- 28.8.3 Performing Cross-Platform Transport of Tablespaces in a PDB
- 28.9 Performing Cross-Platform Transport of Data Files Over the Network
-
25
Duplicating Databases
-
Part VIII Performing User-Managed Backup and Recovery
-
29
Making User-Managed Database Backups
- 29.1 Querying V$ Views to Obtain Backup Information
- 29.2 Making User-Managed Backups of Databases
-
29.3
Making User-Managed Backups of Tablespaces and Data Files
- 29.3.1 Making User-Managed Backups of Offline Tablespaces and Data Files
- 29.3.2 Making User-Managed Backups of Online Tablespaces and Data Files
- 29.4 Making User-Managed Backups of the Control File
- 29.5 Making User-Managed Backups of Archived Redo Logs
- 29.6 Making User-Managed Backups in SUSPEND Mode
- 29.7 Making User-Managed Backups to Raw Devices
- 29.8 Making Backups with Third-Party Snapshot Technologies
- 29.9 Verifying User-Managed Data File Backups
-
30
Performing User-Managed Database Flashback and Recovery
- 30.1 Performing Flashback Database with SQL*Plus
-
30.2
Overview of User-Managed Media Recovery
- 30.2.1 About User-Managed Restore and Recovery
- 30.2.2 Automatic Recovery with the RECOVER Command
- 30.2.3 Recovery When Archived Logs Are in the Default Location
- 30.2.4 Recovery When Archived Logs Are in a Nondefault Location
- 30.2.5 Recovery Using Storage Snapshot Optimization
- 30.2.6 Recovery Cancellation During User-Managed Recovery
- 30.2.7 Parallel Media Recovery
- 30.3 Performing Complete Database Recovery Using SQL*Plus
- 30.4 Performing Incomplete Database Recovery
- 30.5 Recovering a Database in NOARCHIVELOG Mode
-
30.6
Troubleshooting Media Recovery
- 30.6.1 About User-Managed Media Recovery Problems
- 30.6.2 Investigating the Media Recovery Problem: Phase 1
- 30.6.3 Trying to Fix the Recovery Problem Without Corrupting Blocks: Phase 2
- 30.6.4 Deciding Whether to Allow Recovery to Mark as Corrupt Blocks: Phase 3
- 30.6.5 Allowing Recovery to Corrupt Blocks: Phase 4
- 30.6.6 Performing Trial Recovery
-
31
Performing User-Managed Recovery: Advanced Scenarios
- 31.1 Responding to the Loss of a Subset of the Current Control Files
- 31.2 Recovering After the Loss of All Current Control Files
- 31.3 Re-Creating a Control File
- 31.4 Re-Creating Data Files When Backups Are Unavailable
- 31.5 Recovering NOLOGGING Tables and Indexes
- 31.6 Recovering Transportable Tablespaces
- 31.7 Recovering After the Loss of Online Redo Log Files
- 31.8 Recovering from a Dropped Table Without Using Flashback Features
- 31.9 Dropping a Database with SQL*Plus
-
29
Making User-Managed Database Backups
- Glossary
- Index