Oracle Database Administration: The Essential Refe

Errata for Oracle Database Administration: The Essential Refe

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page xvi
The following information was added to the Preface, in the

"How to Contact Us" section: "You can also send us messages electronically. To be put on the mailing list or request a catalog, send email to: info@oreilly.com To ask technical questions or comment on the book, send email to: bookquestions@oreilly.com We have a web site for the book, where we'll list examples, errata, and any plans for future editions. You can access this page at: http://www.oreilly.com/catalog/9781565925168/ For more information about this book and others, see the O'Reilly web site: http://www.oreilly.com"

Anonymous    Mar 01, 2000
Printed
Page 29

In the bottom half of the page, line 5 of the first bullet read: iniTEST It now reads: initTEST (it was missing a "t")

Anonymous    Jun 01, 1999
Printed
Page 35

Code in the middle of the page did read: CREATE TABLESPACE INDEX Now reads: CREATE TABLESPACE INDEXES

Anonymous    Mar 01, 2000
Printed
Page 54
(A note about RAID): All references to "RAID-0" have been changed

to "RAID-1" (3 occurances including turkey-note).

Anonymous    Jun 01, 1999
Printed
Page 55
Line 2, add after "with striping...": (RAID-0) so the line

now reads: "...with striping (RAID-0) of data across..."

Anonymous    Jun 01, 1999
Printed
Page 55

Line 2 of the first paragraph did read: "combines mirrored disks (as in RAID-0)..." Now reads: "combines mirrored disks (as in RAID-1)..."

Anonymous    Jan 01, 2001
Printed
Page 111

The last line on the page did read: num_of_blocks NUMBER Now reads: num_of_blocks NUMBER,

Anonymous    Jan 01, 2001
Printed
Page 112
Added the following line at the top of the page

num_of_bytes NUMBER

Anonymous    Jan 01, 2001
Printed
Page 114
In the first line on the page, changed "distinct keys" to "distinct_keys".

Anonymous    Jan 01, 2001
Printed
Page 114
In the code block in the middle of the page, the group of lines beginning

with: '&owner', and ending with: blks_gets_per_access have all been indented 8 spaces (to the same level, so they line up under the T in TRUNC).

Anonymous    Jan 01, 2001
Printed
Page 121
In the 8th line from the bottom in the second column, changed "CROP

SEQUENCE" to "DROP SEQUENCE".

Anonymous    Oct 01, 2001
Printed
Page 207

The last section of code, second line down, did read: FROM dba_segments It now reads: FROM dba_tables

Anonymous    Mar 01, 2000
Printed
Page 239
At the top, under HASH_JOIN_ENABLED - the default was listed as

"FALSE" - it is now listed as "TRUE".

Anonymous    Mar 01, 2000
Printed
Page 244

The note at the bottom of the page did read: "To override the destination that this parameter specifies, either specify a different destination for manual archiving or use the Server Manager command ARCHIVE LOG START filespec for automatic archiving, where filespec is the new archive destination." It now reads: "On some platforms (e.g., Windows NT) the LOG_ARCHIVE_DEST parameter specifies the name of a directory, while on others (e.g., Unix) it specifies a directory and filename prefix. Be sure to check the documentation for your operating system to determin the exact format to use."

Anonymous    Jan 01, 2001
Printed
Page 276

***NOTE: The following text describing the syntax of ALTER DATABASE should be inserted beginning on page 276. It is not possible to insert this text in a reprint, but we include it here for your reference.*** CREATE/ALTER DATABASE CREATE DATABASE [dbname] CONTROLFILE [REUSE] LOGFILE [GROUP integer] (filespec[,[GROUP integer] filespec ...]) [MAXLOGFILES integer] [MAXLOGMEMBERS integer] [MAXLOGHISTORY integer] [MAXDATAFILES integer] [MAXINSTANCES integer] [ARCHIVELOG | NOARCHIVELOG] [CHARACTER SET charset [NATIONAL CHARACTER SET charset DATAFILE (filespec[,filespec ...])[Autoextend_Clause] Creates a database and specifies parameters associated with it. ALTER DATABASE [dbname] {ARCHIVELOG | NOARCHIVELOG | MOUNT [[STANDBY | CLONE] DATABASE] | CONVERT | OPEN [READ WRITE [RESETLOGS | NORESETLOGS] | READ ONLY] | ACTIVATE STANDBY DATABASE | RENAME FILE 'filename` [,'filename' ...] TO 'filename` [,'filename' ...] | RENAME GLOBAL_NAME TO database[.domain[.domain ...]] | RESET COMPATIBILITY | ENABLE [PUBLIC] THREAD integer | DISABLE THREAD integer | CHARACTER SET character_set | NATIONAL CHARACTER SET character_set | CREATE DATAFILE 'filename'[,'filename' ...] [AS filespec] | DATAFILE 'filename'[,'filename' ...] {ONLINE | OFFLINE [DROP} | RESIZE integer[K | M] | END BACKUP | Autoextend_Clause } | TEMPFILE 'filename'[,'filename' ...] {ONLINE | OFFLINE DROP | RESIZE integer[K | M] | Autoextend_Clause } | ADD LOGFILE [THREAD integer] [GROUP integer] filespec[,[GROUP integer] filespec ...] | ADD LOGFILE MEMBER 'filename' [RESUSE] [,'filename' [RESUSE] ...] TO logfile_descriptor[,logfile_descriptor ...] | DROP {GROUP integer | 'filename` | ('filename','filename'[,'filename' ...])} | DROP LOGFILE MEMBER 'filename'[,'filename' ...] | CREATE STANDBY CONTROLFILE AS 'filename' [REUSE] | BACKUP CONTROLFILE TO {`filename' [REUSE] | TRACE {RESETLOGS | NORESETLOGS]} | RECOVER [AUTOMATIC FROM 'location'] RECOVER [STANDBY] DATABASE [UNTIL {CANCEL | TIME date | CHANGE integer}] | RECOVER [STANDBY] DATABASE USING BACKUP CONTROLFILE | RECOVER [STANDBY] TABLESPACE {tablespace | DATAFILE 'filename`} UNTIL [CONSISTENT WITH] CONTROLFILE | RECOVER TABLESPACE tablespace[,tablespace ...] | RECOVER DATAFILE filename[,filename] | RECOVER LOGFILE filename[,filename] | RECOVER CONTINUE [DEFAULT] | RECOVER CANCEL | RECOVER MANAGED STANDBY DATABASE {TIMEOUT integer | CANCEL [IMMEDIATE]} Changes one or more characteristics of an existing database. Keywords dbname Specifies the name of the database. May be one to eight characters long and must not be a reserved word. CONTROL FILE REUSE Specifies that one or more existing control files specified in INIT.ORA can be reused and overwritten. If this keyword is omitted and any of the control files named in INIT.ORA exists, an error will result. If the parameters specified require that the control file be larger than the current size, the command will fail. Note that this option is not normally used for a new database creation. LOGFILE Specifies the names of one or more redo log files to be created. MAXLOGFILES Specifies the maximum number of redo log file groups that can ever be created for the database. The default and maximum value are operating system-dependent. This value must be at least 2, and should be at least 3. MAXLOGMEMBERS Specifies the maximum number of copies of a redo log group that may exist in the database. The minimum is 1, and the default and maximum are operating system-dependent. MAXLOGHISTORY Specifies the maximum number of archived redo log file groups for automatic media recovery of the Parallel Server. The minimum value is 1, and the default and maximum are operating system-dependent. MAXDATAFILES Specifies the maximum number of datafiles that can ever be created for the database. The minimum is 1, but it should never be set lower than the largest number of datafiles ever created in the database. MAXINSTANCES Specifies the maximum number of instances that can have the database mounted and open. This parameter applies only to the Parallel Server. ARCHIVELOG Specifies that the database will be run in archivelog mode, which means that a redo log group must be archived before the redo log group can be reused. If the group has not been archived, the database will halt until archiving occurs successfully. This mode is required to perform media recovery. NOARCHIVELOG Specifies that redo log groups will not be archived and may be reused immediately by Oracle. This option is the default. CHARACTER SET Specifies the character set that the database will use to store data. This character set cannot be changed after database creation. The choices and default are operating system-dependent. NATIONAL CHARACTER SET Specifies the national character set that will be used for specifically designated columns. If omitted, the default database character set is used. DATAFILE Specifies the names of all datafiles in the database. If omitted, a single datafile will be created by default for the SYSTEM tablespace. Autoextend_Clause Specifies whether a data file will be extended automatically. See Chapter 4 for more details. MOUNT STANDBY DATABASE Specifies that the standby database be mounted. MOUNT CLONE DATABASE Specifies that the clone database be mounted. CONVERT Specifies that the database data dictionary be converted from Oracle7 to Oracle8 or Oracle8i. OPEN READ WRITE Specifies that the database be opened in read/write mode. This option is the default. RESETLOGS Resets the log sequence number to 1 and invalidates all redo entries in the existing online and archived log files. This option should only be specified after performing incomplete media recovery or when opening the database after performing media recovery with a backup control file; otherwise, NORESETLOGS should be used. If the database is opened with the RESETLOGS keyword, you should immediately perform a complete backup of the database. NORESETLOGS Makes no change to the status of the current log sequence number and redo log entries. OPEN READ ONLY Specifies that the database be opened in read-only mode, which makes queries possible but disables write operations. ACTIVATE STANDBY DATABASE Specifies that the state of the database be changed from standby to active. RENAME FILE filename1 TO filename2 Specifies that the name of a datafile, temporary file, or log file be changed in the control file. Note that this keyword does not affect the name of the operating system file. RENAME GLOBAL NAME TO Specifies that the global name of the database be changed to the supplied value, which may be up to eight characters. RESET COMPATIBILITY Specifies that the compatibility of the database be reset to the version specified. This change is effective the next time the database is started. ENABLE THREAD Specifies that the thread of redo log files is enabled in a Parallel Server environment. If the keyword PUBLIC is specified, the enabled thread is available to any instance. Otherwise, the thread is available only to an instance that specifically requests it. DISABLE THREAD Specifies that the thread of redo log files is disabled and made unavailable to all instance of a Parallel Server environment. CREATE DATAFILE Specifies that a new empty datafile be created in place of an old one (which may have been lost without backup). Media recovery must be performed before the datafile is usable. ONLINE Specifies that the datafile is to be brought online. OFFLINE Specifies that the datafile is to be brought offline. RESIZE Specifies that the size of the datafile is to be increased or decreased to the indicated size. END BACKUP Specifies that media recovery will not be performed when the database starts after a hot backup was interrupted. TEMPFILE Specifies that changes be made to a temporary datafile. DROP Specifies that the temporary datafile be removed from the database. ADD LOGFILE Specifies that one or more redo log file groups be added. THREAD may be indicated in a Parallel Server environment. ADD LOGFILE MEMBER Specifies that a new member filename be added to an existing redo log file group. REUSE may be used to indicate that filename already exists. logfile_descriptor Specifies an existing redo log file group either as GROUP integer or as a list of filenames. DROP GROUP Specifies that the entire redo log file group is to be dropped after an ALTER SYSTEM SWITCH LOGFILE statement has been issued. The dropped group may be specified either as GROUP integer or as a list of filenames. DROP LOGFILE MEMBER filename Specifies that one or more individual redo log file members be dropped. CREATE STANDBY CONTROL FILE Specifies that a control file be created to maintain a standby database. BACKUP CONTROL FILE TO Specifies that the current control file be backed up to the indicated filename. If the keywords TO TRACE are specified, a set of SQL statements will be written to the trace file instead of creating a backup of the control file. If RESETLOGS is specified, the SQL statements written will include ALTER DATABASE OPEN RESETLOGS. If NORESETLOGS is specified, the SQL statement ALTER DATABASE OPEN NORESETLOGS will be written. RECOVER FROM Specifies the location from which archived redo log files required for recovery will be read. If the keyword AUTOMATIC is specified, the name of the next archived redo log file required for recovery will be generated, using the LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT initialization parameters. RECOVER DATABASE Specifies that the entire database be recovered. If the STANDBY keyword is supplied, the standby database will be recovered using the control file and archived redo log files from the primary database. The keywords UNTIL CANCELLED may be supplied, specifying that the database be recovered until the operation is canceled using the RECOVER CANCEL clause. The TIME keyword specifies that time-based recovery be performed up to the supplied time. The CHANGE keyword indicates that recovery will be performed to just before the specified system change number. RECOVER DATABASE USING BACKUP CONTROL FILE Specifies that a backup control file (instead of the current control file) be used. RECOVER STANDBY TABLESPACE UNTIL CONSISTENT WITH CONTROL FILE Specifies that tablespace on an old standby database be recovered using the control file from the current standby database. RECOVER STANDBY DATAFILE UNTIL CONSISTENT WITH CONTROL FILE Specifies that datafile on an old standby database be recovered using the control file from the current standby database. RECOVER TABLESPACE Specifies one or more tablespaces (which must be offline) to be recovered. RECOVER DATAFILE Specifies one or more datafiles (which must be offline) to be recovered. RECOVER LOGFILE Specifies that media recovery should continue using the log file(s) supplied. RECOVER CONTINUE DEFAULT Specifies that recovery will continue using the redo log file that would be automatically generated. This keyword is equivalent to RECOVER AUTOMATIC, except that no prompt for filenames exists. RECOVER CONTINUE Specifies that recovery of multiple instances should continue after it was interrupted to disable a thread. RECOVER CANCEL Specifies that cancel-based recovery be ended. RECOVER MANAGED STANDBY DATABASE Specifies that recovery should occur using sustained standby recovery mode, which assumes the standby database as an active component. TIMEOUT Specifies the number of minutes to wait for a requested archived redo log file to become available for writing to the standby database. CANCEL Specifies that sustained recovery be ended after the current archived redo file has been applied, unless the IMMEDIATE keyword, which terminates after applying the next redo log file read is specified. Example Create a new database called TEST: CREATE DATABASE TEST LOGFILE GROUP 1 ('/disk01/oracle/log1.log','/disk02/oracle/log2.log') SIZE 50K, GROUP 2 ('/disk03/oracle/log2.log','/disk04/oracle/log2.log') SIZE 50K MAXLOGIFLES 5 DATAFILE '/disk10/oradata/system01.dbf' SIZE 50M MAXDATAFILES 100 ACHIVELOG;

Anonymous   
Printed
Page 317

The third to last line of code did read: [FLUSH SHARED POOL] It now reads: [FLUSH SHARED_POOL]

Anonymous    Mar 01, 2000
Printed
Page 325

The fifth listed item did read: FLUSH SHARED POOL It now reads: FLUSH SHARED_POOL

Anonymous    Mar 01, 2000
Printed
Page 333
ALTER TABLESPACE

[RENAME 'filename1' TO... now reads: [RENAME DATAFILE 'filename1' TO... (it was missing keyword DATAFILE)

Anonymous    Jun 01, 1999
Printed
Page 333
The following line has been added above the third line from the bottom

of the page: [INITIAL integer[K | M] ]

Anonymous    Jan 01, 2001
Printed
Page 369
The following line has been added at the end of the description for

PCTINCREASE: "Beginning with Oracle8, the PCTINCREASE parameter cannot be specified, and defaults to a value of 0."

Anonymous    Jan 01, 2001
Printed
Page 371

The paragraph under the code example for "Create Sequence" did read: "Changes the characteristics of an Oracle sequence, including starting sequence number, range, number of sequence numbers cached in memory, and whether sequential order is preserved." Now reads: "Creates an Oracle sequence which can be used to automatically generate sequential numbers during database operations."

Anonymous    Jan 01, 2001
Printed
Page 375
Under Term Defininition for NEXT, the last sentence of the paragraph

that begins with "If this value is not a multiple..." has been deleted.

Anonymous    Jan 01, 2001
Printed
Page 389
In the code section, the third to last line

"[READ [ONLY | WRITE]" was removed. This is because the READ ONLY and READ WRITE options apply only to ALTER TABLESPACE, not to CREATE TABLESPACE.

Anonymous    Mar 01, 2000
Printed
Page 389

The 6th line of code under "CREATE TABLESPACE" did read: [MINEXTENTS integer[K | M] ] Now reads: [MINEXTENTS integer]

Anonymous    Jan 01, 2001
Printed
Page 390
The entire "READ ONLY" and "READ WRITE" sections were removed from

the text. This is because the READ ONLY and READ WRITE options apply only to ALTER TABLESPACE, not to CREATE TABLESPACE.

Anonymous    Mar 01, 2000
Printed
Page 411

The last line of the syntax for REVOKE now reads: TO {username | role | PUBLIC} Should read: FROM {username | role | PUBLIC}

Anonymous   
Printed
Page 418
In the 2nd line of the "Use These Data Dictionary Views" column of

Table 14-2, changed "DB" to "DBA".

Anonymous    Oct 01, 2001
Printed
Page 432
Right column; 18th line down from the top

Did read: "V$SQLTEXT_WITH_NEWLINE" It now reads: "V$SQLTEXT_WITH_NEWLINES"

Anonymous    Mar 01, 2000
Printed
Page 456
IN PRINT: "CREATE PUBLIC SYNONYM" listing

"Allows you to execute the CREATE PUBLIC DATABASE LINK command." SHOULD BE: Allows you to exectue the CREATE PUBLIC SYNONYM command.

Anonymous   
Printed
Page 489
In line 7, the second syntax layout for the VARIABLE command omits

most of the datatypes. It should continue (for Oracle8 only): CHAR (n) | NCHAR | NCHAR (n) | VARCHAR2 (n) | NVARCHAR2 (n) | CLOB | NCLOB | REFCURSOR ]

Anonymous   
Printed
Page 999
Startup and shutdown are omitted from the book.

Since these commands are now "SQL" in that they are now accessed through SQL*Plus shouldn't they be documented in the SQL Command syntax? **AUTHOR'S NOTE: This did not occur until Oracle Version 8.1, and we only attempt to be complete up to 8.0.**

Anonymous