Oracle Security By William Heney, Marlene Theriault
Table of Contents
Preface
Conventions Used in This Book
The following conventions are used in this book:
Indicates a tip, suggestion, or general note. For example, we'll tell you if you need to use a particular Oracle version or if an operation requires certain privileges.
Indicates a warning or caution. For example, we'll tell you if Oracle does not behave as you'd expect or if a particular operation has a negative impact on performance.
Italic
Used for script names, filenames, and directory names , and Oracle usernames.
Constant width
Used for code examples.
Constant width italic
In some code examples, indicates an element (e.g., a filename) that you supply.
UPPERCASE
In code examples, generally indicates Oracle keywords.
lowercase
In code examples, generally indicates user -defined items such as variables , parameters, etc.
punctuation
In code examples, enter exactly as shown.
/* and */
In code examples, these characters delimit a comment, which can extend from one line to another.
[ ]
In syntax descriptions, square brackets enclose optional items.
This book contains many examples of SQL scripts that we hope will help improve your database security. Wherever possible in this code, we've followed the conventions listed above. Using these conventions helps make the usage clear and also ensures consistency both within this book and across the O'Reilly Oracle line. However, we don't endorse this style for everyone and recognize that in the real world, DBAs and developers write code in a far less structured and consistent style. Where we obtained working scripts from other sources, we have preserved the original formatting to avoid any possible confusion.
