Oracle8 Administrator's Guide Release 8.0 A58397-01 |
|
This guide is for people who administer the operation of an Oracle database system. These people, referred to as "database administrators" (DBAs), are assumed to be responsible for ensuring the smooth operation of an Oracle database system and for monitoring its use. The responsibilities of database administrators are described in Chapter 1.
The Oracle8 Administrator's Guide contains information that describes the features and functionality of the Oracle8 and the Oracle8 Enterprise Edition products. Oracle8 and Oracle8 Enterprise Edition have the same basic features. However, several advanced features are available only with the Enterprise Edition, and some of these are optional. For example, to perform automated tablespace point-in-time recovery (using Recovery Manager), you must have the Enterprise Edition.
For information about the differences between Oracle8 and the Oracle8 Enterprise Edition and the features and options that are available to you, please refer to Getting to Know Oracle8 and the Oracle8 Enterprise Edition
Attention:
Readers of this guide are assumed to be familiar with relational database concepts. They are also assumed to be familiar with the operating system environment under which they are running Oracle.
As a prerequisite, all readers should read the first chapter of Oracle8 Concepts, "A Technical Introduction to the Oracle Server." This chapter is a comprehensive introduction to the concepts and terminology used throughout this guide.
Administrators frequently participate in installing the Oracle Server software and migrating existing Oracle databases to newer formats (for example, Version 7 databases to Oracle8 format). This guide is not an installation or migration manual.
If your primary interest is installation, see your operating system-specific Oracle documentation.
If your primary interest is database or application migration, see the Oracle8 Migration manual.
In addition to administrators, experienced users of Oracle and advanced database application designers might also find information in this guide useful.
However, database application developers should also see the Oracle8 Application Developer's Guide and the documentation for the tool or language product they are using to develop Oracle database applications.
Every reader of this guide should read Chapter 1 of the Oracle8 Concepts manual, "Introduction to the Oracle Server." This overview of the concepts and terminology related to Oracle provides a foundation for the more detailed information in this guide. The rest of the Oracle8 Concepts manual explains the Oracle architecture and features, and how they operate in more detail.
This guide contains the following parts and chapters.
This appendix contains several specific formulas for estimating space required by schema objects. |
This section explains the conventions used in this manual including the following:
This section explains the conventions used within the text.
Uppercase text is used to call attention to command keywords, object names, parameters, filenames, and so on.
For example, "If you create a private rollback segment, the name must be included in the ROLLBACK_SEGMENTS parameter of the parameter file."
Italicized words within text are book titles or emphasized words.
The syntax diagrams and notation in this manual show the syntax for SQL commands, functions, hints, and other elements. This section tells you how to read syntax diagrams and examples and write SQL statements based on them.
Keywords are words that have special meanings in the SQL language. In the syntax diagrams in this manual, keywords appear in uppercase. You must use keywords in your SQL statements exactly as they appear in the syntax diagram, except that they can be either uppercase or lowercase. For example, you must use the CREATE keyword to begin your CREATE TABLE statements just as it appears in the CREATE TABLE syntax diagram.
Parameters act as place holders in syntax diagrams. They appear in lowercase. Parameters are usually names of database objects, Oracle datatype names, or expressions. When you see a parameter in a syntax diagram, substitute an object or expression of the appropriate type in your SQL statement. For example, to write a CREATE TABLE statement, use the name of the table you want to create, such as EMP, in place of the table parameter in the syntax diagram. (Note that parameter names appear in italics in the text.)
This list shows parameters that appear in the syntax diagrams in this manual and examples of the values you might substitute for them in your statements:
SQL and SQL*Plus commands and statements are separated from the text of paragraphs in a monospaced font as follows:
INSERT INTO emp (empno, ename) VALUES (1000, 'JFEE); ALTER TABLESPACE users ADD DATAFILE 'users2.ora' SIZE 50K;
Example statements can include punctuation, such as commas or quotation marks. All punctuation in example statements is required. All example statements terminate with a semicolon (;). Depending on the application, a semicolon or other terminator may or may not be required to end a statement.
Uppercase words in example statements indicate the keywords within Oracle SQL. When you issue statements, however, keywords are not case sensitive.
Lowercase words in example statements indicate words supplied only for the context of the example. For example, lowercase words may indicate the name of a table, column, or file.
This guide provides examples of the dialog boxes and menus of Enterprise Manager, your primary utility for managing an Oracle database. Illustrations show the character mode Server Manager screen. However, the actual appearance of your screen may differ, depending on your system's user interface.
For more information, see the Oracle Enterprise Manager Administrator's Guide.