DB2 Server for VM: System Administration

Expanding the Database Directory

When a database is initially generated, a calculation is made to determine which portion of the directory will be set aside for the page map table, and which portion will be used for the allocation bitmaps. The size of the page map table determines the maximum number of DBSPACE pages, that is, the maximum logical size of the database. The size of the allocation bitmap determines the maximum number of dbextent pages, that is, the maximum physical size of the database. As the database grows in size with use, it may run short on either logical or physical space. If it is short on logical space, the ADD DBSPACE operation may fail. If it is short on physical space, the ADD DBEXTENT operation may fail. You can expand the directory to correct these situations.

Prior to SQL/DS Version 3 Release 5, the directory could be expanded to accomodate more logical pages by expanding the page map table. With SQL/DS Version 3 Release 5 and later, you can increase the size of the allocation bitmaps and the page map table concurrently. If it is necessary to expand the directory to hold more dbextent pages, the only available option would be to expand the directory for both dbspace and dbextent pages.

Use SQLCDBEX to increase:

The format is:

Figure 53. SQLCDBEX EXEC

>>-SQLCDBEX----Dbname(server_name)-----------------------------><

Dbname(server_name)

The DBNAME parameter is required. Any initial substring for DBNAME can be used as the keyword (for example, DB or D). For server_name, specify the name of the application server. (The name of the application server is defined when the SQLDBINS EXEC is started to generate the database.)

Figure 54 is an example of using SQLCDBEX to expand the directory to hold more dbspace and dbextent pages.

Figure 54. SQLCDBEX EXEC

sqlcdbex dbname(sqlvm350)
ARI0717I Start SQLCDBEX EXEC: 09/28/95 16:41:50 CET.
ARI0721I Get DB2 Server for VM production minidisk WRITE access: SQLDB350 195.
DASD 0195 LINKED R/W; R/O BY     2 USERS
 
ARI6102A Enter DBEXTENT number (or LOGDSK1, LOGDSK2,
         or BDISK) to copy.
         (Enter a null response to end input or
         enter QUIT to exit.)
bdisk
ARI6188A Enter the output block size of the directory.
         Enter 512 or 4096,
         or a null response to use the original size,
         or 111(Quit) to exit.
512
ARI6103A Enter virtual address for new BDISK.
         (Enter a null response to end input or
         enter QUIT to exit.)
300
DMSACP112S C(300) device error
ARI6148I New disk 300 has not been formatted. Program will continue
         to format the disk before copying.
ARI6146D Are you expanding the DB2 Server for VM directory?
         Enter 0(No), 1(Yes), or 111(Quit).
1
ARI6118I Formatting in progress. Please wait...
ARI6130I Disk 300 is formatted successfully.
ARI6200D You have requested to expand the directory.
         Enter 1 to expand the directory to hold more DBSPACE
         pages. Enter 2 to expand the directory to hold more
         DBSPACE and DBEXTENT pages. Enter 111 to quit.
         Enter 1,2 or 111(Quit).
2
ARI6198D Current maximum DBEXTENT pages: 1662976
         New maximum DBEXTENT pages: 2502656
         DBEXTENT pages added: 839680
         Current maximum DBSPACE pages: 3294592
         New maximum DBSPACE pages: 4964352
         DBSPACE pages added: 1669760
         Current directory size: 27362
         Current directory block size: 512
         New directory size: 41046
         New directory block size: 512
         Do you wish to continue with expanding the
         directory to allow the directory to hold
         additional DBEXTENT and DBSPACE pages ?
         Enter 0(No), 1(Yes) or 111(Quit)
1

ARI6131I Copying in progress. Please wait...
ARI0640I 4000 of
         41046 records copied to output disk.
ARI0640I 8000 of
         41046 records copied to output disk.
ARI0640I 12000 of
         41046 records copied to output disk.
ARI0640I 16000 of
         41046 records copied to output disk.
ARI0640I 20000 of
         41046 records copied to output disk.
ARI0640I 24000 of
         41046 records copied to output disk.
ARI0640I 28000 of
         41046 records copied to output disk.
ARI0640I 32000 of
         41046 records copied to output disk.
ARI0640I 36000 of
         41046 records copied to output disk.
ARI0640I 40000 of
         41046 records copied to output disk.
ARI6201I Directory expansion completed successfully.
         It is strongly recommended that a database
         archive be taken immediately.
ARI6108I Minidisk copied successfully. The SQLVM350 SQLFDEF file
         will be updated.
ARI6109I SQLVM350 SQLFDEF file has been updated on the A disk.
 
ARI6102A Enter DBEXTENT number (or LOGDSK1, LOGDSK2,
         or BDISK) to copy.
         (Enter a null response to end input or
         enter QUIT to exit.)
 
ARI0620I SQLVM350 SQLFDEF file
         successfully copied to production disk.
ARI0673I All COPY DBEXTENT processing completed successfully.
ARI0796I End SQLCDBEX EXEC: 09/28/95 17:11:35 CET
ARI0721I Get DB2 Server for VM production minidisk READ access: SQLDB350 195.
Ready; T=90.80/106.77 17:11:40

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]