28 January,2017 by Jack Vamvas
Question: During an application installation this error appeared on the db2diag log
ADM6017E The following table space is full. Table space name: "TEMPSPACE1". The underlying file system is full
There is very little flexibility about changing the application code and also very limited documentation – limiting my understanding of the amount of TEMPSPACE required.
Is there a quick way to workaround this problem?
Answer: There are workarounds to the disk is full error when requiring extra temp tablespace particular problem. Without knowing the details , I suspect it’s some sort of function hitting the data which is causing excessive requirement on the TEMPSPACE1 tablespace. The available disk is reaching a limit.
Your choices are to either a) expand the existing disk upon which the TEMPSPACE1 is hosted or b) Create a tempspace , on another larger disk.
To find out the path use Db2 list tablespaces show detail. The speak to the Linux Administrator \ Storage guys to expand the existing disk supporting the drive
If you’d prefer to create a TEMPSPACE on another drive follow these basic instructions. Customise for your own circumstances
1) provision another drive with sufficient space. In the example below – it’s X:\reorg_temp
2) Create TEMPORARY TABLESPACE . In the example below called MYTEMP
3) Execute the statements
4)Clean up the extra temp space and hand back disk to storage guys.
db2 "CREATE SYSTEM TEMPORARY TABLESPACE MYTEMP1 PAGESIZE 16K MANAGED BY SYSTEM USING ('X:\my_temp') BUFFERPOOL IBMDEFAULTBP DROPPED TABLE RECOVERY OFF" db2 force application all db2stop db2start db2 connect to MY_DB ---run some code --drop tablespace after using db2 "drop tablespace MYTEMP1"