Hitachi

JP1 Version 12 JP1/Performance Management - Remote Monitor for Oracle Description, User's Guide and Reference

2.6.3 Updating an instance environment

To update an instance environment, check the name of the instance that you want to update, and change the instance information. The instance information is set from a PFM - RM host.

Before you change an information item, check the following table. For details about Oracle instance information, see your Oracle documentation.

Organization of this subsection

(1) Windows

Table 2‒29: PFM - RM for Oracle instance information

Item

Description

Specifiable value

Default

oracle_sid

The value of this item can be updated.

ID of the monitored Oracle system (same value as the ORACLE_SID environment variable).

A character string of 255 or fewer bytes that does not include the following characters:

  • Spaces

  • Tabs

  • The following symbols:

    , < >

Previous value

oracle_home#1

The value of this item can be updated.

Oracle home folder of Oracle client used by PFM - RM for Oracle (same value as the ORACLE_HOME environment variable). #2

A character string of 255 or fewer bytes that does not include the following characters:

  • Spaces

  • Tabs

  • The following symbols:

    , < >

Previous value

oracle_version#1

The value of this item can be updated.

Version number of Oracle Client used by PFM - RM for Oracle.

To use Oracle Client 12c or later (about Oracle Client 18c) to monitor an Oracle Database, 12 is set.

A two-digit number.

  • Oracle 11g: 11

  • Oracle 12c or later: 12

Previous value

oracle_user#3

The value of this item can be updated.

Account for monitoring Oracle (for details about accounts that can be specified, and the required privileges, see 2.1.4(2) Create an Oracle account to be used in PFM - RM for Oracle).

A character string of 255 or fewer bytes that does not include the following characters:

  • Spaces

  • Tabs

  • The following symbols:

    , < >

Previous value

oracle_passwd#4

The value of this item can be updated.

Specify the password for the account specified in oracle_user.

A character string of 255 or fewer bytes that does not include the following characters:

  • Spaces

  • Tabs

  • The following symbols:

    , < >

Previous value

net_service_name#1,#5

The value of this item can be updated.

Net service name of the monitored database. For details about the net service name of the monitored database, see the Oracle documentation.

A character string of 255 or fewer bytes that does not include the following characters:

  • Spaces

  • Tabs

  • The following symbols:

    , < >

Previous value

retry_time

The value of this item can be updated.

The number of seconds for which reconnection is attempted when an authentication error is output during Oracle connection.

If an authentication error occurs after the specified period has passed, the PFM - RM for Oracle service stops. When the value is 0, the PFM - RM for Oracle service stops without retrying to re-establish connection in the event of an authentication error.

This item is enabled when startup_always is N.

The specification of this item is ignored when startup_always is Y.

0 to 600 (in seconds).

Previous value

log_path

The value of this item can be updated.

Specify the absolute path name of the agent log output folder.

A character string of 245 or fewer bytes that does not include the following characters:

  • Tabs

  • The following symbols:

    / : , ; * ? " < > |

Notes:

  • You can specify the path to a folder under the installation folder only when the default folder is set.

  • You cannot specify the path to a folder that is used as the output destination of another instance.

Previous value

log_size

The value of this item can be updated.

Specify the maximum size of each agent log file.

1 to 32 (in kilobytes). 16 or a greater value is recommended.

Previous value

timeout

The value of this item can be updated.

The timeout period for Oracle access during a query.

0, or 10 to 3600 (in seconds).

When 0 is specified, timeout monitoring is not performed. When a value from 1 to 9 is specified, it is changed to 10 at runtime.

Previous value

sql_option#6

The value of this item can be updated.

When Y is specified, information about the following items#5 is not collected for PI_PIDB and PD_PDTS records, and the value specified by 0 or numeric_10 is set.

{ Y | N }

Previous value

numeric_10

The value of this item can be updated.

When sql_option is set to Y, the value specified is set for items for which information is not collected. If sql_option is set to N, this specification is disregarded.

0 to 99999.

Note that if the value specified exceeds the maximum value for the data format of the set field (32767 for short and 65535 for ushort), the maximum value for the data format is set.#7

Previous value

startup_always

The value of this item can be updated.

PFM - RM for Oracle may stop due to an Oracle connection error, such as when the monitored Oracle is still starting up when PFM - RM for Oracle starts up.

If Y is specified, start processing continues even if a connection error occurs. If N is specified, start processing will stop if an error occurs.

{ Y | N }

Previous value

localtemp_option#8

The value of this item can be updated.

Option for switching the display of the free space of the locally managed temporary tablespace of PD_PDDB, PI_PIDB, PD_PDDF, PI_PIDF, PD_PDTF, PD_PDTS, and PD_PCTS records.

If Y is specified, display the size of the free space. If N is specified, display the size of the unallocated space.

{ Y | N }

Previous value

nls_lang#9

The value of this item can be updated.

Option for specifying the character encoding used for communication between PFM - RM for Oracle and Oracle Database.

Character code set:

  • In Japanese Windows:

    {AMERICAN_AMERICA.US7ASCII | AMERICAN_AMERICA.JA16SJISTILDE}

  • In Simplified-Chinese Windows:

    {AMERICAN_AMERICA.US7ASCII | AMERICAN_AMERICA.ZHS32GB18030}

  • Other case:

    AMERICAN_AMERICA.US7ASCII

Previous value

undospace_option#10

The value of this item can be updated.

Option for switching how the value displayed as the free space in the UNDO tablespace of the PD_PDDB, PI_PIDB, PD_PDDF, PI_PIDF, PD_PDTS, and PD_PCTS records is determined.

If N is specified, the size of the unallocated space is displayed.

If Y is specified, the size of the free space is displayed.

{ Y | N }

Previous value
#1

The prerequisite product for PFM - RM for Oracle version 10-50 or earlier was Oracle Client 32-bit. The prerequisite product for version 11-00 or later is Oracle Client 64-bit.

The setting method for version 10-50 or earlier cannot be used to connect to an Oracle Database. Therefore, you must set up PFM - RM for Oracle version 11-00 or later on the assumption that Oracle Client 64-bit is used.

Because instance information settings have been changed in version 11-00 or later as shown in the following table, make sure that the information is set up correctly:

Item

PFM - RM for Oracle

10-50 or earlier

11-00 or later

oracle_home

Specify the Oracle home folder for Oracle Client 32-bit.

Specify the Oracle home folder for Oracle Client 64-bit.

oracle_version

Specify the version of Oracle Client 32-bit.

Specify the version of Oracle Client 64-bit.

To use Oracle Client 12c or later (about Oracle Client 18c) to monitor an Oracle Database, 12 is set.

net_service_name

Specify the net service name that can be used to connect to the monitoring-target Oracle Database specified in Oracle Client 32-bit.

Specify the net service name that can be used to connect to the monitoring-target Oracle Database specified in Oracle Client 64-bit.

Notes:

  • To upgrade PFM - RM for Oracle 10-50 or earlier to 11-00 or later, instance information is subject to change, and must therefore be updated before starting the PFM - RM for Oracle service.

    Note that Oracle Client 32-bit is no longer needed, and can be uninstalled if it is not used by any product other than PFM - RM for Oracle.

  • If you specify ORACLE_HOME for Oracle Client 32-bit and start PFM - RM for Oracle, the KAVL18020-E message appears.

#2

If PFM - RM for Oracle uses the client library of an Oracle Database (when Oracle Database 64-bit is installed on a server with PFM - RM for Oracle installed), specify the Oracle home folder of the Oracle Database.

#3

To change a user, use the following procedure:

  1. Delete the objects created by the user you want to change.

  2. Register new objects as the new user.

Performance data is not deleted when a user is changed.

For details about how to delete objects, see 2.3.2(1)(c) Deleting the objects registered in the Oracle Database. For details about how to register objects, see 2.1.4(3)(c) Registering objects in the Oracle Database.

#4

If the expiration date is set on oracle_passwd, once the password is out of date connections to Oracle fail so that PFM - RM for Oracle cannot collect the performance information. In order to avoid connection errors, perform either of the following procedures before the password is expired:

  • Unset the expiration date of the password

  • After updating password, execute the jpcconf inst setup command to update oracle_passwd.

Note that the Oracle DEFAULT profile is applied to the Oracle account created by mk_rmus.sql.

#5

Specify in advance the network service (such as tnsnames.ora) of the Oracle Client used by PFM - RM for Oracle.

Configure the network service definition (such as listener.ora) and run the listener process in advance.

When monitoring Oracle Database instances in an Oracle RAC configuration, set up the PFM - RM for Oracle so that it monitors Oracle Database instances on each node. For details about how to set up, see the Oracle documentation.

Note that the location of tnsnames.ora must be:

oracle_home\network\admin

If tnsnames.ora is located on other folder, PFM - RM for Oracle cannot connect to Oracle.

#6

To obtain each piece of Oracle segment-related information, PFM - RM for Oracle searches Oracle's static data dictionary views DBA_SEGMENTS. If a large number of segments (more than hundreds of thousands) exist for Oracle, information collection requires a significant amount of time. As such, when a large number of segments exist, and the information listed in the following table no longer needs to be collected, set the sql_option to Y during operation.

Table 2‒30: Record names and the values specified for numeric_10 (updating instance information)

Record Name

PFM - View name

Value specified for numeric_10

PD_PDTS

Segments

Enabled

Extents

Enabled

PI_PIDB

DB Files %

Enabled

Log Files %

Enabled

NextAlloc Fails

Enabled

Tablespaces

Enabled

Rollback Segments

Enabled

Rollback Segments Trans

Enabled

Blocks

Enabled

Segments

Enabled

Extents

Enabled

Free Mbytes

Enabled

Overextended

Enabled

High Max Extent

Enabled

Datafiles

Enabled

Mbytes

Enabled

Free Extents

Enabled

Free%

Enabled

Free Change

Enabled

Write%

Enabled

Write/sec

Enabled

Redo Files

Enabled

Links

Enabled

Links Logged On

Enabled

Links In Tran

Enabled

Links Open Cursors

Enabled

Used Change

Enabled

Used Mbytes

Enabled

Rollback Segments Hit%

Enabled

Sort Segments

Enabled

Sorting Users

Enabled

Physical Blocks Read

Always set to 0 because it is a delta item.

Physical Blocks Written

Always set to 0 because it is a delta item.

Physical Reads

Always set to 0 because it is a delta item.

Physical Writes

Always set to 0 because it is a delta item.

#7

If the field format for each record is float or double, since the data is a floating-point number, it may be rounded depending on the specified value.

Example:

When numeric_10 is set to 32767, it may be displayed as 32760.

#8

When localtemp_option is set to Y, collect free space of the locally managed temporary tablespace and information about the extents from v$sort_segment or v$temp_extent_pool of the dynamic performance view. The displayed values of the size of free space are calculated from the size of the used space.

When localtemp_option is set to N, collect free space of the locally managed temporary tablespace and information about the extents from v$temp_space_header of the dynamic performance view. The displayed values of the size of free space are the size of the unallocated space. Since the allocated space is not freed until the temporary tablespace is reconstructed or recreated, the displayed values of free space do not increase until the space is freed.

When issuing query to v$temp_extent_pool view, the Oracle instance goes to sleep. Since this may have effect on the performance of the Oracle instance, you need adequate consideration before localtemp_option is set to Y. For details, see your Oracle documentation.

The following records use v$temp_extent_pool view:

  • Data File (PD_PDDF)

  • Data File Interval (PI_PIDF)

#9

The following figure shows the relationship among data, language environment of the OS, and instance information handled by PFM - RM for Oracle.

Figure 2‒11: Relationship between data and the setting values

[Figure]

PFM - RM for Oracle can collect performance data in SJIS (in Japanese Windows) and GB18030 (in Simplified-Chinese Windows) format as well as 7-bit ASCII format. You must specify nls_lang variable for the language environment of the OS, NLS_CHARACTERSET of the Oracle.

OS language of PFM - RM for Oracle installed

NLS_CHARACTERSET of the monitored Oracle

(Database character set)

nls_lang instance information (this item)

Japanese

JA16SJISTILDE

AMERICAN_AMERICA.JA16SJISTILDE or AMERICAN_AMERICA.US7ASCII#

JA16SJIS

other

AMERICAN_AMERICA.US7ASCII#

Simplified-Chinese

ZHS16GBK

AMERICAN_AMERICA.ZHS32GB18030 or AMERICAN_AMERICA.US7ASCII#

AL32UTF8

other

AMERICAN_AMERICA.US7ASCII#

other language

notdependent

AMERICAN_AMERICA.US7ASCII#
#

Performance data is collected within the scope of 7-bit ASCII characters, likely resulting in unreadable characters.

For any other combination, performance data is collected within the scope of 7-bit ASCII characters, likely resulting in unreadable characters.

When you specify an invalid character code set for the nls_lang instance information, the message KAVL18302-W with errcode 12705 is output, and the connection with Oracle will fail.

In the following cases as well, unreadable characters might occur in the performance data:

  1. The Oracle column length is exceeded.

    If you store data that exceeds the Oracle column length, the last character might become unreadable. If you use PFM - RM for Oracle to collect data in Oracle and that data contains unreadable characters, the last character of the performance data will be unreadable.

  2. The field size of PFM - RM for Oracle is exceeded.

    PFM - RM for Oracle collects performance data of the record field size from Oracle. Therefore, if Oracle contains data that exceeds the field size, the last character of the performance data might be unreadable. The following table lists the applicable fields:

    Record name

    Field name

    Filed size (unit: bytes)

    Parameter Values(PD_PDP)

    Value

    512

    SQL Text(PD_PDSQ)

    Explain Plan

    30,000

    SQL Text

    30,000
#10

When undospace_option is set to N, the size of the unallocated space is collected as the amount of free space in the UNDO tablespace. Space in the UNDO tablespace that becomes available because its retention period has expired is treated as allocated space until it is released.

When undospace_option is set to Y, the size of the free space is collected as the amount of free space in the UNDO tablespace. Space of the UNDO tablespace that becomes available because its retention period has expired is included in the size of the free space.

The following table shows the fields whose values change depending on the specification of the undospace_option:

Record name

Field name

Data File (PD_PDDF)

Free %

Free Mbytes

Used Mbytes

Data File Interval

(PI_PIDF)

Free %

Free Change

Free Mbytes

Used Change

Used Mbytes

Database (PD_PDDB)

Free %

Free Mbytes

Used Mbytes

Database Interval

(PI_PIDB)

Free %

Free Change

Free Mbytes

Used Change

Used Mbytes

Tablespace (PD_PDTS)

Free %

Free Mbytes

Used Mbytes

Max Extend Free %

Max Extend Free Mbytes

Collection Tablespace 2

(PD_PCTS)

Free Mbytes

Use the jpcconf inst list command to check the instance name. To update an instance environment, use the jpcconf inst setup command.

Updating an instance environment involves the steps described below. To update multiple instance environments, repeat the procedure for each instance environment.

To update an instance environment:

  1. Find the instance name.

    Execute the jpcconf inst list command specified with the service key that indicates PFM - RM for Oracle. 

    jpcconf inst list -key RMOracle

    If the specified instance name is SDC, the command displays SDC.

  2. If the PFM - RM for Oracle service is active in the instance environment that is to be updated, stop the service.

    For details about stopping services, see the chapter on starting and stopping Performance Management in the JP1/Performance Management User's Guide.

    If the service is still active in the instance environment that is to be updated when you execute the jpcconf inst setup command, a confirmation message is displayed to enable you to stop the service. If you stop the service, update processing resumes; if you do not stop the service, update processing is canceled.

  3. Execute the jpcconf inst setup command specified with the service key that indicates PFM - RM for Oracle and the instance name.

    For example, if you are updating the instance environment for the PFM - RM for Oracle with instance name SDC, execute the following command: 

    jpcconf inst setup -key RMOracle -inst SDC

  4. Update the instance information for Oracle.

    Enter the information shown in Table 2-29 in accordance with the command's instructions. The current settings are displayed (except for the value of oracle_passwd). To use the displayed value, press the Enter key. When you have finished entering information, the instance environment is updated.

  5. Restart the service in the updated instance environment.

    For details about starting services, see the chapter on starting and stopping Performance Management in the JP1/Performance Management User's Guide.

For details about commands, see the chapter on commands in the manual JP1/Performance Management Reference.

To Page Top

(2) UNIX

Table 2‒31: PFM - RM for Oracle instance information

Item

Description

Specifiable value

Default

oracle_sid

The value of this item can be updated.

ID of the monitored Oracle system (same value as the ORACLE_SID environment variable).

A character string of 255 or fewer bytes that does not include the following characters:

  • Spaces

  • Tabs

  • The following symbols:

    , < >

Previous value

oracle_home#1

The value of this item can be updated.

The value of this item can be updated.

Oracle home folder of Oracle client used by PFM - RM for Oracle (same value as the ORACLE_HOME environment variable). #1

A character string of 255 or fewer bytes that does not include the following characters:

  • Spaces

  • Tabs

  • The following symbols:

    , < >

Previous value

oracle_version#1

The value of this item can be updated.

Version number of Oracle Client used by PFM - RM for Oracle.

To use Oracle Client 12c or later (about Oracle Client 18c) to monitor an Oracle Database, 12 is set.

A two-digit number.

  • Oracle 11g: 11

  • Oracle 12c or later: 12

Previous value

oracle_user#3

The value of this item can be updated.

Account for monitoring Oracle (for details about accounts that can be specified, and the required privileges, see 2.2.4(3) Create an Oracle account to be used in PFM - RM for Oracle).#2

A character string of 255 or fewer bytes that does not include the following characters:

  • Spaces

  • Tabs

  • The following symbols:

    , < >

Previous value

oracle_passwd#4

The value of this item can be updated.

Specify the password for the account specified in oracle_user.

A character string of 255 or fewer bytes that does not include the following characters:

  • Spaces

  • Tabs

  • The following symbols:

    , < >

Previous value

net_service_name#1,#5

The value of this item can be updated.

Net service name of the monitored database. For details about the net service name of the monitored database, see the Oracle documentation.

A character string of 255 or fewer bytes that does not include the following characters:

  • Spaces

  • Tabs

  • The following symbols:

    , < >

Previous value

log_path#6

The value of this item can be updated.

Specify the absolute path name of the agent log output folder.

A character string of 245 or fewer bytes that does not include the following characters:

  • Tabs

  • The following symbols:

    / : , ; * ? " < > |

Notes:

  • You can specify the path to a folder under the installation folder only when the default folder is set.

  • You cannot specify the path to a folder that is used as the output destination of another instance.

Previous value

log_size

The value of this item can be updated.

Specify the maximum size of each agent log file.

1 to 32 (in kilobytes). 16 or a greater value is recommended.

Previous value

timeout

The value of this item can be updated.

The timeout period for Oracle access during a query.

0, or 10 to 3600 (in seconds).

When 0 is specified, timeout monitoring is not performed. When a value from 1 to 9 is specified, it is changed to 10 at runtime.

Previous value

sql_option#7

The value of this item can be updated.

When Y is specified, information about the following items#6 is not collected for PI_PIDB and PD_PDTS records, and the value specified by 0 or numeric_10 is set.

{ Y | N }

Previous value

numeric_10

The value of this item can be updated.

When sql_option is set to Y, the value specified is set for items for which information is not collected. If sql_option is set to N, this specification is disregarded.

0 to 99999.

Note that if the value specified exceeds the maximum value for the data format of the set field (32767 for short and 65535 for ushort), the maximum value for the data format is set.#7

Previous value

startup_always

The value of this item can be updated.

PFM - RM for Oracle may stop due to an Oracle connection error, such as when the monitored Oracle is still starting up when PFM - RM for Oracle starts up.

If Y is specified, start processing continues even if a connection error occurs. If N is specified, start processing will stop if an error occurs.

{ Y | N }

Previous value

localtemp_option#9

The value of this item can be updated.

Option for switching the display of the free space of the locally managed temporary tablespace of PD_PDDB, PI_PIDB, PD_PDDF, PI_PIDF, PD_PDTF, PD_PDTS, and PD_PCTS records.

If Y is specified, display the size of the free space. If N is specified, display the size of the unallocated space.

{ Y | N }

Previous value

nls_lang#10

The value of this item can be updated.

Option for specifying the character encoding used for communication between PFM - RM for Oracle and Oracle Database.

Character code set:

According to LANG of the OS when at the start time of the PFM - RM for Oracle.

  • UTF-8 (Japanese or Simplified-Chinese):

    {AMERICAN_AMERICA.US7ASCII | AMERICAN_AMERICA.AL32UTF8}

  • GB18030:

    {AMERICAN_AMERICA.US7ASCII | AMERICAN_AMERICA.ZHS32GB18030}

  • Other case:

    AMERICAN_AMERICA.US7ASCII

Previous value

undospace_option#11

The value of this item can be updated.

Option for switching how the value displayed as the free space in the UNDO tablespace of the PD_PDDB, PI_PIDB, PD_PDDF, PI_PIDF, PD_PDTS, and PD_PCTS records is determined.

If N is specified, the size of the unallocated space is displayed.

If Y is specified, the size of the free space is displayed.

{ Y | N }

Previous value
#1

The prerequisite product for PFM - RM for Oracle version 10-50 or earlier was Oracle Client 32-bit. The prerequisite product for version 11-00 or later is Oracle Client 64-bit.

The setting method for version 10-50 or earlier cannot be used to connect to an Oracle Database. Therefore, you must set up PFM - RM for Oracle version 11-00 or later on the assumption that Oracle Client 64-bit is used.

Because instance information settings have been changed in version 11-00 or later as shown in the following table, make sure that the information is set up correctly:

Item

PFM - RM for Oracle

10-50 or earlier

11-00 or later

oracle_home

Specify the Oracle home folder for Oracle Client 32-bit.

Specify the Oracle home folder for Oracle Client 64-bit.

oracle_version

Specify the version of Oracle Client 32-bit.

Specify the version of Oracle Client 64-bit.

To use Oracle Client 12c or later (about Oracle Client 18c) to monitor an Oracle Database, 12 is set.

net_service_name

Specify the net service name that can be used to connect to the monitoring-target Oracle Database specified in Oracle Client 32-bit.

Specify the net service name that can be used to connect to the monitoring-target Oracle Database specified in Oracle Client 64-bit.

Notes:

  • To upgrade PFM - RM for Oracle 10-50 or earlier to 11-00 or later, instance information is subject to change, and must therefore be updated before starting the PFM - RM for Oracle service.

    Note that Oracle Client 32-bit is no longer needed, and can be uninstalled if it is not used by any product other than PFM - RM for Oracle.

  • If you specify ORACLE_HOME for Oracle Client 32-bit and start PFM - RM for Oracle, the KAVL18011-E and KAVL18021-E message appear.

#2

If PFM - RM for Oracle uses the client library of an Oracle Database in which Oracle Client 64-bit has been installed, specify the Oracle home folder of the Oracle Database.

#3

To change a user, use the following procedure:

  1. Delete the objects created by the user you want to change.

  2. Register new objects as the new user.

Performance data is not deleted when a user is changed.

For details about how to delete objects, see 2.4.2(1)(c) Deleting the objects registered in the Oracle Database. For details about how to register objects, see 2.2.4(4)(c) Registering objects in the Oracle Database.

#4

If the expiration date is set on oracle_passwd, once the password is out of date connections to Oracle fail so that PFM - RM for Oracle cannot collect the performance information. In order to avoid connection errors, perform either of the following procedures before the password is expired:

  • Unset the expiration date of the password

  • After updating password, execute the jpcconf inst setup command to update oracle_passwd.

Note that the Oracle DEFAULT profile is applied to the Oracle account created by mk_rmus.sql.

#5

Specify in advance the network service (such as tnsnames.ora) of the Oracle Client used by PFM - RM for Oracle.

Configure the network service definition (such as listener.ora) and run the listener process in advance.

When monitoring Oracle Database instances in an Oracle RAC configuration, set up the PFM - RM for Oracle so that it monitors Oracle Database instances on each node. For details about how to set up, see the Oracle documentation.

Note that the location of tnsnames.ora must be:

oracle_home/network/admin

If tnsnames.ora is located on other directory, must therefore set to TNS_ADMIN environment variable in starting user of PFM - RM for Oracle before starting the PFM - RM for Oracle service.

For details about the TNS_ADMIN environment variable, see the Oracle documentation.

#6

Manually save the old path information in a file as history data, since the information is not saved automatically. You may need to acquire the agent log information from the old directory if a problem occurs.

#7

To obtain each piece of Oracle segment-related information, PFM - RM for Oracle searches Oracle's static data dictionary views DBA_SEGMENTS. If a large number of segments (more than hundreds of thousands) exist for Oracle, information collection requires a significant amount of time. As such, when a large number of segments exist, and the information listed in the following table no longer needs to be collected, set the sql_option to Y during operation.

Table 2‒32: Record names and the values specified for numeric_10 (updating instance information)

Record Name

PFM - View name

Value specified for numeric_10

PD_PDTS

Segments

Enabled

Extents

Enabled

PI_PIDB

DB Files %

Enabled

Log Files %

Enabled

NextAlloc Fails

Enabled

Tablespaces

Enabled

Rollback Segments

Enabled

Rollback Segments Trans

Enabled

Blocks

Enabled

Segments

Enabled

Extents

Enabled

Free Mbytes

Enabled

Overextended

Enabled

High Max Extent

Enabled

Datafiles

Enabled

Mbytes

Enabled

Free Extents

Enabled

Free%

Enabled

Free Change

Enabled

Write%

Enabled

Write/sec

Enabled

Redo Files

Enabled

Links

Enabled

Links Logged On

Enabled

Links In Tran

Enabled

Links Open Cursors

Enabled

Used Change

Enabled

Used Mbytes

Enabled

Rollback Segments Hit%

Enabled

Sort Segments

Enabled

Sorting Users

Enabled

Physical Blocks Read

Always set to 0 because it is a delta item.

Physical Blocks Written

Always set to 0 because it is a delta item.

Physical Reads

Always set to 0 because it is a delta item.

Physical Writes

Always set to 0 because it is a delta item.

#8

If the field format for each record is float or double, since the data is a floating-point number, it may be rounded depending on the specified value.

Example:

When numeric_10 is set to 32767, it may be displayed as 32760.

#9

When localtemp_option is set to Y, collect free space of the locally managed temporary tablespace and information about the extents from v$sort_segment or v$temp_extent_pool of the dynamic performance view. The displayed values of the size of free space are calculated from the size of the used space.

When localtemp_option is set to N, collect free space of the locally managed temporary tablespace and information about the extents from v$temp_space_header of the dynamic performance view. The displayed values of the size of free space are the size of the unallocated space. Since the allocated space is not freed until the temporary tablespace is reconstructed or recreated, the displayed values of free space do not increase until the space is freed.

When issuing query to v$temp_extent_pool view, the Oracle instance goes to sleep. Since this may have effect on the performance of the Oracle instance, you need adequate consideration before localtemp_option is set to Y. For details, see your Oracle documentation.

The following records use v$temp_extent_pool view:

  • Data File (PD_PDDF)

  • Data File Interval (PI_PIDF)

#10

The following figure shows the relationship among data, LANG environment variable of at the start time of the PFM - RM for Oracle, and instance information handled by PFM - RM for Oracle.

Figure 2‒12: Relationship between data and the setting values

[Figure]

PFM - RM for Oracle can collect performance data in UTF-8 format (for Japanese and Chinese environment) and GB18030 format (for Chinese environment) as well as 7-bit ASCII format.

The following table lists the values that can be set in nls_lang instance information for the LANG environment variable at the start time of PFM - RM for Oracle:

LANG environment variable of at the start time of PFM - RM for Oracle

nls_lang instance information

(this item)

ja_JP.UTF-8,

ja_JP.utf-8,

zh_CN.UTF-8,

zh_CN.utf8

AMERICAN_AMERICA.AL32UTF8 or AMERICAN_AMERICA.US7ASCII#

zh_CN.gb18030

AMERICAN_AMERICA.ZHS32GB18030 or AMERICAN_AMERICA.US7ASCII#

Other than the above

AMERICAN_AMERICA.US7ASCII#
#

Performance data is collected within the scope of 7-bit ASCII characters, likely resulting in unreadable characters.

For any other combination, performance data is collected within the scope of 7-bit ASCII characters, likely resulting in unreadable characters.

For details about how to set the LANG environment variable of the OS, see 2.2.4(1) Set the LANG environment variable.

When you specify an invalid character code set for the nls_lang instance information, the message KAVL18302-W with errcode 12705 is output, and connection with Oracle will fail.

In the following cases as well, unreadable or lack of characters might occur in the performance data:

  1. The Oracle column length is exceeded.

    If you store data that exceeds the Oracle column length, the last character might become unreadable. If you use PFM - RM for Oracle to collect data in Oracle that contains unreadable characters, the last character of the performance data will be unreadable.

  2. The field size of PFM - RM for Oracle is exceeded.

    PFM - RM for Oracle collects performance data of the record field size from Oracle. Therefore, if Oracle contains data that exceeds the field size, the last character of the performance data might be unreadable. The following table lists the applicable fields:

    Record name

    Field name

    Field size

    (Unit: bytes)

    Parameter Values (PD_PDP)

    Value

    512

    SQL Text (PD_PDSQ)

    Explain Plan

    30000

    SQL Text

    30000

  3. Unreadable or lack of characters in different between database character set of the Oracle and nls_lang instance variable of the PFM - RM for Oracle.

    A data of 2 bytes on the basis of Oracle may be collected at 3 bytes when you set AMERICAN_AMERICA.AL32UTF8 in nls_lang and a database character set for the monitoring is not UTF-8. Therefore, if performance data takes from ORACLE that exceeds the field size, the last character of the performance data might be unreadable. The following table lists the applicable fields:

    Record name

    Field name

    Field size

    (Unit: bytes)

    Collection Tablespace 2(PD_PCTS)

    Tablespace Name

    30

    Collection Instance 2 (PD_PCI)

    Recovery File Dest

    513

    Data File(PD_PDDF)

    File Name

    513

    Tablespace Name

    30

    Data File Interval(PI_PIDF)

    File Name

    513

    Tablespace Name

    30

    Database(PD_PDDB)

    DB Name

    9

    Database Interval(PI_PIDB)

    DB Name

    9

    Instance(PD_PDI)

    Host

    64

    Lock Waiters(PD_PDLW)

    Holding User

    30

    Waiting User

    30

    Minimum Database Interval 2(PI_PMDB)

    DB Name

    9

    Minimum Data File Interval 2(PI_PMDF)

    File Name

    513

    Minimum Tablespace Interval 2(PI_PMTS)

    Tablespace Name

    30

    Open Cursor(PD_PDOC)

    Program

    48

    SQL Text

    60

    Parameter Values(PD_PDP)

    Value

    512

    Session Detail(PD_PDS)

    Machine

    64

    Module

    48

    OS User

    30

    Program

    64

    Schema Name

    30

    User

    30

    Session I/O Interval(PI_PIIO)

    User

    30

    Session Statistics Summary(PD_PDS2)

    Program

    48

    User

    30

    SQL Text(PD_PDSQ)

    Explain Plan

    30,000

    SQL Text

    30,000

    Tablespace Fragmentation(PD_PDTF)

    Tablespace Name

    30

    Tablespace Interval(PI_PITS)

    Tablespace Name

    30

    Tablespace(PD_PDTS)

    Tablespace Name

    30

    Transaction(PD_PDTR)

    User

    30

    Transaction Lock(PD_PDTL)

    Object Name

    30

    Owner

    30

    User

    30
#11

When undospace_option is set to N, the size of the unallocated space is collected as the amount of free space in the UNDO tablespace. Space in the UNDO tablespace that becomes available because its retention period has expired is treated as allocated space until it is released.

When undospace_option is set to Y, the size of the free space is collected as the amount of free space in the UNDO tablespace. Space of the UNDO tablespace that becomes available because its retention period has expired is included in the size of the free space.

The following table shows the fields whose values change depending on the specification of the undospace_option:

Record name

Field name

Data File (PD_PDDF)

Free %

Free Mbytes

Used Mbytes

Data File Interval

(PI_PIDF)

Free %

Free Change

Free Mbytes

Used Change

Used Mbytes

Database (PD_PDDB)

Free %

Free Mbytes

Used Mbytes

Database Interval

(PI_PIDB)

Free %

Free Change

Free Mbytes

Used Change

Used Mbytes

Tablespace (PD_PDTS)

Free %

Free Mbytes

Used Mbytes

Max Extend Free %

Max Extend Free Mbytes

Collection Tablespace 2

(PD_PCTS)

Free Mbytes

Use the jpcconf inst list command to check the instance name. To update an instance environment, use the jpcconf inst setup command.

Updating an instance environment involves the steps described below. To update multiple instance environments, repeat the procedure for each instance environment.

To update an instance environment:

  1. Find the instance name.

    Execute the jpcconf inst list command specified with the service key that indicates PFM - RM for Oracle. 

    jpcconf inst list -key RMOracle

    If the specified instance name is SDC, the command displays SDC.

  2. If the PFM - RM for Oracle service is active in the instance environment that is to be updated, stop the service.

    For details about stopping services, see the chapter on starting and stopping Performance Management in the JP1/Performance Management User's Guide.

    If the service is still active in the instance environment that is to be updated when you execute the jpcconf inst setup command, a confirmation message is displayed to enable you to stop the service. If you stop the service, update processing resumes; if you do not stop the service, update processing is canceled.

  3. Execute the jpcconf inst setup command specified with the service key that indicates PFM - RM for Oracle and the instance name.

    For example, if you are updating the instance environment for the PFM - RM for Oracle with instance name SDC, execute the following command: 

    jpcconf inst setup -key RMOracle -inst SDC

  4. Update the instance information for Oracle.

    Enter the information shown in Table 2-31 in accordance with the command's instructions. The current settings are displayed (except for the value of oracle_passwd). To use the displayed value, press the Enter key. When you have finished entering information, the instance environment is updated.

  5. Restart the service in the updated instance environment.

    For details about starting services, see the chapter on starting and stopping Performance Management in the JP1/Performance Management User's Guide.

For details about commands, see the chapter on commands in the manual JP1/Performance Management Reference.

To Page Top

Copyright (C) 2019, 2020, Hitachi, Ltd.

Copyright (C) 2019, 2020, Hitachi Solutions, Ltd.