2.2.1 Preparation for installing and setting up PFM - RM for Oracle (UNIX)

Check the following before installing and setting up PFM - RM for Oracle.

Organization of this subsection
(1) OS requirements
(2) Network environment settings
(3) OS user permission required to install PFM - RM
(4) Prerequisite programs
(5) Installation and setup in a cluster system
(6) Preparation for acquiring materials when a failure occurs
(7) Cautionary notes

(1) OS requirements

PFM - RM for Oracle runs on the following OSs:

(2) Network environment settings

The following describes the network environment required to run Performance Management.

(a) IP address settings

The PFM - RM host must be set up in a network environment where IP addresses can be resolved from host names. PFM - RM for Oracle will not start in an environment where IP addresses cannot be resolved.

You can use the real host name as a monitoring host name (a host name used in Performance Management System).

In a Windows system, set up the environment so that an IP address can be resolved from the host name returned by the hostname command. In a UNIX system, set up the environment so that an IP address can be resolved from the host name returned by the uname -n command.

For details about the configuration of a monitoring host name, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Note that IP addresses set in the jpchosts file are not used for resolving the IP addresses of monitoring targets.

Use one of the following methods to set the host name and IP address of hosts monitored by Performance Management programs:

Use a real host name or an alias name for the monitoring host name.

For details about the structure of a monitoring host name, see the chapter that describes how to change the system configuration in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Notes on setting IP addresses:
  • If you intend to use Performance Management within multiple LAN environments, set the IP addresses in the jpchosts file. For details, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
  • Performance Management cannot operate on the hosts to which IP addresses are assigned dynamically by DHCP. Make sure that all the hosts on which Performance Management programs are installed are configured with user-specified static IP addresses.
(b) Settings when IPv6 used

Performance Management supports IPv6 environments as well as IPv4 environments as a network configuration. Therefore, Performance Management can operate even in a network configuration in which both an IPv4 environment and an IPv6 environment are used.

PFM - RM for Oracle can communicate with PFM - Manager via IPv6. Note that this explanation applies only when the OS of a host on which PFM - RM for Oracle and PFM - Manager are installed is Windows Server 2008 R2 or Linux.

For details about the scope of communication in an environment with both IPv4 and IPv6, see M. About Communication in IPv4 Environments and IPv6 Environments.

When you want to use IPv6 for communication between PFM - Manager and PFM - RM for Oracle, the settings for using IPv6 must be enabled for both the PFM - Manager host and the PFM - RM host. You can specify the settings by executing the jpcconf ipv6 enable command. The following describes when the command needs to be executed and when it does not need to be executed.

Cases when the jpcconf ipv6 enable command needs to be executed:
  • When switching from an IPv4 environment to an IPv6 environment on each host
  • When switching the PFM - Manager environment from IPv4 to IPv6 in an environment in which both IPv4 and IPv6 are used
Cases when the jpcconf ipv6 enable command does not need to be executed:
  • When each host already operates in an IPv6 environment
  • When PFM - Manager operates in an IPv6 environment in an environment in which both IPv4 and IPv6 are used

The following shows an example of executing the jpcconf ipv6 enable command:

jpcconf ipv6 enable

For details about the jpcconf ipv6 enable command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference. For details about the conditions or occasions for executing the jpcconf ipv6 enable command, see the chapter that describes network configuration examples in an environment that includes IPv6 in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

When you use IPv6 for communication between a monitored host and PFM - RM for Oracle, specify the name of a monitored host on which name resolution can be performed.

Communication between PFM - RM for Oracle and a monitoring target is performed with an IP address that can be resolved. Also, if an IPv4 environment and an IPv6 environment are both used, and communication between PFM - RM for Oracle and the monitoring target fails with an IP address that can be resolved, the communication is not retried by using another IP address.

For example, if communication fails when IPv4 is used, IPv6 is not used to retry communication. Similarly, if communication fails when IPv6 is used, IPv4 is not used to retry communication. Make sure beforehand that a connection can be established.

(c) Port number settings

The following table shows the default port numbers assigned to the services of Performance Management programs. For other services and programs, available port numbers are automatically assigned each time they are started. If you use Performance Management in a firewall environment, use fixed port numbers. For details about how to set fixed port numbers, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Table 2-13 Default port numbers for Performance Management program services (in UNIX)

Service descriptionService nameParameterPort numberRemarks
Service configuration information management facilityName Serverjp1pcnsvr22285The port number used by the Name Server service of PFM - Manager. This port is set up on every Performance Management host.
OpenView linkage facilityNNM Object Managerjp1pcovsvr22292The port number used by the OpenView linkage facility of PFM - Manager and PFM - Base to provide communication between the map manager and object manager. This port is set up on the hosts on which PFM - Manager and PFM - Base are installed.
Service status management facilityStatus Serverjp1pcstatsvr22350The port number used by the Status Server service of PFM - Manager and PFM - Base. This port is set up on the hosts on which PFM - Manager and PFM - Base are installed.
Monitoring console communication facilityView Serverjp1pcvsvr22286The port number used by the View Server service of PFM - Manager.
This port is set up on the hosts on which PFM - Manager is installed.
Web service facilityWeb Service--20358The port number used by the Web Service service of PFM - Web Console.
Web container facilityWeb Console--20359
20360
The port number used by the Web Console service of PFM - Web Console.
JP1/ITSLM linkage facilityJP1/ITSLM--20905The port number set by JP1/ITSLM.
Legend:
--: None

(3) OS user permission required to install PFM - RM

To install PFM - RM for Oracle, use an account with superuser privileges.

(4) Prerequisite programs

This subsection describes the prerequisite programs required to install PFM - RM for Oracle.

The host on which PFM - RM for Oracle is installed is hereafter called "PFM - RM host".

There are roughly two cases in the program configuration of PFM - RM for Oracle. The actual program configuration needs to be determined based on the system configuration.

Install PFM - RM for Oracle on the PFM - Manager host
This configuration is the program configuration for installing PFM - RM for Oracle on the same host on which PFM - Manager is installed. In this program configuration, you need to install Oracle Client on the same host on which PFM - RM for Oracle is installed.
The following figure shows the program configuration in this case:

Figure 2-6 Program configuration (installation of PFM - RM for Oracle on the PFM-Manager host (UNIX))

[Figure]
Install PFM - RM for Oracle on the different host from PFM - Manager host
This configuration is the program configuration for installing PFM - RM for Oracle on the different host from PFM - Manager host.
In this program configuration, you need to install PFM - Base and Oracle Client on the same host on which PFM - RM for Oracle is installed. The following figure shows the program configuration in this case:

Figure 2-7 Program configuration (installation of PFM - RM for Oracle on the same host on which PFM - Base and Oracle Client are installed (UNIX))

[Figure]
(a) Monitoring target programs

The monitoring target programs of PFM - RM for Oracle are as follows:

Note that when a monitoring target program running on a virtualized OS is being monitored, only the functionality of the monitoring target programs guaranteed on the virtualized OS is monitored for the monitoring target program.

(b) Performance Management programs

Install PFM - RM for Oracle and PFM - Base on the PFM - RM host.

PFM - Base is a prerequisite program for PFM - RM for Oracle. Only one instance of PFM - Base is required, even when multiple instances of PFM - RM are installed on one host.

Note that you do not need to install PFM - Base if PFM - Manager and PFM - RM for Oracle are installed on the same host.

To monitor Oracle operation using PFM - RM for Oracle, PFM - Manager and PFM - Web Console are required.

(5) Installation and setup in a cluster system

When you install and set up PFM - RM in a cluster system, the prerequisite network environment and program configuration is different from those for a normal system. There are also additional tasks that must be performed on the executing nodes and standby nodes. For details, see 3. Operating PFM - RM for Oracle in a Cluster System.

(6) Preparation for acquiring materials when a failure occurs

When a failure occurs, you might need to use the core dump files to investigate the cause. Whether the core dump files are output depends on the user environment settings, so confirm in advance that the settings are as follows:

Settings for the size of the core dump files
The maximum size of the core dump files is limited by the size setting (ulimit -c) for the root user's core dump files. Set the scripts as the follows:

ulimit -c unlimited

If this setting violates the security policies of your computer, state this script setting in a comment line as follows:

# ulimit -c unlimited

Note
After the above is stated in a comment line, core dump files might not be output when they should be output, such as when a segment fault or bus error occurs in a process. If this is the case, investigation might be impossible.
Settings for the core dump-related kernel parameter (for Linux only)

If you used the Linux kernel parameter (kernel.core_pattern) to change the default output destination and names of core dump files, the core dump files might not be able to be acquired. Therefore, we recommend that you do not change the settings for the Linux kernel parameter (kernel.core_pattern).

(7) Cautionary notes

Note the following when installing and setting up PFM - RM.

(a) Precautions regarding environment variables

Because Performance Management uses JPC_HOSTNAME as an environment variable, do not set it as a user-specific environment variable, as this will prevent Performance Management from operating properly.

(b) Notes on installing and setting up multiple Performance Management programs on same host

With Performance Management, you can install PFM - Manager, PFM - Web Console, and PFM - RM for Oracle on the same host. When doing so, note the following:

Hint:
To improve system performance and reliability, we recommend running PFM - Manager, PFM - Web Console, and PFM - RM for Oracle on separate hosts.
(c) Notes on upgrading PFM - RM for Oracle

Note the following when upgrading PFM - RM for Oracle.

For details about upgrading, see H. Migration Procedure and Notes on Migration.

(d) Other cautionary notes