Interstage Shunsaku Data Manager Troubleshooting - Microsoft(R) Windows(R) 2000/ Microsoft(R) Windows Server(TM) 2003 - - UNIX - |
Contents
Index
![]() ![]() |
Chapter 1 Overview of Troubleshooting | > 1.4 Recovering the Shunsaku System |
If an error occurs with Shunsaku and operations cannot be continued, the administrator must eliminate the cause of the error and restart Shunsaku before operations recommence.
The following diagram shows the flow from an error occurrence to recovery in Shunsaku:
Follow users' directions corresponding with Shunsaku messages (which are output tin the system log (syslog) or the event log of the server where the error occurred) to eliminate the cause of an error.
Refer to the Messages for information on the response to the message.
Once the cause of the error has been eliminated, execute the shunsysstart command on the target server to restart Shunsaku:
shunsysstart -n Shunsaku system name |
Normal operations will automatically recommence once Shunsaku has been restarted.
If an error has also occurred with a searcher, operations automatically switch from degradation operations to normal operations when Shunsaku is restarted. However, the search data that was allocated to other searchers as part of the degradation process is not restored to its pre-degradation state. Execute the shundresend command to reallocate search data evenly among searchers:
Shundresend -s director identifier |
While search data is being reallocated, lookup data cannot be updated using the shundimport command or APIs.
Contents
Index
![]() ![]() |