Top
Systemwalker Service Quality Coordinator Installation Guide
Systemwalker
Chapter 7 Upgrade Installations > 7.1 Tasks to Perform at the Manager or Enterprise Manager[EE] > 7.1.2 Upgrade Procedure for UNIX Versions
PreviousNext

7.1.2 Upgrade Procedure for UNIX Versions

Required privileges

The user must have the privileges of the system administrator (superuser).


Before performing this procedure

If any Manager or Enterprise Manager resident processes are running, stop the service by referring to "A.8 How to Start and Stop Resident Processes". Also check that the relevant resident processes have stopped correctly.

Point

When upgrade Managers which are operating as cluster system, cancel the cluster operation first.

Refer to "9.4 Uninstalling from a PRIMECLUSTER Cluster System" for information how to cancel the cluster operations, and follow the procedure until execution of the cluster unsetup command.

Procedure (to migrate from V13)

When migrating from V13, the procedure is as follows:

  1. Back up files in /var/opt/FJSVssqc/

    Back up the files in the /var/opt/FJSVssqc/ directory

    Note

    • Backup while the daemons of the Manager or Enterprise Manager are stopping.

    • The PDB is included in these files. Note the size of the backup destination, as the amount of data can become quite large.


  2. Perform upgrade installation of Manager or Enterprise Manager

    Start installing the Manager or Enterprise Manager in the same way as for the initial installation, as described in "3.1.1 Installing a Manager/Enterprise Manager[EE]".

    Note that the upgrade installation performs the following steps automatically:

    • Stops resident processes (as a precaution)

    • Backs up other definition files (in the /etc/opt/FJSVssqc/ directory)

    • Uninstalls the package for the previous version

    • Performs an upgrade installation, inheriting the information that was entered for the prompts during the previous installation

    • Restores the other definition files that have been backed up


  3. Write the files back to /var/opt/FJSVssqc/

    Return the files backed up in "1. Back up files in /var/opt/FJSVssqc/" above to their original path except following files.

    • Backup directory/var/opt/FJSVssqc/PDB/pdb.dat


  4. Apply user definitions to definition files that were not rewritten

    Files that cannot be rewritten automatically are backed up to /etc/opt/FJSVssqc/ and /opt/FJSVssqc/bin with the name as follows:

    • "file nameVnnLnn.extension" or "file nameVnnn.extension"

      (Where the VnnLnn part indicates the version and level prior to the upgrade)

    If a file that was edited prior to the upgrade has been backed up, use the backup file as a basis for editing the file again. The following files are backed up:

    • DSAconfiguration.txt

    • template.dat

    • threshold.sh

    • udataconf.ini

    • pdbmanage.txt


  5. Settings after upgrade installation

    Execute the setting again when the environment that does the upgrade installation corresponds to the following conditions.

    • Two-tier Manager operation

      Execute setup for Two-tier Manager operation again.

      Information

      Refer to "1. Set up a two-tier Manager operation" in the "6.2.2 Tasks to perform on the Manager" for detailed procedure.

    • Cluster system operation

      Execute cluster setup for cluster system operation and resource registration on Managers and Enterprise Manages again.

      Information

      Refer to "3.8 PRIMECLUSTER Cluster System Operation Model" for detailed procedure.

    • Collecting SAP NetWeaver performance information after upgrade from V13.4 or earlier

      When upgrade installation from V13.4.0 or earlier has been done under the environment that collects SAP NetWeaver performance information, encrypt the password defined in PASSWORD in the connection parameters definition file (sqcGetSAPalertmon.ini) of SAP NetWeaver cooperation.

      Information

      Refer to "Connection parameters definition file" in the User's Guide for detailed procedure.

    • Collecting Oracle Database Server performance information after upgrade from V13.5 or earlier

      Wnen upgrade installation from V13.5.0 or earlier has been done under the environment that collects Oracle Database Server performance information, encrypt the password defined in PASS in the [ORA] section in the collection template (template.dat) for management settings of Oracle Database Server.

      Information

      Refer to "How to Set up Oracle Database Server" in the User's Guide for detailed procedure.

    • Initial value of the storage location of the performance database has been changed.

      Execute steps for changing initial value of the storage location of the performance database again.

      Information

      Refer to "6.6.1.1.1 Management Data" for detailed procedure.


  6. Set up a Manager/Enterprise Manager

    Point

    Set up the Manager/Enterprise Manager if the Agent function is to be used on the Manager/Enterprise Manager to collect performance information about the Manager/Enterprise Manager itself.

    Execute sqcRPolicy and sqcSetPolicy as explained in "A.1 Server Resource Information Collection Policy Creation Command".


  7. Start the Manager/Enterprise Manager daemons and confirm that it has started normally

    Start the daemons by referring to "A.8 How to Start and Stop Resident Processes". Also check that the relevant resident processes have started correctly.


  8. Restore the archive files

    If referring a data which was output as archive files before the PDB files conversion, refer to "Archive File" in the User's Guide and restore the archive files backed up in step 1.


Procedure (to migrate from V11 and V12)

When migrating from V11 and V12, the procedure is as follows:

Note

Summary data which collected before the upgrade cannot be referred after the upgrade.

  1. Back up files in /var/opt/FJSVssqc/

    Back up the files in the /var/opt/FJSVssqc/ directory

    Note

    • Backup while the daemons of the Manager or Enterprise Manager are stopping.

    • The PDB is included in these files. Note the size of the backup destination, as the amount of data can become quite large.

    • When upgrading from V11 or V12, change the name of the PDB file (/var/opt/FJSVssqc/PDB/pdb.dat) to "pdbold.dat" and then back it up.


  2. Perform upgrade installation of Manager or Enterprise Manager

    Start installing the Manager or Enterprise Manager in the same way as for the initial installation, as described in "3.1.1 Installing a Manager/Enterprise Manager[EE]".

    Note that the upgrade installation performs the following steps automatically:

    • Stops resident processes (as a precaution)

    • Backs up other definition files (in the /etc/opt/FJSVssqc/ directory)

    • Uninstalls the package for the previous version

    • Performs an upgrade installation, inheriting the information that was entered for the prompts during the previous installation

    • Restores the other definition files that have been backed up


  3. Write the files back to /var/opt/FJSVssqc/

    Return the files backed up in "1. Back up files in /var/opt/FJSVssqc/" above to their original path except following files.

    • Backup directory/var/opt/FJSVssqc/PDB/pdb.dat


  4. Start the Manager/Enterprise Manager daemons and confirm that it has started normally

    Start the daemons by referring to "A.8 How to Start and Stop Resident Processes". Also check that the relevant resident processes have started correctly.


  5. Check pdb.dat

    Check that pdb.dat exists in the following directory:

    /var/opt/FJSVssqc/PDB/


  6. Stop the Manager/Enterprise Manager daemon and confirm that it has stopped normally

    Stop the daemon by referring to "A.8 How to Start and Stop Resident Processes". Also check that the relevant resident processes have stopped correctly.


  7. Execute the ConvPDBV13 command

    /opt/FJSVssqc/bin/ConvPDBV13 -f/etc/opt/FJSVssqc/ConvertV13.opt

    Point

    Specify the following parameters in the ConvertV13.opt file:

    • -o Specifies the path to the old (V11, V12) PDB file

    • -n Specifies the path to the V13 PDB file

    • -s Specifies the path to the SYSTEM SQL CREATE file

    Example

    When specifying parameters for the following options, do not leave a space between the option and the parameter.

    #cd /opt/FJSVssqc/bin

    ./ConvPDBV13 -f/etc/opt/FJSVssqc/ConvertV13.opt
    Processing:
    Old PDB: "/var/opt/FJSVssqc/PDB/pdbold.dat"
    New PDB: "/var/opt/FJSVssqc/PDB/pdb" Extension: ".dat"
    create sql file: "/etc/opt/FJSVssqc/createpdb_data.sql"
    Converting system tables
    Converting table "system"
    Converting table "system_route"
    Converting other tables
    Converting table "compound_data"
    Converting table "ryg_data"
    Converting consolidated tables
    Converting table "consumer_data"
    Converting table "conres_data"
    Converting table "resource_data"
    Converting table "resource_data_wide"
    Converting table "resource_data_vwide"
    Converting table "resource_data_uwide"
    Converting table "resource_data_uuwide"
    Converting table "resource_data_twide"
    Converting table "resource_data_ttwide"
    OK

    Note

    • The time needed for this conversion depends on the I/O performance of the disk. As a guide, it usually takes approximately one hour to convert a 5-GB PDB on an internal disk.

    • When a PDB conversion is performed, the summary data and resource data (collected at 10 minute intervals) will not be converted, so it will not be possible to view this data after an upgrade.

    • To ensure that resource data (collected at 10 minute intervals) are converted, specify the following option in ConvertV13.opt. Note, however, that this will increase the conversion time by two or three times.

      To add resource data (collected at 10 minute intervals): -i600


  8. Executing the sqcPDBupgrade.sh command

    /opt/FJSVssqc/bin/sqcPDBupgrade.sh -pdb /var/opt/FJSVssqc/PDB/pdb.dat

    The following is an example of results after sqcPDBupgrade.bat is executed

    #cd /opt/FJSVssqc/bin
    ./sqcPDBupgrade.sh -pdb /var/opt/FJSVssqc/PDB/pdb.dat
    sqcPDBupgrade succeeded.

    Note

    After conversion, the PDB file for the older version summary data (pdb_SUMMARY.dat) cannot be viewed from the screen , and must be manually deleted.


  9. Apply user definitions to definition files that were not rewritten

    Files that cannot be rewritten automatically are backed up to /etc/opt/FJSVssqc/ and /opt/FJSVssqc/bin with the name as follows:

    • "file nameVnnLnn.extension" or "file nameVnnn.extension"

      (Where the VnnLnn part indicates the version and level prior to the upgrade)

    If a file that was edited prior to the upgrade has been backed up, use the backup file as a basis for editing the file again. The following files are backed up:

    • DSAconfiguration.txt

    • template.dat

    • threshold.sh

    • tsconfig.txt

    • pdbmanage.txt


  10. Settings after upgrade installation

    Execute the setting again when the environment that does the upgrade installation corresponds to the following conditions.

    • Two-tier Manager operation

      Execute setup for Two-tier Manager operation again.

      Information

      Refer to "1. Set up a two-tier Manager operation" in the "6.2.2 Tasks to perform on the Manager" for detailed procedure.

    • Redundant Manager operation

      Execute setup for Redundant Manager operation on Agent and Proxy Manager again.

      Information

      Refer to "2. Set up the Agent for Redundant Manager operation" in the "3.6.4 Tasks to perform on the Agent", or "2. Set up the Proxy Manager for Redundant Manager operation" in the "3.6.3 Tasks to perform on the Proxy Manager" for detailed procedure.

    • If Pull/Push communication is switched during operation after installation

      Switch Pull/Push communication method on Agent or Proxy Manager again.

      Information

      Refer to "4.4.3 Switching from Push to Pull" and "4.4.4 Switching from Pull to Push" for detailed procedure.

    • Collecting SAP NetWeaver performance information after upgrade from V13.4 or earlier

      When upgrade installation from V13.4.0 or earlier has been done under the environment that collects SAP NetWeaver performance information, encrypt the password defined in PASSWORD in the connection parameters definition file (sqcGetSAPalertmon.ini) of SAP NetWeaver cooperation.

      Information

      Refer to "Connection parameters definition file" in the User's Guide for detailed procedure.

    • Collecting Oracle Database Server performance information after upgrade from V13.5 or earlier

      Wnen upgrade installation from V13.5.0 or earlier has been done under the environment that collects Oracle Database Server performance information, encrypt the password defined in PASS in the [ORA] section in the collection template (template.dat) for management settings of Oracle Database Server.

      Information

      Refer to "How to Set up Oracle Database Server" in the User's Guide for detailed procedure.


  11. Set up a Manager/Enterprise Manager

    Point

    Set up the Manager/Enterprise Manager if the Agent function is to be used on the Manager/Enterprise Manager to collect performance information about the Manager/Enterprise Manager itself.

    Execute sqcRPolicy and sqcSetPolicy as explained in "A.1 Server Resource Information Collection Policy Creation Command".


  12. Start the Manager/Enterprise Manager daemons and confirm that it has started normally

    Start the daemons by referring to "A.8 How to Start and Stop Resident Processes". Also check that the relevant resident processes have started correctly.


PreviousNext
Copyright 2003 - 2012 FUJITSU LIMITED