Symptom
- after db2 rename tablespace <SID>#POOLD to <SID>#POOLD2
- attempting to follow solution step 2.5 of SAP NOTE 1019242 - DB6: SQL0960C "maximum number of objects in tablespace"
and specify fully qualified container names in the CREATE TABLESPACE syntax
db2 " \
CREATE LARGE TABLESPACE "<SID>#POOLD" \
. . .
USING ( \
FILE '/db2/<SID>/sapdata/sapdata1/db2sid/NODE0000/SID/#POOLD.container000' 100, \
FILE '/db2/<SID>/sapdata/sapdata2/db2sid/NODE0000/SID/#POOLD.container001' 100, \
FILE '/db2/<SID>/sapdata/sapdata3/db2sid/NODE0000/SID/#POOLD.container002' 100, \
FILE '/db2/<SID>/sapdata/sapdata4/db2sid/NODE0000/SID/#POOLD.container003' 100 \
) \
. . .
"
- DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
SQL0294N The container is already in use. SQLSTATE=42730
Read more...
Environment
- Db2 Linux Unix Windows (LUW)
- SAP Netweaver
Product
Keywords
KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.