|Within the section titled "Managing the Database Buffer Pool", add |the following information after the paragraph that begins "When creating |the buffer pool, by default the page size is 4 KB.":
|When working with Windows 2000, buffer pool sizes up to 64 GB in size are |supported less the size of DB2 and the operating system. (This assumes that |DB2 is the primary product on the system.) This support is available through |Microsoft Address Windowing Extensions (AWE).
|Although AWE can be used with buffer pools of any size, if you require |AWE use on larger buffer pools there are other recommended Windows products. |Windows 2000 Advanced Server provides support for up to 8 GB of memory. Windows |2000 Data Center Server provides support for up to 64 GB of memory.
|DB2 and Windows 2000 must be configured correctly to support AWE buffer |pools. The buffer pool that will take advantage of AWE must exist in the database.
|To have a 3 GB user space allocated, use the /3GB Windows 2000 boot |option. This allows a larger AWE window size to be used. To enable access |to more than 4 GB of memory via the AWE memory interface, use the /PAE |Windows 2000 boot option. To verify that you have the correct boot option |selected, under Control, select System, then select "Startup and Recovery". From the drop-down list you can see the available boot options. If the |boot option (/3GB or /PAE) you want is selected, then you are |ready to proceed to the next task in setting up AWE support. If the option |you want is not available for selection, you must add the option to the boot.ini |file on the system drive. The boot.ini file contains a list of actions to |be done when the operating system is started. Add /3GB, or /PAE, |or both (separated by blanks) at the end of the list of existing parameters. |Once you have saved this changed file, you can verify and select the correct |boot option as mentioned above.
|Windows 2000 also has to be modified to associate the "lock pages in |memory"-right with the user under which DB2 is installed. To set the "lock pages in memory"-right, once you have logged on to Windows 2000 as |the user who installed DB2, under the Start menu on Windows 2000 select the "Administrative Tools" folder, and then the "Local Security Policy" |program. Under the local policies, you can select the user rights assignment |for the "lock pages in memory"-right.
|DB2 requires the setting of the DB2_AWE registry variable. To set this |registry variable correctly, you will need to know the buffer pool ID of the |buffer pool you wish to allow support of AWE. You also need to know the number |of physical pages and the address window pages to allocate. The number of |physical pages to allocate should be some value less than the total available |physical pages. The actual number chosen will depend on your working environment. |For example, if you have an environment where only DB2 and database applications |are used on your system, then you can choose to have from one-half to one |GB less than the total size of the physical pages as the value used with the |DB2_AWE variable. If you have an environment where other non-database applications |are using the system, then you will have to increase the value you subtract |from the total to allow more physical pages for those other applications. |The number used in the DB2_AWE registry variable is the number of physical |pages to be used in support of AWE and for use by DB2. The upper limit on |the address window pages is 1.5 GB, or 2.5 GB when the /3GB Windows 2000 boot option is in effect.
|For information on setting the DB2 registry variable DB2_AWE, see the table |of new and changed registry variables in "Appendix A. DB2 Registry and |Environment Variables" later in this section.
|Within the section titled "Managing Multiple Database Buffer Pools", |add the following paragraph after the paragraph that begins "When working |with your database design, you may have determined that tables with 8 KB page |sizes are best.":
|When working with Windows 2000, the DB2_AWE registry variable can be used |to override the buffer pool size settings in the catalog and configuration |files. Use of this registry variable allows buffer pool sizes of up to approximately |64 GB.
|Within the same section, replace the paragraph just before the note with |the following:
|The reason for allowing the database manager to start with minimal-sized |values is to allow you to connect to the database. You can then reconfigure |the buffer pool sizes, or perform other critical tasks, with the goal of |restarting the database with correct buffer pool sizes. Do not consider operating |the database for an extended time in such a state.
|Within the section titled "Reorganizing Catalogs and User Tables", |the last sentence (with a short list) in the paragraph that begins "The |REORG utility allows you to specify a temporary table space..." |can be replaced by:
|Using the same table space to reorganize tables is faster but greater logging |occurs and there must be enough space for the reorganized table. If you |specify a temporary table space, it is generally recommended that you specify |an SMS temporary table space. A DMS temporary table space is not recommended |since you can only have on REORG in progress using this type of table space.
|Within the section titled "Extending Memory", add the following paragraph |after the third paragraph in this section:
|When allocating Windows 2000 Address Windowing Extensions (AWE) buffer |pools using the DB2_AWE registry variable, the extended storage cache cannot |be used.