Browse Prior Art Database

Implicity created on demand exception table for Load and Set integrity Disclosure Number: IPCOM000010787D
Original Publication Date: 2003-Jan-21
Included in the Prior Art Database: 2003-Jan-21
Document File: 1 page(s) / 45K

Publishing Venue


This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 81% of the total text.

Page 1 of 1

Implicity created on demand exception table for Load and Set integrity

  Exception tables are user-created tables that mimic the definition of the tables that are specified to be checked using SET INTEGRITY with the IMMEDIATE CHECKED option. They are used to store copies of the rows that violate constraints in the tables being checked. The exception tables used with LOAD are identical to the ones used by the SET INTEGRITY statement.

Currently, to create an exception table abc.exception_t1 for load/set integrity on base table abc.t1, user will need to either:
1. issue create table abc.exception_t1 like abc.t1 and then issue alter table abc.exception_t1 add column ts timestamp add column consname clob(32K)
2. Or issue create table abc.exception_t1 - manually list out all the columns in the table and also add in ts timestamp and consname clob(32K)
3. Or db2look to get the create table statement for abc.t1 and then manually modified the script to add the two additional columns

The idea is to implement a short cut way to allows user to perform exception table creation in one statements and also adding new optional feature to set integrity and load to internally issue the create exception table as requested.

We need implement like tablename in place of a column definition (the one that is inside the brackets). This is already implement in DB2 UDB for iSeries.

With the above implemented, we then add new optional clause to both set integrity and load to allow them to specific...