Content

Notes

Please 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-4319

DB

Remove redundant column 'svc_cluster_id'  from perfind_vdisk_tx, optimize indexes

BVQ-7792AlertingMake VDisk copy sync state alertable
BVQ-7793GUIList view: VDisk copy: integrate 'sync state'

Bug fixes

Critical

Issue ID

Module

Description

BVQ-7716

GUI

Sometimes start takes extremely long time in environments with DB2 10.5 FP3

BVQ-7721

Scheduler

 In some environments recalc of the T0 indicators is starting unsteadily or only after a too long time

BVQ-7901SchedulerPerformance data cleanup: MDC ROLLOUT MODE DEFERRED is not supported
BVQ-7995SchedulerDouble call of reorg stop commands

Important

Issue ID

Module

Description

BVQ-7842

GUI

Alerting editor: NPE during creation of the report config in the GUI

BVQ-7852

GUI

Performance view: VDisk: metric cache size (CM, CV) is incorrectly calculated at interval widening

BVQ-7867ReportingReports / DB schema: Einige Custom Reports laufen als Folge der Anpassungen aus BVQ-4319 nicht mehr
BVQ-7890GUIPerfView: Node port: Falsche PortID Detection für V3700 / V5000
BVQ-7891GUI / ReportingCommon Installer: GUI / Reporting Heap Size und Start Menü Folder wird nicht übernommen
BVQ-7902AlertingFür INTBOOLEAN Wert können keine Alert conditions angelegt werden

Issue ID

Module

Description

BVQ-7840

DBSetup

Customize numbering of the installation steps

BVQ-7856

Scheduler

Installer: service name password not yet 'P@ssw0rd' as default

Known problems

Issue ID

Module

Description

IBM PMR 91765,033,724SVC 6.2.0.3Starke Beeinträchtigung der VDisk Latenz durch den SVC CLI Befehl "lsmdiskextent". Gesehen bei einem Cluster mit 8 Nodes (8G4) unter 6.1.0.4.
Ab BVQ 2.4.3 wird dieser Befehl nicht weiter genutzt. Stattdessen wird lsvdiskextent verwendet.

IBM PMR
unknown

SVC 6.4.0.3

Massiv gehäuftes Erreichen des SVC Limits von 10 gleichzeitig konkurrierenden SSH Sessions, kann einen Warmstart der Knoten auslösen.
Fixed seit 6.4.1.3

BVQ-6610BVQ VMwareMultiple Mappings einer VM Virtual Disk (und/oder unterschiedlicher Snapshot-Versionen einer einzelnen) zu einer VM Virtual Machine werden noch nicht unterstützt.
Die kommt z.B. bei Flash Copy Managern wie TSM4VE vor.
BVQ-6623BVQ VMwareScan und Anzeige von Snapshots und deren Kapazitäten werden von BVQ noch nicht unterstützt. Die Used Capacity eine VM Virtual Disk entspricht derzeit der Used Capacity der Original VMDK Datei.
IBM PMR ?SVC Performance Stats

Ab Version 6.1.0.1 beziehen sich SLAV, PLAV und DLAV auf die konsolidierten Backend IO sizes bis zu 256k. Nicht aber die IO-Counter für CTRM und CTP, was dazu führt, daß deren Quotient um den Faktor 8 zu niedrig ausfallen kann. Daher können die VDisk below cache Metriken SLAV und PLAV nicht mehr direkt zur Beurteilung der Backend Latencies verwendet werden. Auch deren Transaction size ist nicht die des Backends (max 32k).

CTD hingegen wurde auf die konsolidierten IO sizes angepasst und liefert weiterhin brauchbare Werte.

DB schema changes

Version
Tables
Description
3.1.2.1N/ASchema-update marking
3.1.2.2PEFIND_VDISK_T0BVQ-4319: redundant column 'svc_cluster_id' deleted . Improved indices
3.1.2.3PERFIND_VDISK_T1BVQ-4319: redundant column 'svc_cluster_id' deleted  . Improved indices
3.1.2.4PERFIND_VDISK_T2BVQ-4319: redundant column 'svc_cluster_id' deleted. Improved indices
3.1.2.5PERFIND_VDISK_T3BVQ-4319: redundant column 'svc_cluster_id' deleted  . Indexe verbessert
3.1.2.6ALERT_*BVQ-7902: adjustments to the alert tables
3.1.2.7v_PERFIND_VDISK_*_CURBVQ-7867: adjustments to the VDisk CUR views

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 FP2

Java Runtime minimum version
1.7.0.55

More information

Please see release notes for BVQ V3.1.1  

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

Update 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 .

 

  1. Preparations
    • Checking for correct function of the environment, in particular function of the scanner.
    • Manual stop of BVQ Scanner and Alerting-service, Scheduler-services and also of all GUIs and reporting-clients
    • Backup of BVQ installation directory and BVQ DB (e.g. DB offline backup with DB2 CMD) 
    • Starting again the BVQ Scanner
  2. Update BVQ Install Package Repository: bvq-package-repository-installer-x64-V3.1.2.exe
    1. DB Schema update
    2. BVQ GUI update
    3. BVQ Reporting Engine update
    4. BVQ Report Module update
    5. BVQ SVC Scanner update (warning)*
    6. BVQ VMware Scanner update
    7. BVQ Scheduler update
    8. BVQ Alerting update
  3. Performing functional tests
  4. If necessary inform colleagues about the need to update locally installed BVQ GUI / report clients.    

PDF Version

Page viewed times