CNV_DMC_HC -
The following messages are stored in message class CNV_DMC_HC: .
It is part of development package CNV_DMC_HC in software component CA-LT. This development package consists of objects that can be grouped under "MWB: Health Checks".
It is part of development package CNV_DMC_HC in software component CA-LT. This development package consists of objects that can be grouped under "MWB: Health Checks".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 - &2: &3 skipped; error with &4 |
| 001 | &1 - &2: Everything OK |
| 002 | &1 - &2: Table has the status 'Failed' |
| 003 | &1: &2 skipped; error with &3 |
| 004 | &1 - &2: Logging table information is missing |
| 005 | &1 - &2: Logging table not created |
| 006 | &1 - &2: Trigger is not active |
| 007 | &1 - &2: Table not created in target system |
| 008 | &1 - &2: Table or synonym not created in source system |
| 009 | &1 - &2: Synonym not created in target system |
| 010 | &1 - &2: Proxy not created in target system |
| 011 | Invalid value for parameter &1: '&2' |
| 012 | Provided parameters do not match the check type for check with ID &1 |
| 013 | Neither a Health Check Config ID nor an active check was specified |
| 014 | No old Health Check results were found; reexecution of check not possible |
| 015 | It is not possible to specify a table without providing a mass transfer |
| 016 | No error messages in the log |
| 017 | Error when connecting to &1 RFC destination &2 for mass transfer ID &3 |
| 018 | Error when connecting to &1 DB connection &2 for mass transfer ID &3 |
| 019 | No &1 connection problems found for mass transfer ID &2 |
| 020 | &1 - &2: It seems as if data is not being replicated; see long text |
| 021 | &1 latency occured due to unexpected reasons; see long text |
| 022 | &1 - &2: No replication has happened up until this point in time |
| 023 | &1 - &2: Logging table has not been checked; see long text |
| 024 | &1 - &2: Object definition has changed in the source system |
| 025 | Job &1 (ID: &2): Job status could not be checked |
| 026 | Job &1 (ID: &2): Job status could not be corrected automatically |
| 027 | Job &1 (ID: &2): Job does not exist |
| 028 | Job &1 (ID: &2): Not authorized to check job status |
| 029 | Job &1 (ID: &2): Job was scheduled without starting date/time |
| 030 | Job &1 (ID: &2): Unknown error |
| 031 | Job &1 (ID: &2): Status of job was incorrect and has been corrected |
| 032 | &1 - &2: Cannot create event �Object Definition Changed� |
| 033 | Check not possible; Customizing data missing for system time zone |
| 034 | Job &1 (ID: &2): Job has been waiting to start for more than 3 minutes |
| 035 | &1: Everything OK |
| 036 | &1 - &2: Cannot copy archived data from consumption table to reload table |
| 037 | Master job is not running; job is being rescheduled |
| 038 | Master job is not running; no configuration is active |
| 039 | Master job is not running |
| 040 | Master job was not running; the job has been started automatically |
| 041 | Master job is running but no configuration is active |
| 042 | Multiple master jobs are running (&1 master jobs are running) |
| 043 | &1 - &2: No job is copying archived data |
| 044 | Master job is planned to run but not running |
| 045 | Master job is running correctly |
| 046 | The status of the master job is unknown |
| 049 | &1 - &2: Median latency (&3) has exceeded warning threshold by &4 |
| 050 | &1 - &2: Median latency (&3) has exceeded error threshold by &4 |
| 051 | &1 - &2: Maximum latency (&3) has exceeded error threshold by &4 |
| 052 | &1 - &2: Latency is within thresholds |
| 053 | &1 - &2: Maximum latency (&3) has exceeded warning threshold by &4 |
| 056 | &1 |
| 058 | &1 - &2: Not authorized to count the entries in logging table &3 |
| 059 | &1 - &2: Unknown error occurred when counting entries of logging table &3 |
| 060 | &1 - &2: Rec. to be processed in logging table &3 exceed threshold &4 |
| 061 | &1 - &2: Records to be processed in logging table &3: &4 |
| 062 | Error while trying to reexecute checks |
| 063 | &1 - &2: Minimum latency (&3) has exceeded warning threshold by &4 |
| 064 | &1 - &2: Minimum latency (&3) has exceeded error threshold by &4 |
| 065 | &1 - &2: Average latency (&3) has exceeded warning threshold by &4 |
| 066 | &1 - &2: Average latency (&3) has exceeded error threshold by &4 |
| 067 | &1 - &2: 1:N replication scenario; consumer is not registered |
| 068 | &1 - &2: 1:N replication scenario; failed to retrieve consumer number |
| 069 | &1 - &2: Logging table &3 does not exist in the source system |
| 070 | &1: Cannot count logging table entries |
| 071 | &1 - &2: Logging table &3 exists in source system |
| 072 | &1 - &2: Logging table &3 in SLT system is not the same as in source (&4) |
| 073 | &1 - &2: Skipping check for table as status is not 'Replication' |
| 074 | &1 - &2: Skipping check for table as replication has not started yet |
| 075 | No messages to display; choose 'Filter' to expand the selection |
| 076 | Notification settings saved |
| 077 | No changes have been made; no data saved |
| 078 | Not authorized to edit settings |
| 079 | Settings are being edited by &1 |
| 080 | E-mail ID &1 is invalid |
| 081 | Warning value &1 cannot be higher than error value |
| 082 | Table &1 does not exist in the mass transfer |
| 083 | &1 - &2: Skipping check for table as replication is suspended |
| 084 | End date/time is greater than start date/time |
| 085 | Error when setting up UI at &1; Line &2 ; RC &3 |
| 086 | No checks selected; Choose at least one relevant check before activating |
| 087 | Start and end date/time need to be provided |
| 088 | The check with ID &1 does not exist |
| 089 | There is no check matching the pattern &1 |
| 090 | No notification interval maintained; Choose a valid value |
| 091 | Job &1 (ID: &2): Job has been running for over 24 hours |
| 092 | Job &1 (ID: &2): Master job has been running for over 24 hours |
| 093 | Health check job is not running; do the checks as instructed |
| 094 | Enter a number between 1 and 600 inclusive for response time threshold |
| 095 | System in maintenance; master job is NOT starting |
| 096 | Job &1 (ID: &2): Job cancelled; maximum runtime exceeded |
| 097 | Job &1 (ID: &2): Cannot cancel job |
| 098 | &1 - &2: SQL error: &3&4 |
| 099 | Notifications are active but no checks are selected for notifications |
| 100 | Scheduled job &1 (ID: &2) could not start and was deleted |
| 101 | Error notification job is not running; job is being rescheduled |
| 102 | Duplicate entries of table &1 exist in Settings for Logging Table Check |
| 103 | Duplicate entries of table &1 exist in Settings for Latency Check |
| 104 | &1&2&3&4 |
| 107 | MT ID &1, table &2; cannot determine settings for automatic restart |
| 108 | &1 - &2: Flags �In Process� and �Failed� reset for table &2 |
| 109 | &1 - &2: No access plan calculation job found for table &2 |
| 110 | &1 - &2: Unprocessed records exist in logging tables (threshold reached) |
| 111 | &1 - &2: Object contains unprocessed records |
| 112 | Cannot determine tables for object &1 |
| 113 | &1 - &2: Trigger information is missing |
| 114 | &1 - &2: Buffer table does not exist |
| 115 | &1 - &2: Buffer table exists with a different structure |
| 120 | Object &1 (MTID &2) deleted from DMC_OBJ_HEADER |