1.4.1 Collecting data for troubleshooting in Windows
- Organization of this subsection
(1) Execute the data collection tool
JP1/AJS3 provides the data collection tools listed in the following table. Use one of these tools according to the operational requirements.
|
Data collection tool |
Description |
|---|---|
|
jajs_log.bat |
Use this tool if you have not changed the output destinations of log files and other data from the defaults, or if you do not need to collect data other than the data collected by default. |
|
_04.bat |
Use this tool if you have changed the output destinations of log files and other data from the defaults, or if you need to collect data other than the data collected by default. You can customize this tool according to the output destinations or the data to be collected. |
For details about how to set up the data collection tool (_04.bat), see 7.1 Collecting log data in the JP1/Automatic Job Management System 3 Configuration Guide.
The following shows examples of executing the data collection tool:
- When executing jajs_log.bat:
C:\>C:\Program Files\HITACHI\JP1AJS2\tools\jajs_log.bat
- When executing the file trouble.bat that is created by customizing _04.bat:
C:\>C:\usertools\trouble.bat
By default, the results of executing the data collection tool are output under %TEMP%\jp1ajs2\backlog. Back up these folders.
When you use the data collection tools in a cluster system, you can collect data by specifying a logical host name. The data collection tools also provide options for limiting the amount of data that is collected. For details on the data collection tools used in Windows, see jajs_log.bat or _04.bat (Windows only) in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
- Cautionary note
-
When you execute the data collection tool, you must open the Command Prompt window as an administrator. If you are not an administrator, UAC will frequently open a confirmation dialog box.
(2) Obtain a dump file
If a STOP error occurs in Windows or if an application crashes, you might have to obtain dump files (a memory dump and a crash dump) and a problem report.
The following describes how to obtain a dump file and a problem report.
(a) How to obtain a dump file
You need to manually obtain a dump file that is output when a problem occurs.
- Cautionary note
-
To output a dump file when a problem occurs, you must specify the settings in advance. For details about how to set the output of dump files, see 7.1.2 Procedure for setting the outputting of a dump file in the manual JP1/Automatic Job Management System 3 Configuration Guide.
(b) How to obtain a problem report
You can detect problems on a target host and find solutions for each problem. If a JP1/AJS3 process terminates because of an application error, use the following procedure to obtain a problem report.
To obtain a problem report:
-
In Control Panel, click Action Center.
The Action Center dialog box opens.
-
Click Maintenance.
The Maintenance menu appears.
-
Under Check for solutions to problem reports, click View reliability history.
The Reliability Monitor dialog box opens.
-
Click View all problem reports.
The Problem Reporting dialog box opens.
-
Double-click the applicable problem.
Details about the problem report appear.
-
Click Copy to clipboard.
-
Copy the text into a text editor, and save the file.
Use the problem report text file as data for investigating the failure.
(3) Check the status of processes
In Windows, start Task Manager and open the Processes page. Check the operating status of processes.
For details about JP1/AJS3 processes, see B.2 Processes (for Windows).
(4) Check the operation data
For the problem that has occurred, check the operation data and record it. You need to check the following information:
-
Details about the operation
-
Time that the problem occurred
-
Machine configuration (the version of each OS, host name, JP1/AJS3 - Manager and JP1/AJS3 - Agent configuration)
-
Whether the problem is reproducible
-
Name of the user, if any, who logged in from JP1/AJS3 - View
-
Name of the user who logged in if JP1/AJS3 - Web Console is used and login is performed from the Web GUI or a user application
(5) Collect error information displayed on the screen
Make hard copies of the following:
-
Windows on the screen when an application error has occurred
-
Error message dialog box
Displayed information when a details button, if any, is clicked
-
Information in the Command Prompt window if the problem occurred during the execution of a command
Before making a hard copy of the Command Prompt window, make the following preparations by using Console in Control Panel:
- Options page
-
Select QuickEdit Mode.
- Layout page
-
Enter 500 in Height of Screen Buffer Size.
(6) Collect information about the embedded database
You need the following information if an error occurs while you are using the embedded database:
-
Data needed to investigate the cause
-
Information needed to re-create the embedded database environment
The following describes how to collect the above information.
(a) Information needed to investigate the cause
To investigate the cause of an error, you mainly need to collect information about the OS and information about the embedded database. Use OS commands to collect information about the OS. Use embedded database commands to collect information about the embedded database.
If you use the support service to solve problems, you must submit the information listed in the table below. This table describes the type of information needed to investigate the cause of problems and how to collect information for each type of problem. Problems are classified into seven levels, of which level 1 has the highest priority.
Problems are grouped by type as follows:
-
Performance
The following processing or operation takes too much time:
-
Startup of the embedded database system (including normal startup, restart, and startup after action has been taken for a failure)
-
Stopping of the embedded database system (including normal stopping and forced stopping)
-
Execution of an operation command for the embedded database
-
-
No response
A response is not returned when the following processing or operation is performed:
-
Startup of the embedded database system (including normal startup, restart, and startup after action has been taken for a failure)
-
Stopping of the embedded database system (including normal stopping and forced stopping)
-
Execution of an operation command for the embedded database
-
-
Abnormal end
One of the following has occurred:
-
Abnormal termination of the embedded database system
-
Abnormal termination of an embedded database process
-
Abnormal termination of an operation command for the embedded database
-
|
No. |
Component |
Information to be collected |
Collection method |
Performance |
No response |
Abnormal end |
|---|---|---|---|---|---|---|
|
1 |
OS |
Windows event log |
Use an OS function (command). |
1 |
1 |
1 |
|
2 |
CPU usage rate and device status |
Use the performance monitor. |
3 |
4 |
3 |
|
|
3 |
Embedded database |
Information about embedded database failures |
Obtain the files under the following folders and store them on a DAT or another storage device:
An error log file, a command log file, remote command information files, and node switching function information files are output to the above folders. |
2 |
2 |
2 |
|
4 |
|
2 |
2 |
2 |
||
|
5 |
|
2 |
2 |
2 |
||
|
6 |
|
2 |
2 |
2 |
||
|
7 |
|
2 |
2 |
2 |
||
|
8 |
Specification difference absorption library error information files |
The error information about the specification difference absorption library is output to embedded-database-practical-directory\UXPLDIR\SPOOL\uxpllog1 and uxpllog2. |
2 |
2 |
2 |
|
|
9 |
Embedded database system definitions |
Obtain the files under embedded-database-practical-directory\conf and store them on a DAT or another storage device. |
4 |
5 |
4 |
|
|
10 |
SQL trace file and error log file |
Obtain the output files and store them on a DAT or another storage device. A file name begins with pderr or pdsql. |
-- |
6 |
5 |
|
|
11 |
System log file |
Use the ajsembdboplog command to unload the system log. Obtain the unload log file and store it on a DAT or another storage device. |
6 |
7 |
6 |
- Legend:
-
--: The information need not be collected.
- Note
-
The size of a file increases at a fixed rate if additional data continues to be stored in the file as a result of redirection. Because such a file takes up disk space, instead use bat files, which can be switched and reused after several generations.
(b) Information needed to re-create the embedded database environment
If a problem occurs during operation of the embedded database, you might need to re-create the environment that produced the problem to test whether the problem is reproducible or to investigate the cause of the problem. To enable this procedure, collect the following information needed to re-create the embedded database environment.
-
conf under the embedded database practical directory (if the user has changed the definition files)
-
Environment variables related to the embedded database
-
Data in the embedded database
Use the ajsembdbrorg command to collect the data in the embedded database.
To collect the information needed to re-create the embedded database environment:
-
Start the embedded database.
-
Execute the ajsembdbrorg command with the -k unld option specified.
-
Save conf under the embedded database practical directory in a folder of your choice.
-
Record the environment variables related to the embedded database.
For details about how to use the ajsembdbrorg command and a description of the command, see 9.2.3 Reorganizing a database in the JP1/Automatic Job Management System 3 Administration Guide.