Silly question on proper use of SCI link.

Question

I have inherited a cluster setup of two 4500s and another cluster of
6500s. Though there are two SCI interfaces connecting each pair, all
of the software is configured to communicate over a 100bt ethernet
link.
My first instinct is to assume a better setup would be to configure
the various processes to use the IP addresses of the cluster interfaces
to communicate, and to stay off of the ethernet unless we are communicating
with processes outside the cluster..
So, does anyone know of any reason I wouldn't want to do this?
Thanks,
Ben Greear ([email protected])

Answer 1

For some use cases, perhaps yours, DML error logging makes sense.
This allows you to issue an INSERT statement and have Oracle put any offending rows into a log table. The other rows still get inserted into the table.
So for Frank's example of 10 rows the INSERT would try to insert all 10. Nine of the rows would get inserted into the table and the error rows would get inserted into the error log table. See 'Inserting Data with DML Error Logging' in the DBA doc
http://docs.oracle.com/cd/B28359_01/server.111/b28310/tables004.htm
When you load a table using an INSERT statement with subquery, if an error occurs, the statement is terminated and rolled back in its entirety. This can be wasteful of time and system resources. For such INSERT statements, you can avoid this situation by using the DML error logging feature.
To use DML error logging, you add a statement clause that specifies the name of an error logging table into which the database records errors encountered during DML operations. When you add this error logging clause to the INSERT statement, certain types of errors no longer terminate and roll back the statement. Instead, each error is logged and the statement continues. You then take corrective action on the erroneous rows at a later time.
DML error logging works with INSERT, UPDATE, MERGE, and DELETE statements. This section focuses on INSERT statements.