Check and Configure Available Space

During conversion, Dynamic Server drops and then recreates the sysmaster database. Depending on which version of Dynamic Server you convert from, the Version 10.0 sysmaster database can be significantly larger.

Partition header pages should not be full; key descriptors will occupy slightly more space after conversion to Dynamic Server 10.0. Use the oncheck -me command to compress extents and reduce the amount of storage used in partition headers.

The root chunk should contain at least ten percent (10%) free space when converting to Dynamic Server 10.0.

In some cases, even if the database server conversion is successful, internal conversion of some databases might fail because of insufficient space for system catalog tables. For more information, see the release notes for this version of Dynamic Server.

You need to add any additional free space to the system prior to the conversion. If the dbspaces are nearly full, you need to add space before you start the conversion procedure. When you initialize Dynamic Server 10.0 on the same root dbspace of the earlier database server, Dynamic Server 10.0 automatically converts the sysmaster database and then each database individually. For a successful conversion of each database, ensure that 2000 kilobytes of free space per database is available in each dbspace.

Use the following SQL statements to determine the free space that each dbspace requires and the free space available. These statements return the free-space calculation in page-size units. The free_space_req column value is the free-space requirement, and the free_space_avail column value is the free space available.

The following SQL statement shows how to determine the free space that each dbspace requires:

DATABASE sysmaster;
SELECT partdbsnum(partnum) dbspace_num, 
       trunc(count(*) * 2000) free_space_req 
   FROM sysdatabases 
GROUP BY 1 
ORDER BY 1;

The following SQL statement queries the syschunks table and displays the free space available for each dbspace:

SELECT dbsnum dbspace_num, sum(nfree) free_space_avail
   FROM syschunks 
GROUP BY 1 
ORDER BY 1;

The dbspace estimates could be higher if you have an unusually large number of SPL routines or indexes in the database.