Oracle RMAN for absolute beginners / Darl Kuhn.
Oracle RMAN for Absolute Beginners is a gentle introduction to the use of Oracle's Recovery Manager software to make backups of an Oracle database, and to restore all or part of a database in the event that data loss occurs. It is often said that a database administrator's #1 job responsib...
Saved in:
Online Access: |
Full Text (via O'Reilly/Safari) |
---|---|
Main Author: | |
Format: | eBook |
Language: | English |
Published: |
Berkeley, CA :
Apress,
2014.
|
Series: | Expert's voice in Oracle.
|
Subjects: |
Table of Contents:
- Machine generated contents note: ch. 1 Getting Started
- Connecting to Your Database
- Establishing OS Variables
- Using OS Authentication
- Using a Password File
- Starting the Database
- Stopping the Database
- Summary
- ch. 2 Files in Support of Backup and Recovery Operations
- Managing Control Files
- Viewing Control File Names and Locations
- Adding a Control File
- Moving a Control File
- Removing a Control File
- Managing Online Redo Logs
- Displaying Online Redo Log Information
- Determining the Optimal Size of Online Redo Log Groups
- Determining the Optimal Number of Redo Log Groups
- Adding Online Redo Log Groups
- Resizing and Dropping Online Redo Log Groups
- Adding Online Redo Log Files to a Group
- Removing Online Redo Log Files from a Group
- Moving or Renaming Redo Log Files
- Implementing Archivelog Mode
- Making Architectural Decisions
- Setting the Archive Redo File Location
- Enabling Archivelog Mode
- Disabling Archivelog Mode
- Reacting to a Lack of Disk Space in Your Archive Log Destination
- Backing Up Archive Redo Log Files
- Managing Tablespaces and Data files
- Understanding the First Five
- Understanding the Need for More
- Creating Tablespaces
- Renaming a Tablespace
- Controlling the Generation of Redo
- Changing a Tablespace's Write Mode
- Dropping a Tablespace
- Using Oracle Managed Files
- Creating a Bigfile Tablespace
- Enabling Default Table Compression within a Tablespace
- Displaying Tablespace Size
- Altering Tablespace Size
- Toggling Data Files Offline and Online
- Renaming or Relocating a Data File
- Summary
- ch. 3 User-Managed Backup and Recovery
- Implementing a Cold-Backup Strategy for a Noarchivelog Mode Database
- Making a Cold Backup of a Noarchivelog Mode Database
- Restoring a Cold Backup in Noarchivelog Mode with Online Redo Logs
- Restoring a Cold Backup in Noarchivelog Mode Without Online Redo Logs
- Scripting a Cold Backup and Restore
- Making a Cold Backup of an Archivelog Mode Database
- Implementing a Hot Backup Strategy
- Making a Hot Backup
- Scripting Hot Backups
- Understanding the Split-Block Issue
- Understanding the Need for Redo Generated During Backup
- Understanding That Data Files Are Updated
- Performing a Complete Recovery of an Archivelog Mode Database
- Restoring and Recovering with the Database Offline
- Restoring and Recovering with a Database Online
- Restoring Control Files
- Performing an Incomplete Recovery of an Archivelog Mode Database
- Summary
- ch. 4 Configuring RMAN
- Understanding RMAN
- Starting RMAN
- RMAN Architectural Decisions
- 1. Running the RMAN Client Remotely or Locally
- 2. Specifying the Backup User
- 3. Using Online or Offline Backups
- 4. Setting the Archive Redo Log Destination and File Format
- 5. Configuring the RMAN Backup Location and File Format
- 6. Setting the Autobackup of the Control File
- 7. Specifying the Location of the Autobackup of the Control File
- 8. Backing Up Archive Redo Logs
- 9. Determining the Location for the Snapshot Control File
- 10. Using a Recovery Catalog
- 11. Using a Media Manager
- 12. Setting the CONTROL_FILE_RECORD_KEEP_TIME Initialization Parameter
- 13. Configuring RMAN's Backup Retention Policy
- 14. Configuring the Archive Redo Logs' Deletion Policy
- 15. Setting the Degree of Parallelism
- 16. Using Backup Sets or Image Copies
- 17. Using Incremental Backups
- 18. Using Incrementally Updated Backups
- 19. Using Block Change Tracking
- 20. Configuring Binary Compression
- 21. Configuring Encryption
- 22. Configuring Miscellaneous Settings
- 23. Configuring Informational Output
- Segueing from Decision to Action
- Summary
- ch. 5 RMAN Backups and Reporting
- Preparing to Run RMAN Backup Commands
- Setting NLS_DATE_FORMAT
- Setting ECHO Setting ECHO
- Showing Variables
- Running Backups
- Backing Up the Entire Database
- Backing Up Tablespaces
- Backing Up Data Files
- Backing Up the Control File
- Backing up the spfile
- Backing Up Archive Redo Logs
- Backing Up FRA
- Excluding Tablespaces from Backups
- Backing Up Data Files Not Backed Up
- Skipping Read-Only Tablespaces
- Skipping Offline or Inaccessible Files
- Backing Up Large Files in Parallel
- Adding RMAN Backup Information to the Repository
- Taking Backups of Pluggable Databases
- While Connected to the Root Container
- While Connected to a Pluggable Database
- Creating Incremental Backups
- Taking Incremental-Level Backups
- Making Incrementally Updating Backups
- Using Block Change Tracking
- Checking for Corruption in Data Files and Backups
- Using VALIDATE
- Using BACKUP ... VALIDATE
- Using RESTORE ... VALIDATE
- Using a Recovery Catalog
- Creating a Recovery Catalog
- Registering a Target Database
- Backing Up the Recovery Catalog
- Synchronizing the Recovery Catalog
- Recovery Catalog Versions
- Dropping a Recovery Catalog
- Logging RMAN Output
- Redirecting Output to a File
- Capturing Output with Linux/Unix Logging Commands
- Logging Output to a File
- Querying for Output in the Data Dictionary
- RMAN Reporting
- Using LIST
- Using REPORT
- Using SQL
- Summary
- ch. 6 RMAN Restore and Recovery
- Determining if Media Recovery Is Required
- Determining What to Restore
- How the Process Works
- Using Data Recovery Advisor
- Using RMAN to Stop/Start Oracle
- Shutting Down
- Starting Up
- Complete Recovery
- Testing Restore and Recovery
- Restoring and Recovering the Entire Database
- Restoring and Recovering Tablespaces
- Restoring Read-Only Tablespaces
- Restoring Temporary Tablespaces
- Restoring and Recovering Data Files
- Restoring Data Files to Nondefault Locations
- Performing Block-Level Recovery
- Restoring a Container Database and Its Associated Pluggable Databases
- Restoring Archive Redo Log Files
- Restoring to the Default Location
- Restoring to a Nondefault Location
- Restoring a Control File
- Using a Recovery Catalog
- Using an Autobackup
- Specifying a Backup File Name
- Restoring the spfile
- Incomplete Recovery
- Determining the Type of Incomplete Recovery
- Performing Time-Based Recovery
- Performing Log Sequence-Based Recovery
- Performing SCN-Based Recovery
- Restoring to a Restore Point
- Restoring Tables to a Previous Point
- Flashing Back a Table
- Flashback Table To Before Drop
- Flashing Back a Table to a Previous Point in Time
- Flashing Back a Database
- Restoring and Recovering to Different Server
- Step 1 Create an RMAN Backup on the Originating Database
- Step 2 Copy the RMAN Backup to the Destination Server
- Step 3 Ensure That Oracle Is Installed
- Step 4 Source the Required OS Variables
- Step 5 Create an init.ora File for the Database to Be Restored
- Step 6 Create Any Required Directories for Data Files, Control Files, and Dump/Trace Files
- Step 7 Start Up the Database in Nomount Mode
- Step 8 Restore the Control File from the RMAN Backup
- Step 9 Start Up the Database in Mount Mode
- Step 10 Make the Control File Aware of the Location of the RMAN Backups
- Step 11 Rename and Restore the Data Files to Reflect New Directory Locations
- Step 12 Recover the Database
- Step 13 Set the New Location for the Online Redo Logs
- Step 14 Open the Database
- Step 15 Add the Temp File
- Step 16 Rename the Database
- Summary
- ch.
- 7 Handling Online Redo Log Failures
- Determining a Course of Action
- Restoring After Losing One Member of Multiplexed Group
- Recovering After Loss of All Members of Inactive Redo Log Group
- Dropping a Log File Group
- Recovering After Loss of All Members of Active Redo Log Group
- Recovering After Loss of All Members of Current Redo Log Group
- Summary
- ch. 8 Data Pump
- Data Pump Architecture
- Getting Started
- Taking an Export
- Importing a Table
- Using a Parameter File
- Exporting and Importing with Granularity
- Exporting and Importing an Entire Database
- Schema Level
- Table Level
- Tablespace Level
- Transferring Data
- Exporting and Importing Directly Across the Network
- Copying Data Files
- Features for Manipulating Storage
- Exporting Tablespace Metadata
- Specifying Different Data File Paths and Names
- Importing into a Tablespace Different from the Original
- Changing the Size of Data Files
- Changing Segment and Storage Attributes
- Filtering Data and Objects
- Specifying a Query
- Exporting a Percentage of the Data
- Excluding Objects from the Export File
- Excluding Statistics
- Including Only Specific Objects in an Export File
- Exporting Table, Index, Constraint, and Trigger DDL
- Excluding Objects from Import
- Including Objects in Import
- Common Data Pump Tasks
- Estimating the Size of Export Jobs
- Listing the Contents of Dump Files
- Cloning a User
- Creating a Consistent Export
- Importing When Objects Already Exist
- Renaming a Table
- Remapping Data
- Suppressing a Log File
- Using Parallelism
- Specifying Additional Dump Files
- Reusing Output File Names
- Creating a Daily DDL File
- Compressing Output
- Changing Table Compression Characteristics on Import
- Encrypting Data
- Exporting Views As Tables
- Disabling Logging of Redo on Import
- Interactive Command Mode
- Entering Interactive Command Mode
- Attaching to a Running Job
- Stopping and Restarting a Job
- Terminating a Data Pump Job.
- Note continued: Monitoring Data Pump Jobs
- Data Pump Log File
- Data Dictionary Views
- Database Alert Log
- Status Table
- Interactive Command Mode Status
- OS Utilities
- Data Pump Legacy Mode
- Data Pump Mapping to the exp Utility
- Data Pump Mapping to the imp Utility
- Summary.