Solution : https://service.sap.com/sap/support/notes/11777 (SAP Service marketplace login required)
Summary :
The SAP Note addresses issue ORA-1632, where an index reaches the maximum number of extents, preventing further growth. The cause is insufficient storage parameters. The solution involves altering the storage parameters NEXT and MAXEXTENTS. Using SAPDBA, navigate to Reorganization -> Alter/show table or index storage parameters, enter the index name, and adjust MAXEXTENTS and NEXT values based on actual and target data volumes. Alternatively, using SQLPLUS, use the commands to modify the NEXT and MAXEXTENTS values for the specified index. Ensure the index name is entered in upper-case letters to reorganize the table or index accordingly.
Key words :
ora-1632ora1632 max # extents <num> reached, sql> alter index <index_name> storage, index <index_name>--> index reached, -> reorganization -> alter/show table, index storage parameters - enter, sql> select next_extent, symptom key word, additional key words, upper-case letters, prerequisites storage parameters
Related Notes :
| 900345 | Backward Release of ORACLE 10.2 - Upgrade Information |
| 662219 | Add. info. on upgrading to SAP Web AS 6.40 ORACLE |
| 533455 | Terminations due to higher number of extents |
| 431357 | SQL error 1632 when accessing table "/SAPAPO/MC01XCCV" |
| 389618 | Composite Note: APO initial data transfer with sales orders |
| 370601 | Composite SAP note: APO 3.0 and 3.1 performance |
| 304597 | Additions to upgrade to Release 4.6C FCS |
| 201874 | Additions for upgrade to 4.6C/4.6C SR1/4.6C SR2 Oracle |
| 192949 | Additional info for upgrade to 4.6C |
| 102208 | Additional Info: Upgrading to 3.1I ORACLE |
| 32206 | CO: Raise MISSING_ENTRY_IN_FPAGE_FCOLUMN |
| 31524 | Maxextent = 100 for new 3.0 installation |
| 3502 | ORACLE Version 6 : ORA1556, Version 7 : ORA1631 |