Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Notes

Note
titlePlease note

Starting with version 3.0 the upgrade from DB2 to version 10.5 FP2 is mandatory.
Please download first this DB2 version from the IBM website and then perform the upgrade. For instructions, please see the following document: DB2 upgrade from version 9.7.4 or higher to 10.5.

 
From version 2.9 a new license file is recommended.
Continued use of the old license file is also possible. In this case, new features will appear as 'Missing' in the license dialog and are thus deactivated. Otherwise the function of BVQ is not affected. 

Highlights

Bugfix release

Improvements

Issue ID

Module

Description

BVQ-8411

GUI

Cluster selection dialog: show SVC code level and modify default sorting

Bug fixes

Critical

Issue ID

Module

Description

BVQ-8459

DB schema migration

Migscript 3.3.0.20 for table PERF_SVC_NODE_PORT sometimes fails

This means that no node port stats are recognized anymore and the directory BVQ-scanner/iostat/instanceX/error is filled up.

BVQ-8460

DB schema migration

Some run-time errors during the execution of mig scripts in DB2CMD are ignored.

Important

Issue ID

Module

Description

BVQ-8392

GUI

Treemap search: several selected objects from different levels lead to an exception

BVQ-8413

GUI

JDBC connection timeouts during slow connections

BVQ-8415

GUI

Performance view: node CPU core metric tooltip doesn't show core ID

Issue ID

Module

Description

BVQ-8410

GUI

Performance view: show VDisk & VDiskCopy cannot be opened with IO group

BVQ-8418

GUI

Performance view: Node2Node: inconsistent tab name und perf-view options window title

Known problems

Issue ID

Module

Description

IBM PMR 91765,033,724SVC 6.2.0.3Severe impairment of the VDisk latency by the SVC CLI command 'lsmdiskextent'. Seen at a cluster with 8 nodes (8G4) under 6.1.0.4.
Starting with BVQ 2.4.3 this command is not used anymore. Instead command 'Isvdiskextent' is used. 
IBM PMR
unknown
SVC 6.4.0.3

Massive accumulation of reaching the SVC limit of 10 simultaneously competitive SSH sessions can trigger a warm restart of the node.
Fixed with 6.4.1.3

BVQ-6610BVQ VMwareMultiple mappings of a VM virtual disk (and/or of different snapshot versions of a single VM) to a VM virtual machine are not supported yet.      
This happens for example with flash copy managers like TSM4VE. 
BVQ-6623BVQ VMwareScan and representation snapshots and thier capacities are not yet supported by BVQ. The 'Used Capacity' of a VM Virtual Disk corresponds currently to the 'Used Capacity' of the original VMDK file 
IBM PMR ?SVC performance stats

Starting with version 6.1.0.1  SLAV, PLAV and DLAV refer to the consolidated backend IO sizes of up to 256k. But not the IO-counter for CTRM and CTP, which means that their quotient may be too low by a factor of 8. Therefore, the VDisk below   cache metrics SLAV and PLAV cannot be used directly to assess the backend latencies. Also their transaction size is not the same of the backend (max 32k).

However, CTD was adapted to the consolidated IO sizes and provides continuously useful values.

IBM PMR ?SVC 7.3
performance stats
Legacy VDisk cache statistics corrupted
IBM PMR ?SVC 7.3
performance stats
Node CPU Core stats =0
IBM defect 197194

SVC 7.3 Performance Stats

CPT, OPT, APT much too high

DB schema changes

Version
Tables
Description
3.3.0.20PERF_SVC_NODE_PORTImproved order of the RENAME TABLE in the script for BVQ-8459

Requirements and restrictions

Requirements of the HW/SW environment

Please see supported environments since BVQ 3.0

Minimum BVQ version required for an update

V2.7

DB2 version

DB2 Express V10.5 FP4

Java Runtime minimum version1.7.0.71 (Java 1.8 not supported)

More information

Please see release notes für BVQ V3.3  

Notes

  • When configuring a topology scanner interval >30 min an adaptation in a GUI configuration file is necessary, concerning the scanner status checks. In this case please contact BVQ support.  
  • The Excel format generated by the BVQ Reporting is compatible with the Excel version of 2003 and higher.  
    This is the format 'XML spreadsheet 2003' (please see this Microsoft article for more information).
    The standard file extension for this format is '.xml'. If it is despite  saved with '.xls', a warning message appears when it is openend with Excel.
  • License changes only take effect after about 2 hours or after restarting the scanner and scheduler.
  • Currently not supported VMware functions:
    • Partitioned VM SCSI volumes, whose partitions are assigned to multiple VM datastores.
    • VM SCSI volumes whose UUIDs are not unique.

Summary: update steps

Warning
titleUpdate references
  1. (warning)* For an upgrade of BVQ Scanner from version 2.7 to 2.8 or higher should be noted that now a VMware Scanner can exist besides the SVC Scanner. Therefore, it is installed in a new default directory bvq-svc-scanner (previously  bvq-scanner). To use the existing scanner configuration again, the update should be proceeded as follows before performing update step 3:
    1. Stop BVQ Scanner services manually
    2. Rename directory bvq-scanner in bvq-svc-scanner
    3. Continue with update step 3.
  2. Before possibly new functions can be used, a new license file is required. 
    After the import of the new license the GUI has to be restarted.
  3. The GUI is delivered with new predefined favorites. Only favorites from User favorites are retained.   

We recommend to follow the sequence of update steps shown below.

...