Do you have any question about this error?
Message type: E = Error
Message class: DB6PM - DB2 UDB for UNIX, Windows: Performance Monitoring
Message number: 379
Message text: WebDynpro has been set as preferred user interface for DB2 LUW systems
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.
DB6PM379
- WebDynpro has been set as preferred user interface for DB2 LUW systems ?The SAP error message DB6PM379 indicates that the WebDynpro user interface has been set as the preferred interface for DB2 LUW (Linux, Unix, Windows) systems. This message typically arises in the context of SAP applications that are using the DB2 database.
Cause:
The error message is generally informational rather than an error that prevents operation. It indicates that the system is configured to use WebDynpro as the preferred user interface for interacting with DB2 LUW systems. This can occur due to:
- Configuration Settings: The system settings or profiles have been configured to prioritize WebDynpro for user interactions.
- System Upgrade or Migration: Changes in the system landscape, such as upgrades or migrations, may have led to this configuration.
- User Preferences: User-specific settings may have been adjusted to prefer WebDynpro.
Solution:
If you are encountering this message and it is causing issues, consider the following steps:
Check Configuration: Review the configuration settings in the SAP system to ensure that WebDynpro is indeed the desired interface. You can check this in the SAP GUI under transaction codes like
SICF
(for Internet Communication Framework) orSPRO
(for customizing).User Preferences: If the message is related to user preferences, you can check the user settings in transaction
SU01
(User Maintenance) to see if the preferred interface can be changed.Documentation: Refer to the SAP documentation or notes related to WebDynpro and DB2 LUW for any specific configurations or recommendations.
Consult SAP Support: If the message is causing operational issues or if you need further clarification, consider reaching out to SAP Support for assistance.
Related Information:
In summary, the DB6PM379 message is primarily informational, indicating a configuration preference. If it is not causing any functional issues, it may not require immediate action. However, if you need to change the preferred interface or if it is causing problems, follow the steps outlined above.
Get instant SAP help. Start your 7-day free trial now.
DB6PM378
SAPGUI has been set as preferred user interface for DB2 LUW systems
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DB6PM377
Directory &1 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DB6PM380
Tablespace &1 not yet existing
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DB6PM381
Old history collectors have been disabled
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.