2.7.1 Notes on operating
-
Before you start PFM - Agent for Oracle, you need to complete installation and setup the Oracle Database and then start the Oracle Database. When the Oracle Database is not running, performance data except for Instance Availability (PD_PDIA) and Server Status (PD_STAT) is not collected. Also, if an Oracle instance or container is mounted, performance data is not collected.
-
After you stop PFM - Agent for Oracle, you can change constitution or perform maintenance of Oracle Database instance or container.
-
When PFM - Agent for Oracle collects the following records obtained dynamic performance v$ views (such as V$ACCESS, V$OPEN_CURSOR), an error (such as ORA-00600, ORA-00602) might be output from the Oracle Database and it might fail to collect the performance data. In this case, when the records are collected at next time, it collects the performance data again.
-
Activity Summary (PD_PDAS) record
-
Open Cursor (PD_PDOC) record
-
Session Detail (PD_PDS) record
-
-
When the port to use in Agent Collector service has been already used, fail to bind to port at the time of Agent Collector service start#. And, when startup_always is set to Y, Agent Collector service is started. In this case, you can not monitor correctly. You stop the service, and confirm port conflict, later start the service.
-
Stop the service of PFM - Agent for Oracle.
jpcspm stop -key Oracle
Stop PFM - Agent for Oracle service which started normally.
jpcspm stop -key Oracle -kill immediate
Stop PFM - Agent for Oracle service which failed to bind to port.
-
Confirm port conflict to use in PFM - Agent for Oracle.
Confirm whether other service do not use a fixed port by jpcconf port define command.
-
Start the service of PFM - Agent for Oracle.
jpcspm start -key Oracle [-inst <instance name>]
# When failed to bind to port, the message KAVE00100-E, KAVE00107-E,
KAVE00160-E are output to common message log.
-
-
If you do not stop PFM - Agent for Oracle before you stop the monitored Oracle Database instance or container, you may not be able to stop the Oracle Database by using the NORMAL shutdown procedure. To stop the Oracle Database, you need to stop PFM - Agent for Oracle beforehand or else use the IMMEDIATE shutdown procedure.
-
When you fail in monitoring using sys account, either set the following 1 and 2 together, or confirm 3 setting.
-
Create a password file.
-
Set "exclusive" as the value of the "remote_login_passwordfile" initialization parameter.
-
Set "true" as the value of the "o7_dictionary_accessibility" initialization parameter.
-
-
If the expiration date is set on oracle_passwd, once the password is out of date connections to Oracle fail so that PFM - Agent 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_user.sql.
For details about the above settings, see the manual for Oracle Database.
-
When a connection error occurred while PFM - Agent for Oracle is running, an error is logged to the sqlnet.log file is stored in the directory specified by Oracle. When you use Oracle Database 11g, or Oracle Database 12c or later without setting ORACLE_BASE, the sqlnet.log is stored in the directory created under the "/" directory. Before you start PFM - Agent for Oracle, the sqlnet.log can also be stored in the directory specified by the ORACLE_BASE environment variable.
-
PFM - Agent for Oracle that monitors performance data for each an instance of the node cannot monitor Oracle RAC One Node configuration has dynamically changed Oracle SIDs.
-
When specifying an execution module in the Windows WOW64 system directory (SysWOW64) for an alarm action definition, see the chapter on notes on creating alarms in the JP1/Performance Management Planning and Configuration Guide.
-
For notes on executing the jpctool service list command for the Agent Collector service or Agent Store service, see the chapter that describes commands in the manual JP1/Performance Management Reference.
-
For notes on executing the jpcspm start command or the jpcspm stop command for PFM - Agent for Oracle, see the chapter that describes commands in the manual JP1/Performance Management Reference.
-
Do not specify a folder as the Performance Management folder if it has a Windows Resource Protection function (WRP) applied,(such as a specified Store database folder or the backup folder). If you do specify such a folder, you might not be able to update or delete files or folders, and the product might not work properly.
-
If you restart the machine by using the reboot command while the PFM - Agent for Oracle service is running, the message shown below might be output to the common message log, indicating that the Agent Collector service has ended abnormally. This message, however, does not actually indicate the occurrence of an error because the Agent Collector service has in fact ended successfully.
KAVF12004-E Agent Collector stopped abnormally.
-
When you perform a new installation of this product, the first icon displayed might be replaced immediately by another icon. This problem concerns only what icon is displayed. Product operation is not affected.