2520447 - DB6: How to check/ recreate the temporary tablespaces when not available

You find the following temporary tablespaces are offline, or the temporary tablespaces have become full.
You want to recreate them.
You want to bring them back online.

PSAPTEMP16
SYSTOOLSTMPSPACE

For the offline status checks, run following command:

db2 list tablespaces show detail

 Tablespace ID                     = 1
 Name                                 = PSAPTEMP16
 Type                                 = System managed space
 Contents                             = System Temporary data
 State                                = 0x'00004000'
Detailed explanation:
 Offline
    
 Tablespace ID                       = 2
 Name                                 = SYSTOOLSTMPSPACE
 Type                                 = System managed space
 Contents                             = User Temporary data
 State                                 = 0x'00004000'
 Detailed explanation:
Offline

Scenario 1: Offline Example:

You may get various errors due to this offline status. For example
- Backup fails with SQL2048N Reason code: "6".
- SQL1585N A temporary table could not be created because there is no available system temporary table space that has a compatible page size.
- Underlying File system maintenance or disk move, mounted file system incorrectly mounted.
- Incorrect permissions on the file system level paths.

Scenario 2: Temporary tablespace full example:

• SP update log (deploy_api.1.log)
  
  message="[jcc][103][10843][4.19.49] Non-recoverable chain-breaking exception occurred during batch processing.
  The batch is terminated non-atomically. ERRORCODE=-4225, SQLSTATE=null";
  SQL statement is "INSERT INTO "J2EE_CONFIGENTRY"("CID","NAMEHASH","NAME","DTYPE","FBLOB","ISFILE") VALUES(?, ?, ?, ?, ?, 1)".
  [EXCEPTION]com.ibm.db2.jcc.am.SqlException: [jcc][103][10843][4.19.49] Non-recoverable chain-breaking exception occurred during batch processing. The batch is terminated non-atomically. ERRORCODE=-4225, SQLSTATE=null
• MESSAGE : ADM6017E The following table space is full. 
  Table space name:"PSAPTEMP16".
  Table space identifier: "3". Container path:
  "/db2/<SID>/<temp_directory>/db2<SID>/NODE0000/<SID>/T0000003/C0000002.TMP". Container identifier: "2".
  
  
  

Scenario 3: Container not accessible.


The db2diag.log may contain errors such as "PSAPTEMP16 and SYSTOOLSTMPSPACE" containers not accessible.  
Examples 

• 2025-11-03-13.36.56.980055+120 I119831607A525       LEVEL: Error
  PID     : 16185                TID : 1              PROC : db2dart
  INSTANCE: db2<SID>               NODE : 000
  HOSTNAME: XXXXXXXXX
  EDUID   : 1
  FUNCTION: DB2 UDB, buffer pool services, sqlbSMSDoContainerOp, probe:815
  MESSAGE : ZRC=0x8402001E=-2080243682=SQLB_CONTAINER_NOT_ACCESSIBLE
            "Container not accessible"
  DATA #1 : <preformatted>
  Error checking container 0 (/db2/<SID>/sapdata5/db2<SID>/NODE0000/<SID>/T0000003/C0000000.TMP) for tbsp 3.  Rc = 870F0011
• 2025-11-03-13.36.56.981018+120 I119832133A381       LEVEL: Error
  PID     : 16185                TID : 1              PROC : db2dart
  INSTANCE: db2<SID>               NODE : 000
  HOSTNAME: XXXXXXXXX
  EDUID   : 1
  FUNCTION: DB2 UDB, buffer pool services, sqlbSMSStartPool, probe:6960
  MESSAGE : ZRC=0x8402001E=-2080243682=SQLB_CONTAINER_NOT_ACCESSIBLE
            "Container not accessible"
• 2025-11-03-13.36.56.981226+120 E119832515A464       LEVEL: Error
  PID     : 16185                TID : 1              PROC : db2dart
  INSTANCE: db2<SID>               NODE : 000
  HOSTNAME: XXXXXXXXX
  EDUID   : 1
  FUNCTION: DB2 UDB, buffer pool services, sqlbStartPools, probe:2404
  MESSAGE : ADM6023I  The table space "PSAPTEMP16" (ID "3") is in state 
            "0x00004000".  The table space cannot be accessed.  Refer to the 
            documentation for SQLCODE -290.
• 2025-11-03-13.36.56.982828+120 I119833482A525       LEVEL: Error
  PID     : 16185                TID : 1              PROC : db2dart
  INSTANCE: db2<SID>               NODE : 000
  HOSTNAME: XXXXXXXXX
  EDUID   : 1
  FUNCTION: DB2 UDB, buffer pool services, sqlbSMSDoContainerOp, probe:815
  MESSAGE : ZRC=0x8402001E=-2080243682=SQLB_CONTAINER_NOT_ACCESSIBLE
            "Container not accessible"
  DATA #1 : <preformatted>
  Error checking container 0 (/db2/<SID>/sapdata5/db2<SID>/NODE0000/<SID>/T0000004/C0000000.UTM) for tbsp 4.  Rc = 870F0011
  80243682=SQLB_CONTAINER_NOT_ACCESSIBLE
            "Container not accessible"
• 2025-11-03-13.36.56.983240+120 E119834390A470       LEVEL: Error
  PID     : 16185                TID : 1              PROC : db2dart
  INSTANCE: db2<SID>               NODE : 000
  HOSTNAME: XXXXXXXXX
  EDUID   : 1
  FUNCTION: DB2 UDB, buffer pool services, sqlbStartPools, probe:2404
  MESSAGE : ADM6023I  The table space "SYSTOOLSTMPSPACE" (ID "4") is in state 
            "0x00004000".  The table space cannot be accessed.  Refer to the 
            documentation for SQLCODE -290.

SAP on IBM Db2 for Linux, UNIX, and Windows

• Database is using automatic storage

Offline, PSAPTEMP16, SYSTOOLSTMPSPACE, SQL1585N, recreate, SUM, upgrade, installation, ABAP, API, Deploy, J2EE_CONFIGENTRY, ERRORCODE=-4225, offline,psaptemp16,systoolstmpspace,sql1585n, Container not accessible. db2 list tablespaces.  , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , BC-DB-DB6-DBA , Database Administration , How To