/SDF/DB6 - DB2 UDB: Alert Monitoring and Alert Configuration
The following messages are stored in message class /SDF/DB6: DB2 UDB: Alert Monitoring and Alert Configuration.
It is part of development package /SDF/STPI/RI in software component SV-SMG-SDD. This development package consists of objects that can be grouped under "Release-Independent Basis Add-On SLM".
It is part of development package /SDF/STPI/RI in software component SV-SMG-SDD. This development package consists of objects that can be grouped under "Release-Independent Basis Add-On SLM".
Message Nr ▲ | Message Text |
|---|---|
| 000 | No values assigned |
| 001 | Check the configuration of the DIAGLEVEL parameter |
| 002 | USEREXIT must be activated in a production system |
| 003 | Check the configuration of the LOCKTIMEOUT parameter |
| 004 | Check the configuration of the SOFTMAX parameter |
| 005 | Check the configuration of the CHNGPGS_THRESH parameter |
| 006 | The parameter must be activated |
| 007 | & |
| 008 | The table/index statistics must be reset for the & table |
| 009 | Overall database buffer hit ratio is too low |
| 010 | Sync. buffer quality is too low |
| 011 | There are lock escalations in your system |
| 012 | There are exclusive lock escalations in your system |
| 013 | There are deadlocks in your system |
| 014 | There are lock timeouts in your system |
| 015 | There are lock waits in your system |
| 016 | There are sort overflows in your system |
| 017 | The catalog cache hit ratio is too low |
| 018 | The package cache hit ratio is too low |
| 019 | The DLCHKTIME parameter value should be lower than LOCKTIMEOUT |
| 020 | DB2 Universal Database for UNIX & Windows: Self-monitoring |
| 021 | &1: &2 has failed. Cause: &3. Affected object: &4 |
| 022 | No configuration entry exists for the reported value |
| 023 | Check the configuration using transaction DB17 |
| 024 | No errors in the alert monitor |
| 029 | Operator &1 is not allowed |
| 030 | The configuration table does not contain data |
| 031 | Invalid data for field &1. Content: &2 |
| 032 | No alert messages have been logged |
| 033 | No entries have been selected with the specified selection criteria |
| 034 | Error when writing to table &1. SY-SUBRC = &2 |
| 035 | Select the line you want to edit |
| 036 | General configuration data could not be found |
| 037 | &1 entries have been deleted |
| 038 | Select the column by which you want to sort |
| 039 | The configuration data was saved |
| 040 | The specified unit is not allowed |
| 041 | The &1 operator needs a value list separated by ';' |
| 042 | The &1 operator requires two figures separated by ':' |
| 043 | Value &1 has an invalid format |
| 044 | Error when deleting table &1. SY-SUBRC = &2 |
| 045 | Error when reading the partition configuration. SY-SUBRC = &1 |
| 046 | Value &1 not allowed |
| 047 | The value &1 is not assigned to an error severity |
| 048 | Description is not complete |
| 049 | The value &1 occurs several times |
| 050 | List box value range for field &1 could not be created |
| 051 | You are not allowed to deactivate this entry |
| 052 | You are not allowed to change this entry |
| 100 | Database buffer pool |
| 101 | Buffering quality |
| 102 | The buffer pool hit ratio is too low |
| 103 | Buffer pool configuration |
| 104 | The buffer pool size is &1 |
| 105 | DB configuration parameter BUFFPAGE is active |
| 107 | Performance-relevant database buffers |
| 108 | Catalog cache: Buffering of table description data |
| 109 | The catalog cache hit ratio is too low |
| 110 | Package cache: Buffering package information for SQL statements |
| 111 | The package cache hit ratio is too low |
| 112 | Sort heap: Number of sort overflows per day |
| 113 | Too many overflows occur in the sort heap |
| 114 | Application lock behavior |
| 115 | Number of deadlocks per day |
| 116 | Too many deadlocks occur in the system |
| 117 | Number of lock escalations per hour |
| 118 | Too many lock escalations occur in the system |
| 119 | Number of exclusive lock escalations per hour |
| 120 | Too many exclusive lock escalations occur in the system |
| 121 | Number of lock timeouts per hour |
| 122 | Too many lock timeouts occur in the system |
| 123 | Number of lock waits per hour |
| 124 | Too many lock waits occur in the system |
| 125 | Measures to optimize performance |
| 126 | Time passed since last table statistics update |
| 127 | The table statistics are current |
| 128 | The table statistics are no longer current |
| 129 | So far, no table statistics have run without errors |
| 130 | Time passed since last table reorganization |
| 131 | The tables have been reorganized |
| 132 | The last table reorganization is too far back in time |
| 133 | So far, no tables have been reorganized successfully |
| 134 | Maximum table change rate since the last statistics update |
| 135 | The change rate is low for all tables |
| 136 | Table &1 has a change rate of &2 percent |
| 137 | Table &1 has a change rate of &2 percent -> statistics update |
| 138 | Maximum number of overflow page accesses since last REORG |
| 139 | The number of overflow pages is low for all tables |
| 140 | Table &1 has more than &2 percent of overflow page accesses |
| 141 | Table &1 has more than &2 percent of overflow page accesses -> REORG |
| 142 | SAP traces |
| 143 | Status of developer trace |
| 144 | Developer trace is deactivated |
| 145 | Developer trace is activated |
| 146 | Status of cumulative DSBL trace |
| 148 | Status of cumulative DSBL trace |
| 149 | Cumulative DBSL trace is deactivated |
| 150 | Cumulative DBSL trace is activated |
| 151 | Distribution of the IO cleaners in percent |
| 152 | Percentage of the pool logspace cleaners |
| 153 | The percentage of the pool logspace cleaner is too low |
| 154 | Percentage of the dirty page steal cleaners |
| 155 | The percentage of the dirty page steal cleaners is too high |
| 156 | Percentage of the dirty page threshold cleaners |
| 157 | The percentage of the dirty page threshold cleaners is too high |
| 200 | Database backup |
| 201 | Time passed since last successful backup |
| 202 | The last database backup is current |
| 203 | The last database backup is too far back in time |
| 204 | So far, no database backup has been performed successfully |
| 205 | Log files |
| 206 | State of the DB2 user exits |
| 207 | The user exit is functioning normally |
| 208 | The user exit is functioning, but errors have occurred |
| 209 | The user exit is not functioning |
| 210 | State of the archiving program for the log files |
| 211 | Archiving is functioning normally |
| 212 | Archiving is functioning normally, but errors have occurred |
| 213 | Archiving is not functioning |
| 214 | Completeness of the log files for a recovery |
| 215 | All log files exist or have been archived successfully |
| 217 | Log files are missing or have not been archived successfully |
| 218 | State of the AdminDB |
| 219 | Availability and installation of the AdminDB |
| 220 | The AdminDB is available |
| 222 | The AdminDB is not available or has not been installed successfully |
| 223 | Mirroring of the AdminDB contents to the R/3 System |
| 224 | The mirrored AdminDB data is current |
| 225 | The mirrored AdminDB data is no longer current |
| 226 | So far, no data of the AdminDB have been mirrored |
| 227 | Online backup |
| 228 | No online backup is running |
| 229 | Online backup is running |
| 231 | Log directory was changed after database restart |
| 232 | Log directory has not been changed |
| 233 | At the next database restart a new log directory will be used |
| 300 | Objects defined in the ABAP Dictionary that are missing in the database |
| 301 | Database tables |
| 302 | All tables are defined in the ABAP Dictionary |
| 303 | The &1 table is not defined in the ABAP Dictionary |
| 305 | Database indexes |
| 306 | All indexes have been created |
| 307 | The &2 index defined on table &1 has not been created |
| 309 | Objects defined in the database that are missing in the ABAP Dictionary |
| 310 | SAP tables |
| 311 | All tables have been created in the database |
| 312 | The &1 table has not been created in the database |