|
View previous topic :: View next topic
|
| Author |
Message |
mallik4u
New User
Joined: 17 Sep 2008
Posts: 75
Location: bangalore
|
|
|
|
Hi,
Could you please let me know the possible reasons why a tablespace will go into AREO* (Advisory Reorg) status.
I have searched in our forum, i have got only one related to AREO* but that says about the way to resolve it.
Thanks & Regards,
Mallik |
|
| Back to top |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
20 seconds on google - from the IBM web site
| Quote: |
| The REORG-pending (AREO*) advisory status indicates that a table space, index, or partition needs to be reorganized for optimal performance. |
|
|
| Back to top |
|
|
GuyC
Senior Member
Joined: 11 Aug 2009
Posts: 1281
Location: Belgium
|
|
| Back to top |
|
|
mallik4u
New User
Joined: 17 Sep 2008
Posts: 75
Location: bangalore
|
|
|
|
Thanks for the reply,
We have got this status for one of our table.Since it is an advisory reorg we ran REPAIR utility with NOAREORPENDSTAR option. This removed the status.
But the application team(team to which this table belongs to) claiming that due to this utility they lost some records.
I just want to check is there any possiblity that tablespace will put in to AREO* status when some mass delete happens or REPAIR really deletes the records from the database? |
|
| Back to top |
|
|
mallik4u
New User
Joined: 17 Sep 2008
Posts: 75
Location: bangalore
|
|
|
|
In IBM site it is mentioned that Tablespace will put into AREO* when table got altered.
But this table was getting accessed by application till today and there were no ALTER happend on the table recently. |
|
| Back to top |
|
|
sushanth bobby
Senior Member
Joined: 29 Jul 2008
Posts: 1020
Location: India
|
|
|
|
Mallik4u,
Since you didn't run REORG till now, can you check the tablespace versions in the catalog
SELECT DBNAME, NAME, OLDEST_VERSION ,CURRENT_VERSION
FROM SYSIBM.SYSTABLESPACE
Thanks,
Sushanth |
|
| Back to top |
|
|
mallik4u
New User
Joined: 17 Sep 2008
Posts: 75
Location: bangalore
|
|
|
|
hi Susanth,
Thanks for the reply!!!
I have ran the query. I got result as Current_Version is 1 and old_version is 0.
Is there any way that i can retrive the old version? |
|
| Back to top |
|
|
sushanth bobby
Senior Member
Joined: 29 Jul 2008
Posts: 1020
Location: India
|
|
|
|
Mallik4u,
| Quote: |
| Is there any way that i can retrive the old version? |
Can you please tell me why do you want to retreive the old version ?
Sushanth |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hi Sushanth,
Seems like something was "altered" after all. . . 
Now the original is needed. . .
Just a guess. |
|
| Back to top |
|
|
sushanth bobby
Senior Member
Joined: 29 Jul 2008
Posts: 1020
Location: India
|
|
|
|
Hi D.sch,
Tablespace versions are basically used for data availability purposes and not for recovery.
So, the options left for Mallik is to,
ALTER the table to backout the changes done earlier & do a REORG.
or
DROP & re-create with the old ddl.
And i don't think tha'ts gonna happen, since malik said,
| Quote: |
| But this table was getting accessed by application till today and there were no ALTER happend on the table recently. |
So, i think for a long time, this has been left un-noticed, so it would be better they take DB2's advice and do a REORG. And get rid of Advisory REORG pending status and tablespace versions.
Thanks,
Sushanth |
|
| Back to top |
|
|
|
|
