Solution : https://service.sap.com/sap/support/notes/46272 (SAP Service marketplace login required)
Summary :
This SAP Note explains the process of implementing a new data class in SAP systems and is relevant for specific databases like DB2 UDB for UNIX and Windows, Informix, Oracle, and DB2/390. It details how to create and manage a new tablespace, align it with a data class through entries in various database system-specific tables, and how to ensure the new data class is recognized by the SAP system. Key steps include defining the new data class and linking it to the newly created memory area. Be wary of potential issues such as data loss post-upgrade if modifications are not managed appropriately, particularly in SAP standard tables through transaction SE16 or ABAP/4 programming.
Key words :
table memory area>taora-pctinc = '0000'taora-ofreelist = '001'taora-ofreegroup = '01'taora-opctfree = '10'taora-opctused = '40' 4, index memory area>iaora-pctinc = '0000'iaora-ofreelist = '01'iaora-opctfree = '10', table memory area>tainf-lockmode = 'row' iainf-tabart = <, taora taora-tabart = <, table memory area> iadb6-tabart = <, data dictionary metadata table dd09l, link data class <-> memory areaafter, data class>taora-tabspace = <, iaora iaora-tabart = <, data class>iaora-tabspace = <
Related Notes :
1513862 | DB6: Table conversion using DB6CONV Version 5.01 or higher |
771191 | Copying BW objects to new tablespaces |
666061 | FAQ: Database objects, segments and extents |
541542 | Upgrade phase INIT_CNTRANS: Container inconsistency |
515968 | DB6: Creating data classes and tablespaces in DBA cockpit |
500252 | Changing data cl. for InfoC. with report RSDG_DATCLS_ASSIGN |
499073 | DB6: conventions for data class names/changes in admin docu |
385163 | Partitioning on ORACLE since BW 2.0 |
371413 | DB data class and size catgory for aggregate tables |
362325 | DB6: Table conversion using DB6CONV Version 4.10 or lower |
178275 | Bitmap Indexes in Wrong Tablespace |
163449 | DB2/390: Implement new data class (TABART) |
118059 | Storage parameter for system copy with R3load |
82211 | Migration under 3.0D, 3.0E with R3load procedure |