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