SDBALM - SAP DB und liveCache Alert Monitoring
The following messages are stored in message class SDBALM: SAP DB und liveCache Alert Monitoring.
It is part of development package SLVC in software component BC-DB-LVC. This development package consists of objects that can be grouped under "liveCache CCMS".
It is part of development package SLVC in software component BC-DB-LVC. This development package consists of objects that can be grouped under "liveCache CCMS".
Message Nr ▲ | Message Text |
---|---|
001 | &1 &2 &3 &4 |
002 | Could not determine value |
003 | Could not determine value, as current instance status: &1 |
004 | Analysis method can only be started in liveCache state ONLINE (&1) |
005 | Analysis method can only be started in SAP DB state ONLINE (&1) |
006 | No SQL connection possible despite ONLINE state (&1) |
007 | Analysis method not possible, as cannot determine liveCache state (&1) |
008 | Analysis method not possible, as cannot determine SAP DB state (&1) |
009 | Could not start analysis method (&1) |
011 | liveCache: Name of the database connection |
012 | SAP DB: Name of the database connection |
013 | liveCache: Database connection |
014 | SAP DB: Database connection |
015 | Data collectors and internal alert monitoring information |
016 | Database instance properties |
017 | Memory management |
018 | Performance |
019 | Backups and recoveries of database instance |
020 | State of the database objects |
021 | External analysis tools |
022 | Set of data collectors |
023 | Internal alert monitoring information |
024 | Database instance status |
025 | Installation information |
026 | Error Messages |
027 | Data Area |
028 | Log area |
029 | Main memory management |
030 | Information about cache accesses |
031 | User tasks |
032 | Monitoring performance-relevant settings and events |
033 | Optimizer statistics |
034 | Last backup |
035 | Last restore |
036 | Defective database indexes |
037 | Check the database structure |
038 | Database Analyzer |
039 | Information about ABAP Dictionary |
040 | Status of Hot Standby Configuration |
044 | Automatic Overwriting of Log Area |
045 | Current status of the liveCache |
046 | Current status of the SAP DB |
047 | liveCache write-protected |
048 | Last stop of the liveCache instance |
049 | Time of the last restart |
050 | Time of the last checkpoint |
051 | Name of the liveCache instance |
052 | Name of the SAP DB instance |
053 | Name of the liveCache server |
054 | Name of the SAP DB server |
055 | Instance type |
056 | Kernel version of the liveCache instance |
057 | Kernel version of the SAP DB instance |
058 | Version of the DBM Server |
059 | Operating System |
060 | liveCache error messages |
061 | Error messages of the SAP DB database |
062 | Error messages during liveCache operation |
063 | Free space in data area in % |
064 | Free memory in log area in % |
065 | Log write |
066 | Status of automatic log backup |
067 | Last known log page number |
068 | Last known log sequence number |
069 | Usage of the data cache in % |
070 | Usage of the data cache with OMS data in % |
071 | Usage of the data cache with SQL data in % |
072 | Usage of the data cache with history/undo data in % |
073 | Usage of the data cache with OMS history data in % |
074 | Usage of the data cache with OMS rollback data in % |
075 | Number of "Out of Memory" exceptions since the last message |
076 | Number of OMS terminations since the last measurement |
077 | Usage of the heap in % |
078 | Usage of the heap in KB |
079 | Maximum usage of the heap in KB |
080 | Size of the system heap in KB |
081 | Setting of the parameter OMS_HEAP_LIMIT |
082 | Hit rate of the data cache in % |
083 | Hit rate for the OMS data in the data cache in % |
084 | Hit rate for the SQL data in the data cache in % |
085 | Hit rate for the history/undo data in the data cache (in %) |
086 | Hit rate for the OMS history data in the data cache in % |
087 | Hit rate for the OMS rollback data in the data cache in % |
088 | Hit rate of the catalog cache in % |
089 | Hit rate of the rollback cache in % |
090 | Hit rate of the converter cache in % |
091 | Number of user tasks in status "Connect Wait" |
092 | Setting of the OMS memory analysis |
093 | Age of the oldest OMS version in hours |
094 | Database trace setting |
095 | Number of log queue overflows since the last measurement |
096 | Proportion of log queue overflows to log queue inserts (in %) |
097 | Last update of optimizer statistics |
098 | Type of last update of optimizer statistics |
099 | Time of the last successful complete data backup |
100 | Return code of the last full data backup |
101 | Time of the last restore |
102 | Number of defective database indexes |
103 | Time of last successful database structure check |
104 | Return code of last database structure check |
105 | Type of last database structure check |
106 | Status of the Database Analyzer |
107 | Last logged Database Analyzer warning with high priority |
108 | Database Analyzer log directory |
109 | Database Analyzer configuration file |
110 | Collection interval of the Database Analyzer in seconds |
111 | Start time of the Database Analyzer |
122 | Version of the kernel in internel notation (xxx.yyy.zzz.uuu) |
123 | Instance type |
124 | Cache accesses (total) - for calculation of the access hitrates |
125 | Cache accesses (successful) - for calculation of the access hitrates |
126 | Size of the data area (MB) |
127 | Data area > &2&3 |
128 | Utilized data area (%) |
129 | Data area used heavily (&1&3 > &2&3) |
130 | Free data area (MB) |
131 | Size of the log area (MB) |
132 | Log area > &2&3 |
133 | Utilized log area (%) |
134 | Log area used heavily (&1&3 > &2&3) |
135 | Free log area (MB) |
141 | Internal version ID of the liveCache/SAP DB alert monitoring |
142 | Time of the last restart (time stamp) |
143 | Time of the last check of the shutdown cause |
144 | Number of log queue overflows (total) |
145 | Number of log queue inserts (total) |
146 | Number of "Out of Memory" exceptions (total) |
147 | Number of OMS terminations (total) |
148 | Server on which the data collection was started |
149 | Status of the connection to the database instance |
150 | Connection using DBMRFC |
151 | Connection using Native SQL |
152 | Connection using DBMRFC or Native SQL |
153 | Data collector status |
154 | Locked data collectors |
155 | State of the data collection (active or inactive) |
156 | Data collector A (highest runtime frequency) |
157 | Data collector B (high runtime frequency) |
158 | Data collector C (medium runtime frequency) |
159 | Data collector D (low runtime frequency) |
160 | Data collection through file access to: dban.prt |
161 | Data collection through file access to: knldiag.err |
162 | Data collection through file access to: lcinit.hist |
163 | Data collector (currently has no function) |
170 | Low free space in data area (&1&3 < &2&3) |
171 | Low free space in log area (&1&3 < &2&3) |
172 | High usage rate in the data cache (&1&3 > &2&3) |
173 | High proportion of OMS data in the data cache (&1&3 > &2&3) |
174 | High proportion of SQL data in the data cache (&1&3 > &2&3) |
175 | High proportion of history/undo data in the data cache (&1&3 > &2&3) |
176 | High proportion of OMS history data in the data cache (&1&3 > &2&3) |
177 | High proportion of OMS rollback data in the data cache (&1&3 > &2&3) |
178 | High number of "Out of Memory" exceptions were raised (&1 > &2) |
179 | High number of OMS terminations occurred (&1 > &2) |
180 | High usage rate in the heap (&1&3 > &2&3) |
181 | Heap size has exceeded threshold value (&1 > &2) |
182 | Low hit rate in the data cache (&1&3 < &2&3) |
183 | Low hit rate for OMS data in the data cache (&1&3 < &2&3) |
184 | Low hit rate for SQL data in the data cache (&1&3 < &2&3) |
185 | Low hit rate for history/undo data in the data cache (&1&3 < &2&3) |
186 | Low hit rate for OMS history data in the data cache (&1&3 < &2&3) |
187 | Low hit rate for OMS rollback data in the data cache (&1&3 < &2&3) |
188 | Low hit rate in the catalog cache (&1&3 < &2&3) |
189 | Low hit rate in the rollback cache (&1&3 < &2&3) |
190 | Low hit rate in the converter cache (&1&3 < &2&3) |
191 | Low volume of user tasks are in the state CONNECT WAIT (&1 < &2) |
192 | High number of log queue overflows (&1 > &2) |
193 | High proportion of overflows to log queue additions (&1% > &2%) |
194 | Optimizer statistics are too old (&1 days > &2 days) |
195 | Last data backup is too old (&1 days > &2 days) |
196 | Last data consistency check is too old (&1 days > &2 days) |
210 | liveCache application call possible |
211 | Cannot call liveCache applications |
212 | Cannot determine whether liveCache applications can be called |
213 | Successful |
214 | Cancel |
215 | Could not determine the cause of the last stop |
216 | Can only determine the cause of the last stop in ONLINE or OFFLINE states |
217 | Active |
218 | Inactive |
219 | Could not determine the status of the archive logging |
220 | Activated (Log fill level > 1.5 * Log segment size) |
221 | Activated |
222 | Not activated |
223 | Could not determine the state of the automatic log backup |
224 | Could not determine the status of the OMS memory analysis |
225 | Could not determine the status of the kernel trace |
226 | Could not determine the number of defective database indexes |
227 | Could not determine the return code of the last data backup |
228 | No data backup in the last three months |
229 | No data consistency check in the last three months |
230 | Unconditional |
231 | Conditional with check on same day |
232 | Conditional with check on previous day |
233 | Conditional with check two days previously |
234 | Conditional with check &1 days previously |
235 | No update of the Optimizer statistics in the last 3 months |
236 | Inactive since &1, &2 |
237 | Could not determine oldest OMS version |
238 | &1 hours |
239 | Could not determine the status of the Database Analyzer |
240 | Could not determine the current status |
241 | Tables only |
242 | All Objects |
243 | No data was restored in the last three months |
244 | Cannot determine date of the last restore |
245 | &1 days |
300 | liveCache Application |
301 | General information about liveCache application |
302 | APO system name |
303 | Version of the APO system |
304 | Version of the liveCache applications (DB procedures) |
305 | Number of work processes |
306 | liveCache application connection information |
307 | Information about LCA connection |
308 | Information about LDA connection |
309 | Information about periodic background jobs and administration reports |
310 | Information about the program /SAPAPO/OM_REORG_DAILY |
311 | Information about the program /SAPAPO/OM_DELETE_OLD_SIMSESS |
312 | Information about the program /SAPAPO/DELETE_LC_ANCHORS |
313 | Information about tracing liveCache applications |
314 | Number of active liveCache application traces |
315 | Number of active liveCache application checks |
316 | Miscellaneous |
317 | Information about critical logging events |
318 | Information about RFC connections relevant for APO |
320 | Information about LEA connection |
321 | Specifications for program SLCA_LCK_SYNCHOWNERS |
322 | Master is not in "online" mode |
323 | Hot standby system does not have a standby database |
324 | Standby is not in "Standby" mode=Admin+LogReceiving+Redo |
325 | Standby checked |
326 | ONLINE |
327 | STANDBY |
328 | UNKNOWN |
329 | Master database and standby database are no longer synchronized |
330 | Hot standby system does not have a master database |
501 | Database availability |
502 | Size of database in MB |
503 | Currently used area in database in MB |
504 | Growth in used memory area in MB since previous day |
598 | liveCache name and liveCache server |
599 | Key performance indicators (KPIs) |
600 | Database system with key performance indicators (KPIs) for NW |
601 | Database name and database server |
602 | System ID with which the database is integrated in DBACockpit |
603 | Database is not available |
604 | Data area > &2&3 |
605 | Data area used heavily (&1&3 > &2&3) |
606 | Data area growing quickly (&1&3 > &2&3) |
607 | Usage of data area between 00:00 and 02:00 |