Message type: E = Error
Message class: DBMAN - Data Manager Message Class
Message number: 380
Message text: Multiple entries found with NCUMTIM 'unlimited'; compression not possible
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The time dimension contains multiple entries for which the timeCompression is terminated.
Contact your system administrator.
To allow compression to be carried out, the entries must first be
removed from the InfoCube.
To do this, you can proceed as follows:
Delete all packages that contain records in which the time reference
characteristic has the value 'unlimited'. You can identify these
packages by using transaction LISTCUBE.
Reload these packages and create a rule in the transformation that maps
the value 'unlimited' to a year before 9000.
Using transaction RSRV, then delete all entries that are no longer used
from the time dimension.
The InfoCube can be compressed again.
Error message extract from SAP system. Copyright SAP SE.
DBMAN380
- Multiple entries found with NCUMTIM 'unlimited'; compression not possible ?The SAP error message DBMAN380 indicates that there are multiple entries found with the NCUMTIM (Next Cumulative Time) set to 'unlimited', which prevents the system from performing data compression. This typically occurs in the context of database management and data archiving processes.
Cause: Multiple Entries: The error arises when there are multiple records in the database that have the same NCUMTIM value set to 'unlimited'. This situation can occur due to incorrect data entries or configuration issues in the database. Data Integrity Issues: It may also indicate a problem with data integrity, where the system is unable to determine which entry should be used for compression. Configuration Settings: The settings related to data archiving or compression may not be properly configured, leading to conflicts.
Solution: To resolve the DBMAN380 error, you can follow these steps: Identify Duplicate Entries: Use SQL queries or SAP transaction codes (like SE16 or SE11) to check the relevant database tables for entries with
Get instant SAP help. Sign up for our Free Essentials Plan.
DBMAN379
Inconsistency in the metadata
What causes this issue? Before compression, the metadata for the dependent objects is collected (dimensions, key figures, partitioning, and so on)....
DBMAN378
Prerequisite for successful compression not fulfilled
What causes this issue? During the initial check the system determined that one or more prerequisites for successful compression has not been fulfill...
DBMAN381
*************** Check-Tool for Condenser
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DBMAN382
Scenario &2 (trace &1): correctly carried out
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.