Solution : https://service.sap.com/sap/support/notes/533455 (SAP Service marketplace login required)
Summary :
This SAP Note addresses errors related to the MAXEXTENTS parameter in Oracle tablespaces, causing failures in creating new extents for database objects, affecting SAP system operations. It outlines possible conditions triggering this issue, notably using Oracle dictionary managed tablespaces with insufficient MAXEXTENTS settings. Recommended actions involve adjusting MAXEXTENTS in the SQLPLUS interface, with specific alterations based on error types—ensuring configurations sustain across system recalibrations (referencing Notes 666061, 214995). For comprehensive maintenance, considering adjustment of NEXTEXTENT values is also advised to preclude future errors.
Key words :
ora-01684alter table <tab> modify partition <part> storage, ora-01685alter index <ind> modify partition <part> storage, lob segment <lob> partition <part>ora-03235, table <tab> partition <part>ora-01685, statementalter table <tab> modify lob, index <ind> partition <part>ora-01693, ora-01631alter table <tab> storage, table <tab> subpartition <subpart>ora-03236, index <ind> subpartition <subpart> reason, ora-01656alter cluster <clus> storage
Related Notes :
| 666061 | FAQ: Database objects, segments and extents |
| 584548 | Unusually high number of redo logs |
| 500340 | FAQ: LOBS |
| 173910 | Cluster: Termination due to TABLESPACE over-run |
| 16277 | ORA1562 / ORA1628 |
| 11777 | ORA-1632 max # extents <n> reached in index <ind.> |