RT - Monitoring infrastructure MSG and alert texts
The following messages are stored in message class RT: Monitoring infrastructure MSG and alert texts.
It is part of development package SMOI in software component BC-CCM-MON. This development package consists of objects that can be grouped under "CCMS: Monitoring Architecture".
It is part of development package SMOI in software component BC-CCM-MON. This development package consists of objects that can be grouped under "CCMS: Monitoring Architecture".
Message Nr ▲ | Message Text |
|---|---|
| 001 | &1 &3 > &2 &3 Current value over threshold value |
| 002 | Frequency &1 &3 > &2 &3 (no. of messages per hour over threshold value) |
| 003 | &1 &3 > &2 &3 1 hour avg. value over threshold value (&4 measurements) |
| 004 | &1 &3 > &2 &3 1 minute avg. value over threshold value (&4 measurements) |
| 005 | &1 &3 > &2 &3 5 minute avg. value above threshold value (&4 measuremts) |
| 006 | &1 &3 > &2 &3 15 minute avg. value above thresh. value (&4 measurements) |
| 007 | &1 &3 < &2 &3 current value below threshold value |
| 008 | Frequency &1 &3 < &2 &3 (No. of messages per hour below threshold value) |
| 009 | &1 &3 < &2 &3 1 hour avg. value below threshold value (&4 measurements) |
| 010 | &1 &3 < &2 &3 1 minute avg. value below threshold value (&4 measuremts) |
| 011 | &1 &3 < &2 &3 5 minute avg. value below threshold value (&4 measuremts) |
| 012 | &1 &3 < &2 &3 15 min. avg. value below threshold value (&4 measurements) |
| 013 | No detailed description available |
| 014 | Frequency &1 &3 > &2 &3 (no. of messages per minute above threshold val) |
| 015 | Frequency &1 &3 > &2 &3 (5 minute avg. value above threshold value) |
| 016 | Frequency &1 &3 > &2 &3 (15 min. avg. value above threshold value) |
| 017 | Frequency &1 &3 < &2 &3 (no. of messages per minute above threshold val) |
| 018 | Frequency &1 &3 < &2 &3 (5 min. avg. value below threshold value) |
| 019 | Frequency &1 &3 < &2 &3 (15 min. avg. value below threshold value) |
| 020 | &1 successfully executed |
| 021 | SALI test: 1: &1 2: &2 3: &3 4: &4 and 2: &2 3: &3 again |
| 022 | This monitor attrib. describes the status of the OS collector (SAPOSCOL) |
| 023 | The OS collector (SAPOSCOL) is not running (error code: &1) |
| 024 | The OS collector (saposcol) is not running |
| 025 | The OS collector (saposcol) is running |
| 026 | File System: Hard disk space available |
| 027 | Free disk space &1 &3 short of &2 &3 |
| 028 | File system: Fill Level - Percentage |
| 029 | File system for &1 &3 full (threshold value: &2 &3) |
| 030 | &1 successfully executed |
| 031 | Unable to create MTE &1 &2 |
| 032 | Unable to determine operating system data (error code: &1) |
| 033 | Unable to send value to &1 |
| 034 | MT &1 does not exist |
| 035 | CPU Utilization: &1 &3 > &2 &3 15 min. avg. value over threshold value |
| 036 | CPU Load: &1 &3 > &2 &3 15 min. avg. value over threshold value |
| 037 | &1 &3 > &2 &3 15 min. avg. value over threshold value |
| 038 | &1 &3 < &2 &3 15 min. avg. value over threshold value |
| 039 | &1 started |
| 040 | Table &1 cannot be locked |
| 041 | Adopt responsibility for global monitoring segment (&1 inactive) |
| 042 | Startup tools executed |
| 043 | Monitoring segment status updated from '&1' to 'Online' |
| 044 | Tool could not be assigned for MT &1 |
| 045 | RFC Problem: &1&2 (Function module: &3, RFC destination: &4) |
| 046 | Tool &1 run on &2 at &3 |
| 047 | Buffer value for the application server |
| 048 | File systems for the application server |
| 049 | Runtime messages for self-monitoring of CCMS monitoring architecture |
| 050 | Messages regarding delivered data collectors |
| 051 | Monitoring Object: File system |
| 052 | Technical name for the file system |
| 053 | Monitoring object: CPU |
| 054 | CPU: Average usage |
| 055 | CPU: Average number of waiting processes |
| 056 | Monitoring object: Paging (page overlapping) |
| 057 | Paging: Page in: Pages per second |
| 058 | Paging: Page out: Pages per second |
| 059 | Monitoring object: Swap Space |
| 060 | Available Swap Space |
| 061 | Percentage of Swap Space used |
| 062 | Monitoring object: OS collector (SAPOSCOL) |
| 063 | CCMS monitoring architecture self-monitoring: RFC problems |
| 064 | Monitoring object: Buffer |
| 065 | Buffer: Percentage use of directory |
| 066 | Buffer: Percentage usage of buffer memory |
| 067 | Buffer: Hit rate |
| 068 | Application server: Number of logged-on users |
| 069 | Error occurred when calling an SALS function: &1&2 |
| 070 | System log log attribute: various |
| 071 | System log log attribute: application |
| 072 | System log log attribute: background processing |
| 073 | System log log attribute: Basis System |
| 074 | System log log attribute: operation tracking (CCMS) |
| 075 | System log log attribute: database |
| 076 | System log log attribute: customer message |
| 077 | System log log attribute: communication |
| 078 | System log attribute: spool / print |
| 079 | System log log attribute: security |
| 080 | System log attribute: transport system |
| 081 | System log log attribute: batch input |
| 082 | SAPMSSY8 started |
| 083 | SAPMSSY8 completed in &1 sec. |
| 084 | Update of table ALCONSEG complete |
| 085 | Customizing data compared with DB |
| 086 | Tool assignment compared with DB |
| 087 | Startup methods started |
| 088 | CCMS monitoring architecture self-monitoring: SAPMSSY8 messages |
| 089 | >> Tool dispatching started for application server segment |
| 090 | CCMS monitoring architecture self-monitoring: SAPMSSY8 runtime |
| 091 | CCMS self-monitoring: Runtime of the SAPMSSY8 &1 &3 exceeds &2 &3 |
| 092 | CCMS monitoring architecture: Sample data supplier: MO |
| 093 | CCMS Monitoring Architecture: Sample data supplier: Performance MA |
| 094 | CCMS Monitoring Architecture: Sample data supplier: Status message MA |
| 095 | Parameter &1 = &2 invalid (valid: &3 ... &4) |
| 096 | Invalid parameter combination: &1 >= &2 necessary! |
| 097 | CCMS self-monitoring: Number of completed alerts in the database |
| 098 | Number of completed alerts in database &1 exceeds threshold value &2 |
| 099 | >> Tool dispatching started for segment & using CCMS agent |
| 100 | &1 &2 |
| 101 | &1 successfully completed |
| 102 | &1 [&2] in &3 on &4 |
| 103 | Method dispatcher &1 for segment &2 started |
| 104 | Invalid tool dispatcher name: &1 |
| 105 | Invalid dialog mode: &1 |
| 106 | Invalid tool start mode: &1 |
| 107 | System could not determine which methods to execute: &1 &2 |
| 108 | System could not read RFC destination (&1), MTE: &2 |
| 109 | System could not determine technical method information for tool &1 |
| 110 | Method starter cannot start a method as no method selected |
| 111 | Method dispatcher &1 for segment &2 ended |
| 112 | Tool starter cannot start any tools as user/dispatcher name missing |
| 113 | Invalid maximum runtime value (&1) |
| 114 | Invalid tool start mode (&1) |
| 115 | Unable to set runtime status for data collection method (&1), MTE: &2 |
| 116 | Could not set alert status for auto-reaction method (&1), MTE: &2 |
| 117 | & |
| 118 | Segment name &1 is invalid |
| 119 | Cannot start tool &1 |
| 120 | Method &1: Runtime exceeded (&2 seconds) |
| 121 | Unable to determine the tool that terminated: &1 |
| 122 | Method &1 terminated. This affects MTE: &2 |
| 123 | Method dispatcher &1 already running for segment &2 |
| 124 | Error in lock management - cannot start method dispatcher &1 |
| 125 | Monitoring object: dialog service |
| 126 | Average response time of dialog service |
| 127 | &1 &3 > &2 &3 Dialog response time exceeds threshold (&4 dialog steps) |
| 128 | Average dispatcher wait time per dialog step |
| 129 | &1 &3 > &2 &3 Dialog wait time exceeds threshold (&4 dialog steps) |
| 130 | Average load and generation time for GUI objects |
| 131 | &1 &3 > &2 &3 Dialog load/gen. time exceeds threshold (&4 dialog steps) |
| 132 | Average time for processing logical database requests |
| 133 | &1 &3 > &2 &3 Dialog DB request time exceeds threshold (&4 dialog steps) |
| 134 | Average usage of dialog work processes of an application server |
| 135 | &1 &3 > &2 &3 dialog workprocess utilization exceeds threshold value |
| 136 | Average usage of dispatcher wait queue for dialog work processes |
| 137 | &1 &3 > &2 &3 dialog workprocess queue length exceeds threshold |
| 138 | Average time for long-running dialog work processes |
| 139 | Long-running report &4 has been running &1 &3 in dialog. Threshold: &2 &3 |
| 140 | ABAP program terminations in dialog work processes |
| 141 | CCMS monitoring architecture: data supplier example: message log MA |
| 142 | ABAP error: &1 in SNAP: &2 (client &3) |
| 143 | ABAP SQL error: &1 in SNAP: &2 |
| 144 | Response time exceeds one hour for report &1 (user: &2 client: &3) |
| 145 | Average number of dialog steps per minute |
| 146 | Average time for monitoring during a dialog step |
| 147 | &1 &3 > &2 &3 number of dialog steps per minute exceeds threshold |
| 148 | &1 &3 > &2 &3 monitoring time exceeds threshold value (&4 dialog steps) |
| 149 | &1: &2&3&4 |
| 150 | CCMS self-monitoring: number of free active alert slots in shared memory |
| 151 | Only &1 &3 free slots for active alerts (threshold &2 &3 slots) |
| 152 | Alert data for segment & downloaded |
| 153 | Overflow when calculating available disk space for &1 &2 |
| 154 | Waiting for startup method to execute &1 (method dispatcher: &2) |
| 155 | Startup method error: &1 (method dispatcher: &2, Time: &3, Status: &4) |
| 156 | Monitoring object: background service |
| 157 | Average percentage usage of background work processes of a server |
| 158 | &1 &3 > &2 &3 Background work process load exceeds threshold |
| 159 | Program error when executing background jobs |
| 160 | Monitoring object: Information about spool service |
| 161 | Spool work process load percentage |
| 162 | &1 &3 > &2 &3 Spool work process load exceeds threshold |
| 163 | Subtree: Spool service |
| 164 | Utilized area of dispatcher queue (percentage) |
| 165 | &1 &3 > &2 &3 Utilized area of dispatcher queue exceeds threshold value |
| 166 | Utilized area of spool service queue (percentage) |
| 167 | &1 &3 > &2 &3 Utilized area of spool request queue exceeds threshold |
| 168 | Utilized area of spool request queue for processing in order (in %) |
| 169 | &1 &3 > &2 &3 Spool request queue (in order) exceeds threshold |
| 170 | Utilized area of entire device cache (percentage) |
| 171 | &1 &3 > &2 &3 Utilized area of device cache exceeds threshold |
| 172 | Utilized area of fixed device cache (percentage) |
| 173 | &1 &3 > &2 &3 Utilized area of fixed device cache exceeds threshold val. |
| 174 | Utilized area of host spool request list (percentage) |
| 175 | &1 &3 > &2 &3 Utilized area of host spool request list exceeds threshold |
| 176 | Monitoring object: output devices |
| 177 | Subtree: enqueue |
| 178 | Monitoring object: enqueue client |
| 179 | Monitoring object enqueue client: Frequency |
| 180 | Monitoring object enqueue client: wait time |
| 181 | Monitoring object: Enqueue server |
| 182 | Monitoring object enqueue server: Percentage length of the queue |
| 183 | &1 &3 > &2 &3 enqueue: Frequency above threshold |
| 184 | &1 &3 > &2 &3 Enqueue: Wait time above threshold |
| 185 | &1 &3 > &2 &3 Length of the enqueue server queue above threshold |
| 186 | Status of developer trace |
| 187 | Status of system trace |
| 188 | Startup method (executed immediately after the server starts) |
| 189 | >> Created monitor attributes for executing startup method |
| 190 | Startup method &1 is not released as a data collection method |
| 191 | Monitoring context: operating system data for a dedicated database host |
| 192 | Operating system data for a dedicated database host: file systems |
| 193 | Transactional RFC and queued RFC |
| 194 | Transactional RFC: activities according to destination |
| 195 | Transactional RFC calls (ARFCSSTATE table) |
| 196 | Transactional RFC: Logical units of work waiting to be executed |
| 197 | Minimum number of calls with status SYSLOAD |
| 198 | Minimum number of calls with status CPICERR |
| 199 | Minimum number of calls with status SYSFAIL |
| 200 | Transactional RFC: Number of old calls |
| 201 | tRFC: React to alerts |
| 202 | qRFC outbound queue: status |
| 203 | qRFC incoming queue: status |
| 204 | Blocked outbound queue: Client &1 Q name &2 status &3 dest &4 |
| 205 | Blocked inbound queue: Client &1 Q name &2 status &3 dest &4 |
| 206 | Message: &1: Queue name follows |
| 207 | Monitoring object: Availability of SAP work processes |
| 208 | SAP work processes |
| 209 | Monitoring object: Allocation of SAP work processes |
| 210 | Availability of dialog work processes |
| 211 | Availability of background work processes |
| 212 | Availability of spool work processes |
| 213 | Availability of update1 work processes |
| 214 | Availability of update2 work processes |
| 215 | Availability of enqueue work processes |
| 216 | &1 &3 < &2 &3 average availability in 15 minute period below threshold |
| 217 | Number of dialog work processes |
| 218 | Number of background work processes |
| 219 | Number of spool work processes |
| 220 | Number of update1 work processes |
| 221 | Number of update2 work processes |
| 222 | Number of enqueue work processes |
| 223 | Swaps due to full buffer per minute |
| 224 | Number of buffer swaps exceeded threshold |
| 225 | Total number of calls not executed or with errors |
| 226 | Transactional RFC: Internal error in method |
| 227 | Internal error in method: &, Error: & |
| 228 | ALE CPI C error: Target\Program\Client &1, user &2, function &3, TID &4 |
| 229 | ALE SYSFAIL error: Target\program\client &1, user &2, function &3, TID &4 |
| 230 | &1 Details: connected to database server &1, database &2 (&3, &4) |
| 231 | Monitoring object: connection of database client |
| 232 | Database client connection: database server and other details |
| 233 | Cannot determine own RFC destinations |
| 234 | CCMS Self-monitoring: number of free slots in shared mem. segm. for MTE |
| 235 | Only &1 free slots in shared memory segments for MTE (threshold &2 slots) |
| 236 | Number of pages to be output in spool request queue |
| 237 | &1 &3 > &2 &3 Number of pages in spool request queue exceeds threshold |
| 238 | Monitoring object: commit charge |
| 239 | Available commit charge |
| 240 | Used commit charge in percent |
| 241 | Background dispatching for methods can only be started in background |
| 242 | No segments with status ONLINE found in local system |
| 243 | Could not start tool dispatching for segment &1 |
| 244 | Starting background dispatching on server &1 ... |
| 245 | End of background dispatching on server &1 |
| 246 | &1: Cannot start TOOLSET_STARTER: &2 |
| 247 | TOOLSET_STARTER, RFC destination &1: &2 |
| 248 | Monitoring object: LAN |
| 249 | LAN -- Packets in: Packets per second |
| 250 | LAN -- Packets out: Packets per second |
| 251 | LAN -- Number of collisions |
| 252 | LAN system of the application server |
| 253 | Background method dispatching not possible - no jobs released |
| 254 | Background method dispatching not possible - job does not exist |
| 255 | Cannot determine information about job for background tool dispatching |
| 256 | SAP dialog service monitoring object: Front end wait time |
| 257 | &1 &3 > &2 &3 Frontend response time exceeds threshold (&4 dialog steps) |
| 258 | Average time use in network (excluding roundtrips) |
| 259 | &1 &3 > &2 &3 Network runtime exceeds threshold (&4 dialog steps) |
| 260 | Cannot read rule description & from database |
| 261 | Performance attribute: Frontend response time (transaction-specific) |
| 262 | Monitoring context for transaction-specific monitoring |
| 263 | Monitoring object "client" for transaction-specific monitoring |
| 264 | Monitoring object "transaction" for transaction-specific monitoring |
| 265 | Monitoring obj. "ClientTransaction" for transaction-specific monitoring |
| 266 | Referenced monitoring object for transaction-specific monitoring |
| 267 | Performance attribute for dialog response time (transaction-specific) |
| 268 | Performance attribute for dialog queue length (transaction-specific) |
| 269 | Performance attribute for dialog load time (transaction-specific) |
| 270 | Performance attribute for database query time (transaction-specific) |
| 271 | Reference to a monitoring object |
| 272 | Monitoring object for self-monitoring of transaction-specific monitoring |
| 273 | Perf. attribute for no. of references in transaction-specific monitoring |
| 274 | CCMS self-monitoring: Space problems in shared memory monitoring segment |
| 275 | Cannot create MTE [&1] (MTE class [&2]), context [&3]: [&4] |
| 276 | Cannot create monitoring context &1 due to lack of space [class &2] |
| 277 | Operating system data for a dedicated database host: LAN system |
| 278 | You are not authorized to run this report |
| 279 | Method & has exceeded the maximum runtime |
| 280 | CCMS self-monitoring: Frequency of active alerts in shared memory segment |
| 281 | Disk - Summary MTE for local application server |
| 282 | Disk - Summary MTE for remote application server |
| 283 | Monitoring object: Disk |
| 284 | Monitoring attribute: Disk utilization |
| 285 | Performance attribute: Disk response time (ms) |
| 286 | Performance attribute: Disk KB transferred per second |
| 287 | Error: Invalid disk name |
| 288 | Yes: & communication error(s) (tRFC calls with status CPICERR) |
| 289 | No: 0 communication errors (tRFC calls with status CPICERR) |
| 290 | Yes: & communication error(s) in qRFC queues |
| 291 | No: 0 communication errors in qRFC queues |
| 292 | CCMS standard transaction: normal response time |
| 293 | You are not authorized to run this report |
| 294 | Short dump: &1 (client &3) (user &4) (&2) |
| 295 | Error in HTML control; could not display URL |
| 296 | URL must begin with standard protocol. Enter = Continue |
| 297 | No parameters added to URL; standard URL is used |
| 298 | & - & |
| 299 | Status: Operation modes and instances |
| 300 | ******** Message IDs 300-349 for performance database ********* |
| 301 | Error getting monitoring contexts from the application server |
| 302 | Error reading MTE information from the monitoring segment |
| 303 | Error reading detailed MTE performance data from the monitoring segment |
| 304 | TID of MTE &1 has become invalid; TID has been assigned to the new MTE &2 |
| 305 | Invalid TID of MTE &1 renewed |
| 306 | Job SAP_CCMS_PERFDB_COLL was sucessfully saved |
| 307 | Job SAP_CCMS_PERFDB_REORG was sucessfully saved |
| 308 | Enter the job execution date |
| 309 | Enter a valid date |
| 310 | >> Background request started on application server &1 |
| 311 | Error getting list of active application servers from monitor segment |
| 312 | Error communicating with application server &1 |
| 313 | Error collecting data from application server &1 |
| 314 | Error scheduling job; job not scheduled |
| 315 | Method starter cannot determine own RFC destination |
| 316 | User & is not authorized to start methods |
| 317 | A schema for this ID already exists; choose another ID |
| 318 | No schema exists for this schema ID |
| 319 | Schema sucessfully deleted |
| 320 | Schema could not be deleted as schema ID &1 does not exist |
| 321 | Performance database reorganized |
| 322 | Cannot determine data for method & |
| 323 | Method &1 is not released as &2 |
| 324 | Unable to delete schema; check MTECLASS and SYSTEMID |
| 325 | Unable to save schema due to error |
| 326 | Lock management error; monitor conversion not possible |
| 327 | Subtree: Monitoring-relevant data for operating system |
| 328 | Subtree: Database client of SAP instance |
| 329 | Subtree: Services on SAP instance |
| 330 | Subtree: Basis services of SAP instance (traces, buffer, memory mgmt) |
| 331 | Monitoring object: Settings for development and system traces |
| 332 | Subtree: SAP instance memory management |
| 333 | Reorganization schema not found |
| 334 | Error when saving schema |
| 335 | Error creating MTE |
| 336 | Error when reading performance data |
| 337 | Dispatcher: Method &1 deactivated, not registered (MTE &3/&2 [&4]) |
| 338 | Dispatcher: Method &1 ended with RC = &2 (MTE: &3 [&4]) |
| 339 | Self-monitoring of CCMS monitoring architecture: SAPMSSYT runtime |
| 340 | CCMS self-monitoring: SAPMSSYT runtime &1 &3 exceeds &2 &3 |
| 341 | SAPMSSYT started |
| 342 | SAPMSSYT ended successfully |
| 343 | CCMS agent availability and status |
| 344 | Self-monitoring of CCMS agents |
| 345 | Self-Monitoring of CCMS Agents: &1 in CSMSEGM, missing CSM_BK |
| 346 | SAPMSSYT cannot get any data from CSM_BK through CCMS agents: RC = &1 |
| 347 | &1: CCMS agent is inactive |
| 348 | Subtree: Process monitoring |
| 349 | ****End of Message IDs for Performance DB ******* |
| 350 | Monitoring context for external components |
| 351 | Monitoring attribute that describes the status of the monitoring object |
| 352 | Monitoring attribute: "Heartbeat" of the monitoring object |
| 353 | Monitoring attribute: Availability history of the monitoring object |
| 354 | Monitoring object is active |
| 355 | Monitoring object is inactive |
| 356 | Monitoring object |
| 357 | Availability and status of systems and instances |
| 358 | Availability and status of an instance |
| 359 | Availability: Replication status of component |
| 360 | Availability of a system or instance as a percentage |
| 361 | 15-minute average for system/instance only available for &1 &3 |
| 362 | Availability: Active messages of the component |
| 363 | &1&2&3&4 |
| 364 | &1: Instance is new |
| 365 | &1: Instance inactive |
| 366 | &1: Instance active |
| 367 | Existing instances correspond to checked entries |
| 368 | There are new instances, or some are missing |
| 369 | No instances are marked for check |
| 370 | Choose an icon of a system or instance |
| 371 | Unable to convert monitor set &1 (database format &2) |
| 372 | GUID generation failed - Conversion terminated |
| 373 | Error saving monitor set &1 (owner: &2, database format 3) |
| 374 | Cannot convert monitor (&1, &2, database format 2) |
| 375 | qRFC Out queue status |
| 376 | qRFC in queues |
| 377 | Transactional RFC |
| 378 | Availability: percentage availability of component |
| 379 | 15-minute average for component only available for &1 &3 |
| 380 | Shift aggregate schema &1 saved |
| 381 | Shift aggregate schema &1 deleted |
| 382 | &1 shift aggregate schema does not exist |
| 383 | Heartbeat: Time passed since last signal from component |
| 384 | Heartbeat: Inactive since &1 &3 (threshold: &2 &3) |
| 385 | Active since &3: Last test: &4 |
| 386 | Inactive since &3. Last test: &4 |
| 387 | Starting ... |
| 388 | Stopping ... |
| 389 | Only values between 0 and 1 are permitted |
| 390 | Canceled |
| 391 | Cannot determine status |
| 392 | Pausing ... |
| 393 | Auto-reaction &1 started.Sending office mail from &2 to &3 (addr. typ.&4) |
| 394 | CCMS self-monitoring: &1 contexts from &2 systems invalidated in cache |
| 395 | System configuration |
| 396 | Client data in alert monitor |
| 397 | Shift aggregate schema has not been defined |
| 398 | Problem deleting schema &1 |
| 399 | No entries found for system &1 |
| 400 | Error getting data from &1 |
| 401 | ITS monitoring: Performance attribute |
| 402 | ITS monitoring: Message log attribute |
| 403 | Method &1 terminated by user |
| 404 | No authorization to execute method &1 |
| 405 | CCMS self-monitoring: &1 alerts in cache invalidated |
| 406 | CCMS self-monitoring: &1 TIDs from &2 requests in cache invalidated |
| 407 | CCMS monitoring of files: Monitoring context |
| 408 | CCMS monitoring of files: Monitoring object for a file |
| 409 | CCMS monitoring of files: Full path of file |
| 410 | CCMS monitoring of files: Number of new lines |
| 411 | CCMS monitoring of files: Entries according to template |
| 412 | Process &1 (&2): User time: &3 System time: &4 |
| 413 | Obsolete Alerts: Migration required |
| 414 | Obsolete Alert: Text &1 Subtype &2 Value &3 |
| 415 | Subtree: Update Service |
| 416 | Monitoring object SAP update task V1 |
| 417 | SAP update task V1: Average response time per dialog step |
| 418 | SAP update task V1: Average wait time in dispatcher queue |
| 419 | SAP Update Task V1: Percentage load for update task work process |
| 420 | Monitoring object SAP update task V2 |
| 421 | SAP update task V2: Average response time per dialog step |
| 422 | SAP update task V2: Average wait time in dispatcher queue |
| 423 | SAP Update Task V2: Percentage load for update2 task work process |
| 424 | Monitoring object SAP update general |
| 425 | Update requests with errors |
| 426 | Maximum Load of roll area [KB] since system start |
| 427 | Currently used roll area [KB] |
| 428 | Currently used roll area [%] |
| 429 | Maxmimum paging area load [KB] since system start |
| 430 | Currently used paging area [KB] |
| 431 | Currently used paging area [%] |
| 432 | Monitoring object roll and paging area |
| 433 | Please choose the application servers and press 'SAVE' again. |
| 434 | Enter SchemaID to be created before pressing create button. |
| 435 | Start method &1 for MTE &2 [&3]... |
| 436 | System could not determine MTE data for TID &1&1 |
| 437 | >> Tool Dispatcher &1 for Segment &2 ended. &3 methods in &4 seconds |
| 438 | System unable to delete SAP default schemas |
| 439 | Schemata cannot begin with "SAP" |
| 440 | Warning: &1 unprocessed requests deleted from CSMCENTOOL after 24 h |
| 441 | The description should be unique |
| 442 | >> Start the central system tool dispatching on server &1 ... |
| 443 | >> End central system tool dispatching on server &1 |
| 444 | Current size of paging area [KB] |
| 445 | Current size of roll area [KB] |
| 446 | Central system tool dispatching can only be started in the background |
| 447 | The OS collector (saposcol) version &1 is running |
| 448 | Method &1 reporting errors: &2&3&4 |
| 449 | Dispatcher: Method &1 deactivated due to return code &2, MTE: &3 [&4] |
| 450 | &1 Alerts automatically completed, as they are older than &2 days old |
| 451 | &1 Alerts automatically completed, as free space fell below &2 % |
| 452 | &1 is executed as startup method |
| 453 | CCMSPING communication error: System &1 host &2 unknown |
| 454 | CCMSPING communication error: System &1 service &2 unknown |
| 455 | CCMSPING communication error: System &1 message server not accessible |
| 456 | CCMSPING not accessible &1 |
| 457 | CCMSPING system error &1 |
| 458 | CCMSPING: internal error; check agent installation |
| 459 | &1 ended |
| 460 | Average time for roundtips during a dialog step |
| 461 | &1 &3 > &2 &3 time for roundtrips above threshold value (&4 dialog steps) |
| 462 | Monitoring pause successfully saved |
| 463 | Error while saving the settings |
| 464 | Short dump [&1] no longer available |
| 465 | No short dump specified |
| 466 | CCMSPING timeout for system &1: ping is repeated once |
| 467 | CCMSPING NIECONN for system &1; system not accessible |
| 468 | CCMSPING error or error in CCMSPING configuration |
| 469 | System not available; instance data will not be updated |
| 470 | RFC_PING: No instance entered in config table for system &1 |
| 471 | RFC_PING: No favorite instance for system &1 group &2 |
| 472 | RFC_PING: Check is being performed for system &1 |
| 473 | RFC_PING: Check failed; internal error RC = &1 |
| 474 | Availability check: RFC_PING to logon groups or instances |
| 475 | Number of calls with status SYSLOAD |
| 476 | Incoming calls (ARFCRSTATE table) |
| 477 | Inbound scheduler error: Client &1 name &2 status &3 |
| 478 | No QIN scheduler error |
| 479 | Minimum number of calls in the ARFCRSTATE table |
| 480 | Outbound Queue: Status |
| 481 | Inbound Queue: Status |
| 482 | No alerts exist |
| 483 | QIN scheduler error: Client &1 Q-name &2 status &3 |
| 484 | Message: &1; scheduler name follows |
| 485 | No QOUT scheduler error |
| 486 | QOUT scheduler error: Client &1 destination &2 status &3 |
| 487 | QOUT Scheduler |
| 488 | QIN Scheduler |
| 489 | Error messages: outbound queues |
| 490 | Outbound queues that have not been processed |
| 491 | Client &1 queue &2 has not been processed for &3 days |
| 492 | Select a queue group |
| 493 | Select a queue assignment entry |
| 494 | qRFC function module not available actively in system: &1 |
| 495 | Monitoring pause(s) successfully deleted |
| 496 | qRFC: unregistered inbound queue |
| 497 | Unregistered inbound queue: Client &1 queue &2 |
| 498 | CCMS monitoring of files: File size |
| 499 | System is inactive or could not access CCMSPING |
| 500 | SAP system release |
| 501 | Code page |
| 502 | SAP system components |
| 503 | No detailed description available |
| 504 | No detailed description available |
| 505 | No detailed description available |
| 506 | No detailed description available |
| 507 | No detailed description available |
| 508 | No detailed description available |
| 509 | No detailed description available |
| 510 | No detailed description available |
| 511 | No detailed description available |
| 512 | No detailed description available |
| 513 | No detailed description available |
| 514 | No detailed description available |
| 515 | No detailed description available |
| 516 | No detailed description available |
| 517 | No detailed description available |
| 518 | No detailed description available |
| 519 | No detailed description available |
| 520 | No detailed description available |
| 521 | No detailed description available |
| 522 | No detailed description available |
| 523 | No detailed description available |
| 524 | No detailed description available |
| 525 | No detailed description available |
| 526 | No detailed description available |
| 527 | No detailed description available |
| 528 | No detailed description available |
| 529 | Status: Operation modes and instances |
| 530 | Status: Operation modes and instances |
| 531 | Status: Operation modes and instances |
| 532 | Status: Operation modes and instances |
| 533 | Status: Operation modes and instances |
| 534 | Status: Operation modes and instances |
| 535 | Status: Operation modes and instances |
| 536 | No detailed description available |
| 537 | No detailed description available |
| 538 | No detailed description available |
| 539 | No detailed description available |
| 540 | No detailed description available |
| 541 | Monitoring object: ABAP SQL errors |
| 542 | Attribute: ABAP SQL errors |
| 543 | Monitoring object: ABAP runtime environment |
| 544 | Short dumps in ABAP |
| 545 | Monitoring object: Syslog of SAP application server |
| 546 | Frequency of system log messages in SAP application server |
| 547 | Subtree with instance-specific Basis objects of SAP application server |
| 548 | Status: &1 delay: &2 timestamp: &3 timezone: &4 |
| 549 | Event/Status/Count: &1 since: &2 timezone: &3 message: &4 |
| 550 | Test event/status/count: &1 since: &2 timezone: &3 message: &4 |
| 551 | SAP buffer: ABAP program (Program) |
| 552 | SAP buffer: Generic key (GenericKey) |
| 553 | SAP Buffer: Single record (SingleRecord) |
| 554 | SAP buffer: Screen (Screen) |
| 555 | SAP buffer: Menu (CUA) |
| 556 | SAP buffer: table definition (TableDefintion) |
| 557 | SAP Buffer: Field description (FieldDescription) |
| 558 | SAP buffer: initial record layout (InitialRecords) |
| 559 | SAP buffer: table short description (ShortNameTAB) |
| 560 | &1 &3 > &2 &3 (15 Min.) SAP buffer directory usage exceeds threshold |
| 561 | &1 &3 > &2 &3 (15 Min.) SAP buffer:buffer storage usage exceeds threshold |
| 562 | &1 &3 < &2 &3 (15 Min.) SAP buffer hitrate below threshold |
| 563 | &1 &3 > &2 &3 (15 Min.) SAP buffer swap exceeds threshold |
| 564 | Data Supplier |
| 565 | &1&2&3&4 |
| 566 | Monitoring jobs |
| 567 | &1 started at &2 |
| 568 | &1 started at &2, ended at &3 |
| 569 | Test status: &1 delay: &2 timestamp: &3 timezone: &4 |
| 570 | Delay: &1 |
| 571 | &1 &3 > &2 &3 (15 Min.) Adjusted response time exceeds threshold |
| 572 | &1 &3 > &2 &3 (15 Min.)Transact-spec. dialog resp. time exceeds threshold |
| 573 | &1 &3 > &2 &3 (15 Min.) Trans. spec. dialog queue lgth exceeds threshold |
| 574 | &1 &3 > &2 &3 (15 Min.) trans. spec. dialog load time exceeds threshold |
| 575 | &1 &3 > &2 &3 (15 Min.) trans. spec. DB query time exceeds threshold |
| 576 | &1 &3 > &2 &3 (15 Min.)trans. spec. frontend resp. time exceeds threshold |
| 577 | &1 > &2 Number of users logged on to application server exceeds threshold |
| 578 | RFC_PING to instance &1 was not successfully performed |
| 579 | RFC_PING to instance &1 was successfully performed |
| 580 | Cannot find system &1 in table CSMSYS; check table |
| 581 | Availability of the J2EE Server |
| 582 | GRMG Customizing successfully uploaded |
| 583 | Customizing error: &1&2 |
| 584 | Log file monitoring: Alert triggered |
| 585 | GRMG scenarios deleted successfully: &1 &2 |
| 586 | &1 ended with errors |
| 587 | No entries selected - select entries completely |
| 588 | Status of execution of GRMG scenarios: Successful or failed |
| 589 | >> Dispatching for auto-reaction tools for app. server segment started |
| 590 | >> Dispatching for auto-react. tools for seg. & started using CCMS agent |
| 591 | Component &1 initialized |
| 592 | Component &1 was started |
| 593 | Could not start component &1; exception: &2 |
| 594 | Could not start component &1; element: &2, exception: &3 |
| 595 | Could not start component &1 |
| 596 | Could not initialize component &1 |
| 597 | Component &1 was not initialized; exception: &2 |
| 598 | Component &1 was not initialized; element: &2, exception; &3 |
| 599 | Component &1, block: &2, value: &3 |
| 600 | &1 &3 > &2 &3 (15 Min.) Commit Charge load exceeds threshold |
| 601 | &1 &3 > &2 &3 (15 Min.) Collisions in LAN exceeds threshold |
| 602 | &1 &3 > &2 &3 (15 Min.) No. of incoming packets in LAN exceeds threshold |
| 603 | &1 &3 > &2 &3 (15 Min.) No. of outbound packets in LAN exceeds threshold |
| 604 | &1 &3 > &2 &3 (15 Min.) No. of pages paged in exceeds threshold |
| 605 | &1 &3 > &2 &3 (15 Min.) Number of paged out pages exceeds threshold |
| 606 | &1 &3 > &2 &3 (15 Min.) Swap area utlization exceeds threshold |
| 607 | UNICODE system: Cannot create local operating system tree |
| 608 | UNICODE system: Install SAPCCMSR agent |
| 609 | CCMSPING is reporting itself as active; &1 method is not executed |
| 610 | Monitoring attribute: idle time for all CPUs in system |
| 611 | Could not delete GRMG scenario: &1 &2 |
| 612 | GRMG scenarios started |
| 613 | GRMG scenario entry not found in table GRMG_SCENARIOS |
| 614 | A GRMG scenario must have at least one property |
| 615 | The selected properties have been deleted |
| 616 | Could not save changes: &1 &2 &3 &4 |
| 617 | Saposcol: data collection not up to date |
| 618 | File systems excluded from monitoring |
| 619 | Process monitoring was checked |
| 620 | Monitoring object: "Monitored Processes" |
| 621 | Monitoring object: "Monitored Processes", configuration |
| 622 | Monitoring object: Pattern for process names |
| 623 | Monitoring attribute: Number of running processes for a process name |
| 624 | Monitoring attribute: Total CPU usage for a process name |
| 625 | Monitoring attribute: Total memory usage for a process name |
| 626 | Percentage of currently used background processing capacity |
| 627 | Subtree with attributes for availability of monitored systems |
| 628 | Version of CCMS System Component Repository |
| 629 | ABAP version number of program SAPMSSY8 |
| 630 | Valid SAP Basis/Web AS release of application server |
| 631 | Subtree for transaction and client-specific monitoring |
| 632 | Name of monitored file system |
| 633 | Runtime of job for collection of data for PerfDB database |
| 634 | Subtree with attributes for PerfDB performance database |
| 635 | Name of monitored application server |
| 636 | Terminated jobs on an application server |
| 637 | Number of released jobs that are waiting to be executed |
| 638 | Subtree with cross-system attributes for background processing |
| 639 | Cross-system number of background work processes for high priority jobs |
| 640 | Subtree with cross-system attributes for background processing |
| 641 | Cross-system number of free background work processes |
| 642 | Number of jobs that are waiting for execution (cross-system average) |
| 643 | Number of background work processes in entire system |
| 644 | Average time for processing logical database requests |
| 645 | Response time of long-running dialog work processes (last value) |
| 646 | Monitored transactions/clients |
| 647 | Subtree with the most important memory sizes from Memory Management |
| 648 | Spool number that is assigned to each output request |
| 649 | Messages for an output server |
| 650 | Subtree with cross-system attributes for spool system |
| 651 | Wait time in spool service in seconds |
| 652 | Subtree for CCMS self-monitoring |
| 653 | Subtree with attributes for program SAPMSSY8 |
| 654 | Release status of SAP kernel |
| 655 | Exception occurred while monitoring the AI infrastructure |
| 656 | Update status |
| 657 | Update records older than one day |
| 658 | &1 canceled update records |
| 659 | Update is active |
| 660 | Warning: update is inactive. |
| 661 | Update information |
| 662 | Average response time of dialog service - determined using CCMSPING |
| 663 | Standardized response time of dialog service - determined using CCMSPING |
| 664 | Number of users logged on - determined using CCMSPING |
| 665 | Report &1, &4 &2, &3 |
| 666 | Function &1, &4 &2, &3 |
| 667 | Transaction &1, &4 &2, &3 |
| 668 | URL &1&4, Method &2, &3 |
| 669 | Update is active |
| 670 | Not available; last test : &4 |
| 671 | Unknown host; last test : &4 |
| 672 | Unknown service; last test : &4 |
| 673 | Not accessible; last test : &4 |
| 674 | GRMG scenario &1 downloaded; file: &2, directory: &3 |
| 675 | Download of scenario Customizing failed; reason: &1 |
| 676 | Scenario: &1; status message: &2&3&4 |
| 677 | No system groups found in CCMS System Component Repository |
| 678 | Group &1 does not contain any systems |
| 679 | You are not authorized for the CCMS System Component Repository |
| 680 | Internal error in CCMS System Component Repository - check SCR |
| 681 | Object for GUID &1 not found in System Component Repository |
| 682 | Object for group &1 not found in System Component Repository |
| 683 | No systems determined for system group &1 |
| 684 | Error when accessing table ALPFPARAM |
| 685 | Extended logging of data collection is now activated |
| 686 | Extended logging of data collection is now deactivated |
| 687 | Check is performed in background |
| 688 | Initialization is performed in background |
| 689 | Cannot start data collection check |
| 690 | Cannot delete old job &1; delete manually |
| 691 | System &1 not found under the monitored systems |
| 692 | No monitored systems found in group &1 |
| 693 | Internal error in monitored system control; notfiy SAP |
| 694 | No unmonitored systems found in group &1 |
| 695 | Processing in background started |
| 696 | Reference system group successfully deleted |
| 697 | CCMS self-monitoring: Number of alerts in table ALALRTGUID |
| 698 | Number of alerts in ALALRTGUID &1 exceeds threshold value &2 |
| 699 | You can only select from the "Reference System Groups" |
| 700 | CRM Internet Sales logon not possible |
| 701 | Scenario version must be &1 |
| 702 | JCO could not create client for " &1 " |
| 703 | JCO could not connect with " &1 " |
| 704 | JCO could not create Repository for " &1 " |
| 705 | Shop list has been retrieved |
| 706 | Specify scenario name: B2B or B2C |
| 707 | Response is " &1 " |
| 708 | Response from login check is " &1 " |
| 709 | Information about Shop has been retrieved |
| 710 | No information available about the shop |
| 711 | Java HTTP exception |
| 712 | No ORO parser |
| 713 | HTTP/1.1 > 400. Return code is " &1 " |
| 714 | HTTP/1.1 200 OK, <next_url> is nicht not specified |
| 715 | HTTP/1.1 200 OK Return code is " &1 " |
| 716 | IPC heartbreak exception - "&1" |
| 717 | IPC heartbreak server code return "&1" |
| 718 | Heartbeat alert: Last measurement value more than &1 seconds old |
| 719 | CCMSPING RFC destination &1 does not exist |
| 720 | No connection exists to the J2EE Server |
| 721 | Connection exists to J2EE |
| 722 | Select only one system group for the consistency check |
| 723 | No RFC destination found for CCMSPING |
| 724 | CCMSPING: For system &1 M-Server type &2 return message &3 |
| 725 | Load balancing; quality of application server |
| 726 | Load balancing; messages about preferred logon instances |
| 727 | To protect passwords, property type PW cannot be changed |
| 728 | Scenario without protected password downloaded - please maintain |
| 729 | Number of CPUs |
| 730 | Percentage of dialog work processes in PRIV mode |
| 731 | Number of errors in dialog work processes |
| 732 | Number of errors in dialog work processes per minute |
| 733 | Number of completed dialog work processes |
| 734 | Number of errors in background work processes |
| 735 | Number of errors in background work processes per minute |
| 736 | Number of completed background work processes |
| 737 | Number of errors in spool work processes |
| 738 | Number of errors in spool work processes per minute |
| 739 | Number of completed spool work processes |
| 740 | Number of errors in update 1 work processes |
| 741 | Number of errors in update 1 work processes per minute |
| 742 | Number of completed update 1 work processes |
| 743 | Number of errors in update 2 work processes |
| 744 | Number of errors in update 2 work processes per minute |
| 745 | Number of completed update 2 work processes |
| 746 | Number of errors in enqueue work processes |
| 747 | Number of errors in enqueue work processes per minute |
| 748 | Number of completed enqueue work processes |
| 749 | Enqueue statistics - for more information, see long text |
| 750 | Data collection successfully performed for log file monitoring |
| 751 | File exists |
| 752 | File does not exist |
| 753 | No CCMSPING agent groups exist |
| 754 | CCMSPING group entries successfully deleted |
| 755 | Group &1 deleted, but assignments to systems still exist |
| 756 | CCMSPING agent push mode is not activated, method on hold |
| 757 | No CCMSPING agents logged onto system |
| 758 | CCMSPING RFC destination &1 of group &2 does not exist |
| 759 | &4: For system &1, message server type &2, return message &3 |
| 760 | "Named Users" analysis |
| 761 | Consistency check: System Repository (SCR / System Landscape Dir. (SLD) |
| 762 | Performance attribute: DIALOG response time |
| 763 | &1 &3 > &2 &3 DIALOG response time exceeds threshold (&4 dialog steps) |
| 764 | Performance attribute: HTTP response time |
| 765 | &1 &3 > &2 &3 HTTP response time exceeds threshold (&4 dialog steps) |
| 766 | Performance attribute: DIALOG and RFC response time |
| 767 | &1 &3 > &2 &3 DIALOG+RFC resp. time exceeds threshold (&4 dialog steps) |
| 768 | Validity of SIDadm credentials used by intregated CCMS Agents |
| 770 | ITS subtree |
| 771 | Memory used for BusinessHTML templates |
| 772 | Memory used by ITS-Sessions |
| 773 | Number of ITS-Sessions |
| 774 | Share of kernel memory used by all kernel components |
| 775 | Share of the ITS-Quota used by the ITS |
| 777 | Runtime of Data Collector of new OS data |
| 780 | Scheduling of external commands using CCMS agents |
| 781 | Logical name of a command stored in agent |
| 782 | Scheduling a command with specific parameters in CCMS agents |
| 783 | First execution of command at &1. Execution interval: &2 seconds |
| 784 | Command started [rc = &1]; next start after &2 seconds |
| 785 | &1: Asynchronous start of "TOOLSET_STARTER" not possible (method &2) |
| 787 | &1 &3 > &2 &3 (15 min.) transact.-spec. roll time exceeds threshold value |
| 788 | Performance attribute: roll time (transaction-specific) |
| 790 | ABAP error: [&1] in report[&4] in SNAP:[&2] (user &3) |
| 791 | ABAP SQL error: [&1] in report[&4] in SNAP:[&2] (user &3) |
| 792 | Short dump: [&1] in report[&4] in SNAP:[&2] (user &3) |
| 793 | Number of user sessions by type |
| 800 | Event Log Monitoring |
| 801 | Subtree for a monitored event log |
| 802 | Event log entries |
| 820 | Operation system monitoring subtree |
| 821 | Performance attribute CPU: average utilization (user) |
| 822 | Performance attribute CPU: average utilization (system) |
| 823 | Performance attribute CPU: average utilization (idle) |
| 824 | Performance attribute CPU: interrupts per second |
| 825 | Performance attribute CPU: system calls |
| 826 | Performance attribute CPU: context switches |
| 827 | Performance attribute LAN: errors per second for inbound packets |
| 828 | Performance attribute LAN: errors per second for outbound packets |
| 829 | Performance attribute disk: wait time |
| 830 | Performance attribute disk: service time |
| 831 | Performance attribute disk: queue length |
| 832 | Paging: Page In (Kilobytes per second) |
| 833 | Paging: Page Out (Kilobytes per second) |
| 834 | Memory: free memory space |
| 835 | Memory: configured memory |
| 836 | Central User Administration |
| 850 | **** 850-899 Belongs to Virtualization |
| 851 | System Model Type |
| 852 | Processor Type |
| 853 | Processor Frequency |
| 854 | Partition Name |
| 855 | Partition ID |
| 856 | Partition Type |
| 857 | SMT Mode (On, Off) |
| 858 | Number of SMT Threads |
| 859 | Capped (On, Off) |
| 860 | Number of Virtual CPUs |
| 861 | Physical CPU Entitlement |
| 862 | Percent of Physical CPU Entitlement Consumed |
| 863 | Number of CPUs in Pool |
| 864 | Physical CPU Consumed |
| 865 | Physical CPU Idle |
| 866 | Available Physical CPUs |
| 867 | Percent of Available Physical CPUs Consumed |
| 868 | Pool Utility Authorization |
| 869 | SAP buffer: Number Range Buffer |
| 870 | Number Range Buffer: maximum number of entries |
| 871 | Number Range Buffer: number of free entries |
| 875 | SAP buffer: Calendar |
| 876 | SAP buffer: Export/import |
| 877 | SAP buffer: OTR (Online Text Repository) |
| 878 | SAP buffer: Export/import to Shared Memory |
| 879 | SAP buffer: Table Buffer |
| 880 | Distribution of user &1, section &2: No acknowledgement since &3 |
| 882 | Profile parameter &1 is set to value &2. |
| 883 | Monitoring object Extended global memory |
| 884 | Current size of Extended global memory [KB] |
| 885 | Current use of Extended global memory [%] |
| 886 | Current use of Extended global memory [KB] |
| 887 | Maxmimum use of Extended global memory [KB] since system start |