Solution : https://service.sap.com/sap/support/notes/206439 (SAP Service marketplace login required)
Summary :
This SAP Note discusses increased disk space usage due to large BDoc message flow and Middleware trace tables in CRM Middleware. Overly high log or trace levels and lack of scheduled reorganization can deteriorate performance. Solutions include adjusting log and trace settings to optimal levels and ensuring regular execution of reorganization programs (SMO6_REORG, SMO6_REORG2). Proper scheduling of these programs across all clients is critical. Further details and configurations for managing log levels post Upgrade to Release 3.0 and higher are explained, including how to set default settings for Middleware trace environments.
Key words :
0 error 1 warning 2 flow services 3 detail level 1 4 detail level 2 2, automatically written / flow servicestrace level 3 = detail level 1, ----------------------------------key crmgeneralparamname trace-levelparamname2 env=mparam, reorganizing specific crm middleware statistical data, -table space full-trace level 1 = warning, technology -> middleware -> monitoring -> message flow -> set, choose middleware -> administration -> define middleware parameters, strong warningstrace level 4 = detail level 2, set default log level 'e', choose set default settings
Related Notes :
| 706478 | Preventing Basis tables from increasing considerably |
| 675725 | Unnecessary BDocs in SRM (EBP) from queue CSA_MASS_BUPA |
| 638551 | Deactivating creation of BDoc messages |
| 623195 | Flow-specific entries in the SMOFPARSFA table |
| 600007 | Standard variant for report SMO6_REORG does not exist |
| 536414 | CRM 3.0/3.1 SAP Composite Note: Middleware reorganization |
| 503002 | Performance problems during BDoc processing |
| 494901 | SAPKU30008: Support Package 8 for EBP 3.0/CRM 3.0 |
| 487915 | BDoc message flow tables are not reorganized |
| 328791 | Quick deletion of trace files from the CRM server |
| 206366 | Performance problems or high I/O load due to traces |