Writing data in to exception table should treated as a ERROR in Replicate
Problem: While Writing data in to exception table is treated as a warning in Replicate.
Current state : In AEM Warnings are not captured and in Replicate it is treated as a warning writing records to exception table.
Future State: The records which logs to exception table Should be treated as ERROR instead of WARING. We want this to be implemented in replicate and AEM.
Log:
00009728: 2020-10-22T17:55:30 [TARGET_APPLY ]T: INSERT statement for table 'SAPABAP1.attrep_apply_exceptions' was not found in the pool, going to allocate a new statement (statement_manager.c:1667)
00009728: 2020-10-22T17:55:30 [TARGET_APPLY ]W: Source changes that would have had no impact were not applied to the target database. Refer to the 'attrep_apply_exceptions' table for details (endpointshell.c:6566)
What is the Challenge: This is more of a challenge (not an issue) due to the growing use of replicate (14 PROD and 20 plus stage servers with 260 tasks and 15K plus tables replicating currently) in our environment where we are writing data to “multiple” (50 plus) target databases. As you know replicate pushes data to attrep_apply_exception table to target to which it writes for “each” task (250 tasks ). The challenge is writes data to 50 plus databases (mostly different) and we are adding more each sprint. Hence it is practically impossible to keep tab of when records are written in exception tables and sometimes we realize that a lot of records are written to exception tables after business reports missing data or someone manually looks up the data by querying the table.
What is the Ask: Provide a setup where if a Task writes data/records to attrep_apply_exception tables (for whatever reason; to start with – below example, would be nice based on Data errors, Apply Conflicts, choose based on target database name etc), a “notification” can be configured OR provide an API that can report a task writing data to attrep_exception_table. This will enable run/support teams to look into the records and take corrective actions “immediately”. Additionally, will help in creating a data governance process where specific data stewards or data owners gets alerted when data is written in attrep_apply_exceptions table.
00009728: 2020-10-22T17:55:30 [TARGET_APPLY ]W: Source changes that would have had no impact were not applied to the target database. Refer to the 'attrep_apply_exceptions' table for details (endpointshell.c:6566)
Current Impact: Scenarios where business had reported to Support team about missing data. Goal is IT finds out missing data before business reports it.
NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.
