Display Error Transaction Details
New(2): PREMIUM => 8888
New(3): NAME => MADHU
PL/SQL procedure successfully completed.
As shown in the above output, error#1 and
error#2 are the result of update failures because the
corresponding rows were not found at destination table on the
Apply side. The error message is no data found. Error#3
is the result of inserting a duplicate row which resulted in
unique key constraint violation. Error#4 is the result of
foreign key constraint violation at destination table.
Figure 7.3 shows the general Streams
related views in a single glance.
Figure 7.3 General Streams Related
static and dynamic views
The description of each of the view
This view shows the archived log file
details. It shows the names of the log files, and the start and
end SCN values. Whenever a Capture process halted for any valid
reason, on resumption it still must go back to archive log files
to scan the redo entries. It is important to keep track of the
archive log files location and monitor the removal of the
archived log files from the file system. If the archived logs
are removed before the Capture process has completed its scan,
the Capture process will abort. Failing to have right archive
log will abort the Capture process.