Introduction

Oracle DBA Survival Guide focuses on the job of the database administrator. Much
of the text describes Oracle technical topics, but they are presented as background
material to understand how to deal with problems and why things work the way they
do. Practical experience and solutions to problems that I have encountered are
inserted along the way. The book is divided into many topics to enable you to focus
on those that are most important to your immediate situation. You can save the
remaining chapters for a cold winter night by the fireplace.
This is a thick book. Its usefulness on the job will be determined by how quickly you
can find the information that you need. The following quick-access tools have been
used:
u Summary lists of contents at the beginning of each part and each chapter
u Liberal use of bullet-points and lists
u Note, Tip, Caution, and Warning boxes
u Checklists
u Illustrations, screen shots, and tables for ready reference
Part IV focuses on the development of a database administration scheme. This is a
turning point for the book because it marks where the reader has been presented
CONTENTS xix
with the background material, tools, and alternatives needed to perform the job of
the DBA. Here is where the focus shifts from the detailed “how do I” to the formation
of an overall vision of what is to be accomplished and how. DBAs should form a clear
vision of the “big picture” for several reasons:
u Many DBAs have extremely heavy workloads; an overall view helps you
avoid duplicated or wasted effort (if you’re lucky, you may even get home on
time occasionally).
u Because the database is the central point for many different applications
and systems, the DBA is often asked questions that relate to the overall
flow of information in the business. There are a lot of people who know
their niches very well, but few understand the functioning of the entire
organization. The DBA is often asked to provide this understanding for
corporate data.
u Oracle is, by its very nature, a complex system. You need to understand
exactly what is going on, exactly what is running, and exactly where
everything is to be able to solve problems. Often a problem in one place is
actually only a symptom of a larger problem in another part of the system.
Very few, if any, readers will read this book cover to cover in one sitting. However,
the task descriptions, experiences, technical background topics, and touch of
philosophy (that I cannot help interjecting) provide the balance needed by Oracle
DBAs in the field.