Donald K. Burleson Oracle Tips

Oracle8 RECOVERY MANAGER FACILITY

Oracle8 introduces the recovery manager RMAN, which is the Enterprise Backup Utility on steroids. RMAN allows backup of database files at the block level and automatically performs datafile compression by only backing up blocks that have been used or altered. In incremental mode, the RMAN only backs up blocks that have been altered or added in the database, greatly reducing the size of required backups.

RMAN also allows the following:

The above text is an excerpt from Mike Ault’s Oracle DBA Made Simple by Rampant TechPress.

RMAN uses a recovery catalog; however, you can use RMAN without a catalog from just the data stored in the control files, but you are restricted to a subset of RMANs capabilities in this mode. The catalog contains information on the following:

The above text is an excerpt from Mike Ault’s Oracle DBA Made Simple by Rampant TechPress.

RMAN creates backup sets that consist of backup pieces. Backup pieces are parts of the backup set at a size that is predetermined and usually based on backup media capacity of operating system file size limitations. Backup sets can be written to disk or secondary storage, can include a backup control file, and can span multiple OS files (pieces). Backup devices that are supported on your system are cataloged in the v$backup_device dynamic performance table.

RMAN backup sets that contain archive logs are called, appropriately enough, archivelog backup sets. With Oracle8 you cannot write archive logs directly to tape, but a job can be scheduled using RMAN to back archive log backup sets to tape or other storage.

RMAN produces either full or incremental backups. A full backup  is a backup of one or more data files that contains all blocks of the data file(s) that have been modified or changed. Full backups can be created out of:

The above text is an excerpt from Mike Ault’s Oracle DBA Made Simple by Rampant TechPress.

Each backup set can be associated with a tag that can be used to identify it in subsequent operations. The tag doesn’t have to be unique. RMAN selects the most recent backup set in the case of backup sets with duplicate tags.

RMAN automatically detects corruptions and logs these in v$backup_corruption and v$copy_corruption dynamic performance tables. Corrupt blocks are still backed up.

The above text is an excerpt from Mike Ault’s Oracle DBA Made Simple by Rampant TechPress.

Oracle Performance Troubleshooting

Oracle performance troubleshooting is one of the most complex areas of Oracle database administration.  To be successful, you need pre-written diagnostic scripts and expert advice.  In his latest book Oracle Performance Troubleshooting, Robin Schumacher shares his secrets and ready-to-run scripts.

Get your copy of Oracle Performance Troubleshooting today and receive immediate access to the Online Code Depot! It’s only $19.95 (I don’t think it is right to charge a fortune for books!) and you can buy it right now and get immediate access to the online code depot:

http://www.rampant-books.com/book_2003_1_perf.htm