|
|
Currently, replicating new Adabas fieldsto target RDBMS (for example from an ADADBS NEWFIELD) is not possible.
An Initial State is required instead, which is not always a viable option in a production environment.
Can ARF / ART be enhanced to include this option?
| Use Case | Replication |
| Created on Brainstorm | 10.13.2016 12:43 pm |
| Brainstorm ID | 4113 |
Your idea is already implemented. Pls. see the documentation link below and the text copied for your convenience:
https://documentation.softwareag.com/adabas/ark381/arf/art/amr/amr_use.htm
Adabas-RDBMS Synchronization Level:
Select the level at which the Event Replicator Target Adapter should synchronize the RDBMS table layout with the Adabas file.
The RDBMS-Adabas file synchronization (activated by this option) is triggered by the use of a new GFB and field table (GFFT) in the subscription you use for replication. Therefore, if you make changes to your Adabas database file or field structure, you must generate a new GFB/GFFT (using the Data Mapping Tool) and apply it to the appropriate subscription definition, prior to replicating data with the new structure.
Valid values for this option are:
ignore: This is the default. The existing table layout is ignored, differences between the RDBMS table layout and the Adabas file are ignored, and no synchronization occurs.
This setting might cause Event Replicator Target Adapter processing to stop if you have made changes to your Adabas database file or field structure and have included a newly-generated GFB/GFFT in the subscription you use for replication. When the Event Replicator Target Adapter receives the newly-structured replicated data, but this option is set to "ignore", it will not attempt to synchronize the RDBMS table layout with the new Adabas database structure. Any new or enhanced fields will not be recognized by the Event Replicator Target Adapter and processing will stop.
warn: Warning messages are written to the log about the differences between the RDBMS table layout and the Adabas file, but no synchronization occurs.
This setting might cause Event Replicator Target Adapter processing to stop if you have made changes to your Adabas database file or field structure and have included a newly-generated GFB/GFFT in the subscription you use for replication. When the Event Replicator Target Adapter receives the newly-structured replicated data, but this option is set to "ignore", it will not attempt to synchronize the RDBMS table layout with the new Adabas database structure (although it will issue a warning message). Any new or enhanced fields will not be recognized by the Event Replicator Target Adapter and processing will stop.
error: Event Replicator Target Adapter processing stops if the differences between the RDBMS table layout and Adabas file cause errors. No synchronization occurs.
apply: The RDBMS is altered (synchronized) with the Adabas file, with the following limitations:
No columns in the RDBMS table are removed, although they can be added.
The size or length of a data field will not be reduced. It can only be increased.
Data type conversions will not occur (for example, if Column A used to be an integer but has been changed to VARCHAR).
Added or altered columns cannot contain foreign key, unique key, or a primary key attribute.
RDBMS columns cannot be renamed.