RSENQ - Sperr-Manager
The following messages are stored in message class RSENQ: Sperr-Manager.
It is part of development package RSENQ in software component BW-WHM. This development package consists of objects that can be grouped under "Lock Manager".
It is part of development package RSENQ in software component BW-WHM. This development package consists of objects that can be grouped under "Lock Manager".
Message Nr ▲ | Message Text |
---|---|
000 | ***Messages for the Lock Manager*** |
001 | Lock action & does not exist |
002 | Lock NOT set for: & |
003 | Lock set for: & |
004 | Data package &1 from request &2 has been updated already in InfoCube &3 |
005 | The system has not finished loading request &1 into data target &2 |
006 | Lock NOT deleted for: & |
007 | Lock deleted for: & |
008 | Loading data target &1 |
009 | Lock in lock manager could not be set; Objects &1 &2 &3 &4 |
010 | Data target &1 is being compressed |
011 | Request &2 is currently being loaded from data target &1 |
049 | Aggregate &1 being used as source for filling an aggregate |
050 | A roll up is running for InfoCube &1 |
051 | The roll up for InfoCube &1 has terminated |
052 | The change run has been started already by user &1 |
053 | The system is not able to fill the aggregates at this time |
054 | Aggregate &1 is locked by user &2 |
055 | You cannot role up cube &1 (aggregates are filled from &2) |
056 | Change run is not possible, because aggregates are being filled |
057 | Sort the aggregate catalog locked by &1 |
058 | InfoCube &1 is locked by change run &2 |
059 | InfoCube &1 is locked by terminated change run &2& |
060 | Hierarchy &1 is locked by change run &2 |
061 | Hierarchy &1 is locked by terminated change run &2 |
062 | Attributes of characteristic &1 are locked by change run &2 |
063 | Attributes of characteristic &1 are locked by terminated change run &2 |
064 | The action is locked by a change run |
065 | The action is locked by a change run |
066 | "Adjustment of variable aggregates" takes place in the start phase |
067 | Change run for time-dependent aggregates already started |
068 | InfoCube &1 locked by terminated time-change run &2 |
069 | InfoCube &1 is locked by time-change run &2 |
070 | Action is locked by time-change run &1 |
071 | Action locked by terminated time-change run &2 |
072 | Object &1 for BEA index is locked by user &2 |
073 | BWA index &1 is being filled |
074 | Lock already set for BWA index &1 |
075 | Index for InfoObject '&1' has already been filled by user '&2' |
076 | Index for InfoObject '&1' cannot be filled because of locks |
077 | Locks already set for index for characteristic '&1' |
078 | Collector already started by user &1 |
079 | Process for deleting master data indexes is already running |
080 | Deleting master data |
081 | Indexing currently running locks hierarchy &1 |
082 | Cannot start deleting master data indexes at the moment |
083 | User &2 is already running an index activation for object &1 |
084 | Cannot start index activation at the moment |
085 | Deletion of master data index is already running |
086 | Cannot start deletion of master data index at the moment |
087 | Index activation is running |
113 | Errors when reading the enqueue for table 'RSENQ_PROT_ENQ' |
114 | Cannot determine a background process for writing the application log |
115 | Cannot find scheduled or current job &1 |
116 | Background job is running and will update the rest of the logs |
117 | Background job is scheduled |
118 | Logs exist that have not yet been updated and that have been terminated |
119 | There are logs that have been terminated |
120 | There are logs that have not yet been updated |
121 | All logs updated successfully to the application log |
150 | *----------------------- Archiving (150-169) -----------------------* |
151 | An archiving run locks InfoProvider &1 (archivation object &2) |
200 | ------------------------Repartitioning (200-220)--------------------- |
201 | A repartitioning run locks InfoProvider &1 (action &2) |
221 | ------------------------Object Migration (221-240)--------------------- |
222 | Database lock already set |
223 | Lock already set by another application. Action canceled |
224 | Cannot remove lock |
225 | Could not set lock: Object already locked by &1 &2 |
226 | Data target not specified. Cannot lock |
227 | Could not set lock: Object already locked by &1 &2 &3 |
228 | Incorrect parameter passed to &1 &2 |