Solution : https://service.sap.com/sap/support/notes/407260 (Connexion à SAP Service Marketplace requise)
Résumé :
This SAP Note provides guidance on compressing InfoCubes using ORACLE as the database platform, detailing the process, expected results, and performance considerations. Key areas covered include the necessity of the P-index on the E-fact table for compression effectiveness, data integrity assurance during compression interruptions, and techniques to manage and enhance compression performance. Techniques include verifying index existence using transaction DB02, optimizing data loading, and handling errors like ORA-4030 by managing secondary indexes through transactions like SE14. The guidelines aim to ensure efficient data compression without loss, maintaining both data accessibility and system performance.
Mots Clés :
attribute/hierarchy change run, identical 'logical' key, logical key includes, finest time characteristics, 'compr-dual'-flag, running queries parallel, prevent ressource shortages, parameters i_infocube = <techn, elementary database check, entire fact table
Notes associées :
| 1461926 | FAQ: BW report SAP_INFOCUBE_DESIGNS |
| 1233601 | Message RSDA 228 when archived data is deleted |
| 590370 | Too many uncompressed request (f table partitions) |
| 486395 | Error during request deletion of F-fact table, 20BSP20-21CSP |
| 455281 | Selective deletion dumps with ORA-03113 in report GP<xyz> |
| 430486 | Overview/repair of F fact table of an BW InfoCube |
| 428440 | Selective Deletion dumps with at RAISE x_message |
| 409338 | Compression and upgrade from BW1.2 to BW2.0 |
| 385163 | Partitioning on ORACLE since BW 2.0 |
| 375132 | Performance optimization for InfoCube condensation |