Errata

Fig 2-2, for which the preceding text is described as "the relevant multi_
threaded server INIT.ORA parameters," probably should include an eggman box
as well as walrus. It is not clear how the two listener addresses give rise
to the three listeners and one host of the diagram.

In figure 2-3, should that be two distinct instances pointing at the the
same database per the definitions of instance and and database given on
page 4?

usually reside in? Is this file required? The text says it is needed to
"customize."

manager to connect to the listener that is listening on port 1521? The
later example of different protocols makes it seem unlikely to be the
second ADDRESS section.

misspelling. Should be "TRANSACTIONS".

Job_queue_process".

definition.

be included? Is there a job created, as stated in the previous paragraph.
Shouldn't the job be shown in fig 9-1?

significant here than in Figure 9-1.

I would like to suggest consistency in labeling objects in the diagrams that
are contrasting the different types of snapshots. "EMP_SNAP" (Figure 9-1) is
almost certainly the same as "Emp Snapshot User View" (Figure 9-2), but as a
reader, I have to wonder if they have been marked differently for any reason.
The use of consistent labels and selection of objects to include would focus
attention on the significant differences.

up instructions, that for multi-master has neither the instructions nor a
pointer to where the instructions are to be found in the book.

Middle of second paragraph reads:

"Snapshot refreshes perform updates by deleting the old record and
reinserting it with its new values."

After highlighting this in my book, I reviewed the actual update code
included on page 204. There, rather than delete/insert, actual updates are
performed. Which is correct?

When adding a master site for replication, the book lists the master
definition site PHQS.BIGWHEEL.COM instead of PSLS.BIGWHEEL.COM.

name and schema name are different, which they are in this example.

the first parameter is listed as "gname" (typically identifying
a replication group name); in fact it is a "sname" (a schema name).

The page shows an example of how to execute the
dbms_repcat.make_column_group package but the first parameter listed shows
GNAME and it should read SNAME.

and eighth lines of code from the top of page 351 now read:

EXECUTE dbms_repcat.add_priority_site

Should read:

EXECUTE dbms_repcat.add_site_priority_site