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.1 Upgrade Procedure for Windows Versions
PreviousNext

7.1.1 Upgrade Procedure for Windows Versions

Required privileges

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


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.3 Uninstallation under a MSCS/Failover Clustering 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. Create backup of archive files

    If upgrade has been done from V13.4.0 and earlier, PDB file conversion will be performed, so it will not be possible to view summary data and monitor data that are from before the upgrade installation, but the data output as archive files can be referred

    Refer to "Archive files" in the User' Guide as necessary, and backup archive files.

    Note

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


  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/Enterprise Manager[EE]".

    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

    Note

    If upgrade has been done from V13.2.0 or earlier on Enterprise Managers, retention period for log (Troubleshoot) is set as default (7 days).

    Refer to "6.7.2 Changing the retention period of log data (Troubleshoot)" when the retention period needs to be changed.


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

    Files that cannot be overwritten are backed up using the following file names under <variableFileStorageDir>\SystemwalkerSQC\control and <installDir>\SystemwalkerSQC\bin:

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

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

    These backed up files are as follows. If corrections have been added to the following files, perform the editing again using the backup files as the base:

    • DSAconfiguration.txt

    • template.dat

    • threshold.bat

    • udataconf.ini

    Point

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


  4. 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.7 Cluster System Operation Model for MSCS/Failover Clustering" 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

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


  5. 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".


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


  7. 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. Perform upgrade installation of Manager or Enterprise Manager

    Start installing 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

    • 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

    • Modifications to the file name of the PDB file

      The file name has been modified as follows:

      • V11.0L10 : pdbV11L10.dat

      • V12.0L10 : pdbV12L10.dat

      • V12.0L11 : pdbV12L11.dat

    Note

    If upgrade has been done from V11 or V12 on Managers, retention period for log (Troubleshoot) is set as default (7 days).

    Refer to "6.7.2 Changing the retention period of log data (Troubleshoot)" when the retention period needs to be changed.


  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. Execute the pdb_convert.exe command

    Installation directory\bin\pdb_convert.exe -f variable 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


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


  7. 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 are backed up using the following file names under <variableFileStorageDir>\SystemwalkerSQC\control and <installDir>\SystemwalkerSQC\bin:

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

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

    These backed up files are as follows. If corrections have been added to the following files, perform the editing again using the backup files as the base:

    • DSAconfiguration.txt

    • template.dat

    • threshold.bat

    • tsconfig.txt

    Point

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


  8. 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 setup on Agent or 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.


  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.

    Execute sqcRPolicy and sqcSetPolicy 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.


PreviousNext
Copyright 2003 - 2012 FUJITSU LIMITED