By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,557 Members | 1,068 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,557 IT Pros & Developers. It's quick & easy.

Puzzled

P: n/a
Hi,

On running a load, I get the following summary:
What are the rows deleted ? There were more rows thatn that there to
begin with.
Number of rows read = 64692
Number of rows skipped = 0
Number of rows loaded = 64692
Number of rows rejected = 0
Number of rows deleted = 89
Number of rows committed = 64692

load from tab.dat of del modified by usedefaults pagefreespace=0
totalfreespace=0 chardel_ coldel~ decpt. replace into db.tab
NONRECOVERABLE

Mar 7 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
TheSpongebob wrote:
Hi,

On running a load, I get the following summary:
What are the rows deleted ? There were more rows thatn that there to
begin with.
Number of rows read = 64692
Number of rows skipped = 0
Number of rows loaded = 64692
Number of rows rejected = 0
Number of rows deleted = 89
Number of rows committed = 64692

load from tab.dat of del modified by usedefaults pagefreespace=0
totalfreespace=0 chardel_ coldel~ decpt. replace into db.tab
NONRECOVERABLE


Well, what are the other messages (the ones before that summary) telling
you?

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Mar 7 '06 #2

P: n/a
TheSpongebob wrote:
Hi,

On running a load, I get the following summary:
What are the rows deleted ? There were more rows thatn that there to
begin with.
Number of rows read = 64692
Number of rows skipped = 0
Number of rows loaded = 64692
Number of rows rejected = 0
Number of rows deleted = 89
Number of rows committed = 64692

load from tab.dat of del modified by usedefaults pagefreespace=0
totalfreespace=0 chardel_ coldel~ decpt. replace into db.tab
NONRECOVERABLE

I think these are due to unique key violations.

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Mar 7 '06 #3

P: n/a
Thanx. Key violations they were !

DB2 "deleted" some rows on me. Mind you, the rows were never actually
on the table and they weren't "deleted" off the flat file ...
I learned how to dump the messages too for next time.

Thanx guys.

Mar 7 '06 #4

P: n/a
LOAD has the responsability to get the data in there as fast as possible.
So duplicate key are not immediately checked and are therefore put into the
page. In the second phase of the load, the indexes are either maintained
and or rebuilt. At that point the load will recognize duplicate keys on
unique indexes. The row being already in the table, it is deleted.
If you run the same load with the following ... FOR EXCEPTION
tabschema.tabname
then load will keep the first key encountered and insert into the exception
table any duplicate subsequently met.
Please note that only for duplicate keys, both the delete and insert will be
logged.

So, as previously mentioned your 89 rows were most probably duplicate keys
deleted.

HTH, Pierre.
--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"TheSpongebob" <ga*****@sympatico.ca> a écrit dans le message de news:
11**********************@i40g2000cwc.googlegroups. com...
Thanx. Key violations they were !

DB2 "deleted" some rows on me. Mind you, the rows were never actually
on the table and they weren't "deleted" off the flat file ...
I learned how to dump the messages too for next time.

Thanx guys.


Mar 8 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.