Oracle Security
by Marlene Theriault & William Heney



This errata page lists errors outstanding in the most recent printing.  


If you have any error reports or technical questions, you can send them to
booktech@oreilly.com.  (Please specify the printing date of your copy.)


This page was updated on April 7, 1999.


Here's a key to the markup:

        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification



Confirmed errors:


(95) Delete the sentence that reads: 

	In Oracle8, there were no rows selected. 

Replace with the following paragraph:

	In Oracle8, there were no rows selected because a bug has been 
	introduced in this view. According to Mark B. Wallace, a DBA with 
	Database Architechs, in Oracle8 a BITAND function was used to 
	handle a new "hidden column" feature, and the programmer did not 
	take into consideration the interaction between this function and the 
	outer join. If the privilege that has been granted is not a 
	column-oriented privilege, the outer join will be activated, will 
	generate a null row for COL$, and the BITAND comparison will fail. 
	Therefore, no row-oriented information will be reported for this 
	view in current versions of Oracle8.


{256} The syntax model in middle should read (2nd line):

	WHENEVER <SUCCESSFUL> or <NOT SUCCESSFUL>

Also, the list just below that, last line, should read:

	WHENEVER NOT SUCCESSFUL