Hitachi

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

4.4.4 Setup procedure

This subsection describes how to set up Performance Management to run in a cluster system.

Setup must be performed first on the executing node and then on the standby node.

[Figure] indicates a task to be performed on the executing node. [Figure] indicates a task to be performed on the standby node. [Figure] indicates a setup item that is required depending on the environment or an optional setup item used when the default is to be changed.

Organization of this subsection

(1) Register PFM - Agent for Oracle[Figure] [Figure] [Figure]

To perform integrated management of PFM - Agent for Oracle using PFM - Manager and PFM - Web Console, you must register PFM - Agent for Oracle with PFM - Manager and PFM - Web Console.

The conditions and procedure for registering PFM - Agent for Oracle are the same as when a cluster system is not used. For details about the conditions and procedure for registering PFM - Agent for Oracle, see 3.1.4(2) Register PFM - Agent for Oracle.

To Page Top

(2) Mount the shared disk[Figure]

Make sure that the shared disk is mounted. If the shared disk is not mounted, use the cluster software or the volume manager to mount it.

To Page Top

(3) Set up the logical host environment for PFM - Agent for Oracle [Figure]

Execute the jpcconf ha setup command to set up the logical host environment. When you execute the command, the necessary files are copied to the shared disk, the logical host definition is set up, and the logical host environment is created.

Note:

Before you execute the command, stop all Performance Management programs and services throughout the Performance Management system. For details about how to stop services, see the chapter on operating Performance Management in the JP1/Performance Management User's Guide.

To set up the logical host environment:

  1. Execute the jpcconf ha setup command to create the logical host environment for PFM - Agent for Oracle.

    Execute the command as follows:

    jpcconf ha setup -key Oracle -lhost jp1-halora -d /jp1

    Use the -lhost option to specify the logical host name. In the example above, the logical host name is jp1-halora. For DNS operation, specify a logical host name with the domain name portion removed.

    Specify the name of the shared disk directory as the environment directory name of the -d option. For example, if you specify -d /jp1, the directory /jp1/jp1pc is created, and the files for the logical host environment are created in that directory.

    Note:

    PFM - Agent for Oracle runs on file systems. When the database is built on RAW devices or ASM, the shared disk must be based on a file system.

  2. Execute the jpcconf ha list command to check the logical host settings.

    Execute the command as follows:

    jpcconf ha list -key all

    Confirm that the logical host environment you created has been set up correctly.

To Page Top

(4) Set the connection-target PFM - Manager[Figure]

Execute the jpcconf mgrhost define command to specify which PFM - Manager is to manage PFM - Agent for Oracle.

  1. Execute the jpcconf mgrhost define command to set the connection-target PFM - Manager.

    Execute the command as follows:

    jpcconf mgrhost define -host jp1-hal -lhost jp1-halora

    Use the -host option to specify the host name of the connection-target PFM - Manager. If that PFM - Manager is running in a logical host environment, specify the logical host name of the PFM - Manager in the -host option. In the example above, the logical host name of PFM - Manager is jp1-hal.

    Use the -lhost option to specify the logical host name of PFM - Agent for Oracle. In the example above, the logical host name of PFM - Agent for Oracle is jp1-halora.

    Although an example of interactive command execution is shown here, the jpcconf mgrhost define command can be also executed non-interactively. For details about the jpcconf mgrhost define command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

To Page Top

(5) Create an Oracle account to be used[Figure] [Figure]

Create an Oracle account that has specific system privileges to collect performance data for the Oracle Database monitored by PFM - Agent for Oracle.

For details about how to create an Oracle account, see 3.1.4(3) Create an Oracle account to be used in PFM - Agent for Oracle.

This setup task is unnecessary when you use the sys account.

To Page Top

(6) Set up an instance environment[Figure]

You execute the jpcconf inst setup command to set up an instance environment for PFM - Agent for Oracle.

The setup procedure is the same as the setup procedure in a non-cluster system, except that, in a cluster system, you must specify the logical host name in the -lhost option when executing the jpcconf inst setup command.

In a cluster system, the jpcconf inst setup command is executed in the following format: 

jpcconf inst setup -key Oracle -lhost logical-host-name -inst instance-name

Although an example of interactive command execution is shown here, the jpcconf inst setup command can be also executed non-interactively. For details about the jpcconf inst setup command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

As the agent log output folder (the value of log_path), specify the path of a folder that is on the shared disk.

For details about other settings and procedures, see 3.1.4(4) Set up an instance environment.

To Page Top

(7) Set up the logical host environment for other Performance Management programs [Figure] [Figure]

At this point, set up any other Performance Management programs, such as PFM - Manager or PFM - Agent, on the same logical host.

For details about how to set up these products, see the chapters on setup and operation in a cluster system in the JP1/Performance Management User's Guide, and the chapter on operation in a cluster system in the manuals for the applicable version of PFM - Agent.

To Page Top

(8) Specify network settings[Figure] [Figure]

This setup task is necessary only when you change the network settings to match the configuration in which Performance Management is used.

The following are the two network setting items:

To Page Top

(9) Change the size of log files[Figure] [Figure]

Performance Management outputs its operating status to a set of proprietary log files called a common message log. Perform this setting only if you want to change the default file size.

For details, see the chapter on installation and setup in the JP1/Performance Management Planning and Configuration Guide.

To Page Top

(10) Change the storage location of performance data[Figure] [Figure]

Perform this setting only if you want to change the folders where the database of performance data managed by PFM - Agent for Oracle is saved, backed up, exported, or imported.

For details, see 3.4.1 Changing the storage location of performance data.

To Page Top

(11) Setting up the action log[Figure] [Figure]

This setting is required to output action log when alarm occur. The action log stores history information that is output in conjunction with the alarms for thresholds related to system load and other conditions.

For details about how to set up the action log, see K. Outputting Action Log Information.

To Page Top

(12) Export the logical-host environment definition file[Figure]

Once you have created the logical host environment for PFM - Agent for Oracle, export the environment definition as a file. In the export process, a file containing the collective definition information for all Performance Management programs set up on that logical host is output. Export the environment definition only after you have set up all additional Performance Management programs on the logical host.

To export the environment definition of the logical host:

  1. Execute the jpcconf ha export command to export the environment definition of the logical host.

    The definition information for the logical host environment you created is output to an export file. You can give this file any name you wish.

    For example, execute the command as follows to output the logical host environment definition to the file lhostexp.txt: 

    jpcconf ha export -f lhostexp.txt

    Although an example of interactive command execution is shown here, the jpcconf ha export command can be also executed non-interactively. For details about the jpcconf ha export command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

To Page Top

(13) Copy the logical-host environment definition file to the standby node[Figure] [Figure]

Copy the file you exported in (12) Export the logical-host environment definition file from the executing node to the standby node.

To Page Top

(14) Unmount the shared disk [Figure] [Figure]

Complete setup by unmounting the file system. Note that if you intend to continue using the shared disk, you do not need to unmount the file system at this point.

Note:

Check whether the jp1pc directory and the files for the logical host environment exist on the local disk in the environment directory of the logical host that you set up. If they exist, this indicates that setup was performed without mounting the shared disk. In this case, take the following action:

  1. Using the tar command, archive the jp1pc directory in the environment directory on the local disk.

  2. Mount the shared disk.

  3. If the environment directory you specified does not exist on the shared disk, create it now.

  4. Extract the tar file into the environment directory on the shared disk.

  5. Unmount the shared disk.

  6. Delete the jp1pc directory and its contents from the environment directory on the local disk.

To Page Top

(15) Import the logical-host environment definition file[Figure]

On the standby node, import the exported file you copied from the executing node.

Use the jpcconf ha import command to set up the environment definition for the Performance Management programs of the logical host that you created on the executing node so that they to run on the standby node. If more than one Performance Management program was installed on the logical host, the definition information for all of the programs is imported in batch form.

Note that the shared disk does not need to be online when you execute this command.

  1. Execute the jpcconf ha import command to import the environment definition of the logical host.

    Execute the command as follows:

    jpcconf ha import -f lhostexp.txt

    Although an example of interactive command execution is shown here, the jpcconf ha import command can be also executed non-interactively. For details about the jpcconf ha import command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

    When you execute the command, the settings on the standby node are changed to reflect the environment described in the export file. This sets up the standby node to run PFM - Agent for Oracle as a logical host.

    If you used the jpcconf port command to assign fixed port numbers during setup, the same port numbers will take effect on the standby node.

  2. Execute the jpcconf ha list command to check whether the logical host is set up correctly.

    Execute the command as follows:

    jpcconf ha list -key all

    Check whether the same output is displayed as when you executed jpcconf ha list on the executing node.

To Page Top

(16) Register PFM - Agent for Oracle in the cluster software[Figure] [Figure]

If you intend to use Performance Management programs in a logical host environment, make sure that the programs are registered in the cluster software. Also, set up the environment so that the Performance Management programs are started and stopped based on instructions from the cluster software.

This subsection describes the settings to be specified to register PFM - Agent for Oracle in the cluster software.

In UNIX, you will typically need to register control methods for Start, Stop, Process monitoring, and Forced stop in the cluster software.

The following table shows how to set these control methods for PFM - Agent for Oracle.

Table 4‒5: Control methods for PFM - Agent for Oracle registered in the cluster software

Item

Description

Start

Start PFM - Agent for Oracle by executing the following commands:

/opt/jp1pc/tools/jpcspm start -key AH -lhost logical-host-name
/opt/jp1pc/tools/jpcspm start -key Oracle -lhost logical-host-name -inst instance-name

Start PFM - Agent for Oracle after the shared disk and the logical IP address have been made usable.

Stop

Stop PFM - Agent for Oracle by executing the following commands:

/opt/jp1pc/tools/jpcspm stop -key Oracle -lhost logical-host-name -inst instance-name
/opt/jp1pc/tools/jpcspm stop -key AH -lhost logical-host-name

Stop PFM - Agent for Oracle before the shared disk and the logical IP address are made unusable.

If the service has stopped due to a failure, the jpcspm stop command returns 3. In this case, assume that the command terminated normally, because the service has stopped. For cluster software that evaluates the execution result from a return value, convert the return value to 0, for example.

Process monitoring

Use the ps command to check whether the monitored processes are running: 

ps -ef | grep "process-name logical-host-name" | grep -v "grep monitored-process"

Monitored processes are as follows:

  • jpcagto

  • agto/jpcsto

  • jpcah

For each of these processes, execute the following command:

  • For jpcagto

    ps -ef | grep "jpcagto_instance-name logical-host-name" | grep -v "grep jpcagto"

  • For agto/jpcsto

    ps -ef | grep "agto/jpcsto_instance-name logical-host-name" | grep -v "grep agto/jpcsto"

  • For jpcah

  • ps -ef | grep "jpcah logical-host-name" | grep -v "grep jpcah"

Hitachi also recommends that you provide a control method that allows the cluster software to temporarily stop monitoring. This can be used when temporarily stopping Performance Management, for example, during system maintenance (thereby stopping the cluster software from monitoring files that are undergoing maintenance).

Forced stop

To perform a forced stop, execute the following command:

/opt/jp1pc/tools/jpcspm stop -key all -lhost logical-host-name -kill immediate

As the service key of the first argument, you can specify only all.

Note:

Execution of this command forcibly stops all Performance Management processes in the specified logical host environment by sending a SIGKILL signal to the processes. That is, the Performance Management system is stopped at the logical host level, not at the individual service level.

Set up the cluster software to only perform a forced stop if a normal stop fails.
Notes:

  • Because Performance Management programs that are to be registered in the cluster software must be started and stopped based on instructions from the cluster software, do not set them up to start automatically when the OS starts.

  • If the cluster software evaluates execution results on the basis of the return value, set up the Performance Management programs to convert their command return values to values the cluster software expects. For the command return values of Performance Management programs, see the explanation of the command.

  • If you use the ps command to monitor operations, check in advance the outputs of the ps command. The command outputs PFM - Agent for Oracle processes as the concatenations of the logical host name and the monitoring instance names. Make sure that the displayed PFM - Agent for Oracle processes are not truncated. If any one of the displayed PFM - Agent for Oracle processes is truncated, then shorten the instance names so that the displayed processes are no longer truncated.

    In addition, when using the ps command to identify the process name and logical host name, if you use ( ) (parentheses) or [ ] (square brackets), the process name and logical host name might not be acquired. If this happens, check the ps command reference of the OS, and then execute the command again.

  • Start PFM - Agent for Oracle after starting Oracle, and stop it before stopping Oracle. If you are using the Oracle listener# for establishing connections and want to connect PFM - Agent for Oracle and the Oracle database, first start the listener and then start Agent for Oracle.

#

If Y was specified for sqlnet of the instance environment settings, the net service name specified in net_service_name uses the listener for connections. Before establishing connections, you must configure the environment on the Oracle database side to be able to establish connections by using the listener.

To Page Top

(17) Check whether services can be started and stopped from the cluster software[Figure] [Figure]

Check whether the cluster software is operating correctly by using it to issue start and stop requests to Performance Management programs on each node.

To Page Top

(18) Set up the environment in the cluster system[Figure] [Figure]

After setting up the Performance Management programs, use PFM - Web Console to set up the environment for the programs. You will then be able to display reports on the operating status of monitoring targets, and notify users whenever a problem occurs.

For details about setting up the environment for Performance Management programs, see the chapters on setup and operation in a cluster system in the JP1/Performance Management User's Guide.

To Page Top

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

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