1

Topic: It would be desirable particulars about SYSPROC.ADMIN_MOVE_TABLE

Does not go.
Swears:
[spoiler]------------------------------ the Gated in commands------------------------------
CALL SYSPROC.ADMIN_MOVE_TABLE (
' DB2ADMIN ';
' R_COMPONENTS_VALUE ';
' LARGESPACE2 ';
' LARGESPACE2 ';
' LARGESPACE2 ';
";
";
";
";
";
' MOVE ');
------------------------------------------------------------------------------
CALL SYSPROC.ADMIN_MOVE_TABLE (' DB2ADMIN ', ' R_COMPONENTS_VALUE ', ' LARGESPACE2 ', ' LARGESPACE2 ', ' LARGESPACE2 ', ", ' '," ",", ' MOVE ')
SQL2103N Procedure ADMIN_MOVE_TABLE did not manage to be fulfilled, as any
Aspect of the initial table or the table of assignment by procedure ADMIN_MOVE_TABLE not
It is supported. The reason code: "6". SQLSTATE=5UA0M
SQL2103N Procedure ADMIN_MOVE_TABLE did not manage to be fulfilled, as any aspect of the initial table or the table of assignment is not supported by procedure ADMIN_MOVE_TABLE. The reason code: "6".
Explanation:
Procedure SYSPROC.ADMIN_MOVE_TABLE allows to move the data from
One tabular space in another. For example, if is
Existing tabular spaces DMS, in which attribute Reclaimable
Storage it is not included, this procedure allows to transfer this data in
New tabular spaces DMS, in which attribute Reclaimable Storage
It is included. Procedure ADMIN_MOVE_TABLE cannot work from the initial
The table or the assignment table as they exist in the present
The moment in a database. On the aspect hindering operation, specifies the code
The reasons:
6
Following situations are possible:
* The type of the initial table is not supported.
* On the table relational restrictions are not defined.
* The table is in a state of the postponed check
Integrity or not an unoperated state.
7
....[/spoiler]
That for unsupported type - it is not clear.
With restrictions it is not transferred, without restrictions too it is not transferred.
State quite to itself working, at first sight.
Information from here it is small:
https://www.ibm.com/support/knowledgece … 54864.html
Here even parameters plainly are not painted.
There is a topic where it is written that removal of indexes helps, deleted - does not help.  deleted - does not help.
It is possible to find, of course, a window, to make ddl, to preempt the data, to correct ddl that in a new place created, to create, load.
But at first it is troublesome, secondly it is not assured that I will provide all unobvious subtleties of type automatically generated ID. And here such, like, valuable function, but happiness refuses to give for not clear reason...

2

Re: It would be desirable particulars about SYSPROC.ADMIN_MOVE_TABLE

Fair teapot;
Show ddl a file from:

 db2look-d mydb-e-z DB2ADMIN-t R_COMPONENTS_VALUE-o DB2ADMIN.R_COMPONENTS_VALUE.ddl 

3

Re: It would be desirable particulars about SYSPROC.ADMIN_MOVE_TABLE

The fair teapot, the colleague from Rostov mentioned that a problem in Russian-speaking comments to columns.

4

Re: It would be desirable particulars about SYSPROC.ADMIN_MOVE_TABLE

Guzya wrote:

the Fair teapot, the colleague from Rostov mentioned that a problem in Russian-speaking comments to columns.

And you launched on db 9.7.6?

5

Re: It would be desirable particulars about SYSPROC.ADMIN_MOVE_TABLE

Chumakov_JA wrote:

it is passed...
And you launched on db 9.7.6?

And still there there are foreign keys
And here command CALL SYSPROC.ADMIN_MOVE_TABLE
Refuses to transfer if there is a foreign key
Though if probably to bypass it then it will be remarkable.

6

Re: It would be desirable particulars about SYSPROC.ADMIN_MOVE_TABLE

Chumakov_JA wrote:

and here command CALL SYSPROC.ADMIN_MOVE_TABLE
Refuses to transfer if there is a foreign key
Though if probably to bypass it then it will be remarkable.

But after all for 9.7 in the description ADMIN_MOVE_TABLE in section Restrictions about it it is told:
Foreign keys (referential constraints) are not supported, either parent or child
This restriction has been removed in 10.1.2 (which already too it is removed from support, as well as 9.7) and in all newer versions.

7

Re: It would be desirable particulars about SYSPROC.ADMIN_MOVE_TABLE

Chumakov_JA wrote:

it is passed...
And you launched on db 9.7.6?

On 9.7.9.
Other experiments end, I will try comments .

8

Re: It would be desirable particulars about SYSPROC.ADMIN_MOVE_TABLE

[quote =
It is possible to find, of course, a window, to make ddl, to preempt the data, to correct ddl that in a new place created, to create, load.
But at first it is troublesome, secondly it is not assured that I will provide all unobvious subtleties of type automatically generated ID. And here such, like, valuable function, but happiness refuses to give for not clear reason...

It is strange that you believe that it is function valuable, works mandatory as it is necessary and gives "happiness" (we suppose that all types would be supported and problems with comments would not be). Also will not check behind it, whether really it provided these any unobvious subtleties? For a long time already the script would write.