Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2009
    Location
    Zoetermeer, Holland
    Posts
    746

    Unanswered: figure out syntax of ADMIN_MOVE_TABLE

    On my XP workstation with express-C 9.7.2. in am testing/playing with the ADMIN_MOVE_TABLE feature(sample database with one of the simplest tables). Worked well untill I tried table-partitioning. This syntax is not accepted
    Code:
    CALL SYSPROC.ADMIN_MOVE_TABLE
    		(		CURRENT_SCHEMA
    			,	'SALES'
    			,	'TS04_SALES_DAT'
    			,	'TS04_SALES_IDX'
    			,	'TS04_SALES_DAT'
    			,	'REGION , SALES'
    			,	 NULL
    			,	"(SALES_DATE) (STARTING '1/1/1900' ENDING '1/1/2100' EVERY 1 YEAR)"
    			,	 NULL
    			,	 NULL
    			,	'MOVE'
    		);
    All very basic stuff I am trying to accomplish. Anyone figured it out the right syntax for this?

  2. #2
    Join Date
    Jan 2009
    Location
    Zoetermeer, Holland
    Posts
    746
    NEVER MIND! Figured it out myself: Is not going to work because table-parttioning is not enabled on express-C

  3. #3
    Join Date
    Jan 2009
    Location
    Zoetermeer, Holland
    Posts
    746
    So I grab a server with v9.7.2. installed and there the most simple attempt fails with:
    Code:
    SQL0751N  Routine "" (specific name "") attempted to execute a statement that
    is not allowed.  SQLSTATE=HY00
    db2diag:
    Code:
    2010-12-16-15.12.14.817000+060 E6774524F836       LEVEL: Error
    PID     : 3588                 TID  : 3364        PROC : db2fmp64.exe
    INSTANCE: TST                  NODE : 000
    EDUID   : 3364
    FUNCTION: DB2 UDB, database application extension for utili, adminotm_online_table_move, probe:18483
    DATA #1 : String, 8 bytes
    schemaname    
    DATA #2 : String, 14 bytes
    Tablename
    DATA #3 : String, 4 bytes
    MOVE
    DATA #4 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -751   sqlerrml: 0
     sqlerrmc: 
     sqlerrp : SQL09072
     sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
               (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
     sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)    
               (7)      (8)      (9)      (10)        (11)     
     sqlstate: HY00
    It does not like what I am doing, but what am I doing wrong?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •