Do you have any question about this error?
Message type: E = Error
Message class: DB6PM - DB2 UDB for UNIX, Windows: Performance Monitoring
Message number: 389
Message text: Special or space characters in a threshold name are not permitted.
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.
DB6PM389
- Special or space characters in a threshold name are not permitted. ?The SAP error message DB6PM389 indicates that there are special or space characters in a threshold name that are not permitted. This error typically occurs in the context of database monitoring or performance management within SAP systems, particularly when configuring thresholds for alerts or monitoring metrics.
Cause:
The error is caused by the inclusion of invalid characters in the name of a threshold. SAP has specific naming conventions that restrict the use of certain characters, including spaces and special characters, to ensure consistency and avoid issues in processing.
Solution:
To resolve this error, you should:
Identify the Threshold Name: Determine which threshold name is causing the error. This may involve reviewing the configuration settings where the threshold is defined.
Modify the Threshold Name: Change the threshold name to remove any special characters or spaces. Use only alphanumeric characters (letters and numbers) and underscores (_) if needed. For example:
- Instead of
Threshold Name 1!
, useThreshold_Name_1
.Save Changes: After modifying the threshold name, save the changes and check if the error persists.
Test the Configuration: Once the changes are made, test the configuration to ensure that the threshold is functioning as expected without triggering the error.
Related Information:
By following these steps, you should be able to resolve the DB6PM389 error and successfully configure your thresholds without any issues.
Get instant SAP help. Start your 7-day free trial now.
DB6PM388
Detailed data about running phases is not available
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DB6PM387
ABAP source viewer is not available. See SAP Note 1493490.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DB6PM390
Priority aging service class has been created
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DB6PM391
Priority aging service class has been dropped
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.