Verifying Tablespace Size

Complete this procedure to increase the tablespace size of your DB2 for Linux, Windows, and UNIX database.

  1. In the DB2 for Linux, Windows, and UNIX Control Center, look at the size of the business data 32K tablespace for the environment your are upgrading, for example PRODDTAT32K for PROD.

  2. Look at the number of blocks used in that tablespace and convert to MB by dividing by 32. (For our shipped demo data, the number of blocks used is 352 and this corresponds to 11MB.)

  3. Increase the size of the CTLI tablespace (for example, PRODCTLI) by at least that amount to accommodate the intermediate table F00165T used during F00165 conversion. This can be done by adding an additional container through the Control Center (all containers for one tablespace must be the same size), or by signing onto the Enterprise Server as the instance owner, connecting to the environment database, and extending the tablespace container size as follows (substituting your database_name):

    DB2 connect to database_name
    DB2 alter tablespace PRODCTLI EXTEND (ALL 11M)
    

    Substitute the database name for the environment you are upgrading, the correct tablespace name and the correct number of MB. If you have made extensive use of Media Objects, you will have used more space in the xDTAT32K tablespace.

  4. Increase the size of the DTAT4K tablespace by the same amount. This is to accommodate the converted F00165 table.

    Additionally, you should increase the size of the xxxDTAT4K and DTAI tablespaces to accommodate an extra copy of your largest tables.

    If upgrading the DEV environment, make sure you have enough spare space in the OW_DEV tablespaces to accommodate the demo data, which is much larger than it was in previous releases. Look at the script ow_dev_tbsp.unxow_dev_tbsp.nt and increase the tablespaces accordingly.