Errata

PRAGMA RESTRICT_REFERENCES

is now in bold.

was a Yes line extending to the right of the line pointing down. It has
been removed. The Yes goes with the line going down.

"DBMS_SQL.BIND_VARIABLE(cur, 'varname', 'a', 100);"

now reads:

"DBMS_SQL.BIND_VARIABLE(cur, 'varname', var_name_in);"

also includes:

PROCEDURE DBMS_SQL.DEFINE_COLUMN_LONG
(c IN INTEGER
,position IN INTEGER);

DBMS_SQL.DESC_T should be DBMS_SQL.DESC_TAB
in both the first paragraph and in the code block below it.

In the second bulleted item, the last line of code now reads:

DBMS_SQL.DEFINE_ARRAY... (not DEFINE_COLUMN)

Lines 11-14 in the code sample did read:

message_tblmessage_tbltype;
call_statusINTEGER;

/* empty table used to free and release memory */
null_message_tblmessage_tbltype;

Three of these lines were missing spaces. They now read:

message_tbl message_tbltype;
call_status INTEGER;

/* empty table used to free and release memory */
null_message_tbl message_tbltype;

reads:

"Do not own lock; cannot convert"

It should read:

"Already own lock specified by 'id' or 'lockhandle'

read:

"The Enable ... from DBMS_OUTPUT.PUT_LINE (and PUT and PUTF)
procedure."

Now reads:

"The Enable ... from DBMS_OUTPUT.PUT_LINE (and PUT) procedure."

format like this:

All PL/SQL versions: Oracle 8.0 and above only:
FUNCTION UTL_FILE.FOPEN ( FUNCTION UTL_FILE.FOPEN (
location IN VARCHAR2, location IN VARCHAR2,
filename IN VARCHAR2, filename IN VARCHAR2,
open_mode IN VARCHAR2) open_mode IN VARCHAR2,
RETURN file_type; max_linesize IN BINARY_INTEGER)
RETURN file_type;

and added the following to the parameter list:

max_linesize

The maximum number of characters per line, including the
newline character, for this file. Minimum is 1, maximum is
32767.

UTL_FILE.INVALID_MAXLINESIZE

The seventh and eighth lines of code on the page did read:

UTL_FILE.PUT_LINE
(TO_CHAR (emprec.empno) || .....

Now read:

UTL_FILE.PUT_LINE
(fileID,TO_CHAR (emprec.empno) || .....

The first sentence in the second-to-last paragraph on the page did read:

"We can conclude from this test that the IS_OPEN function returns TRUE
if the id field of a UTL_FILE.FILE_TYPE record is NULL."

Now reads:

"We can conclude from this test that the IS_OPEN function returns FALSE
if the id field of a UTL_FILE.FILE_TYPE record is NULL."

return clob

now reads:

return bfile
and,
return book_rec.chapter_file

now reads:

return book_rec.book_file

and,

SELECT chapter_file

now reads:

SELECT book_file

The second line on the page now reads:

"...using the following statements (stored in the
compare_text.sql file):

The next 3 lines of code have been deleted. The rest of the code now
reads:

SELECT chapter_descr, chapter_text
FROM my_book_text
WHERE chapter_descr = '&1'

ROLLBACK;

EXEC DBMS_OUTPUT.PUT_LINE ('Rollback completed');

SELECT chapter_descr, chapter_text
FROM my_book_text
WHERE chapter_descr = '&1'
END;
/

The first code example did read:

SELECT chapter_descr, chapter_text
FROM my_book_text
WHERE chapter_descr = '&1'
ROLLBACK;

EXEC DBMS_OUTPUT.PUT_LINE ('Rollback completed');

SELECT chapter_descr, chapter_text
FROM my_book_text
WHERE chapter_descr = '&1'
END;
/

Now reads:

SELECT chapter_descr, chapter_text
FROM my_book_text
WHERE chapter_descr = '&1';
ROLLBACK;

EXEC DBMS_OUTPUT.PUT_LINE ('Rollback completed');

SELECT chapter_descr, chapter_text
FROM my_book_text
WHERE chapter_descr = '&1';
END;
/

(Added semi-colons after each '&1'.)

colon. It did read:

CREATE OR REPLACE PACKAGE blobby
IS
TYPE adpage_rectype IS RECORD (
customer_id NUMBER,
persuasive_picture BFILE
),

Now reads:

CREATE OR REPLACE PACKAGE blobby
IS
TYPE adpage_rectype IS RECORD (
customer_id NUMBER,
persuasive_picture BFILE
);

colon. It did read:

CREATE OR REPLACE PACKAGE chapter
IS
TYPE diagram_rectype IS RECORD (
chapter_num NUMBER,
diagram BLOB
),

Now reads:

CREATE OR REPLACE PACKAGE chapter
IS
TYPE diagram_rectype IS RECORD (
chapter_num NUMBER,
diagram BLOB
);

colon. It did read:

IS
TYPE poll_results_rectype IS RECORD (
speech_num NUMBER,
speech_txt CLOB
),

Now reads:

IS
TYPE poll_results_rectype IS RECORD (
speech_num NUMBER,
speech_txt CLOB
);

DBMSLOB.NOEXIST_DIRECTORY
DBMSLOB.NOPRIV_DIRECTORY
DBMSLOB.INVALID_DIRECTORY

There is now an underscore in 'DBMS_LOB'.

The fifth line of the second code example did read:

PROCEDURE check_open (loc IN BFILE, descr IN VARCHAR2)

Now reads:

PROCEDURE check_open (loc IN BFILE, descr IN VARCHAR2);

(colophon) The second-to-last paragraph did read:

"our books use RepKover, a durable and flexible lay-flat binding. If
the page count exceeds RepKover's limit..."

Now reads:

"our books use a durable and flexible lay-flat binding. If the page
count exceeds this binding's limit..."

@compare_text

@compare_text

@compare_text

@compare_text

@compare_text

Line -6 now reads:

FUNCTION DBMS_ROWID.ROWID_ROW_NUMBER (row_id IN ROWID)

The last bit of the last line of code now reads:

... (rowid_value, NULL, NULL, 0) = 1;

This DBMS_DDL.....

The third INIT.ORA parameter that supposedly affects the
behavior of the SNP processes is JOB_QUEUE_KEEP_CONNECTIONS.
This parameter has been made obsolete in Oracle8i. In fact,
it apparently never actually had any effect under previous releases,
although it has been documented as having various effects. Some sources
say that it controlled the database sessions held by the SNP background
processes; others say that it controlled the sessions in remote databases
for jobs using database links.

Although setting this parameter appears to do no harm,
it is best to leave it alone.

When you are using the ISUBMIT procedure, a subtle problem
can arise from the fact that next_date has datatype VARCHAR2
instead of DATE (as in SUBMIT). When DATE values are assigned to
next_date in calls to ISUBMIT, an implicit conversion to VARCHAR2 is
done using the session's current NLS_DATE_FORMAT as the date mask. This can
result in unexpected truncation of next_date. For instance, if the
session NLS_DATE_FORMAT is 'YY-MM-DD', dates assigned to next_date will be
truncated to 12:00 a.m. To avoid this problem, either make sure that the
session NLS_DATE_FORMAT includes all date components or supply next_date
as a fully specified VARCHAR2.

("Interval Value") are now enclosed in single quotes as in the table
on page 670

and also, row 2,

"Every day at 8:00 p.m."

now reads

"Every day at 8:00 a.m."

(ab IN OUT dbms_utility.uncl_array,

now reads

(tab IN OUT dbms_utility.uncl_array,

("ab" should be "tab")

Line 6 now reads:

Table 15-2 lists the programs in DBMS_REPCAT_ADMIN

and, under "DBMS_REPCAT_ADMIN exceptions" toward the bottom of the
page, the line begins:

The DBMS_REPCAT_ADMIN package may ......