Errata 530-0 Kyte (corrected in the 2nd printing)
+ +Updated 11/21/06
+ +|
+ Page |
+
+ Original Sentence |
+
+ Corrected Sentence |
+
|
+ xxxii |
+
+ you can have SELECT on V$STATNAME,
+ V$MYSTAT and V$LATCH granted directly to you |
+
+ you must have select on v_$statname, v_$mystat, v_$latch, and v_$timer granted
+ directly to you |
+
|
+ 38 |
+
+ I had fallen into the trap of thinking “I
+ know all about databases,” because I had worked with SQL/DS, DB2, Ingres,
+ Sybase, Informix, SQLBase, Oracle, and others. |
+
+ I had fallen into the trap of thinking “I
+ know all about databases,” because I had worked with SQL/DS, DB2, Ingress,
+ Sybase, Informix, SQLBase, Oracle, and others. |
+
|
+ 89 |
+
+ A traditional cooked file system is usable
+ by only one computer is a clustered environment. |
+
+ A traditional cooked file system is usable
+ by only one computer in a clustered environment. |
+
|
+ 124 |
+
+ You can “turn it on" in your session
+ via the ALTER SESSION command or at the system level via the ALTER SESSION
+ command. |
+
+ You can “turn it on" in your session
+ via the ALTER SESSION command or at the system level via the ALTER SYSTEM
+ command. |
+
|
+ 159 |
+
+ *Figure 5.2 contains 3 instances of the
+ number 5in small boxes* |
+
+ *The number 5 should be replaced with the
+ letter S in all 3 boxes* |
+
|
+ 169 |
+
+ Theys come from having that many fewer PGAs
+ allocated. Each dedicated/shared server has a PGA. |
+
+ They come from having that many fewer PGAs allocated. Each dedicated/shared server has a PGA. |
+
|
+ 185 |
+
+ After all, I had been using databases for
+ quite a while and was considered something of an expert in this field (in
+ addition to Sybase, SQL Server, and Informix, I had used Ingress, DB2, Gupta SQLBase, and a variety of other databases). |
+
+ After all, I had been using databases for
+ quite a while and was considered something of an expert in this field (in
+ addition to Sybase, SQL Server, and Informix, I had used Ingres, DB2, Gupta SQLBase, and a variety of other databases). |
+
|
+ 490 |
+
+ between 0 bytes (for NULL) and 22 bytes |
+
+ between 0 bytes (for trailing NULL
+ columns) and 22 bytes |
+
|
+ 646 |
+
+ we have job_queue_processes set to
+ 0.... |
+
+ we have job_queue_processes
+ set to 8 |
+
|
+ 649 |
+
+ Chapter
+ 15: Data Loading and Unloading This first half of this chapter focuses on |
+
+ Chapter
+ 15: Data Loading and Unloading This first half of this chapter focuses on |
+
|
+ SPECIAL NOTE FROM AUTHOR: Big_Table For examples throughout this book, I use a table called BIG_TABLE. Depending on which
+ system I use, this table has between one record and four million records and
+ varies in size from 200MB to 800MB. In all cases, the table structure is the
+ same. To create BIG_TABLE, I wrote a script that does the following: * Creates an empty
+ table based on ALL_OBJECTS. This dictionary view is used to populate the BIG_TABLE. * Makes this table NOLOGGING. This is optional. I
+ did it for performance. Using NOLOGGING mode for a test table is safe; you won't use it in a
+ production system, so features like Oracle Data Guard will not be enabled. * Populates the
+ table by seeding it with the contents of ALL_OBJECTS and then iteratively inserting into itself,
+ approximately doubling its size on each iteration. * Creates a primary
+ key constraint on the table. * Gathers
+ statistics. * Displays the
+ number of rows in the table. To build the BIG_TABLE table, you can run + the following script at the SQL*Plus prompt and pass in the number of rows you + want in the table. The script will stop when it hits that number of rows. + |
+