8.4.2 In UNIX
- Organization of this subsection
(1) Log information about the OS
Collect the information about the OS. The following table lists the information about the OS:
|
Type of information |
Details |
Default file name |
Collected by jpcras command |
|---|---|---|---|
|
System log |
syslog |
|
Y#1 |
|
Process information |
List of processes |
-- |
Y |
|
System file |
hosts file |
/etc/hosts |
Y |
|
/etc/inet/ipnodes#2 |
Y#3 |
||
|
services file |
/etc/services |
Y |
|
|
OS information |
Patch information |
-- |
Y |
|
Kernel information |
-- |
Y |
|
|
Version information |
-- |
Y |
|
|
Network status |
-- |
Y |
|
|
Environment variable |
-- |
Y |
|
|
Host name |
-- |
Y |
|
|
Dump information |
core file#4 |
-- |
Y |
- Legend:
-
Y: Can be collected
--: Not applicable
- #1
-
You cannot collect this data when using a system that is set to output data using the default path and file name. Collect the data manually.
- #2
-
The /etc/inet/ipnodes file exists only in Solaris. Collect this file together with the /etc/hosts file.
- #3
-
Only the jpcras command in PFM - Manager 08-50 or later, or PFM - Base 08-50 or later, can collect this data
- #4
-
In HP-UX 11i V3 (IPF), you can use the coreadm command to change the name of a core file. After renaming, the jpcras command cannot collect any files whose name does not begin with core. For these files, collect information manually.
(2) Information about Performance Management
Collect the information about Performance Management. If the problem relates to a network connection, also collect information from the machine that is the connection target.
The following table lists the information about Performance Management:
|
Type of information |
Details |
Default file name |
Collected by jpcras command |
|---|---|---|---|
|
Common message log |
Message log output by Performance Management (sequential files) |
/opt/jp1pc/log/jpclog{01|02}#1 |
Y |
|
Performance Management (wraparound files) |
/opt/jp1pc/log/jpclogw{01|02}#1 |
Y |
|
|
Configuration information |
Configuration information files |
-- |
Y |
|
Output of jpctool service list command |
-- |
Y |
|
|
Version information |
Product version |
-- |
Y |
|
Log information |
-- |
Y |
|
|
Database information |
Agent Store service |
|
Y |
|
Trace log |
Trace information for Performance Management services |
--#2 |
Y |
|
Agent log |
Normal log for processing related to acquisition of PFM - Agent for Oracle records |
/opt/jp1pc/agto/agent/instance-name/log/agtoinf{01|02}#3 |
Y#4 |
|
Error log for processing related to acquisition of PFM - Agent for Oracle records |
/opt/jp1pc/agto/agent/instance-name/log/agtoerr{01|02}#3 |
Y#4 |
|
|
Install log#5 |
Standard log for Hitachi Program Product Installer |
/etc/.hitachi/.hitachi.log /etc/.hitachi/.hitachi.log {01|02|03|04|05} /etc/.hitachi/.install.log /etc/.hitachi/.install.log{01|02|03|04|05} |
N |
- Legend:
-
Y: Can be collected
N: Cannot be collected
--: Not applicable
- #1
-
For details about the output format of the log files, see the chapter on detecting errors in Performance Management in the JP1/Performance Management User's Guide.
- #2
-
For details about the storage directories for trace logs, see 8.3.2 List of log files and directories.
- #3
-
For details about the output format of an agent log and how to change the storage folder, see 8.3.2 List of log files and directories.
- #4
-
The jpcras command collects agent log information only from the currently specified output destination folder. If you change the output destination folder for agent logs, you need to manually collect data from the agent log files that were output before the change.
- #5
-
Collect this information if installation failed.
(3) Operation information
Collect the following information about the operation that was being performed when the problem occurred:
-
Details of the operation
-
Time when the error occurred
-
Machine configuration (version of each OS, host name, configuration of PFM - Manager and PFM - Agent)
-
Whether the error is reproducible
-
Name of any Performance Management user who logged in from PFM - Web Console
(4) Error information
Collect the following error information:
-
Messages output to the console when an error occurs during command execution
(5) Information about performance data
Collect the following information about performance data. You must also collect files located on the machine, command results, and registry information.
The following table shows information about performance data that is specially collected by PFM - Agent for Oracle in an environment in which PFM - Agent for Oracle is installed.
|
Type of information |
Details |
File name#1 |
Collected by jpcras command |
|---|---|---|---|
|
PDNL record information |
Output result of lsnrctl (Oracle command) |
/opt/jp1pc/agto/agent/instance-name/pdnl.out |
Y |
|
PDNL record information |
Output result of lsnrctl (Oracle command) |
/opt/jp1pc/agto/agent/instance-name/lsnrctl.status.pdnl.out.err.txt |
Y |
|
PDNL record information |
Execution result of hostname |
/opt/jp1pc/agto/agent/instance-name/sqlnet.tmp |
Y |
|
PDLS record information |
Output result of lsnrctl (Oracle command) |
/opt/jp1pc/agto/agent/instance-name/pdls.out |
Y |
|
PDLS record information |
Output result of lsnrctl (Oracle command) |
/opt/jp1pc/agto/agent/instance-name/lsnrctl.status.pdls.out.err.txt |
Y |
|
Error information during Oracle connection#2 |
Error code when an error occurs for the Oracle connection |
/opt/jp1pc/agto/agent/instance-name/pdia_xxxxx_status.db#3 |
Y |
|
Internal maintenance information |
Log file for OCI functions |
/opt/jp1pc/agto/agent/instance-name/ocilog.txt |
Y |
- Legend:
-
Y: Can be collected
- #1
-
When a logical host is used, replace /opt/jp1pc with environment-directory/jp1pc
- #2
-
This file may be created when an error occurs during an Oracle connection.
- #3
-
xxxxx is replaced with any string.
(6) Other information
Also collect the following information:
-
Arguments specified in the command when an error occurs during command execution