How To Fix DB6PM420 - The use of wildcards is not permitted

DB6PM420 - Overview

• Message type: E = Error

• Message class: DB6PM - DB2 UDB for UNIX, Windows: Performance Monitoring

• Message number: 420

• Message text: The use of wildcards is not permitted

Self-Explanatory Message

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.

What else can you do?

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.

DB6PM420 - Details

• The SAP error message DB6PM420, which states "The use of wildcards is not permitted," typically occurs in the context of database operations where a wildcard character (like % or *) is used in a query or command that does not support it. This can happen in various scenarios, such as when defining database objects, executing SQL queries, or configuring certain settings in SAP.
  
  Cause:
  
  Improper Query Syntax: The error often arises when a SQL query or command includes wildcard characters in a context where they are not allowed. For example, using wildcards in a database object name or in certain parameters.
  Database Restrictions: Some databases have restrictions on the use of wildcards in specific commands or contexts, which can lead to this error.
  
  Configuration Issues: Incorrect configuration settings in the SAP system or the database can also lead to this error.
  
  
  Solution:
  
  
  Review the Query/Command: Check the SQL query or command that triggered the error. Ensure