Solution : https://service.sap.com/sap/support/notes/1019242 (SAP Service marketplace login required)
Summary :
SAP applications experience SQL error -960 during table creation when the DB2 tablespace object limit is reached, currently capped at approximately 5100 objects. The problem often arises post-system copy, potentially given multiple table categories (TABARTS) allocated to a single tablespace. SAP systems segregate TABARTS into various tablespaces by default, preventing this issue under standard operations stored in tables TADB6, IADB6, and TSDB6. IBM has no immediate plans to raise the object limit. The recommended workaround involves renaming affected tablespaces, creating new ones with identical properties, and realigning access rights to accommodate the new configuration.
Key words :
file '/db2/sid/sapdata1/node0000/psappooldnew, file '/db2/sid/sapdata1/node0000/psappoolinew, extentsize 2 prefetchsize automatic dropped table recovery, create tablespace psappooldin nodegroup sapnodegrp_sidmanaged, db2 rename tablespace psappoold, psappool2ddb2 rename tablespace psappooli, db2 node group, error code -960 occurs, assign access rights, create tablespace psappooli
Related Notes :
| 1250466 | DB6: Perform database administration, keeping SAP AS running |