Solution : https://service.sap.com/sap/support/notes/997535 (SAP Service marketplace login required)
Summary :
Users are encountering ABAP dumps (CONNE_IMPORT_WRONG_COMP_TYPE, CX_SY_IMPORT_MISMATCH_ERROR) in SAP during database performance data collection in RSORAT4M, RSORAT5M, and potentially RSORAT6M with the error title: “Error when attempting to IMPORT object 'HIST2'.” The root cause is a type inconsistency between the table MONI and modified ABAP structures. The recommended solution involves manually deleting specific MONI records using transaction ST03N, navigating to 'Expert Mode' and then to 'Performance Database' under 'Collector and Performance Analysis.' If problematic MONI records persist causing dumps, further deletions are advised. Clients wishing to preserve historical data should refer to SAP Note 1000275 for guidance on data archiving and viewing.
Key words :
performance analysis -> performance database -> monitoring database -> contents4, database related history background job, database performance data collector, abap modified internal structures, database related history, growth related issues, tables/indexes history, monikey entry causing, error break point, prerequisites type inconsistency
Related Notes :
| 1303289 | SAP_COLLECTOR_FOR_PERFMONITOR dump during history IMPORT |
| 1225811 | Program 'SAPLSAPWL_STAT'causes long runtimes during Alerts |
| 1143639 | Log Report not updated : Showing N/A in spool of FF job |
| 1000275 | DB02: history data backup procedure. |