Hi Sean, Thanks for your so quick response. I just tried to use cleanat, it seems that it will only drop DTM LOG. After executing cleanat, there still exists one table: TRAFODION._DTM_.TDDL
So this table will not be dropped by cleanat, right? [cid:image003.png@01D2D61B.C142B080] [cid:image001.png@01D2D61C.3861AF40] Best regards, Yuan Email: yuan....@esgyn.cn<mailto:yuan....@esgyn.cn> Cellphone: (+86) 13671935540 From: Sean Broeder [mailto:sean.broe...@esgyn.com] Sent: Friday, May 26, 2017 11:34 AM To: user@trafodion.incubator.apache.org Subject: RE: Initialize trafodion drop will not drop DTM tables Hi Yuan, The reason initialize Trafodion, drop does not drop DTM tables is that the DTM is running and still using them. I'm not practiced in offline restore. Does it use scripts that don't require Trafodion to be running? Perhaps you can leverage the cleanat script as follows. initialize Trafodion, drop sqstop cleanat offline restore sqstart Regards, Sean From: Liu, Yuan (Yuan) [mailto:yuan....@esgyn.cn] Sent: Thursday, May 25, 2017 8:28 PM To: user@trafodion.incubator.apache.org<mailto:user@trafodion.incubator.apache.org> Subject: Initialize trafodion drop will not drop DTM tables Hi Trafodioners, I found that when I did 'initialize trafodion, drop' the DTM related tables would not be dropped. Could anyone explain why this happened? For the feature of 'offline restore', we need to make sure there is no TRAFODION.* table exist in HBase, otherwise the restore will fail. So I am thinking can we have such enhancement that we drop all TRAFODION.* tables when 'initialize trafodion, drop'? Does that make sense? [cid:image004.png@01D2D61B.C142B080] [cid:image005.png@01D2D61B.C142B080] Best regards, Yuan Email: yuan....@esgyn.cn<mailto:yuan....@esgyn.cn> Cellphone: (+86) 13671935540
