Interstage Shunsaku Data Manager Troubleshooting - Microsoft(R) Windows(R) 2000/ Microsoft(R) Windows Server(TM) 2003 - - UNIX -

1.3.3 Checking and Handling the Process Down

Use the procedure below to identify error events to check and handle any process downs.

Inform a Fujitsu systems engineer if the problem is identified.
Refer to Chapter 3 - Collecting troubleshooting Information for more information on how to collect troubleshooting information.

This following procedure explains how to find out if a Shunsaku process is downed and the core file has been collected.

1. Checking APIs or command message codes:
   • APIs:
     A process down may have occurred if the following API message codes are displayed even if Shunsaku is activated:
     • conductor : shn06003u
     • director : shn02013u
     • searcher : shn04005u
     • sorter : shn07016u
   • Command:
     A process down may have occurred if the following message codes are output by a command even if Shunsaku is activated:
     • conductor : shn26023u
     • director : shn22011u, shn22010u, shn30364u (These might be a searcher degradation or a searcher failover.)
     • searcher : shn24009u
     • sorter : shn27021u

2. Checking the system log (syslog) or event log:
   If any of the message codes in Step 1 are found, search for the following message codes in the system log (syslog) or event log:
   • conductor : shn06003u
   • director : shn02013u
   • searcher : shn04005u
   • sorter : shn07016u

   Checking whether the core file exists:
   Refer to the environment file of the identifier in which the message in Step 2 is displayed. Check the directory specified by the CoreFileFolder parameter in the environment file to find out whether the core file referred to in the error message in Step 2 exists.