
Signature
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany
>> Hi!
>>
[quoted text clipped - 11 lines]
> hidden). Now you can change the BP and re-activate the database with the
> new, reduced size.
We are on a 64-bit machine and Windows and when you connect to the database
the pagefile (Windows virtual memory) grows for Gbs and it takes almost an
hour for connect to succeed.
I just thought that there is a command like activate database with default
bufferpool :)))
Best regards,
Kovi

Signature
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Serge Rielau - 29 May 2007 14:39 GMT
>>> Hi!
>>>
[quoted text clipped - 16 lines]
> I just thought that there is a command like activate database with default
> bufferpool :)))
I pinged backstage and here is the recommendation:
DB2_OVERRIDE_BPF
Operating system: All
Default: not set, Values: a positive numeric number of pages OR
<entry>[;<entry>…] where <entry>=<buffer pool ID>,<number of pages>
This variable specifies the size of the buffer pool, in pages, to be
created at database activation, rollforward recovery, or crash recovery.
It is useful when memory constraints cause failures to occur during
database activation, rollforward recovery, or crash recovery. The memory
constraint could arise either in the rare case of a real memory shortage
or, because of the attempt by the database manager to allocate a large
buffer pool, in the case where there were inaccurately configured buffer
pools. For example, when even a minimal buffer pool of 16 pages is not
brought up by the database manager, try specifying a smaller number of
pages using this environment variable. The value given to this variable
overrides the current buffer pool size.
You can also use <entry>[;<entry>…] where <entry>=<buffer pool
ID>,<number of pages> to temporarily change the size of all or a subset
of the buffer pools so that they can start up.

Signature
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab