taken as part of the statement that caused it. A constraint that is defined as nondeferrable cannot be modified to be enforced at the end of a transaction. Deferred constraints that are checked only when a transaction is committed. If any constraint violations are detected at commit time, the entire transaction is rolled back. 4) Guidelines for defining Constraints: Primary and unique constraints: Place indexes in a separate tablespace Use non-unique indexes if bulk loads are frequent Self-referencing foreign keys: o Define or enable foreign keys after initial load o Defer constraint checking 5) Create the EXCEPTIONS table by running the utlexcpt1.sql.script Use subquery on EXCEPTIONS to locate rows with invalid data.s Identify invalid data by using a subquery on the EXCEPTIONS table: SQL> SELECT rowid, id, last_name, dept_id 2 FROM hr. employee 3 WHERE ROWID in (SELECT row_id 4 FROM exceptions) 6 FOR UPDATE;
6) A profile is a named set of password and resource limits Password aging and expiration Password history Password complexity verification Account locking CPU time I/O Operations 7) Create the profile to limit the password settings, and assign theprofile to the user by using the CREATE USER or ALTER USERcommand.Password limit settings in profiles are always enforced.When password management is enabled, the user account can belocked or unlocked by using the CREATE USER or ALTER USERcommand.08)
You've reached the end of your free preview.
Want to read all 4 pages?
- Spring '16
- data integrity, password history