db2 => create table z2 (a integer) in alexaidx
DB20000I Pøíkaz SQL byl úspì¹nì dokonèen.
db2 => alter table z2 add restrict on drop
DB20000I Pøíkaz SQL byl úspì¹nì dokonèen.
db2 => call sysproc.admin_move_table(current
schema,'Z2','USERSPACE1','USERSPACE
1','USERSPACE1',NULL,NULL,NULL,NULL,NULL,'INIT')


Výsledná sada 1
--------------

KEY VALUE


--------------------------------
---------------------------------------------
--------------------------------------------------------------------------------
---
AUTHID MAJITEL


INDEXNAME


INDEXSCHEMA


INIT_END 2010-06-08-08.24.13.953000


INIT_START 2010-06-08-08.24.13.718000


STAGING Z2AAAAXSs


STATUS COPY


TARGET Z2AAAAXSt


VERSION 09.07.0002



Bylo vybráno 9 záznamù.

Stav pøi návratu = 0
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

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:

--
Helmut K. C. Tessarek
DB2 Performance and Development

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/