Top
Systemwalker Service Quality Coordinator Installation Guide
Systemwalker
Chapter 7 Upgrade Installations > 7.1 Tasks to Perform at the Manager or Enterprise Manager
PreviousNext

7.1 Tasks to Perform at the Manager or Enterprise Manager

The procedure for performing an upgrade installation of a Manager or Enterprise Manager is provided below.

Note

  • If upgrade has been done from V11 or V12, summary data which collected before the upgrade cannot be referred after the upgrade.

  • If upgrade has been done from the earlier level of V13, summary data which collected before the upgrade cannot be referred after the upgrade, but the data output as archive files can be referred by restoring.


Required privileges

Windows

The user must have the privileges of a member of the Administrators group.

UNIX

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 or daemon by referring to "A.8 How to Start and Stop Resident Processes". Also check that the relevant resident processes have stopped correctly.


Procedure

The procedure is as follows:

Windows

  1. Perform upgrade installation of Manager or Enterprise Manager

    Start installing the Manager in the same way as for the initial installation, as described in "3.1.1 Installing a Manager" or "3.1.5 Installing an Enterprise Manager".

    The message "An older version of this software is already installed on this system. Would you like to upgrade? will appear. Select "YES". Then specify the retention period for troubleshooting information as prompted.

    Note that the upgrade installation performs the following steps automatically:

    • Stops resident processes (as a precaution)

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

    • Backs up definition files that are not overwritten

    • Backs up the PDB file from the old version (as pdbV11L10.dat when upgrading from V11.0 or pdbV12L10.dat when upgrading from V12.0)


  2. Start the Manager/Enterprise Manager service and confirm that it has started normally

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


  3. Check the PDB file (pdb.dat)

    Check the PDB file (pdb.dat) exists in the following directory:

    variable file storage directory\data


  4. Stop the Manager/Enterprise Manager service and confirm that it has stopped normally

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


  5. Backup the archive files (When upgrade from the earlier level of V13)

    If conversion of PDB files described in step 7 has been done after upgrade installation, summary data which collected before the upgrade cannot be referred, but the data output as an archive files can be referred. If necessary, refer to section 12.2.2, "Archive File" in the User's Guide and make a backup as archive files.

    Note

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

    • If upgrade has been done from V11 or V12, summary data which collected before the upgrade cannot be referred after the upgrade.


  6. Execute the pdb_convert.exe command

    Note

    Execute the pdb_convert.exe command as follows only when upgrading from versions 11 or 12:

    Installation directory\bin\pdb_convert.exe -fvariable file storage directory\control\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


      An example showing how these parameters are specified in the ConvertV13.opt file is provided below.

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

      The file already has default values specified. These values do not need to be changed if they are suitable for the operating environment.

      -oC:\SystemwalkerSQC\data\pdbV12L10.dat

      -nC:\SystemwalkerSQC\data\pdb.dat

      -sC:\SystemwalkerSQC\control\createpdb_data.sql


    Example

    An example showing the execution of pdb_convert.exe is shown below. (This example shows how to upgrade from V12.0L10.)

    C:\Program Files\SystemwalkerSQC\bin>pdb_convert.exe -f C:\SystemwalkerSQC\control\ConvertV13.opt
    Processing:
    Old PDB: "C:\SystemwalkerSQC\data\pdbV12L10.dat"
    New PDB: "C:\SystemwalkerSQC\data\pdb" Extension: ".dat"
    create sql file: "C:\SystemwalkerSQC\control\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 PDB will be converted when upgrading from V11 or V12. 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 has been converted, summary data and resource data (collected at 10 minute intervals) will not be converted, so after an upgrade is performed, it will not be possible to view the data prior to the upgrade in the Summary window, Drilled-Down window, or 10-minute reports.

    • 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 summary data (collected at 10 minute intervals): -i600


  7. Executing the sqcPDBupgrade.bat command

    <Installation directory>\bin\sqcPDBupgrade.bat -pdb <variable file storage directory>\data\pdb.dat


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

    C:\Program Files\SystemwalkerSQC\bin>sqcPDBupgrade.bat -pdb "C:\SystemwalkerSQC\data\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.


  8. Apply user definitions to definition files that were not overwritten

    Apply the user definitions that have been made to the definition files that were not overwritten.
    Files that cannot be overwritten have been backed up to the variable file storage directory\SystemwalkerSQC\control\ directory as "file nameVnnLnn.extension" (where the VnnLnn part indicates the version and level prior to the upgrade). If files that were edited before the upgrade have been backed up, perform the edit operations again based on the backed up files.

    These backed up files are as follows:

    • DSAconfiguration.txt

    • template.dat

    • threshold.bat

    • tsconfig.txt

    Note

    Backup files are created regardless of whether they have been edited.


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

    Create and deploy a collection policy as explained in "A.1 Server Resource Information Collection Policy Creation Command".


  10. Start the Manager/Enterprise Manager service and confirm that it has started normally

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


  11. Restore the archive files

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


UNIX

  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 in the same way as for the initial installation, as described in "3.1.1 Installing a Manager"/"3.1.5 Installing an Enterprise Manager".

    Select "YES" when the prompt appears asking whether to upgrade the existing installation. Then specify the retention period for troubleshooting information as prompted.
    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.


  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. Backup the archive files (When upgrade from the earlier level of V13)

    If conversion of PDB files described in step 9 has been done after upgrade installation, summary data which collected before the upgrade cannot be referred, but the data output as an archive files can be referred. If necessary, refer to section 12.2.2, "Archive File" in the User's Guide and make a backup as archive files.

    Note

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

    • If upgrade has been done from V11 or V12, summary data which collected before the upgrade cannot be referred after the upgrade.


  8. Execute the ConvPDBV13 command

    Note

    Execute the ConvPDBV13 command as follows only when upgrading from versions 11 or 12:

    /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 PDB will be converted when upgrading from V11 or V12. 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


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


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

    Files that cannot be rewritten automatically are backed up to /etc/opt/FJSVssqc/ with the name file nameVnnLnn (where VnnLnn 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

    Note

    Backup files are created regardless of whether they have been edited.


  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.

    Create and deploy a collection policy 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.


  13. Restore the archive files

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


PreviousNext
Copyright FUJITSU LIMITED 2003 - 2011