DB10 - Database Monitor: messages
The following messages are stored in message class DB10: Database Monitor: messages.
It is part of development package SDMO in software component BC-DB-ORA-CCM. This development package consists of objects that can be grouped under "Database Monitor".
It is part of development package SDMO in software component BC-DB-ORA-CCM. This development package consists of objects that can be grouped under "Database Monitor".
Message Nr ▲ | Message Text |
|---|---|
| 000 | No detailed description available |
| 001 | &1: invalid value '&2' for &3 |
| 002 | &1: function call &2 failed with exception &3. Affected MTE: &4 |
| 003 | Error messages of the database-independent part of the database monitor |
| 004 | Database monitor errors (all databases) |
| 005 | &1: Collection method parameter &2 has invalid value &3 |
| 006 | Space management-related information |
| 007 | Performance-related information |
| 008 | Backup- and restore-related information |
| 009 | ABAP Dictionary-related information |
| 010 | User-related information |
| 011 | Monitoring of database operations logged in the XDB interface |
| 012 | Other database checks and noteworthy conditions |
| 013 | ABAP Dictionary objects that are not found in the database |
| 014 | Objects in the database are not defined in the ABAP Dictionary |
| 015 | Some objects are not found in both the database and the ABAP Dictionary |
| 016 | Further system checks |
| 017 | Creation status of optional indexes |
| 018 | Self-monitoring of the database monitor |
| 019 | &1: Unknown SY-DBSYS = '&2' |
| 020 | Status of XDB operations that have finished, successful and unsuccessful |
| 021 | Status of currently running database operations |
| 022 | Invalid value &1 = '&2' needs to be corrected to evaluate xdb tables |
| 023 | Improper maintenance of the XDB interface is reported here |
| 024 | Collection method &1: parameter &2 has invalid value &3 |
| 025 | Invalid value &1 = '&2' needs to be corrected to evaluate XDB tables |
| 026 | Approximately &1 &2 entries not processed; UPD_OP field not set properly |
| 027 | XDB_ID &1 could not be processed due to improper maint. of the XDB tables |
| 028 | The unique identifier for a particular db op. logged in the XDB interface |
| 029 | Unable to find XDB node in which to report the following XDB_ID &1 |
| 032 | Partial operation &1 started at &2 and finished at &3 &4 |
| 033 | Partial operation &1 started at &2 and is expected to finish at &3 |
| 034 | Partial operation '&1' started at &2 |
| 035 | Operation has status &1, started at &2, and finished at &3 &4 |
| 042 | Operation started on &1 |
| 043 | Operation has status &1 and is expected to finish on &2 |
| 044 | Operation has status &1 |
| 045 | Job with XDB ID &1 started on &2 and finished at &3 &4 |
| 046 | Job with XDB ID &1 started on &2 and finished &3 (end time unknown) |
| 047 | Operation started on &1 and has status &2 &3 (end time unknown) |
| 048 | Invalid value &1 = '&2' needs to be corrected to evaluate xdb tables |
| 049 | Approximately &1 &2 entries not processed; UPD_OP field not set properly |
| 051 | XDB ID &1 has invalid DBAML-BEGIN_OP '&2' |
| 052 | DBARCL.TRIAL ('&1') invalid for partial operation with XDB ID &2 |
| 053 | Partial operation &1 with XDB ID &2 has an invalid start date ('&3') |
| 054 | XDB_ID &1 could not be processed |
| 055 | XDB_ID &1 could not be processed. Invalid status '&2' |
| 056 | XDB_ID &1 has status '&2', but the invalid return code '&3' |
| 057 | Operation has status '&1' but invalid return code '&2' |
| 058 | Job with XDB ID '&1' has status '&2' but invalid return code '&3' |
| 059 | Job with XDB ID &1 has status 'COMPLETED', but its end time is not set |
| 060 | &1 ended OK. Op. started at &2 ended at &3 |
| 061 | Function: &1 &2. Started/Ended at: &3 OK. Status/log file: &4 |
| 062 | Object: &1. Started/Ended at: &2 OK. Obj status/type: &3 |
| 063 | &1 ended with warnings. Op. started at &2 ended at &3 |
| 064 | &1 ended with errors. Op. started at &2 ended at &3 |
| 065 | Object: &1. Started/Ended at: &2 with warnings. Obj status/type: &3 |
| 066 | Object: &1. Started/Ended at: &2 with errors. Obj status/type: &3 |
| 067 | Function: &1 &2. Started/Ended at: &3 with warnings. Status/log file: &4 |
| 068 | Function: &1 &2. Started/Ended at: &3 with errors. Status/log file: &4 |
| 089 | Description of this job ID |
| 100 | &1 &2 &3 &4 |
| 101 | &1: called with invalid dialog mode &2 |
| 102 | &1 could not read tool info |
| 103 | &1: function call &2 failed with exception &3 |
| 110 | More information about the last SAP consistency check |
| 111 | Reports when the last SAP consistency check was run |
| 112 | SAP consistency check just finished |