The update SQL used in ADMIN_MOVE_TABLE is not using parameter
markers, causing many statements in the package cache.
The impact is minimal, but can cause many entries in the package
cache:
$ db2 get snapshot for dynamic sql on $sid | grep OTM_SEM | wc
-l
253
e.g.
Statement text = UPDATE
SYSTOOLS.OTM_SEMAPHORE_TABLE SET (VALUE,TABSCHEMA,TABNAME) =
('SEM_LOCK','DB2INST1','TABLE01') WHERE VALUE = 'SEM_UNLOCK' AND
SEM_NAME = ? WITH RR
Statement text = UPDATE
SYSTOOLS.OTM_SEMAPHORE_TABLE SET (VALUE,TABSCHEMA,TABNAME) =
('SEM_LOCK','DB2INST1','TABLE02') WHERE VALUE = 'SEM_UNLOCK' AND
SEM_NAME = ? WITH RR
Statement text = UPDATE
SYSTOOLS.OTM_SEMAPHORE_TABLE SET (VALUE,TABSCHEMA,TABNAME) =
('SEM_LOCK','DB2INST1','TABLE03') WHERE VALUE = 'SEM_UNLOCK' AND
SEM_NAME = ? WITH RR
Statement text = UPDATE
SYSTOOLS.OTM_SEMAPHORE_TABLE SET (VALUE,TABSCHEMA,TABNAME) =
('SEM_LOCK','DB2INST1','TABLE04') WHERE VALUE = 'SEM_UNLOCK' AND
SEM_NAME = ? WITH RR
Statement text = UPDATE
SYSTOOLS.OTM_SEMAPHORE_TABLE SET (VALUE,TABSCHEMA,TABNAME) =
('SEM_LOCK','DB2INST1','TABLE05') WHERE VALUE = 'SEM_UNLOCK' AND
SEM_NAME = ? WITH RR
Statement text = UPDATE
SYSTOOLS.OTM_SEMAPHORE_TABLE SET (VALUE,TABSCHEMA,TABNAME) =
('SEM_LOCK','DB2INST1','TABLE06') WHERE VALUE = 'SEM_UNLOCK' AND
SEM_NAME = ? WITH RR
Statement text = UPDATE
SYSTOOLS.OTM_SEMAPHORE_TABLE SET (VALUE,TABSCHEMA,TABNAME) =
('SEM_LOCK','DB2INST1','TABLE07') WHERE VALUE = 'SEM_UNLOCK' AND
SEM_NAME = ? WITH RR
Statement text = UPDATE
SYSTOOLS.OTM_SEMAPHORE_TABLE SET (VALUE,TABSCHEMA,TABNAME) =
('SEM_LOCK','DB2INST1','TABLE08') WHERE VALUE = 'SEM_UNLOCK' AND
SEM_NAME = ? WITH RR
Statement text = UPDATE
SYSTOOLS.OTM_SEMAPHORE_TABLE SET (VALUE,TABSCHEMA,TABNAME) =
('SEM_LOCK','DB2INST1','TABLE09') WHERE VALUE = 'SEM_UNLOCK' AND
SEM_NAME = ? WITH RR
Statement text = UPDATE
SYSTOOLS.OTM_SEMAPHORE_TABLE SET (VALUE,TABSCHEMA,TABNAME) =
('SEM_LOCK','DB2INST1','TABLE10') WHERE VALUE = 'SEM_UNLOCK' AND
SEM_NAME = ? WITH RR |
