Do you have any question about this error?
Message type: E = Error
Message class: S06 - SAP Netweaver Workload Collector
Message number: 858
Message text: Already an aggregate
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.
S06858
- Already an aggregate ?The SAP error message S06858, which states "Already an aggregate," typically occurs in the context of SAP BW (Business Warehouse) or SAP HANA when you are trying to create or modify an aggregate that already exists. This error indicates that the system has detected that the aggregate you are attempting to create is already defined in the system.
Cause:
- Duplicate Aggregate Definition: You are trying to create an aggregate that has already been defined in the system.
- Incorrect Configuration: There may be a misconfiguration in the data model or the aggregate settings.
- System Cache: Sometimes, the system cache may not be updated, leading to confusion about existing aggregates.
Solution:
Check Existing Aggregates:
- Go to the relevant InfoCube or DataStore Object (DSO) and check the list of existing aggregates. You can do this in the SAP BW modeling tools or transaction codes like RSA1.
- If the aggregate already exists, you may not need to create a new one. Instead, you can use the existing aggregate.
Modify Existing Aggregate:
- If you need to change the structure or settings of the existing aggregate, you can modify it instead of creating a new one.
Delete Unused Aggregates:
- If there are old or unused aggregates that are no longer needed, consider deleting them to avoid confusion.
Clear Cache:
- If you suspect that the issue is related to caching, you can clear the cache for the InfoCube or aggregate. This can be done using transaction code
RSADMIN
orRSCUSTV10
to manage aggregates and their caches.Check for Transport Issues:
- If you are working in a development environment and transporting changes to production, ensure that the transport does not contain conflicting definitions.
Consult Documentation:
- Review SAP documentation or notes related to aggregates for any specific guidelines or updates that may apply to your version of SAP BW or HANA.
Related Information:
By following these steps, you should be able to resolve the S06858 error and manage your aggregates effectively in SAP BW or HANA.
Get instant SAP help. Start your 7-day free trial now.
S06857
&1 exceptions were raised; the last exception was: &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
S06856
Collector parameters set to SAP default values (table SWNCCOLLPARAM)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
S06859
&1 entries deleted from table &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
S06860
Total collector started, &1 instances to process
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.