Do you have any question about this error?
Message type: E = Error
Message class: DB6PM - DB2 UDB for UNIX, Windows: Performance Monitoring
Message number: 351
Message text: History of Data Collector &1 has been reset
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
DB6PM351
- History of Data Collector &1 has been reset ?The SAP error message DB6PM351, which states "History of Data Collector &1 has been reset," typically relates to the database performance monitoring and data collection processes within SAP systems, particularly those using the SAP DB (MaxDB) or other database systems integrated with SAP.
Cause:
Data Collector Reset: This message indicates that the history of the data collector for a specific database has been reset. This can happen due to various reasons, such as:
- Manual intervention by a database administrator.
- System maintenance or upgrades that require resetting the data collector.
- Configuration changes that affect how data is collected or stored.
- Automatic resets based on certain thresholds or conditions defined in the system.
Configuration Issues: Sometimes, the configuration settings for the data collector may not be optimal, leading to resets.
Database Performance Issues: If the database is experiencing performance issues, it may trigger a reset of the data collector to clear out old data and start fresh.
Solution:
Check Configuration: Review the configuration settings for the data collector. Ensure that they are set up correctly and that there are no parameters that could lead to unintended resets.
Monitor Database Performance: Use SAP tools or database monitoring tools to check the performance of the database. Look for any anomalies or performance bottlenecks that could be causing the data collector to reset.
Review Logs: Check the database logs and SAP application logs for any related messages or errors that could provide more context on why the reset occurred.
Consult Documentation: Refer to the SAP documentation or the specific database documentation for guidance on data collector settings and best practices.
Contact Support: If the issue persists or if you are unsure about the cause, consider reaching out to SAP support or your database administrator for further assistance.
Related Information:
By following these steps, you should be able to identify the cause of the DB6PM351 error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
DB6PM350
Action only permitted from system &1 (see SAP Note 1232928)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DB6PM349
Action only permitted for local database connection
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DB6PM352
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DB6PM353
Data Collector '&1' has been updated
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.