HVR Release Life Cycle

From HVR
Jump to: navigation, search


Support duration for HVR releases

  • A major HVR release (e.g. HVR 5.0 or 4.6) is supported for 5 years from its General Availability (GA) release date.
  • A minor release (e.g. HVR 4.6.0) or an HVR patch (e.g. HVR 4.6.0/1 or HVR 4.6.0/1.1) does not prolong the support duration. For example if HVR 4.6 will expire at date X then that date will not be extended if HVR 4.6.2 is released a year later.
  • HVR offers “extended” support beyond these end-support dates. The duration of extended support is determined on a case-by-case basis.

The following shows release & support dates for the most recent five HVR versions:


HVR release GA release date End of support from HVR HVR support status
HVR 5.2 2017-07-19 2021-07-19 regular
HVR 5.1 2016-10-18 2021-10-18 regular
HVR 5.0 2016-04-20 2021-04-20 regular
HVR 4.7 2015-03-24 2020-03-24 regular
HVR 4.6 2014-04-30 2019-04-30 regular
HVR 4.5 2013-11-11 2018-11-11 regular
HVR 4.4 2012-07-17 2017-07-17 support ended
HVR 4.3 2010-05-21 2015-05-21 support ended

Compatibility between HVR versions


  • All supported HVR releases with the same initial number (e.g. HVR 5) are runtime compatible with each other. For example, if A, B, C and D are different supported HVR versions, then an HVR GUI running version A can be used to a hub machine running version B, which captures from a machine with version C and integrates to a machine with version D.
  • HVR versions with the same initial number are runtime compatible with older versions whose major release date was up to 5 years ago (the same as the support duration above), but compatibility with versions older than this is not maintained. For example HVR 4.7 is runtime compatible with HVR 4.4 but not with HVR 4.3 versions, because HVR 4.4 was still supported when HVR 4.7 was released, whereas HVR 4.3 was not.
  • Compatibility between HVR 4 and HVR 5 is more limited. HVR version 5 hub machines can talk to HVR 4 capture and integrate machines and vice versa (as long as HVR 5 features are not used). HVR version 5's GUI installations can talk to a remote HVR 4 hub, and will work with the old (HVR 4) actions. HVR version 4's GUI will connect to a remote HVR 5 hub, but with limited functionality.
  • When using a mix of HVR versions, note that each bug fix or feature is only effective if the correct machine is upgraded. For example, if a new HVR release fixes an integrate bug, then that release must be installed on the machine(s) which do integrate. So if only the GUI and/or hub machine is upgraded, then there will be no benefit. To decide whether each machines needs to be upgraded, see the descriptions in the release notes $HVR_HOME/hvr.rel. Each description ends with a line says which machine must be upgraded for that specific bug fix or feature to be effective.

Supported Operating System (OS) releases

  • The HVR release notes (in $HVR_HOME/hvr.rel) describe the supported OS versions (such as “Solaris for SPARC, version 9 and higher”) for each HVR release.
  • HVR only specifies the initial OS version; certification for subsequent OS versions (e.g. Solaris version 10) by HVR is automatic, due to OS supplier’s own forward compatibility guarantees.
  • Once an OS version is supported by HVR, support for that platform will continue until the OS supplier ends its “mainstream support”. After that date HVR support goes from “regular” to “sunset” support, which means that HVR support continues (including new HVR versions for it), but eventually it will be withdrawn without notice.
  • A customer may request that HVR makes support for an OS version “extended” instead of “sunset”, which means that support will not be withdrawn as long as the customer continues to share information about the production status of that OS version for the customer.
  • A consequence of the end of HVR support is that HVR is no longer able to supply patches for that OS version.

To see which OS releases are supported by HVR, please consult the HVR Platform Compatibility Matrix


The following shows the OS suppliers support status of specific OS versions as known by HVR.


OS version Release date

from supplier

End of mainstream

support from supplier

HVR support status
AIX 7.2 2015-12-01 2018-12-31 regular
AIX 7.1 2010-09-10 2019-12-31 regular
AIX 6.1 2008-09-12 2017-04-30 regular
AIX 5.3 2004-08-13 2012-04-30 sunset by IBM
AIX 5.2 2002-10-18 2009-04-30 sunset by IBM
HPUX Itanium 11.31 2007-01-02 2014-01-12 sunset by HP
HPUX Itanium 11.23 2003-01-10 2010-01-12 sunset by HP
Red Hat 7 2014-06-10 2024-06-10 regular
Red Hat 6 2010-10-11 2020-11-30 regular
Red Hat 5 2007-03-15 2017-03-31 regular
Red Hat 4 2005-02-14 2012-02-29 sunset by RedHat
SUSE ES 12 2014-10-27 2024-10-31 regular
SUSE ES 11 2009-03-24 2019-03-31 regular
SUSE ES 10 2006-06-17 2013-07-31 sunset by SUSE
SUSE ES 9 2004-03-08 2011-08-31 sunset by SUSE
Solaris 11 2011-01-11 2021-01-11 regular
Solaris 10 2005-01-01 2018-01-01 regular
Solaris 9 2002-01-03 2011-01-10 sunset by Oracle
Solaris 8 2000-01-02 2009-01-03 sunset by Oracle
Windows Server 2012 2012-10-30 2018-09-01 regular
Windows Server 2008 2008-12-29 2015-01-13 sunset by Microsoft
Windows Server 2003 2003-05-28 2010-07-13 sunset by Microsoft
Windows XP 2009-04-14 sunset by Microsoft
Windows Server 2000 2000-03-31 2005-06-30 sunset by Microsoft

Supported DBMS releases

  • The HVR release notes (in $HVR_HOME/hvr.rel) describe the supported DBMS versions (such as “Oracle: version 10.1, 10.2, 11.1 and 11.2”) for each HVR release. The list of supported DBMS versions is different for HVR on each OS platform.
  • Subsequent major versions of the DBMS (such as “Oracle 12”) are not automatically supported, but may be recertified by HVR after QA testing. But patches to a supported DBMS version are automatically supported by HVR (no recertification is done at patch level).
  • Once a DBMS version is supported by HVR on a given OS platform, support for that DBMS version will continue at least until the DBMS supplier ends its “mainstream support”. After that date HVR support goes from “regular” to “sunset” support, which means that HVR support continues (including new HVR versions for it), but eventually it will be withdrawn without notice.
  • A customer may request that HVR makes support for a DBMS version “extended” instead of “sunset”, which means that support will not be withdrawn as long as the customer continues to share information about the production status of that DBMS version for the customer.
  • A consequence of the end of HVR support is that HVR is no longer able to supply patches for that DBMS.

To see which DBMS releases are supported by HVR, please consult the HVR Platform Compatibility Matrix


The following shows the DBMS suppliers support status of specific DBMS versions as known by HVR.


DBMS version Release date

from supplier

End of mainstream

support from supplier

HVR support status
Oracle 12.1 2013-01-06 2018-01-07 regular
Oracle 11.2 2009-01-09 2016-01-01 regular
Oracle 11.1 2007-01-08 2012-01-08 sunset by Oracle
Oracle 10.2 2005-01-07 2010-01-07 sunset by Oracle
Oracle 10.1 2004-01-01 2009-01-01 sunset by Oracle
Oracle 9.2 2002-01-07 2007-01-07 sunset by Oracle
Oracle 8.1 2000-01-09 2004-01-12 sunset by Oracle
Ingres 10.2 regular
Ingres 10.1 2017-05-31 regular
Ingres 10.0 2016-12-31 regular
Ingres 9.2 2015-12-31 sunset by Actian
Ingres 9.1 2011-12-31 sunset by Actian
Ingres 9.0 2011-12-31 sunset by Actian
Ingres 3.0 2007-12-31 sunset by Actian
Ingres 2.6 2012-09-31 sunset by Actian
SQL Server-2016 2016-06-01 2021-07-13 regular
SQL Server 2014 2014-06-05 2019-06-05 regular
SQL Server 2012 2012-05-20 2017-11-07 regular
SQL Server 2008 2008-11-06 2014-08-07 sunset by Microsoft
SQL Server 2005 2006-01-14 2011-12-04 sunset by Microsoft
DB2 for i 7.2 2014-05-02 regular
DB2 for i 7.1 2010-04-23 regular
DB2 on LUW 10.5 2013-07-26 regular
DB2 on LUW 10.1 2012-06-11 regular
DB2 on LUW 9.8 2010-01-15 2015-01-05 sunset by IBM
DB2 on LUW 9.7 2010-11-19 2015-01-05 sunset by IBM
DB2 on LUW 9.5 2007-12-14 2014-01-05 sunset by IBM
DB2 on LUW 9.1 2006-06-22 2012-01-05 sunset by IBM


Analytic DBMS version Release date

from supplier

End of mainstream

support from supplier

HVR support status
Actian Matrix (Paraccel) 5.2/5.3 2017-12-31 regular
Actian Matrix (Paraccel) 5.0/5.1 2016-12-01 regular
Actian Matrix (Paraccel) 4.0 2015-07-01 sunset by Actian
Actian Vector (Vectorwise) 5.0 2017-12-31 regular
Actian Vector (Vectorwise) 4.0 2017-12-31 regular
Actian Vector (Vectorwise) 3.5 2014-03-31 2017-03-31 regular
Actian Vector (Vectorwise) 3.0 2013-04-15 2016-04-15 sunset by Actian
Actian Vector (Vectorwise) 2.5 2012-06-01 2015-06-01 sunset by Actian
Actian Vector (Vectorwise) 2.0 2011-11-01 2014-11-01 sunset by Actian
Greenplum 4.3 2013-12-01 2018-04-30 regular
Greenplum 4.2 2011-11-28 2015-09-30 sunset by Pivotal
Greenplum 4.0 2010-08-27 2013-11-30 sunset by Pivotal
RedShift 1.0 2013-02-14 regular
Teradata 15 & 15.10 regular
Teradata 14 & 14.10 regular
Teradata 13 & 13.10 regular