DB2 is no longer your heart disease

The following article mainly tells you about the correct cracking solution for the DB2 component system, in order to better describe it, we will give a more detailed introduction to the method of listing error cases for cracking. The following is a detailed description of the main content of the article. We hope you will have a better understanding of it after browsing.

Case study:

Create a 20 GB tablespace In the DB2 database of the AIX system. The specific SQL statement is as follows:

 
 

  
  
CREATE REGULAR TABLESPACE HTDC_DATA PAGESIZE 8 K MANAGED BY DATABASE  
  
  
USING ( FILE ’/db2_tag/TABLE_SPACES/HTDC_DATA/HTDC_DATA.dat’ 20G)  
  
  
EXTENTSIZE 16 OVERHEAD 10.67 PREFETCHSIZE 16 TRANSFERRATE 0.04  
  
  
BUFFERPOOL BPHTDC  
  
  
DROPPED TABLE RECOVERY OFF  
 
 

Error code: SQLCODE 0968C

Error message: File System is full. (DB2 File System is full)

Cause: the maximum file size allowed by the current user identity is exceeded.

Solution:

Log on to the AIX Terminal

 
 

  
  
telnet IPAddress 
 
 

Enter System

 
 

  
  
root  
  
  
PassWord  
 
 

Switch user to db2admin

 
 

  
  
Su-db2admin
  
  
PassWord
  
  
Change the fsize to 100 GB (209715100 bytes)
 
 

Chuser fsize = 209715100 db2admin

Restart the computer

Shutdown-Fr

Log on to the system again and switch the user to db2admin.

 
 

  
  
su - db2admin  
  
  
PassWord  
  
  
db2start  
  
  
db2  
  
  
connect to HTDC user db2admin using ******  
  
  
CREATE REGULAR TABLESPACE HTDC_DATA PAGESIZE 8 K MANAGED BY DATABASE  
  
  
USING ( FILE ’/db2_tag/TABLE_SPACES/HTDC_DATA/HTDC_DATA.dat’ 20G)  
  
  
EXTENTSIZE 16 OVERHEAD 10.67 PREFETCHSIZE 16 TRANSFERRATE 0.04  
  
  
BUFFERPOOL BPHTDC  
  
  
DROPPED TABLE RECOVERY OFF  
 
 

The above content is an introduction to the solution to the problem of the DB2 file system being full. I hope you will have some gains.