Buffer Pool Analyzer messages (BPOK)
This topic lists and describes all Buffer Pool Analyzer client messages and describes possible user responses.
Related reading: For messages regarding the Buffer Pool Analysis function of IBM® Tivoli® OMEGAMON® XE for DB2® Performance Expert on z/OS® refer to IBM Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS; IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS: Messages.
- BPOK5000
The bpd file does not contain all required information. - BPOK5001
The size for one or more objects is unknown. - BPOK5002
One or more objects are not placed correctly. - BPOK5003
The value supplied for {0} is not a valid decimal number. - BPOK5004
Negative numbers are not allowed for total sizes. This applies to buffer pools and hiperpools. - BPOK5005
The sum of virtual and hiperpool sizes cannot be zero. - BPOK5006
The program cannot process the data. - BPOK5007
The directory {0} does not exist. - BPOK5008
No data view selected. - BPOK5009
The file that you opened is corrupted. - BPOK5010
The file that you opened is corrupted. - BPOK5011
The value supplied for {0} is not a valid integer. - BPOK5012
The value supplied for {0} is out of range. - BPOK5013
The relation between the minimum and the maximum value is incorrect. - BPOK5014
Do you want to save your changed pattern file? - BPOK5015
One or more values of the characteristics data are not valid. - BPOK5017
All data values in the requested data view are zero. - BPOK5018
Do you want to permanently delete the report? - BPOK5023
The system is out of memory. - BPOK5024
Sorting by table headers will be disabled. A very large number of objects are displayed and sorting would be slow. - BPOK5033
The buffer pool data file is not compatible. - BPOK5034
Parsing of buffer pool data file failed. - BPOK5035
No entry from list of recommended patterns is selected. - BPOK5036
No entry from list of user-defined patterns is selected. - BPOK5037
No write access to {0}. - BPOK5038
The bpd files do not contain any data about DB2 table spaces or indexes that can be used for the DBID/OBID translation. - BPOK5100
Incorrect file transfer mode ASCII was used. - BPOK5101
Invalid Collect Report Data record format used. - BPOK5102
Invalid file type. - BPOK5103
Invalid file type and incorrect file transfer mode ASCII was used. - BPOK5104
Invalid file format. - BPOK5199
Unknown file format. - BPOK5800
Wrong date format. - BPOK5801
The start date is later than the begin date. - BPOK5802
One Date lies out of the recorded time frame. - BPOK5803
One of the selected files is not a bpd file. - BPOK5804
Parsing Process failed. - BPOK5805
File exists. New file name has been generated for the result. - BPOK5806
Invalid buffer pool name(s) {0} entered. - BPOK5902
The connection to CIMOM failed. - BPOK5903
The connection to the database failed. - BPOK5905
The access to CIMOM was disabled. - BPOK5906
The monitored DB2 instance is not active. - BPOK5907
The monitored DB2 instance is not started. - BPOK5908
An SQL error occurred. - BPOK6000
Internal buffer pool analysis error. - BPOK7000
The selected DB2 Connect gateway is currently not active. Switch to history mode and select a date and time at which the DB2 Connect gateway was active.
Parent topic: Troubleshooting and messages