|Chapter 10: Direct Path Loads|
GNIS.WATERFALLS.WATERFALLS_COUNTY_FK was re-enabled.
Constraint GNIS.WATERFALLS.WATERFALLS_CK was validated
GNIS.WATERFALLS.WATERFALLS_COUNTY_FK was not re-validated due to ORACLE error 2298.
|not found in the parent table to which the FOREIGN KEY constraint refers. If you|
|query the user_constraints view now, you’ll find that the validated column for the|
CONSTRAINT_NAME STATUS VALIDATED
------------------------------ -------- -------------
WATERFALLS_PK ENABLED VALIDATED
WATERFALLS_CK ENABLED VALIDATED
WATERFALLS_COUNTY_FK ENABLED NOT VALIDATED
As you’ve seen, SQL*Loader writes an error message to the log file if it can’t vali-date a constraint. However, to solve the problem, you really need to know more than just that the problem occurred. You need to know the error that prevented the constraint from being validated, and you also need to know which rows of data led to the error occurring. Using the optional EXCEPTIONS keyword in the REENABLE clause, you can cause the ROWIDs of all problem rows to be inserted into an exceptions table. In the following example, the exceptions table is named waterfalls_exc:
Trigger GNIS."WATERFALLS_BEFORE_UPDATE" was disabled before the load.
Trigger GNIS."WATERFALLS_BEFORE_INSERT" was disabled before the load.
Trigger GNIS."WATERFALLS_BEFORE_DELETE" was disabled before the load.
|This is the Title of the Book, eMatter Edition|
|Copyright © 2001 O’Reilly & Associates, Inc. All rights reserved.|