Prev: canceling admin_move_table fails if source table have restrict on drop
Next: Incremental Restore question
From: Helmut Tessarek on 8 Jun 2010 14:48 This is a bug and I asked the owner of the code to open an APAR. It will be fixed in the next fixpack. The only workaround for now is to drop the restrict on drop constraint and to recreate it afterwards. On 8.6.2010 02:31, hsn_ wrote: > db2 => call sysproc.admin_move_table(current > schema,'Z2','USERSPACE1','USERSPACE > 1','USERSPACE1',NULL,NULL,NULL,NULL,NULL,'CANCEL') > SQL0672N Operace DROP nen� pro tabulku "MAJITEL.Z2AAAAXSt" povolena. > SQLSTATE=55035 -- Helmut K. C. Tessarek DB2 Performance and Development /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ |