DHCDC_REC - Message for Recording Area of CDC ABAP Agent
The following messages are stored in message class DHCDC_REC: Message for Recording Area of CDC ABAP Agent.
It is part of development package LT_DHCDC_REC in software component EIM-DH-ABA-CDC. This development package consists of objects that can be grouped under "SAP Data Hub - CDC ABAP Agent - Recording (Dev. Package)".
It is part of development package LT_DHCDC_REC in software component EIM-DH-ABA-CDC. This development package consists of objects that can be grouped under "SAP Data Hub - CDC ABAP Agent - Recording (Dev. Package)".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Specify the name of the application table |
| 002 | Lock on table DHCDC_RECID failed |
| 003 | Insert into DHCDC_RECID for tablle &1 failed |
| 004 | Maximum object ID in table DHCDC_RECID has been reached |
| 005 | Table name not specified |
| 006 | Subscriber logging table &1 is unknown |
| 007 | Observer process error |
| 008 | Observer job is stopped due to system maintenance |
| 009 | Error occurred while processing application table |
| 010 | Table &1; failed to lock table DHCDC_RECCONTROL (recording control) |
| 011 | It looks like structure of source object was changed. Observer restart |
| 100 | Database type "&1" is not supported |
| 101 | Error while creating DDL instance (see next error for details) |
| 102 | Compiler error (see next error for details) |
| 103 | Metadata error (see next error for details) |
| 104 | Failed to determine DB type of connection &1 (see previous error) |
| 105 | Error while creating logging table (see next error for details) |
| 106 | Error while deleting logging table (see next error for details) |
| 107 | Error during creation of sequence instance (see previous error) |
| 108 | Error while processing sequence |
| 109 | Field &1 is expected in the logging table but is not present |
| 110 | Field &1 is not expected in the logging table but is present |
| 111 | Field &1 is expected in position &3, but field &2 is in this position |
| 112 | Field &1 is expected in position &2, but is present in position &3 |
| 113 | Field &1 is expected to be a key field, but is not a key field |
| 114 | Field &1 is not expected to be a key field, but is a key field |
| 115 | Data type of field &1 is expected to be &2, but is &3 |
| 116 | Role name of field &1 is expected to be &2, but is &3 |
| 117 | Data length of field &1 is expected to be &2, but is &3 |
| 118 | Number of decimal places of field &1 is expected to be &2, but is &3 |
| 200 | Error while creating the name for the master logging table |
| 201 | Error while creating the name for the subscriber logging table |
| 202 | Table &1 not found |
| 203 | Error while initializing class LOGTAB (see next error for details) |
| 204 | Error while processing logging table |
| 205 | Error while checking logging table |
| 206 | Last replicated pointer not found |
| 207 | Error while reading structure of logging table &1 (see next error) |
| 208 | Logging table &1 is already processed by observer process |
| 301 | Table &1 does not have a master logging table |
| 302 | Reading the recording object ID for table &1 failed |
| 303 | Table &1 does not exist |
| 304 | Table name is empty |
| 305 | Dropping trigger &1 failed |
| 306 | Creating trigger of type &1 for table &2 failed |
| 307 | Reading trigger names for table &1 from DB failed |
| 308 | Failed to connect to the database using DB connection &1 |
| 309 | Reading trigger code for table &1 from DB failed |
| 310 | Error while processing database triggers |
| 311 | Specify the name of the ZDO clone table |