DB6 - DB6: Alert Monitoring and Alert Configuration
The following messages are stored in message class DB6: DB6: Alert Monitoring and Alert Configuration.
It is part of development package STU6 in software component BC-DB-DB6. This development package consists of objects that can be grouped under "DB6: Performance-Monitor (UNIX/Windows)".
It is part of development package STU6 in software component BC-DB-DB6. This development package consists of objects that can be grouped under "DB6: Performance-Monitor (UNIX/Windows)".
Message Nr ▲ | Message Text |
|---|---|
| 022 | No configuration entry exists for the reported value |
| 025 | Not supported |
| 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 needed |
| 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 needed |
| 142 | SAP traces |
| 143 | Status of developer trace |
| 144 | Developer trace is deactivated |
| 145 | Developer trace is activated |
| 147 | Status of cumulative DSBL trace |
| 148 | Cumulative DBSL trace is deactivated |
| 149 | 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 cleaners 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 |
| 158 | Sort heap: Percentage of overflows during sort processing |
| 159 | Percentage of overflows is &1 percent |
| 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 active |
| 208 | The user exit is functioning, but errors have occurred |
| 209 | The user exit is not active |
| 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 SAP 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 |
| 314 | Secondary key |
| 315 | All secondary keys have been created in the database |
| 316 | The secondary key &2 defined on table &1 is missing |
| 318 | Inconsistencies between the database and the SAP definition |
| 319 | Tables |
| 320 | All tables are consistent |
| 321 | The descriptions of table &1 in the DB and ABAP Dictionary are different |
| 323 | Indexes |
| 324 | All indexes are consistent |
| 325 | The description of index &1 of table &2 is different |
| 327 | Tablespaces |
| 328 | All tablespaces are consistent |
| 329 | The descriptions of TS &1 in the DB and ABAP Dictionary are different |
| 400 | Check progam to prepare the selective statistics update |
| 401 | Time passed since last successful job run |
| 402 | Job ran successfully |
| 403 | The last job run is too far back in time |
| 404 | So far the job has not run successfully |
| 405 | Job scheduling |
| 406 | The job has been scheduled correctly |
| 407 | The jobs are scheduled too far apart |
| 408 | The job is not scheduled |
| 409 | Runtime fluctuations |
| 410 | The job runtimes fluctuate within the specified range |
| 411 | The job runtimes are fluctuating considerably |
| 412 | The fluctuation range of the runtimes is too high |
| 413 | Statistics update for all tables of the SAP System |
| 414 | Statistics update for critical tables of the SAP System |
| 415 | Reorganization of database tables |
| 416 | Archiving of log files |
| 417 | Deletion of archived log files |
| 418 | Mirroring of the AdminDB contents to the SAP System |
| 419 | Database backup |
| 420 | DB2 for Linux, UNIX, and Windows: System check |
| 500 | DB2 for Linux, UNIX, and Windows: System check |
| 501 | Time passed since last successful check run |
| 502 | The last check is current |
| 503 | The last check is too far back in time |
| 504 | So far no check has been completed successfully |
| 505 | Messages logged during the database system check |
| 506 | Information: &1 |
| 507 | Warning: &2 |
| 508 | Error: &3 |
| 509 | Important configuration parameters of the database manager |
| 510 | Database monitor settings |
| 511 | Buffer pool monitoring |
| 512 | The DFT_MON_BUFPOOL switch is set |
| 513 | The DFT_MON_BUFPOOL switch is not set |
| 514 | An invalid value has been returned for the DFT_MON_BUFPOOL switch |
| 515 | Lock behavior monitoring |
| 516 | The DFT_MON_LOCK switch is set |
| 517 | The DFT_MON_LOCK switch is not set |
| 518 | An invalid value has been returned for the DFT_MON_LOCK switch |
| 519 | Sort heap monitoring |
| 520 | The DFT_MON_SORT switch is set |
| 521 | The DFT_MON_SORT switch is not set |
| 522 | An invalid value has been returned for the DFT_MON_SORT switch |
| 523 | Statement cache monitoring |
| 524 | The DFT_MON_STMT switch is set |
| 525 | The DFT_MON_STMT switch is not set |
| 526 | An invalid parameter value has been returned for the DFT_MON_STMT switch |
| 527 | Table access monitoring |
| 528 | The DFT_MON_TABLE switch is set |
| 529 | The DFT_MON_TABLE switch is not set |
| 530 | An invalid value has been returned for the DFT_MON_TABLE switch |
| 531 | Monitoring of the UOWs (Unit of Work) |
| 532 | The DFT_MON_UOW switch is set |
| 533 | The DFT_MON_UOW switch is not set |
| 534 | An invalid value has been reported for the DFT_UOW switch |
| 535 | Diagnosis |
| 536 | Database error log scope |
| 537 | Errors and warnings are logged |
| 538 | Too many or too few diagnosis messages have been logged |
| 540 | Important configuration parameters of the database engine |
| 541 | Performance-relevant parameters |
| 542 | Time interval to determine deadlock situations |
| 543 | The DLCHKTIME parameter value is low enough |
| 544 | Der DLCHKTIME parameter value is too high |
| 546 | Threshold for starting the asynchronous page cleaners |
| 547 | Der CHNGPGS_THRESH parameter value is within the valid range |
| 548 | Der CHNGPGS_THRESH parameter value is out of range |
| 550 | Time frame to resolve lock situations |
| 551 | Der LOCKTIMEOUT parameter value is in the valid range |
| 552 | The LOCKTIMEOUT parameter value is out of recommended range |
| 553 | The LOCKTIMEOUT parameter is not set |
| 554 | Logging-relevant parameters |
| 555 | Ensuring roll forward recovery |
| 556 | The LOGRETAIN parameter is set |
| 557 | The LOGRETAIN parameter is not set |
| 558 | An invalid value has been returned for the LOGRETAIN parameter |
| 559 | Activation of the user exit |
| 560 | The USEREXIT parameter is set |
| 561 | The USEREXIT parameter is not set |
| 562 | An invalid value has been returned for the USEREXIT parameter |
| 563 | Soft checkpoints control |
| 564 | The SOFTMAX parameter is within the valid range |
| 565 | The SOFTMAX parameter is out of range |
| 567 | State or availability of the tablespaces |
| 568 | Availability of the tablespace and its containers |
| 569 | Status of the tablespace |
| 570 | The tablespace is available |
| 571 | The tablespace is not available. Status = &1 |
| 573 | Status of the container |
| 574 | The container is available |
| 575 | The container is not available |
| 576 | An invalid status value has been reported for the container |
| 577 | State of database-specific file systems |
| 578 | State of the log directory |
| 579 | The log directory is available |
| 580 | The log directory is not available |
| 582 | State of the log archive |
| 583 | The log archive is available |
| 584 | The log archive is not available |
| 586 | Log files of the database system |
| 587 | Entries in the DB2 diag log |
| 588 | Entries in the DB2 alert log |
| 589 | Log files of the user exit |
| 590 | Entries in the user exit log |
| 591 | Entries in the user exit error log |
| 592 | High-water marks |
| 593 | Maximum fill level of the primary log files |
| 594 | No storage shortages in the primary log file |
| 595 | The primary log file may overflow |
| 596 | The primary log file is full |
| 597 | Maximum fill level of the secondary log files |
| 598 | No storage shortages in the secondary log file |
| 599 | The secondary log file may overflow |
| 600 | The secondary log file is full |
| 601 | Automatic reorganization of log tables |
| 602 | Deletion of old entries in the alert message log |
| 603 | Old entries have been deleted |
| 604 | Old entries have not been deleted |
| 606 | Deletion of old data collector entries |
| 607 | Resetting old RUNSTATS check control table entries |
| 608 | No old entries exist |
| 609 | Old entries have been reset |
| 613 | Maximum fill level of the database heap |
| 614 | No storage shortages in the database heap |
| 615 | The database heap may overflow |
| 616 | The database heap is full |
| 617 | Current resource consumption |
| 618 | Current fill level of the log files |
| 619 | Too many log files are full |
| 620 | Technical restrictions of the database |
| 621 | Maximum size of a tablespace |
| 622 | The tablespace has almost reached its maximum size |
| 623 | Maximum size of the log file |
| 624 | The log file has almost reached its maximum size |
| 625 | Current lock list usage |
| 626 | The lock list contains too many locks |
| 627 | Current database heap usage |
| 628 | There is not enough free space in the database heap |
| 629 | Database-specific kernel information |
| 630 | Archiving of log files |
| 631 | Redirected restore tool |
| 632 | Restore of archived log files during recovery |
| 633 | User exit for archiving log files |
| 634 | Data collector for performance and alert monitor |
| 635 | Reorganization of tablespaces |
| 636 | Snapshot information |
| 637 | Update statistics and reorganization check |
| 638 | Tablespace and container configuration |
| 639 | History of database backups |
| 640 | Installation program of the AdminDB |
| 641 | Mirroring of the AdminDB to the SAP System |
| 642 | Command line processor interface |
| 643 | Release &1 / platform &2 / &3 patch level &4 |
| 645 | Unable to execute program. Reason: &1 |
| 646 | Database backup using the DBA Planning Calendar |
| 647 | User-defined functions installed on the database |
| 648 | Configuration data of the file systems |
| 649 | The function has been cataloged |
| 651 | The function has not been cataloged |
| 652 | Execution of operating system commands |
| 653 | Settings of DB2-specific environment variables |
| 654 | Path name of the log archive |
| 655 | Value &1 |
| 657 | Environment variable not set |
| 659 | Maximum number of objects in a tablespace |
| 660 | The tablespace has almost reached its maximum number of objects |
| 661 | Error messages from db2diag.log |
| 662 | Error message from db2diag.log |
| 663 | Informational message |
| 664 | Warning message |
| 665 | Error message |
| 666 | Warning messages from db2diag.log |
| 667 | Warning message from db2diag.log |
| 668 | Threshold violations |
| 669 | Thrshold predicate |
| 670 | No threshold violations |
| 671 | Threshold violation |
| 700 | Monitoring the disk space of DMS tablespaces |
| 701 | Disk space usage of the tablespace in percent |
| 702 | Not enough free space available |
| 703 | Monitoring the disk space of database file systems |
| 704 | Disk space usage of the file system in which the log directory is located |
| 705 | Disk space usage of the file system in which the log archive is located |
| 706 | Monitoring the disk space usage of SMS tablespaces |
| 707 | Monitoring the disk space usage of the SMS tablespace containers |
| 708 | Disk space usage of the file system in which the container is located |
| 709 | Disk space usage of storage paths |
| 710 | Disk space usage of the file system in which the DB directory is located |
| 711 | Primary log usage (> 100% means secondary log files allocated) |
| 712 | Primary log is full (> 100% means secondary log files allocated) |
| 800 | Status of Remote Connection |