Versions Compared

Old Version 10

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Norman Eichelbaum

Saved on

Key

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

...

Note
titlePlease note

Starting with version 3.0 the upgrade from DB2 to version 10.5 FP2 FP5 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. 

...

Issue ID

Module

Description

BVQ-8402

GUI

Docking: Sobald im Main Window keinen Tab mehr offen ist, lässt sich kein Tab aus bestehenden Undock-Main-Windows heraus in das Main Window ziehenwhen all tabs are closed in the main window,  no tabs from the existing undock main windows can be pulled out into the main window anymore

BVQ-8403

GUI

Docking: X-Button: Zieht man einen Tab per D&D aus dem Main Window heraus, so entsteht ein Undock-Main-Window ohne X-Buttonbutton: when a tab is taken with D&D out from the main window , a undock main window without X button is produced

BVQ-8404

GUI

Docking: X-Button: Sobald im Undock-Main-Windows ein neuer Tab per +-Button erzeugt wird. Nach dem Wechseln des Input-Focus erscheint dieser wiederbutton: when a new tab is created via '+' button in the undock main windows. It reappears after changing the input focus

BVQ-8440

GUI

Performance -Ansichtview: Optionsoptions: Objektliste: Remove eines visible Objektes führt zur Visibility des Oberstenobject list: remove of a visible object causes the visibility of the uppermost

BVQ-8490

GUIFavoriten

: Rename Favorite wirkt sich nicht auf den Namen in Add Favorite ausFavorites: rename favorite has no effect on the name in add favorite.

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 Statsperformance stats

CPT, OPT, APT much too high
BVQ-8602GUI Nodes of models V7000-100, V7000-300, V3700 are not properly differentiated because of the same node type 300 - fix expected in BVQ V3.4
BVQ-8589SVC ScannerBei InV7000-300 Systemen haben systems FC - und SAS-Ports die gleiche and SAS ports have the same WWPN. Primary Key verletzt. Daher wurden SAS Ports komplett aus key is not properly implemented. Therefore SAS ports were completely removed from BVQ 3.3.2 entfernt. Fix erwartet expected in BVQ V3.3.3

DB schema changes

Version
Tables
Description
3.3.0.19PERF_SVC_NODE_PORTMigsript adapted also for V5000 ports

...

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 Advanced Workgroup Server Edition V10.5 FP4FP5
Filename: v10.5fp5_ntx64_server_t.exe

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

More information

Please see release notes für BVQ V3.3.1 

...

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

...