Collect the information about the OS. Table 7-8 lists the information about the OS:

Table 7-8 Information about the OS

Type of information	Details	Default file name	Collected by jpcras command
System log	Windows event log	--	Y
Process information	List of processes	--	Y
System file	hosts file	system-folder\system32\drivers\etc\hosts	Y
	services file	system-folder\system32\drivers\etc\services	Y
OS information	System information	--	Y
	Network status	--	Y
	Host name	--	Y
	Windows firewall information	--	Y
Dump information (in Windows Server 2003)	Dr. Watson log file	system-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log# system-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dump#	Y
Dump information (in Windows Server 2008)	Problem Reports and Solutions log file	user-mode-process-dump-output-folder\program-name.process-ID.dmp Example: jpcagt1.exe.2420.dmp	N

Legend:

Y: Can be collected

N: Cannot be collected

--: Not applicable

#

If you set up Dr. Watson to output log files to a different folder, collect the information from that folder.

Collect the log information about Performance Management. If the problem relates to a network connection, also collect information from the machine that is the connection target. Table 7-9 lists the log information about the Performance Management:

Table 7-9 Log 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)	installation-folder\log\jpclog{01|02}#1	Y
	Message log output by Performance Management (wraparound files)	installation-folder\log\jpclogw{01|02}#1	Y
Configuration information	Configuration information files	--	Y
	Output of jpctool service list command	--	Y
Version information	Product versions	--	Y
	Log information	--	Y
Database information	Remote Monitor Store service	installation-folder\agt1\store\instance-name\stpd The following files under the installation-folder\agt1\store\instance-name\stpi folder: *.DB *.IDX	Y
Trace log	Trace information for Performance Management services	--#2	Y
Agent log	Normal log for processing related to acquisition of PFM - RM for Oracle records	installation-folder\agt1\agent\instance-name\log\agt1inf{01|02}#3	Y#4
	Error log for processing related to acquisition of PFM - RM for Oracle records	installation-folder\agt1\agent\instance-name\log\agt1err{01|02}#3	Y#4
Install log#5	Message logs from installation (in Windows Server 2008)	The following files under the system-folder \TEMP\HCDINST folder: HCDMAIN.LOG HCDINST.LOG product-model-name.LOG	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 Job Management Partner 1/Performance Management User's Guide.

#2

For details about the storage folders for trace logs, see 7.3.2(2) Trace log.

#3

For details about the output format of an agent log and how to change the storage folder, see 7.3.2(3) Agent log.

#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.

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 - RM for Oracle)
• Whether the error is reproducible
• Name of any Performance Management user who logged in from PFM - Web Console

Collect hard copies of the following:

• Windows on the screen when the application error occurred
• The error dialog boxes (Also copy the detailed information if a dialog box contains a Details button.)
• Information in the Command Prompt window or [Administrator Console] window when an error occurs during command execution

In Windows Server 2008, if a Performance Management process stops due to an application error, obtain a user dump.

In Windows Server 2008, if a Performance Management process stops due to an application error, obtain a problem report.

Collect the following information about performance data. If a problem occurred during network connection, 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 - RM for Oracle in an environment in which PFM - RM for Oracle is installed.

Table 7-10 Information about performance data

Type of information	Details	Default file name	Collected by jpcras command
Error information during Oracle connection#1	Error code when an error occurs for the Oracle connection	installation-folder\agt1\agent\instance-name\pdia_xxxxx_status.db#2	Y
Internal maintenance information	Log file for OCI functions	installation-folder\agt1\agent\instance-name\ocilog.txt	Y

Legend:

Y: Can be collected

#1

This file may be created when an error occurs during an Oracle connection.

#2

xxxxx is replaced with any string.

Also collect the following information:

• Arguments specified in the command when an error occurs during command execution.
• Content of System Information under System Tools under Accessories.
• Contents of System and Application in the Windows Event Viewer.