| ORA-1632: [message #119007] |
Tue, 10 May 2005 05:01  |
Jun Galolo
Messages: 3
Registered: December 2003
|
Junior Member |
|
|
pls help,
one of our table/index of same tablespace has this daily error, and i have increase the capacity of the said table/index daily.
is there a way can I minimize such error?
anyway I am using oracle 7.3 with OS AIX.
thanks,
jun
|
|
|
|
| Re: ORA-1632: [message #119019 is a reply to message #119007] |
Tue, 10 May 2005 05:27  |
girish.rohini
Messages: 744
Registered: April 2005
Location: Delhi (India)
|
Senior Member |
|
|
HI
Two possible ways to resolve this are :
1. Increase the MAXEXTENTS parameter value in the initialization file.
2. Increase the PCTINCREASE parameter value in the initialization file.
Regds
Girish
|
|
|
|
| Re: ORA-1632: [message #119055 is a reply to message #119019] |
Tue, 10 May 2005 08:12 |
sunil_v_mishra
Messages: 506
Registered: March 2005
|
Senior Member |
|
|
hi
ORA-01632 max # extents (string) reached in index string.string
Cause: An index tried to extend past MAXEXTENTS.
Action: If the value of MAXEXTENTS in the index storage clause is less than the maximum (based on your block size), raise it. Otherwise, re-create the index with larger extent sizes so that the total number of extents falls below the maximum.
From:- sunil
|
|
|
|
| Re: ORA-1632: [message #119062 is a reply to message #119055] |
Tue, 10 May 2005 08:24 |
 |
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
|
Senior Member
Account Moderator |
|
|
>>one of our table/index of same tablespace has this daily error, and i have increase the capacity of the said table/index daily.
You have to do the proper estimation and set the storage values in Tablespace level and not in table / index level ( Unless you have a specific need to have the particular index/table to have a different storage clause than others).
What kind of operations are done here?
In case of frequent imports never export with compress=Y.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
