Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 

 

Deletion RAC of Archive Redo Logs

Oracle RAC Cluster Tips by Burleson Consulting

This is an excerpt from the bestselling book Oracle Grid & Real Application Clusters.  To get immediate access to the code depot of working RAC scripts, buy it directly from the publisher and save more than 30%.


After a successful backup, the archive logs should be deleted.  RMAN can automate the deletion of archive logs. It is suggested that only the logs that have actually been backed up be deleted. To achieve the deletion of backed up archive logs, the BACKUP command is issued with either the DELETE INPUT or DELETE ALL INPUT clause following the ARCHIVELOG portion of the command.

The command to delete just the archive logs that have been backed up for instance v10g1 would be:

BACKUP DATABASE PLUS ARCHIVELOG delete INPUT;

The command used to delete all of the archive logs at the archive log destination would be:

BACKUP DATABASE PLUS ARCHIVELOG delete ALL INPUT;

To be absolutely sure that only backed up archive logs are deleted, use the DELETE command with a MAINTENANCE connection in RMAN. For the example with instances v10g1 and v10g2:

ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK CONNECT 'SYS/kr87m@ault1';
DELETE ARCHIVELOG LIKE '%arc_dest_1%'
BACKED UP 1 TIMES TO DEVICE TYPE sbt;
RELEASE CHANNEL;

ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK CONNECT 'SYS/kr87m@ault1';
DELETE ARCHIVELOG LIKE  '%arc_dest_1%'
BACKED UP 1 TIMES TO DEVICE TYPE sbt;
RELEASE CHANNEL;

The BACKED UP 1 TIMES clause appears in the above commands. This tells RMAN not to delete the archive logs unless it has a record of them being backed up at least once. The $arch_dest_1% token tells what logs to remove and translates into the value specified for log_archive_dest_1 for the instance specified in the connection alias, such as: @AULT1.

RMAN is capable of autolocating files it needs to backup. RMAN, through the database synchronization and resync processes, is aware of which files it needs to backup for each node. RMAN can only backup the files it has autolocated for each node on that node.

During recovery, autolocation means that only the files backed up from a specific node will be written to that node.

Backup Procedures for RMAN and RAC

Various aspects of the backup procedures using RMAN have been presented thus far. In this section, they will be tied into a coherent set of backup procedures. Essentially, RMAN scripts will be used to perform a cluster file system backup with a single drive, a raw file system backup with multiple drives, and a raw file system backup with a single drive.

CFS Single Tape Drive Backup

Perhaps the simplest RAC backup is the CFS backup using a single tape drive. Basically, one backup device and one channel are configured, and the backup command is ready to be issued. After connecting to both the RMAN catalog database and the target database, the following RMAN commands would be issued:

CONFIGURE DEVICE TYPE sbt PARALLELISM 1;
CONFIGURE DEFAULT DEVICE TYPE TO sbt;
BACKUP DATABASE PLUS ARCHVIELOG delete INPUT;

The backup set of commands is simple in a CFS single tape drive backup because all nodes can see all drives in the CFS array, which allows any node to backup the entire instance.

 


This is an excerpt from the bestselling book Oracle Grid & Real Application Clusters, Rampant TechPress, by Mike Ault and Madhu Tumma.

You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.

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


 

 
��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational