Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle Database 12c Backup and Recovery Survival Guide

You're reading from   Oracle Database 12c Backup and Recovery Survival Guide A comprehensive guide for every DBA to learn recovery and backup solutions

Arrow left icon
Product type Paperback
Published in Sep 2013
Publisher Packt
ISBN-13 9781782171201
Length 440 pages
Edition 1st Edition
Arrow right icon
Toc

Table of Contents (22) Chapters Close

Oracle Database 12c Backup and Recovery Survival Guide
Credits
About the Author
Acknowledgement
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
1. Understanding the Basics of Backup and Recovery 2. NOLOGGING Operations FREE CHAPTER 3. What is New in 12c 4. User-managed Backup and Recovery 5. Understanding RMAN and Simple Backups 6. Configuring and Recovering with RMAN 7. RMAN Reporting and Catalog Management 8. RMAN Troubleshooting and Tuning 9. Understanding Data Pump 10. Advanced Data Pump 11. OEM12c and SQL Developer Scenarios and Examples – A Hands-on Lab Index

Troubleshooting RMAN performance using tracing


Enabling tracing on RMAN can be done in a couple of ways. As with any other trace file, the information collected will be huge and won't be very well formatted. This option should be used as the last option and in extreme cases only, for example, when RMAN has become completely non-responsive. As it won't be easy to find the relevant bottleneck from reading the raw trace files, you should let Oracle Support staff read and analyze it to find the actual reasons for the bottleneck. It's certainly not going to be a good idea to generate RMAN trace files on a regular practice.

There can be three possible ways to enable tracing for RMAN:

  • Using the DEBUG option

  • Using the 10046 trace event

  • Using the SQLNET tracing

The DEBUG command, as we discussed at the start of this chapter, is meant to debug various categories. Since for RMAN, the biggest reason for bottlenecks would be I/O, you can enable debugging using the following category:

$ rman target / log=...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image