reorg & data corruption

[GB]

Hi,

Is it risky to force the application doing a reorg, can I corrupt my
data or is it a tolerated operation (db2 v7 on win2k)?

db2diag.log shows this:

2005-02-12-19.42.22.644000 Instance:DB2 Node:000
PID:1516(db2syscs.exe) TID:1840 Appid:*LOCAL.DB2.050212181622
relation_data_serv sqlrreorg_sendinfo Probe:190 Database:DEVTEST
DIA1003C The interrupt has been received.

ZRC=0xFFFF8403

I tried to stop reorgs manually several times and I always got access
immediately to the table again, is it always like this ?

Greg
P.S. I'm suddenly quite actively asking question on this newsgroup, hope
I can answer some soon also !

[Pierre Saint-Jacques]

This is working as designed I think.
A v7 reorg acquires a superexclusive lock on the table, copies it to
work on the copy and when done replaces old table with reorged copy.
If you interrupt a V7 reorg, you get access to the old table immediately
but have to redo the reorg from the groud up.

Because of this, I don't think you'll corrupt your data. I'd bacjkup
it's tbsp. and test it before doing this on critical data.

HTH, Pierre.

GB wrote:

Hi,

Is it risky to force the application doing a reorg, can I corrupt my
data or is it a tolerated operation (db2 v7 on win2k)?

db2diag.log shows this:

2005-02-12-19.42.22.644000 Instance:DB2 Node:000
PID:1516(db2syscs.exe) TID:1840 Appid:*LOCAL.DB2.050212181622
relation_data_serv sqlrreorg_sendinfo Probe:190 Database:DEVTEST
DIA1003C The interrupt has been received.

ZRC=0xFFFF8403

I tried to stop reorgs manually several times and I always got access
immediately to the table again, is it always like this ?

Greg
P.S. I'm suddenly quite actively asking question on this newsgroup, hope
I can answer some soon also !

--
Pierre Saint-Jacques - Reply to: sescons at attglobal dot net
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.