Book Image

Oracle Database 11g : Underground Advice for Database Administrators

By : April Sims
Book Image

Oracle Database 11g : Underground Advice for Database Administrators

By: April Sims

Overview of this book

Today DBAs are expected to deploy and manage large databases with quality service and little to no downtime. The DBA's main focus is on increasing productivity and eliminating idle redundancy throughout the enterprise. However, there is no magic set of best practices or hard and fast rules that DBAs need to follow, and this can make life difficult. But if DBAs follow some basic approaches and best practices, tasks can be performed more efficiently and effectively.This survival guide offers previously unwritten underground advice for DBAs. The author provides extensive information to illuminate where you fit in, and runs through many of the tasks that you need to be watchful of, extensively covering solutions to the most common problems encountered by newcomers to the world of Oracle databases.The book will quickly introduce you to your job responsibilities, as well as the skills, and abilities needed to be successful as a DBA. It will show you how to overcome common problems and proactively prevent disasters by implementing distributed grid computing—scalable and robust—with the ability to redeploy or rearchitect when business needs change. Reduce downtime across your enterprise by standardizing hardware, software, tools, utilities, commands, and architectural components.This book will also help you in situations where you need to install Oracle Database 11g or migrate to new hardware making it compliant with a Maximum Availability Architecture. By the end of this book you will have learned a lot and gained confidence in your abilities. You will be armed with knowledge as to which tools are best used to accomplish tasks while proactively moving towards an automated environment.
Table of Contents (14 chapters)
Oracle Database 11g—Underground Advice for Database Administrators
Credits
About the author
About the reviewers
Preface
Index

Recommended order of migration


It is assumed that you, the DBA, would attempt multiple variations of a migration project in a non-production or standby environment first (See Chapter 5 for testing scenarios) for several weeks to months before even attempting any changes to production. As you should notice, the database is not the very last thing to migrate; it is the optimizer. You aren't really migrating the optimizer, as you will be enabling the newest features of the optimizer by manipulating the related database parameters. In reality, you are migrating the statistics (see Chapter 8 for more details).

Changes that survive testing are migrated to production gradually so that disruptions are kept to a minimum. The entire migration process should begin when a new version is first released, even while in beta. That would give a long period of time to test a new major release of Oracle. Often a year or more will pass before it is fully tested for production use. The following is a personal...