Top
Systemwalker Service Quality Coordinator User's Guide
Systemwalker

1.3.2 Definition Method

Definition Procedure

  1. Make settings on the Systemwalker Service Quality Coordinator side.
    Definitions for getting Oracle performance information must be made in the collection template.

    Refer to "Chapter 9 Collection Template" for more information about how to make these definitions.

  2. Check and set up path information for Oracle.

    [Windows]

    Make sure that the path for Oracle has been set up in the PATH environment variable. The PATH environment variable should have been set up automatically when Oracle was installed, but the path for Oracle must be added to the PATH variable if it has not been set up already for some reason.

    Refer to the Oracle manuals for more information.

    [UNIX]

    Make settings in the collection template.

    Refer to "9.1 How to Set up Oracle Database Server" for more information.


If this linkage function is used, the following items are collected by default:

The definition procedure explained below allows the following items to also be collected:

Point

There is no need to perform the following procedure if the operating requirements can be met using the items that are collected by default.


Procedure for extending monitoring items

  1. Stop Systemwalker Service Quality Coordinator if it is running on the target node.

  2. Edit the "template.dat" file.

    Definition location

    [Windows]

    <variable file storage directory>\control\template.dat

    [UNIX]

    /etc/opt/FJSVssqc/template.dat

    Content to be modified

    :

    #########################################

    # Oracle Information

    [ORA]

    DCAID="ORA"

    INTERVAL=5

    SID=""

    USERNAME=""

    PASS=""

    VER="*.*.*"

    ORAHOME=""

    *Add here

    #########################################

    :

    The following keys can be added:

    Item name

    Key

    ORA_USR

    USR="ON" or "OFF"

    ORA_IO

    IO="ON" or "OFF"

    ORA_QUEUE

    QUEUE="ON" or "OFF"

    ORA_MEMORY

    MEMORY="ON" or "OFF"

    ORA_RETR

    RETR="ON" or "OFF"

    ORA_TSS

    TSS="ON" or "OFF"

    ORA_TSF

    TSF="ON" or "OFF"

    ORA_OSE

    OSE="ON" or "OFF"

    ORA_DFS

    DFS="ON" or "OFF"

    ORA_FS

    FS="ON" or "OFF"

    ORA_SEGS

    SEGS="ON" or "OFF"

    ORA_RC

    RC="ON" or "OFF"

    ORA_LC

    LC="ON" or "OFF"

    ORA_LT

    LT="ON" or "OFF"

    ORA_REDO

    REDO="ON" or "OFF"

    ORA_WAIT

    WAIT="ON" or "OFF"

    ORA_RBS

    RBS="ON" or "OFF"

    ORA_FMEM

    FMEM="ON" or "OFF"

    Add items, specifying "ON" for the keys for the items for which the item name is to be displayed in the Detailed tree of the Console, and specifying "OFF" for the keys for the items for which the item name does not need to be displayed.


  3. Edit the Oracle Collection SQL Definition Source file.

    Definition location

    [Windows]

    <variable file storage directory>\control\dsa_ora_all.sql

    <variable file storage directory>\control\dsa_ora_<Oracle version>.sql

    [UNIX]

    /opt/FJSVssqc/control/dsa_ora_all.sql

    /opt/FJSVssqc/control/dsa_ora_<Oracle version>.sql


    Definition files

    The "dsa_ora_all.sql" definition file contains definitions for the collection SQL statements that are common to all Oracle versions.

    The "dsa_ora_<Oracle version>.sql" definition files contain definitions for the collection SQL statements that are specific to each version of Oracle.

    This is because the SQL definition method for collecting ORA_IO varies depending on the version of Oracle.

    The definition files that have been prepared already are listed below.

    /etc/opt/FJSVssqc/control/dsa_ora_all.sql

    [For V9]

    /etc/opt/FJSVssqc/control/dsa_ora_v9.sql

    [For V10 or later]

    /etc/opt/FJSVssqc/control/dsa_ora_v10.sql

    For each of these files, remove the comment identifier "--" for the processing corresponding to the items to be monitored.

    The following example shows how to collect the "ORA_USR" item.

    Definition example

    [Before modification]

    The monitoring item names are determined here. However, "ORA_QUEUE" is replaced by "ORA QUE" and "ORA_MEMORY" is replaced by "ORA MEM".

    -- ORA USR records %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

    -- TABLES NEED TO BE READ: V$SYSSTAT

    -- The following data collection parameter set repo

    -- the database.

    --

    -- [0300] COLUMN

    -- (PKEY, INTERVAL, SAMPLE, INTERVAL, SAMPLE, IN

    -- DELIM=",";

    * -- PROMPT dsa_oracle_data_start 300 column 7 interva

    * -- SELECT VALUE SYSSTAT

    * -- FROM V$SYSSTAT

    * -- WHERE NAME IN ('logons cumulative'

    * -- ,'logons current'

    * -- ,'opened cursors cumulative'

    * -- ,'opened cursors current'

    * -- ,'user calls'

    * -- ,'user commits'

    * -- ,'user rollbacks'

    * -- )

    * -- ORDER BY NAME;


    Delete the "--" from within the scope of the SQL statement, starting from the "PROMPT" line (the lines indicated by *). Be careful not to delete the "--" in the header information.

    [After modification]

    The monitoring item names are determined here. However, "ORA_QUEUE" is replaced by "ORA QUE" and "ORA_MEMORY" is replaced by "ORA MEM".

    -- ORA USR records %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

    -- TABLES NEED TO BE READ: V$SYSSTAT

    -- The following data collection parameter set repo

    -- the database.

    --

    -- [0300] COLUMN

    -- (PKEY, INTERVAL, SAMPLE, INTERVAL, SAMPLE, IN

    -- DELIM=",";

    * PROMPT dsa_oracle_data_start 300 column 7 interva

    * SELECT VALUE SYSSTAT

    * FROM V$SYSSTAT

    * WHERE NAME IN ('logons cumulative'

    * ,'logons current'

    * ,'opened cursors cumulative'

    * ,'opened cursors current'

    * ,'user calls'

    * ,'user commits'

    * ,'user rollbacks'

    * )

    * ORDER BY NAME;


    Modify other monitoring items that need to be added in the same way.