 |
| Unix for Oracle DBAs Pocket Reference 2001, Podręczniki, 130 linux and unix ebooks, unix |
 |
|
|
[ Pobierz całość w formacie PDF ] Unix for Oracle DBAs Pocket Reference By Publisher : O'Reilly Pub Date : January 2001 ISBN : 0-596-00066-9 • Ta b l e o f Pages : 110 • • • • • Chapter 1. Unix for Oracle DBAs Pocket Reference 1.1 Introduction The Unix for Oracle DBAs Pocket Reference is a quick reference describing the Unix commands most often used by Oracle database administrators. It's the result of my 20 years of accumulating Unix tips and techniques. For each of the commands included in this book, I've provided the basic syntax and a short, illustrative example. This guide also contains many short Unix scripts that should save you dozens of hours of manual effort. I've organized the commands and examples in this book into the following major topic areas: Understanding Unix Gives you a little bit of the history of Unix and tells you some things that you need to know regarding case sensitivity, safety, and shells. Building Unix Commands Describes the process of creating complex Unix commands for Oracle. Unix Server Environment Describes the commands that make Unix easier for DBAs. Process Management Describes the basic Unix commands you use to display and manage server processes. Server Values Shows you how to display relevant server values in Unix. Memory and CPU Management Shows the main commands used to display information about memory segments, swap space, and semaphores used by an Oracle database. Also covers commands used to monitor CPU utilization. Semaphore Management Shows you how to monitor semaphore usage by your Oracle server and how to remove semaphore sets for an instance that has crashed. System Log Messages Shows you how to view operating-system log files. Server Monitoring Describes the details of using the server utilities vmstat , sar , and glance . File Management Describes commands that assist in file management tasks. Disk Management Shows you how to get information about the disks on your system. This section includes commands to list physical volumes, logical volumes, and mount points. Miscellaneous Shell Scripts Presents a number of shell scripts that I've found to be useful over the years, but that don't fit into any of the other sections. Writing this pocket reference was especially challenging because of the dialect differences between the major implementations of Unix. For example, commands in HP-UX are often different from those in Sun Solaris. I've emphasized commands that are common to all Unix dialects. Where differences occur, I've attempted to cover the following platforms: HP-UX, IBM AIX, and Sun Solaris. You'll also find some specific dialect commands for IRIX and DEC Unix. In addition to experimenting with the commands shown in this book, I encourage you to read more about them in books such as Unix in a Nutshell by Arnold Robbins (O'Reilly). Also, remember that the online Unix manpages are a great source of information about Unix commands. For example, to learn about the cat command, enter man cat at the command prompt. 1.1.1 Acknowledgments This type of book requires the dedicated efforts of many people, and I have worked closely as a team with many others who have supported this effort. Foremost, I need to acknowledge the efforts of my wife, Janet Burleson, whose impatience with Unix syntax led to the development of this book. This book certainly would not have been possible without a tremendous amount of hard work and support from the staff of O'Reilly & Associates. In particular, I would like to express my thanks to Jonathan Gennick, one of the Oracle Series editors, whose dedication to quality added a great deal of value to this text. Jonathan provided countless hours of work editing and improving each section in this book. Three technical reviewers also contributed generously of their time and efforts in order to make this a better book. My thanks to Dan Hardin, John-Paul Navarro, and Joseph Testa for their many comments and suggestions. Ellie Volckhausen designed the cover, and I want to thank her (I think) for giving me the fly book. It's certainly a memorable distinction. Flies are annoying, as is Unix at times. It's my sincere hope that after reading this book you will find Unix to be much less annoying than any pesky fly. 1.1.2 Conventions Used in This Book It is important to remember that all Unix commands are case-sensitive and should be entered exactly as displayed in this text. The following conventions are used in this book: Italics Used for script, file, and directory names, variables, utilities, commands in text, and new terms where defined. Constant Width Used for code examples. Constant Width Italics In some code examples, indicates an element (e.g., a filename) that you supply. Constant Width Bold Used to indicate user input in code examples. [] In syntax examples, square brackets enclose optional items. Indicates a tip, suggestion, or general note. Indicates a warning or caution. 1.1.3 Long Code Lines One aspect of Unix that caused my editor and me much consternation as we worked on this book was the problem of dealing with long Unix code lines in a narrow book format. When you start combining several Unix commands together as one large compound command, you quickly exceed the 50 characters or so that fit on one printed line in this book. Tabular output from the various monitoring utilities also typically exceeds 50 characters in width. After much discussion and debate, we came up with some solutions. Our approach to handling long code lines recognizes the following four categories: • Long commands introduced by preceding text • Long commands in input/output examples • Wide columnar output • Unix script examples Long commands that appear by themselves, and that are introduced by preceding text, are simply allowed to wrap to the width of the printed line. For example: ps -ef|grep "ora_"|grep -v grep|grep $ORACLE_SID|awk '{print $2}'|xargs kill -9 In these cases, it's usually obvious from the context that the multiple printed lines really represent one long Unix command. Similarly, I allow commands to wrap in input/output examples, as shown here: [ Pobierz całość w formacie PDF ] |