Top
Systemwalker Service Quality Coordinator Installation Guide
Systemwalker

6.6.1 Changing the PDB/Archive File Storage Location

By splitting the Manager physical disk into summary data, resource data and archive files, the number of Agents that can be managed by one Manager can be extended to approximately 300.

Refer to "6.6.1.1.2 Summary Data and Resource Data" to store the summary data and resource data into the separated disk, and refer to "6.6.1.2 Changing the Archive File Location" to store the archive files into the separated disk.

6.6.1.1 Changing the PDB Storage Location

The performance database consists of the file types described in the sections below.

To distribute disk I/O and disk space, the performance database location can be changed according to file type - the procedure to do that depends on the file type.

File name

Description

Procedure

pdb.dat

This is a single file for storing management data.

Basically, it does not need to move to other places.

6.6.1.1.1 Management Data

pdb_SUMMARY_yyyymmdd.dat

These files store summary data. A new file is created each day, and the "yyyymmdd" part of the file name indicates the date when the file was created.

6.6.1.1.2 Summary Data and Resource Data

(If the Management Data has moved on operation of the old edition, refer to "6.6.1.1.1 Management Data", too.)

pdb_10MIN_yyyymmdd.dat

These files store resource data (which is collected at 10 minute intervals). A new file is created each day, and the "yyyymmdd" part of the file name indicates the date when the file was created.

pdb_1HR_yyyymmdd.dat

These files store resource data (which is collected at hourly intervals). A new file is created each week, and the "yyyymmdd" part of the file name indicates the date of the Sunday in the week when the file was created.

pdb_1DAY_yyyymmdd.dat

These files store resource data (which is collected at daily intervals). A new file is created each month, and the "yyyymmdd" part of the file name indicates the date of the first day of the month when the file was created.

6.6.1.1.1 Management Data

This section explains the procedure for changing the default location of performance database. The location of Management Data (pdb.dat) is the default location of performance database.

Use the following procedure to move the PDB (Management Data) default location to another location:

Note

If setup for cluster operations has been performed using sqcsetupclp/sqcsetupcls (the cluster setup commands), the variable file directory changes to the shared disk.

Information

Basically, performance database default location does not need to move to other places. If the database has moved on operation of the old edition, there is no problem as it is.

  1. Stop and confirm the service or daemon

    When moving the PDB, if Enterprise Manager/Manager services or daemons are running, stop the services or daemons, refer to "A.8 How to Start and Stop Resident Processes" section for more information. Also check that the resident processes have stopped correctly.


  2. Moving PDB files

    Move the PDB files (pdb.dat, summary data and resource data) stored in the following directory to a selected location.
    Immediate after the installation, PDB file is not existed. Create directory only:

    Windows

    <variable file storage directory>\data\

    UNIX

    /var/opt/FJSVssqc/PDB/


  3. Changing the DSAconfiguration.txt file

    When settings of the "Management data" and initial value of the storage location for performance database have been changed, change the database path in the following definitions file :

    Windows

    <variable file storage directory>\control\DSAconfiguration.txt

    UNIX

    /etc/opt/FJSVssqc/DSAconfiguration.txt

    Change the following database path in red in the above definition file to the new path:


    Sample definition

    Windows

    [DsaPDBWriter]

    database=D:\SQC\data\pdb.dat

    [DsaPDBWriter_sum]

    database=D:\SQC\data\pdb.dat

    [DsaPDBReader]

    database=D:\SQC\data\pdb.dat

    [PDBMANAGE]
    command=pdb_manage.exe -d "D:\SQC\data\pdb.dat"


  4. Changing the pdbmgr.txt file

    Change the database path in the following definitions file:

    Windows

    <Installation directory>\setup\pdbmgr.txt

    UNIX

    /opt/FJSVssqc/setup/pdbmgr.txt

    Change the following database path in red in the above definition file to the new path:


    Sample definition

    Windows

    [PDBMANAGE]

    command=pdb_manage.exe -d "D:\SQC\data\pdb.dat"


  5. Start and confirm the service or daemon

    Start the service or daemon, refer to "A.8 How to Start and Stop Resident Processes" section for more information. Also check that the resident processes have started correctly.


6.6.1.1.2 Summary Data and Resource Data

To move the performance database (summary and resource data) to another location from the default location, perform the procedure below.

Note

If setup for cluster operations has been performed using sqcsetupclp/sqcsetupcls (the cluster setup commands), the variable file directory changes to the shared disk.

  1. Stop the Service and Daemon

    If the Enterprise Manager/Manager service/daemon are running, then stop them (refer to "A.8 How to Start and Stop Resident Processes" for details). Additionally, make sure that the resident processes have stopped correctly.


  2. Move the PDB files

    Move following directory to a selected location. (If the storage location of the performance database (management data) is changed by following the steps described in the "6.6.1.1.1 Management Data", following directory means destination location of the management data)
    Immediate after the installation, PDB file is not existed. Create directory only.

    Windows

    <variable file storage directory>\data\

    UNIX

    /var/opt/FJSVssqc/PDB/

    The names of the PDB files are shown below (then location can be changed according to file type):

    • When summary data PDB files are moved:
      pdb_SUMMARY_yyyymmdd.dat

    • When resource data (10 min) PDB files are moved:
      pdb_10MIN_yyyymmdd.dat

    • When resource data (1 hr) PDB files are moved:
      pdb_1HR_yyyymmdd.dat

    • When resource data (1 day) PDB files are moved:
      pdb_1DAY_yyyymmdd.dat


  3. Change the PDB file location

    Execute the following command with the destination directory-name. Refer to "sqcSetPDBStore (PDB File Location Change Command)" in the Reference Guide for details on the command.


    Point

    Assign the directory on the separated physical disk for the summary data and the resource data (10 minutes/1 hour/1 day) with sqcSetPDBStore (PDB File Location Change Command), when splitting the Manager physical disk into summary data, resource data and archive files to extended the number of Agents that can be managed by one Manager to approximately 300.


    Format

    Windows

    <installation directory>\bin\sqcSetPDBStore.bat -M|-m|-h|-d -S directory-name

    UNIX

    /opt/FJSVssqc/bin/sqcSetPDBStore.sh -M|-m|-h|-d -S directory-name


    Options

    -M

    Executes summary data PDB file operations.

    -m

    Executes resource data (10 minutes) PDB file operations.

    -h

    Executes resource data (1 hour) PDB file operations.

    -d

    Executes resource data (1 day) PDB file operations.

    -S <directory path>

    Changes the PDB file location to the specified directory path.

    Specify the -M, -m, -h, and -d options together to change the location of the PDB files for each option.

    Specify the absolute path.


  4. Start the Service and Daemon

    Refer to "A.8 How to Start and Stop Resident Processes" for details. Additionally, make sure that the resident processes have started correctly.


Point

  • When moving back the storage location of the PDB file to the default location (if the storage location of the performance database (management data) has been changed by following the steps described in the "6.6.1.1.1 Management Data", following directory means destination location of the management data), according to the following procedures as well as above-mentioned.

    1. Stop and confirm the service/daemon

    2. Move the PDB file to the default storage location

    3. Execute the change location command of the PDB file.
      Specify -R option instead of -S option.

    4. Start and confirm the service/daemon.

  • The storage location of the PDB file can be confirmed by specifing -V option with -M, -m, -h, or -d option.


6.6.1.2 Changing the Archive File Location

To move the archive files to another location, perform the procedure below.

Note

If setup for cluster operations has been performed using sqcsetupclp/sqcsetupcls (the cluster setup commands), the variable file directory changes to the shared disk.

  1. Stop the Service and Daemon

    If the Enterprise Manager/Manager service/daemon are running, then stop them (refer to "A.8 How to Start and Stop Resident Processes" for details). Additionally, make sure that the resident processes have stopped correctly.


  2. Move the archive files

    Windows

    Move the archive files other than BackupPDBinsert_state.dat stored in the directory below to another directory.
    Immediate after the installation, PDB file is not existed. Create directory only.

    <variable file directory>\spool\BackupPDBinsert\

    Note

    Please do not move BackupPDBinsert_state.dat.

    UNIX

    Move all files in the directory below to another directory.
    Immediate after the installation, PDB file is not existed. Create directory only.

    /var/opt/FJSVssqc/BackupPDBinsert/


  3. Change the DSAconfiguration.txt file

    Windows

    <variable file storage directory>\control\DSAconfiguration.txt

    UNIX

    /etc/opt/FJSVssqc/DSAconfiguration.txt

    Change the content of the [BackupPDBinsert] section out_dir parameter to the new path in the definition file. The parts that will need to be changed are shown below in red.


    Parts that will need to be changed

    [BackupPDBinsert]

    execute_style=on

    path=dsa_file.exe

    ~Omitted~

    # dsa_file specific parameters

    out_dir=%WORKING_DIRECTORY\BackupPDBinsert

    out_file=pdbinsert_%c_%n.txt

    check_interval=60

    operation=CYCLE

    cycle_num=3

    new_file_interval=86400

    new_file_start=0


    Definition example

    Windows

    [BackupPDBinsert]

    execute_style=on

    path=dsa_file.exe

    ~Omitted~

    # dsa_file specific parameters

    out_dir=D:\BackupPDBinsert

    out_file=pdbinsert_%c_%n.txt

    check_interval=60

    operation=CYCLE

    cycle_num=3

    new_file_interval=86400

    new_file_start=0


  4. Start the Service and Daemon

    Refer to "A.8 How to Start and Stop Resident Processes" for details. Additionally, make sure that the resident processes have started correctly.