Id | Title |
---|---|
RT248 | Monitoring object: LAN |
RT249 | LAN -- Packets in: Packets per second |
RT250 | LAN -- Packets out: Packets per second |
RT251 | LAN -- Number of collisions |
RT252 | LAN system of the application server |
RT253 | Background method dispatching not possible - no jobs released |
RT254 | Background method dispatching not possible - job does not exist |
RT255 | Cannot determine information about job for background tool dispatching |
RT256 | SAP dialog service monitoring object: Front end wait time |
RT257 | &1 &3 > &2 &3 Frontend response time exceeds threshold (&4 dialog steps) |
RT258 | Average time use in network (excluding roundtrips) |
RT259 | &1 &3 > &2 &3 Network runtime exceeds threshold (&4 dialog steps) |
RT260 | Cannot read rule description & from database |
RT261 | Performance attribute: Frontend response time (transaction-specific) |
RT262 | Monitoring context for transaction-specific monitoring |
RT263 | Monitoring object "client" for transaction-specific monitoring |
RT264 | Monitoring object "transaction" for transaction-specific monitoring |
RT265 | Monitoring obj. "ClientTransaction" for transaction-specific monitoring |
RT266 | Referenced monitoring object for transaction-specific monitoring |
RT267 | Performance attribute for dialog response time (transaction-specific) |
RT268 | Performance attribute for dialog queue length (transaction-specific) |
RT269 | Performance attribute for dialog load time (transaction-specific) |
RT270 | Performance attribute for database query time (transaction-specific) |
RT271 | Reference to a monitoring object |
RT272 | Monitoring object for self-monitoring of transaction-specific monitoring |
RT273 | Perf. attribute for no. of references in transaction-specific monitoring |
RT274 | CCMS self-monitoring: Space problems in shared memory monitoring segment |
RT275 | Cannot create MTE [&1] (MTE class [&2]), context [&3]: [&4] |
RT276 | Cannot create monitoring context &1 due to lack of space [class &2] |
RT277 | Operating system data for a dedicated database host: LAN system |
RT278 | You are not authorized to run this report |
RT279 | Method & has exceeded the maximum runtime |
RT280 | CCMS self-monitoring: Frequency of active alerts in shared memory segment |
RT281 | Disk - Summary MTE for local application server |
RT282 | Disk - Summary MTE for remote application server |
RT283 | Monitoring object: Disk |
RT284 | Monitoring attribute: Disk utilization |
RT285 | Performance attribute: Disk response time (ms) |
RT286 | Performance attribute: Disk KB transferred per second |
RT287 | Error: Invalid disk name |
RT288 | Yes: & communication error(s) (tRFC calls with status CPICERR) |
RT289 | No: 0 communication errors (tRFC calls with status CPICERR) |
RT290 | Yes: & communication error(s) in qRFC queues |
RT291 | No: 0 communication errors in qRFC queues |
RT292 | CCMS standard transaction: normal response time |
RT293 | You are not authorized to run this report |
RT294 | Short dump: &1 (client &3) (user &4) (&2) |
RT295 | Error in HTML control; could not display URL |
RT296 | URL must begin with standard protocol. Enter = Continue |
RT297 | No parameters added to URL; standard URL is used |
RT298 | & - & |
RT299 | Status: Operation modes and instances |
RT300 | ******** Message IDs 300-349 for performance database ********* |
RT301 | Error getting monitoring contexts from the application server |
RT302 | Error reading MTE information from the monitoring segment |
RT303 | Error reading detailed MTE performance data from the monitoring segment |
RT304 | TID of MTE &1 has become invalid; TID has been assigned to the new MTE &2 |
RT305 | Invalid TID of MTE &1 renewed |
RT306 | Job SAP_CCMS_PERFDB_COLL was sucessfully saved |
RT307 | Job SAP_CCMS_PERFDB_REORG was sucessfully saved |
RT308 | Enter the job execution date |
RT309 | Enter a valid date |
RT310 | >> Background request started on application server &1 |
RT311 | Error getting list of active application servers from monitor segment |
RT312 | Error communicating with application server &1 |
RT313 | Error collecting data from application server &1 |
RT314 | Error scheduling job; job not scheduled |
RT315 | Method starter cannot determine own RFC destination |
RT316 | User & is not authorized to start methods |
RT317 | A schema for this ID already exists; choose another ID |
RT318 | No schema exists for this schema ID |
RT319 | Schema sucessfully deleted |
RT320 | Schema could not be deleted as schema ID &1 does not exist |
RT321 | Performance database reorganized |
RT322 | Cannot determine data for method & |
RT323 | Method &1 is not released as &2 |
RT324 | Unable to delete schema; check MTECLASS and SYSTEMID |
RT325 | Unable to save schema due to error |
RT326 | Lock management error; monitor conversion not possible |
RT327 | Subtree: Monitoring-relevant data for operating system |
RT328 | Subtree: Database client of SAP instance |
RT329 | Subtree: Services on SAP instance |
RT330 | Subtree: Basis services of SAP instance (traces, buffer, memory mgmt) |
RT331 | Monitoring object: Settings for development and system traces |
RT332 | Subtree: SAP instance memory management |
RT333 | Reorganization schema not found |
RT334 | Error when saving schema |
RT335 | Error creating MTE |
RT336 | Error when reading performance data |
RT337 | Dispatcher: Method &1 deactivated, not registered (MTE &3/&2 [&4]) |
RT338 | Dispatcher: Method &1 ended with RC = &2 (MTE: &3 [&4]) |
RT339 | Self-monitoring of CCMS monitoring architecture: SAPMSSYT runtime |
RT340 | CCMS self-monitoring: SAPMSSYT runtime &1 &3 exceeds &2 &3 |
RT341 | SAPMSSYT started |
RT342 | SAPMSSYT ended successfully |
RT343 | CCMS agent availability and status |
RT344 | Self-monitoring of CCMS agents |
RT345 | Self-Monitoring of CCMS Agents: &1 in CSMSEGM, missing CSM_BK |
RT346 | SAPMSSYT cannot get any data from CSM_BK through CCMS agents: RC = &1 |
RT347 | &1: CCMS agent is inactive |