Suggest an Idea

[Srini_Vadlamudi]

STEPS

Customer uses to DROP and create "EXISTING_TABLE" "

1.CREATE NEW_TABLE

2.COPY EXISTING_TABLE to NEW_TABLE

3.DROP the EXISTING_TABLE

4.RENAME THE NEW_TABLE to EXISTING_TABLE NAME

5. CONTINUE COLLECTING CHANGES for "EXISTIG_TABLE"    

===========================================================

• Their default is to IGNORE DROP
• Logstream and replication tasks DB2 LUW( SAP)  
• TABLE SELECTION  = %.%   ( they do not select the name of the table having the DROP  issue) 

===================================
1) When they do the drop  of the EXISTING_TABLE:  

At this point, the drop table is recorded in Replicate log for Logstream task. 

Note that DROP table statement isn't thrown as Error but as Warning in Child/Replication task if "When source table is dropped:" 

Expected Behavior:

1. Throw the warning message as Error so that we could catch it.

[Ola_Mayer]

This requirement is not clear. Can you please explain why are you expecting an error message?

[dtylerlivingston]

Hi Ola,

Our DB2 team performs maintenance called OTM (Online Table Maintenance).  This is kicked off via the application (SAP) but runs as a maintenance function on the database.  The maintenance routine is core functionality provided by IBM.  The steps described do occur but these are not manually/independently run, the DB2 OTM process performs these activities. 

After OTM and only occasionally (about 10% of tables) Attunity Replicate shows it is replicating a table but is not; the task shows green but no data is flowing.  We have thousands of tables and identifying when this occurs is difficult.  Warning messages are thrown in the logs but instead of warnings we'd like these to be Errors.  This would alert us to the issue and allow us to take appropriate action. 

[JitenderR]

Hi Ola

To further clarify the requirement, I have created the attached diagram detailing out the OTM process. Also, below are additional notes, 

• This is applicable only to DB2 LUW tables. And specifically, when SAP ECC (or any other SAP application) is provisioned on DB2 database.
• This is an IBM provided functionality and detailed in this link ; process is designed to mainly claim disk space.- https://www.ibm.com/developerworks/data/library/techarticle/dm-1306adminmovetable/index.html
• The ask is, referring to the attached diagram, 
  • In SWAP stage, when the original table (that is tagged to replicate) is RENAMED (currently not a supported functionality for IBM DB2 LUW endpoint), that is when replicate loses the connection or stops replicating (currently as expected)
  • Later in SWAP stage, the _stage table is then renamed to the original table (same as the name which replicate was replicating; but from metadata standpoint, these are two different).
  • Hence the ask is, provide a switch (or some internal parameter) where replicate continuously polls DB2 metadata for a set amount of time or set number or retries with an interval, so that it can get the updated metadata of the RENAMED (or SWAPPED table) and ensure replication continuous without manual intervention. 

Let us know for any additional questions. 

Regards

JR 

OTM Process for DB2 LUW Tables

[dtylerlivingston]

Hi Ola,

Can you comment on the status having changed from "Open - Collecting Feedback" to "Open - New"?  Does that mean this request has some interest within Qlik?  I could provide more details and/or overview of how this occurs if it helps.

Thanks,

Tyler Livingston

[Ola_Mayer]

Srini,

I'm not sure I understand the issue.

The customer selected 'IGNORE Drop'. Why would you expect an ERROR.

[dtylerlivingston]

Hi Ola,

The opening comment may be misleading in that this is a maintenance process provided by IBM.  That comment states what the OTM process does.  It is used to reclaim storage space of DB2 systems and was frequently used for a period of time though use has dropped (primary system moved to HANA).  There was no option to stop business from using it but Attunity was losing connectivity to tables but tasks were showing green (no data replicating and no errors).  The request is to support a manufacturer supported maintenance routine.

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

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.