Solution : https://service.sap.com/sap/support/notes/627246 (SAP Service marketplace login required)
Summary :
When Oracle's Automatic Segment Space Management (ASSM) is used, creating new objects can trigger an ORA-02168 error due to invalid FREELISTS values. This issue stems from storage parameters with 'NULL' values for FREELISTS in Tab types. To resolve, modifications can be applied to the SDB2FORA ABAP report, specifically in the TABSTORAGE_DBS_GET, INDSTORAGE_DBS_GET, and FILL_PARTY_TAB forms, setting ORA parameters 'ofreelist' and 'ofreegroup' to 1 when they are less than 1. This preemptive correction helps ensure compatibility during object creation, and further adjustments should be made in the SDB2FORA report for INDSTORAGE_DBS_GET to avoid related issues.
Key words :
ind_para-tablespace_name ind_para-initial_extent ind_para-next_extent ind_para-min_extents ind_para-max_extents ind_para-pct_increase ind_para-freelists ind_para-freelist_groups ind_para-pct_free oraindpara-indextype oraindpara-party correction prid changing rc, assm end appstor party_tab _partname party_para-partition, prid 'e' 'da619' 'user_indexes', prid 'e' 'da619' 'user_tables', oraindpara-party = ', reading oracle system table user_indexes, ind_para-freelist_groups < 1, ind_para-freelist_groups = 1, ind_para-freelists < 1, ind_para-freelists = 1
Related Notes :
| 946141 | Inst. SAP Systems on UX/Oracle 10.2 with R3SETUP |
| 782140 | OCS: Known problems with Support Packages in Basis Rel. 6.20 |
| 775810 | Use of ASSM in R3 Releases 31I to 610 |
| 672651 | OCS: Known problems with Support Packages in Basis Rel.6.40 |
| 447925 | OCS: Known problems with Supp. Packages in Basis Rel.6.20 |