| SDBALM170 |
Low free space in data area (&1&3 < &2&3) |
| SDBALM171 |
Low free space in log area (&1&3 < &2&3) |
| SDBALM172 |
High usage rate in the data cache (&1&3 > &2&3) |
| SDBALM173 |
High proportion of OMS data in the data cache (&1&3 > &2&3) |
| SDBALM174 |
High proportion of SQL data in the data cache (&1&3 > &2&3) |
| SDBALM175 |
High proportion of history/undo data in the data cache (&1&3 > &2&3) |
| SDBALM176 |
High proportion of OMS history data in the data cache (&1&3 > &2&3) |
| SDBALM177 |
High proportion of OMS rollback data in the data cache (&1&3 > &2&3) |
| SDBALM178 |
High number of "Out of Memory" exceptions occurred (&1 > &2) |
| SDBALM179 |
High number of OMS terminations occurred (&1 > &2) |
| SDBALM180 |
High usage rate in the heap (&1&3 > &2&3) |
| SDBALM181 |
Heap size has exceeded threshold value (&1 > &2) |
| SDBALM182 |
Low hit rate in the data cache (&1&3 < &2&3) |
| SDBALM183 |
Low hit rate for OMS data in the data cache (&1&3 < &2&3) |
| SDBALM184 |
Low hit rate for SQL data in the data cache (&1&3 < &2&3) |
| SDBALM185 |
Low hit rate for history/undo data in the data cache (&1&3 < &2&3) |
| SDBALM186 |
Low hit rate for OMS history data in the data cache (&1&3 < &2&3) |
| SDBALM187 |
Low hit rate for OMS rollback data in the data cache (&1&3 < &2&3) |
| SDBALM188 |
Low hit rate in the catalog cache (&1&3 < &2&3) |
| SDBALM189 |
Low hit rate in the rollback cache (&1&3 < &2&3) |
| SDBALM190 |
Low hit rate in the converter cache (&1&3 < &2&3) |
| SDBALM191 |
Few user tasks have status CONNECT WAIT (&1 < &2) |
| SDBALM192 |
High number of log queue overflows (&1 > &2) |
| SDBALM193 |
High proportion of overflows to log queue additions (&1% > &2%) |
| SDBALM194 |
Optimizer statistics are too old (&1 days > &2 days) |
| SDBALM195 |
Last data backup is too old (&1 days > &2 days) |
| SDBALM196 |
Last data consistency check is too old (&1 days > &2 days) |
| SDBALM210 |
liveCache application call possible |
| SDBALM211 |
Cannot call liveCache applications |
| SDBALM212 |
Cannot determine whether liveCache applications can be called |
| SDBALM213 |
Successful |
| SDBALM214 |
Cancel |
| SDBALM215 |
Could not determine the cause of the last stop |
| SDBALM216 |
Can only determine the cause of the last stop in ONLINE or OFFLINE states |
| SDBALM217 |
Active |
| SDBALM218 |
Inactive |
| SDBALM219 |
Could not determine the status of the archive logging |
| SDBALM220 |
Activated (Log fill level > 1.5 * Log segment size) |
| SDBALM221 |
Activated |
| SDBALM222 |
Not activated |
| SDBALM223 |
Could not determine the status of the automatic log backup |
| SDBALM224 |
Could not determine the status of the OMS memory analysis |
| SDBALM225 |
Could not determine the status of the kernel trace |
| SDBALM226 |
Could not determine the number of defective database indexes |
| SDBALM227 |
Could not determine the returncode of the last data backup |
| SDBALM228 |
No data backup in the last three months |
| SDBALM229 |
No data consistency check in the last three months |
| SDBALM230 |
Unconditional |
| SDBALM231 |
Conditional with check on same day |
| SDBALM232 |
Conditional with check on previous day |
| SDBALM233 |
Conditional with check two days previously |
| SDBALM234 |
Conditional with check &1 days previously |
| SDBALM235 |
No update of the Optimizer statistics in the last 3 months |
| SDBALM236 |
Inactive since &1, &2 |
| SDBALM237 |
Could not determine oldest OMS version |
| SDBALM238 |
&1 hours |
| SDBALM239 |
Could not determine the status of the Database Analyzer |
| SDBALM240 |
Could not determine the current status |
| SDBALM300 |
liveCache Application |
| SDBALM301 |
General information about liveCache application |
| SDBALM302 |
SCM system name |
| SDBALM303 |
Version of the SCM system |
| SDBALM304 |
Version of the liveCache applications (DB procedures) |
| SDBALM305 |
Number of work processes |
| SDBALM306 |
liveCache application connection information |
| SDBALM307 |
Information about LCA connection |
| SDBALM308 |
Information about LDA connection |
| SDBALM309 |
Information about periodic background jobs and administration reports |
| SDBALM310 |
Information about the program /SAPAPO/OM_REORG_DAILY |
| SDBALM311 |
Information about the program /SAPAPO/OM_DELETE_OLD_SIMSESS |
| SDBALM312 |
Information about the program /SAPAPO/DELETE_LC_ANCHORS |
| SDBALM313 |
Information about tracing liveCache applications |
| SDBALM314 |
Number of active liveCache application traces |
| SDBALM315 |
Number of active liveCache application checks |
| SDBALM316 |
Miscellaneous |
| SDBALM317 |
Information about critical logging events |
| SDBALM318 |
Information about RFC connections relevant for SCM |
| SDBALM320 |
Information about LEA connection |
| SDBALM321 |
Specifications for program SLCA_LCK_SYNCHOWNERS |
| SDBALM322 |
Master is not in "online" mode |
| SDBALM323 |
Hot standby system does not have a standby database |
| SDBALM324 |
Standby is not in "Standby" mode=Admin+LogReceiving+Redo |
| SDBALM325 |
Standby checked |
| SDBALM326 |
ONLINE |
| SDBALM327 |
STANDBY |
| SDBALM328 |
UNKNOWN |
| SDBALM330 |
Hot standby system does not have a master database |
| SDBALM501 |
Database availability |
| SDBALM502 |
Size of database in MB |
| SDBALM503 |
Currently used area in database in MB |
| SDBALM504 |
Growth in used memory area in MB since previous day |
| SDBALM598 |
liveCache name and liveCache server |
| SDBALM599 |
Key performance indicators (KPIs) |
| SDBALM600 |
Database system with key performance indicators (KPIs) for NW |
| SDBALM601 |
Database name and database server |
| SDBALM602 |
System ID with which the database is integrated in DBACockpit |
| SDBALM603 |
Database is not available |
| SDBALM604 |
Data area > &2&3 |
| SDBALM605 |
Data area used heavily (&1&3 > &2&3) |
| SDBALM606 |
Data area growing quickly (&1&3 > &2&3) |