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.

strange problem while reorganizing the table, cannot do anything

P: n/a
Hi,

We were trying to run the following set of commands

Alter table----successfull
reorg table---successfull
Alter table---successfull
Reorg table----------took lots of time....without specifying any error

THis table was a fairly small table(51000 rows) and its previous
reorgs had hardly taken any time...
This time it took more than an hour and still continued...

We tried to kill that session that was doing the reorg...
The session could not be killed...
It said...that force application command was succesfull but showed
that session was still there...
We tried it many times, but the same problem persisted...

We tried Quiesce the database command......it also continued for
long...without any success....

Now we have tried to forcefully stop the database instance......but
even that itself is taking time...

What could be the possible reasons...and more importantly....the
remedies...for it...

If we restart the AIX box, can it screw up the whole Database?

It's very urgent...
Rahul
Nov 15 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On Nov 15, 5:51 pm, Rahul Babbar <rahul.babb...@gmail.comwrote:
Hi,

We were trying to run the following set of commands

Alter table----successfull
reorg table---successfull
Alter table---successfull
Reorg table----------took lots of time....without specifying any error

THis table was a fairly small table(51000 rows) and its previous
reorgs had hardly taken any time...
This time it took more than an hour and still continued...

We tried to kill that session that was doing the reorg...
The session could not be killed...
It said...that force application command was succesfull but showed
that session was still there...
We tried it many times, but the same problem persisted...

We tried Quiesce the database command......it also continued for
long...without any success....

Now we have tried to forcefully stop the database instance......but
even that itself is taking time...

What could be the possible reasons...and more importantly....the
remedies...for it...

If we restart the AIX box, can it screw up the whole Database?

It's very urgent...

Rahul
Hi,

The above problem was resolved by killing the db2 processes using
'kill'.
Thankfully, everything is fine..

Although the source of the problem is still a mystery..

Thanks

Rahul
Nov 15 '07 #2

P: n/a
Alter table----successfull
reorg table---successfull
Alter table---successfull
Reorg table----------took lots of time....without specifying any error
What sort of ALTER was the second one?

Nov 15 '07 #3

P: n/a
On Nov 15, 8:18 pm, deangc <dean.cochr...@gmail.comwrote:
Alter table----successfull
reorg table---successfull
Alter table---successfull
Reorg table----------took lots of time....without specifying any error

What sort of ALTER was the second one?
All the alters were to make the not nullable column to make it a
nullable column.
Nov 15 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.