Versions Compared

Key

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

6.0 Upgrade Process

Build: zephyr_5.0_14749_setup_iRev_2028
Released Build numbers:

Version

4.7

4.8

4.8.2

4.8.1.2

5.0

5.0.1

5.0.2

5.0.3

5.1

5.1.1

5.1.2

Build#

9213

13321

13818

13842

14587

14667

14749

15001

15420

15434

15442

 
Note: upto 5.0 customer has to come by Old Upgrade process and from 5.0 / 5.0.1/ 5.0.2 →6.0  new upgrade process.  Migration is not supported in 6.0
Mandate**  : For new upgrade process, before starting upgrade take full backup & DB dump and keep somewhere and start the new upgrade process*
Note:  1. While upgrading to 6.0 , we have to stop the server and run the upgrader 2. If zautomation is set in 5.1 then post successful upgrade to 6.0, again user has to configure zautomation manually (copy zautomation license to license folder, and edit the license.properties file) ZAutomation Configuration with ZE  3. If SSO is set in 5.1 then post successful upgrade to 6.0, again user has to copy the certificate in (Zephyr directory \zephyrdata\ persist ) and restart the server 4. If ssl is set in older version of zephyr ( 5.0, 5.0.1, 5.0.2 ,5.0.3 ,5.1 ,5.1.1 ,5.1.2 ) , then post successful upgrade to 6.0, then user has to manually uncomment the security tag in web.xml files which is present in zephyr directory and then need to restart the server      a.  Zephyr directory\tomcat\webapps\flex\WEB-INF\web.xml      b.  Zephyr directory\tomcat\webapps\zephyr\WEB-INF\web.xml

...

TO 5.1(Build#)

...

 

...

 

...

 

...

 

...

 

...

MySQL

...

SQL Server

...

Oracle

...

 

...

4.7 (Build #9213 - MySQL)

...

  • 4.7 → 5.0 old upgrade process
  • 5.0 →6.0 new Upgrader

...

  • 4.7 → 5.0 old upgrade process
  • 5.0(MySQL) → Migrate to 5.0 SQL Server
  • 5.0 →6.0 new Upgrader

...

  • 4.7 → 5.0 old upgrade process
  • 5.0(MySQL) → Migrate to 5.0 Oracle
  • 5.0 →6.0 new Upgrader

...

 

...

4.8 (Build #13321 - MySQL)

...

  • 4.8 → 5.0 old upgrade process
  • 5.0 →6.0 new Upgrader

...

  • 4.8 → 5.0 old upgrade process
  • 5.0(MySQL) → Migrate to 5.0 SQL Server
  • 5.0 →6.0 new Upgrader

...

  • 4.8 → 5.0 old upgrade process
  • 5.0(MySQL) → Migrate to 5.0 Oracle
  • 5.0 →6.0 new Upgrader

...

 

...

4.8.2 (Build # 13818 - MySQL)

...

  • 4.8.2 → 5.0 old upgrade process
  • 5.0 →6.0 new Upgrader

...

  • 4.8.2 → 5.0 old upgrade process
  • 5.0(MySQL) → Migrate to 5.0 SQL Server
  • 5.0 →6.0 new Upgrader

...

  • 4.8.2 → 5.0 old upgrade process
  • 5.0(MySQL) → Migrate to 5.0 Oracle
  • 5.0 →6.0 new Upgrader

...

 

...

4.8.1.2 (Build # 13842 - MySQL)

...

  • 4.8.1.2 → 5.0 old upgrade process
  • 5.0 →6.0 new Upgrader

...

  • 4.8.1.2 → 5.0 old upgrade process
  • 5.0(MySQL) → Migrate to 5.0 SQL Server
  • 5.0 →6.0 new Upgrader

...

  • 4.8.1.2 → 5.0 old upgrade process
  • 5.0(MySQL) → Migrate to 5.0 Oracle
  • 5.0 →6.0 new Upgrader

...

 

...

4.8 (Build #13321 - SQLServer)

...

Not Supported

...

  • 4.8 → 4.8.2 restore + 4.8.2 → 5.0 old upgrade process
  • 5.0 →6.0 MsSQL with new upgrader

...

Not Supported

...

 

...

4.8.2 (Build # 13818 - SQLServer)

...

Not Supported

...

  • 4.8.2 → 5.0 old upgrade process
  • 5.0 →6.0 MsSQL with new upgrader

...

Not Supported

...

 

...

4.8.1.2 (Build # 13842 - Oracle)

...

Not Supported

...

Not Supported

...

  • 4.8.1.2 → 5.0 Upgrade without dropping db
  • 5.0 →6.0 Oracle with new upgrader

...

 

...

5.0 (Build # 14587 -MySQL)

...

  • 5.0 →5.1 new Upgrader

...

  • 5.0(MySQL) → Migrate to 5.0 SQL Server
  • 5.0 →6.0 new Upgrader

...

  • 5.0(MySQL) → Migrate to 5.0 Oracle
  • 5.0 →6.0 new Upgrader

...

 

...

5.0 (Build # 14587 -MSSQL)

...

Not Supported

...

  • 5.0 →5.1 MsSQL with new upgrader

...

Not Supported

...

 

...

5.0 (Build # 14587 -Oracle)

...

Not Supported

...

Not Supported

...

  • 5.0 →5.1 Oracle with new upgrader

...

 

...

5.0.1(Build # 14667 -MySQL)

...

  • 5.0.1 →6.0 new Upgrader

...

  • 5.0.1(MySQL) → Migrate to 5.0.1 SQL Server
  • 5.0.1 →6.0 new Upgrader

...

  • 5.0.1(MySQL) → Migrate to 5.0.1 Oracle
  • 5.0 →6.0 new Upgrader

...

 

...

5.0.1(Build # 14667 -MSSQL)

...

Not Supported

...

  • 5.0.1 →5.1 MsSQL with new upgrader

...

Not Supported

...

 

...

5.0.1(Build # 14667 -Oracle)

...

Not Supported

...

Not Supported

...

  • 5.0.1 →6.0 Oracle with new upgrader

...

 

...

5.0.2(Build # 14749 -MySQL)

...

  • 5.0.2 →6.0 new Upgrader

...

  • 5.0.2(MySQL) → Migrate to 5.0.2 SQL Server
  • 5.0.2 →6.0 new Upgrader

...

  • 5.0.2(MySQL) → Migrate to 5.0.2 Oracle
  • 5.0.2 →6.0 new Upgrader

...

 

...

5.0.2(Build # 14749 -MSSQL)

...

Not Supported

...

  • 5.0.2 →6.0 MsSQL with new upgrader

...

Not Supported

...

 

...

5.0.2(Build # 14749 -Oracle)

...

Not Supported

...

Not Supported

...

  • 5.0.2 →6.0 Oracle with new upgrader

...

 

...

5.0.3(Build # 15001 -MySQL)

...

  • 5.0.3 →6.0 new Upgrader

...

Not Supported

...

Not Supported

...

 

...

5.0.3(Build # 15001 -MSSQL)

...

Not Supported

...

  • 5.0.3 →6.0 MsSQL with new upgrader

...

Not Supported

...

 

...

5.0.3(Build # 15001 -Oracle)

...

Not Supported

...

Not Supported

...

  • 5.0.3 →6.0 Oracle with new upgrader

...

 

...

5.1(Build # 15420 -MySQL)

...

  • 5.1 →6.0 new Upgrader

...

Not Supported

...

Not Supported

...

 

...

5.1(Build # 15420 -MSSQL)

...

Not Supported

...

  • 5.1 →6.0 MsSQL with new upgrader

...

Not Supported

...

 

...

5.1(Build # 15420 -Oracle)

...

Not Supported

...

Not Supported

...

  • 5.1 →6.0 Oracle with new upgrader

...

 

...

5.1.1(Build # 15434 - MySQL)

...

  • 5.1.1 →6.0 new Upgrader

...

Not Supported

...

Not Supported

...

 

...

5.1.1(Build # 15434 -MSSQL)

...

Not Supported

...

  • 5.1.1 →6.0 MsSQL with new upgrader

...

Not Supported

...

 

...

5.1.1(Build # 15434 -Oracle)

...

Not Supported

...

Not Supported

...

  • 5.1.1 →6.0 Oracle with new upgrader

...

 

...

5.1.2(Build # 15442 -MySQL)

...

  • 5.1.2 →6.0 new Upgrader

...

Not Supported

...

Not Supported

...

 

...

5.1.2(Build # 15442 -MSSQL)

...

Not Supported

...

  • 5.1.2 →6.0 MsSQL with new upgrader

...

Not Supported

...

 

...

5.1.2(Build # 15442 -Oracle)

...

Not Supported

...

Not Supported

...

  • 5.1.2 →6.0 Oracle with new upgrader

...

 

...

 

...

 

...

 

...

 

...

 

...

upgrader from command

...

 

...

 

...

 

...

 

...

 

...

 

...

MySQL Upgrader command for windows

...

<upgrader file name> -VzMySQLPath='C:\Program Files\MySQL\MySQL Server 5.6\bin\mysql.exe' -VzMySQLCnfFilePath='C:\Program Files\MySQL\MySQL Server 5.6\my-default.ini'

...

 

...

 

...

 

...

 

...

MySQL upgrader command for Linux

...

<upgrader file name> -VzMySQLPath='/usr/bin/mysql' -VzMySQLCnfFilePath='/etc/mysql/my.cnf'

...

 

...

 

...

 

...

 

...

Embedded Upgrader command

...

<upgrader file name> -VzMySQLPath='C:\Program Files\Zephyr\mysql\bin\mysql.exe' -VzMySQLCnfFilePath='C:\Program Files\Zephyr\mysql\my.ini'

...

 

...

 

...

 

...

 

...

For MSSQL Upgrader

...

For windows double click & For linux sh <upgrader file name>.sh (No need to pass any arguments like MySQL)

...

 

...

 

...

 

...

 

...

For Oracle Upgrader

...

For windows double click & For linux sh <upgrader file name>.sh (No need to pass any arguments like MySQL)

...

 

...

 

...

 

...

 

 
-------------------------------------------------------------------------------------------------------------------------
1. Mysql : 4.7 → 5.0 → 6.0 , 4.8 → 5.0 → 6.0 , 4.8.2 → 5.0 → 6.0, 4.8.1.2 →5.0 → 6.0 ,5.0 → 6.0 , 5.0.1 → 6.0 ,5.0.2 → 6.0 ,5.0.3 → 6.0 ,5.1 → 6.0 ,5.1.1 → 6.0 ,5.1.2 → 6.0 .
   Scenario 1:

  1. Upgrade 4.7 to 5.0 in MySQL db → Upgrade from 5.0 → 6.0.

   Scenario 2:

  1. Upgrade 4.8 to 5.0 in MySQL db → Upgrade from 5.0 → 6.0.

   Scenario 3:

  1. Upgrade 4.8.2 to 5.0 in MySQL db → Upgrade from 5.0 → 6.0.

   Scenario 4:

  1. Upgrade 4.8.1.2 to 5.0 in MySQL db → Upgrade from 5.0 → 6.0.

...


Column

This section applies specifically to the Zephyr Enterprise product and provides instructions on upgrading the Zephyr Enterprise instance. The information below is generally used to ensure that system administrators can upgrade and update their Zephyr Enterprise product instance. 


The information and links below provide an in-depth knowledge and step-by-step guide to assist your system administrator with upgrading Zephyr Enterprise from an earlier version to a 6.0 instance.


Info
titleBest Practice Before Upgrading

As a best practice before upgrading, we strongly recommend performing a backup of your database to ensure data integrity and to make the upgrade as seamless as possible during the transition.

  • Database backups are extremely ideal when you are upgrading your Zephyr instance to retain your data if any issues occur during the upgrade process.

For any upgrade, ensure that a database backup is performed.

Please navigate through the links below that best describe your preferred upgrade environment. 

Table of Contents


Child pages (Children Display)
alltrue
pageUpgrade to 6.0

Guidelines

...

  1. After Upgrade is done before starting the server and all connections to database should be terminated
  2. In Cluster environment all other nodes should be down

Upgrader from command


MySQL Upgrader command for windows

<upgrader file name> -VzMySQLPath='C:\Program Files\MySQL\MySQL Server 5.6\bin\mysql.exe' -VzMySQLCnfFilePath='C:\Program Files\MySQL\MySQL Server 5.6\my-default.ini'

MySQL upgrader command for Linux

<upgrader file name> -VzMySQLPath='/usr/bin/mysql' -VzMySQLCnfFilePath='/etc/mysql/my.cnf'

Embedded Upgrader command

<upgrader file name> -VzMySQLPath='C:\Program Files\Zephyr\mysql\bin\mysql.exe' -VzMySQLCnfFilePath='C:\Program Files\Zephyr\mysql\my.ini'

For MSSQL Upgrader

For windows double click & For linux sh <upgrader file name>.sh (No need to pass any arguments like MySQL)

For Oracle Upgrader

For windows double click & For linux sh <upgrader file name>.sh (No need to pass any arguments like MySQL)

 
-------------------------------------------------------------------------------------------------------------------------
1. Mysql : 4.7 → 5.0 → 6.0 , 4.8 → 5.0 → 6.0 , 4.8.2 → 5.0 → 6.0, 4.8.1.2 →5.0 → 6.0 ,5.0 → 6.0 , 5.0.1 → 6.0 ,5.0.2 → 6.0 ,5.0.3 → 6.0 ,5.1 → 6.0 ,5.1.1 → 6.0 ,5.1.2 → 6.0 .
   Scenario 1:

  1. Upgrade 4.7 to 5.0 in MySQL db → Upgrade from 5.0 → 6.0.

   Scenario 2:

  1. Upgrade 4.8 to 5.0 in MySQL db → Upgrade from 5.0 → 6.0.

   Scenario 3:

  1. Upgrade 4.8.2 to 5.0 in MySQL db → Upgrade from 5.0 → 6.0.

   Scenario 4:

  1. Upgrade 4.8.1.2 to 5.0 in MySQL db → Upgrade from 5.0 → 6.0.

   Scenario 5:
       1. Upgrade from 5.0 → 6.0.
   Scenario 6:
       1. Upgrade from 5.0.1 → 6.0.
    Scenario 7:
       1. Upgrade from 5.0.2 → 6.0.
    Scenario 8:
       1. Upgrade from 5.0.3 → 6.0.
    Scenario 9:
       1. Upgrade from 5.1 → 6.0.
    Scenario 10:
       1. Upgrade from 5.1.1 → 6.0.
     Scenario 11:
       1. Upgrade from 5.1.2 → 6.0.

2. Sql Server:

4.7 → 5.0 → 6.0 , 0

4.8 → 5.0 → 6.0  , 40

4.8.2 → 5.0 →6.0 , 40

4.8.1.2 →5.0 → 6.0  , 50

5.0 →6.0  , 5.0.1 → 6.0  ,0

5.0.2 → 6.0 ,5.0.3 → 6.0  ,0

5.1 → 6.0 ,

5.1.1 → 6.0 ,

5.1.2 → 6.0 .0


    4.7/4.8.1.2 to 5.0(MSSQL)  direct upgrade is not possible.

Since we don't have upgrader for that.
    Following steps to be followed for MSSQL DB Migration.    

 Scenario 1: From 4.7 (MySQL) to 5.1 SQL Server


    1. Install 5.0 in MYSQL db 
    2. Upgrade 4.7 to 5.0 in MYSQL db 
    3. Take backup from 5.0 in MYSQL db
    4. Install 5.0 in MSSQL db 
    5. Restore backup taken from 5.0(MYSQL) to 5.0(MSSQL)
    6. Upgrade 5.0(MSSQL) to 6.0 (MSSQL).

     Scenario 2: From 4.8 SQL Server to 6.0 SQL Server    

  1. 4.8 → 4.8.2 restore + 4.8.2 → 5.0 Upgrade → 6.0 Upgrade

    Scenario 3: From 4.8.2 SQL Server to 6.0 SQL Server    

  1. Upgrade 4.8.2 to 5.0 in SQL Server db → 6.0 Upgrade

    Scenario 4: From 4.8.1.2 to 6.0 SQL Server    


    1. Install 5.0 in MYSQL db 
    2. Upgrade 4.8.1.2(MySQL) to 5.0 in MYSQL db 
    3. Take backup from 5.0 in MYSQL db
    4. Install 5.0 in MSSQL db 
    5. Restore backup taken from 5.0(MYSQL) to 5.0(MSSQL)
    6. Upgrade 5.0(MSSQL) to 6.0 (MSSQL).

     Scenario 5: From 5.0 MySQL to 6.0 SQL Server

  1. Install 5.0 in MySQL db  → Create data.
  2. Restore backup taken from 5.0(MYSQL) to 5.0(MSSQL)
  3. Upgrade 5.0(MSSQL) to 6.0 (MSSQL)

       
   Scenario Scenario 6: From 5.0.1 MySQL to 6.0 SQL Server

  1. Install 5.0.1 in MySQL db  → Create data.
  2. Restore backup taken from 5.0.1(MYSQL) to 5.0.1(MSSQL)
  3. Upgrade 5.0(MSSQL) to 6.0 (MSSQL).

   
  Scenario Scenario 7: From 5.0.2 MySQL to 6.0 SQL Server

...

  1. DIrect Upgrade from 5.0.3 → 6.0


 
Scenario 9 : From 5.1 SQL Server to 6.0 SQL Server
 

  1. DIrect Upgrade from 5.1 → 6.0


 
Scenario 10 : From 5.1.1 SQL Server to 6.0 SQL Server
 

  1. DIrect Upgrade from 5.1.1 → 6.0


 
Scenario 11 : From 5.1.2 SQL Server to 6.0 SQL Server
 

  1. DIrect Upgrade from 5.1.2 → 6.0

Command used for restore:       Linux: ./restoreAll.sh -FORCE       Windows: restoreAll.bat -FORCE  
------------------------------------------------------------------------------.0 SQL Server

  1. DIrect Upgrade from 5.1.2 → 6.0

Command used for restore:       Linux: ./restoreAll.sh -FORCE       Windows: restoreAll.bat -FORCE  


3. Oracle 11G:  4.8.1.2 →6.0

...

Scenario 1: From 4.8.1.2 MySQL to 6.0 Oracle


    1. Install 5.0 in MYSQL db 
    2. Upgrade 4.8.1.2(MySQL) to 5.0 in MYSQL db 
    3. Take backup from 5.0 in MYSQL db
    4. Install 5.0 in Oracle db 
    5. Restore backup taken from 5.0(MYSQL) to 5.0(Oracle)
    6. Upgrade 5.0 (Oracle) to 6.0 (Oracle). 

   Command used for restore:
      Linux: ./restoreAll.sh -FORCE       Windows: restoreAll.bat -FORCE  

Scenario 2: From 4.8.1.2 Oracle to 6.0 Oracle

  1. Copy Zephyr data some where then follow below steps.
  2. Uninstall 4.8_13842 using below command.(Uninstall by skiping DB drop)

...

  1. In DB → Select User for runing Query (i.e → ALTER SESSION SET current_schema ="ITCC"(wink)
  2. Now after selecting Current User run these queries → LG_Oracle_dashboard_index_issue.sql
  3. Now Run 6.0 installer and select Upgrade mode .

Scenario 3: From 5.0 MySQL to 6.0 Oracle

Install 5.0 in MySQL db → Create data. Restore backup taken from 5.0(MYSQL) to 5.0(Oracle) Upgrade 5.0(Oracle) to 6.0 (Oracle)

...

 .

Scenario 4: From 5.0.1 MySQL to 6.0 Oracle

Install 5.0.1 in MySQL db → Create data. Restore backup taken from 5.0.1(MYSQL) to 5.0.1(Oracle) Upgrade 5.0.1(Oracle) to 6.0 (Oracle).

Scenario 5 : From 5.0.2 MySQL to 6.0 Oracle

Install 5.0.2 in MySQL db → Create data. Restore backup taken from 5.0.2(MYSQL) to 5.0.2(Oracle) Upgrade 5.0.2(Oracle) to 6.0  (Oracle).

Scenario 6 : From 5.0.3 Oracle to 6.0 Oracle

DIrect Direct Upgrade From 5.01.3 → 61 → 6.0 

Scenario 7 : From 5.1 Oracle to 6.0 Oracle

DIrect Direct Upgrade From 5.1.1 → 6→ 6.0 

Scenario 8 : From 5.0.3 Oracle to 6.0 Oracle

DIrect Direct Upgrade From 5.1.1 → 6.0 
 

Scenario 9: From 5.0.3 Oracle to 6.0 Oracle

 
DIrect Direct Upgrade From 5.1.2 1 → 6.0 
Upgrade for Linux
Image Removed

...