cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Using ADMIN_TABLE_MOVE or DB6CONV to move VBDATA

Former Member
0 Likes
2,846

When trying to correct DB2 DB Deadlocks on VBDATA using saptools procedure (SAP Note1430621) we received the following error from the db2 command prompt

db2 => call saptools.online_table_move('SAPWAD','VBDATA','WAD#VBDATAD','WAD#VBDATAI','','','','','"VBKEY" VARCHAR(96) NOT NULL WITH DEFAULT '' '' ,"VBMODCNT" INTEGER NOT NULL WITH DEFAULT 0 ,"VBBLKNO" INTEGER NOT NULL WITH DEFAULT 0 ,"VBLEN" SMALLINT NOT NULL WITH DEFAULT 0 ,"VBDATA" VARCHAR(30000) FOR BIT DATA ','MOVE');

SQL0440N No authorized routine named "SAPTOOLS.ONLINE_TABLE_MOVE" of type

"PROCEDURE" having compatible arguments was found. SQLSTATE=42884

and when using the same syntax within a .sql script receive the error:

jq03a010:db2wad 58> ./onlinemove.sql

./onlinemove.sql: Syntax error at line 1: `(' not expected.

Instead of having to use the ADMIN_TABLE_MOVE procedure, can we use DB6CONV to move special flag "VBDATA" VARCHAR(30000) FOR BIT DATA ', as shown in the script below:

call saptools.online_table_move(

'SAPWAD',

'VBDATA',

'WAD#VBDATAD',

'WAD#VBDATAI',

'',

'',

'',

'',

'"VBKEY" VARCHAR(96) NOT NULL WITH DEFAULT '' '' ,

"VBMODCNT" INTEGER NOT NULL WITH DEFAULT 0 ,

"VBBLKNO" INTEGER NOT NULL WITH DEFAULT 0 ,

"VBLEN" SMALLINT NOT NULL WITH DEFAULT 0 ,

"VBDATA" VARCHAR(30000) FOR BIT DATA ',

'MOVE')

;

View Entire Topic
Former Member
0 Likes

With this error from SE38 report DB6CONV;

SQL2104N  The ADMIN_MOVE_TABLE procedure could not be completed

at this time by this user.  Reason code: "9".  SQLSTATE=5UA0M

Answer is: select the failed tables one-by-one, and click on the RESET button, then select the main job of the Tablespace and click on RESET button. Then select all the entries and DELETE them.

Click on the "New Conversion" button to reprocess the failed entries. Select the source and target Tablespace, then the target Index and L. Choose the Online radio button and SAVE. Now the tables are being reprossesed, problem solved.

Cheers, Kabelo T.