Oracle Security

Errata for Oracle Security

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 49
On the third line in the section "A Caution About Using Views,"

replaced the words: "This action occurs" with "If the GROUP BY clause or a UNION statement is used in the definition, the data is gathered in the temporary tablespace"

Anonymous    Apr 01, 1999
Printed
Page 55

Just below the second set of SQL, the text used to read: mary then grants access privileges to the synonym either to PUBLIC or to specific users. Changed to read: mary then grants access privileges by way of the synonym either to PUBLIC or to specific users.

Anonymous    Apr 01, 1999
Printed
Page 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.

Anonymous   
Printed
Page 253
The figure 10-1 has been changed.

The word "by" in "by user" has been changed to caps. The text "session and access" has been changed to all caps. Also, WHENEVER SUCCESSFUL UNSUCCESSFUL Has been changed to: WHENEVER [NOT] SUCCESSFUL

Anonymous    Apr 01, 1999
Printed
Page 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

Anonymous