KFPS01820-E
Server aa....aa failed. process ID=bb....bb, service group name=cc....cc, run mode=dd....dd, critical state=e,critical mask=ff....ff, end state=gg....gg, server type=hhh (E+L)
The server aa....aa has stopped. The following status is detected.
Value of gg....gg |
Description |
---|---|
007f 0009 |
The system accepted a request for forced termination of the server process. This message appears when the ajsembdbcancel command is executed. Determine the cause of the forced termination request for the process (including execution of the ajsembdbcancel command) based on the message output before or after this message, and then take action as required. |
0003 0083 |
The system accepted a request of forced termination of the server process. Determine the cause of the forced termination request for the process based on the status of the executed transaction and the message output before or after this message, and then take action as required. |
0006 0086 0100 0800 |
The embedded database process terminated abnormally because an error was detected during processing. Determine the cause of the abnormal termination based on the message output before or after this message, and then take action as required. |
8000 |
An attempt to start a process failed or a process terminated abnormally due to insufficient memory. Take one of the following actions:
|
c000 |
A connect system call was issued, but connection was not established because the connection destination had gone down or because a network failure occurred. |
c100 |
The second or later SQL response could not be sent because the connection destination had gone down or because a network failure occurred. |
c200 |
A timeout of the embedded database client was detected during a transaction when the embedded database client had control. |
c300 |
The remote communication socket was closed because an error occurred in the destination during communication processing. |
c400 |
A timeout of the client was detected when the client had control and a transaction was not in progress. Alternatively, a timeout related to pd_watch_pc_client_time specified in the embedded database system was detected during connection of a Windows embedded database client. |
c500 |
A special file (FIFO) could not be obtained when the server was started. |
c600 |
The maximum number of transactions that can be processed concurrently on the embedded database was exceeded. Since many rollbacks might have occurred, wait for completion of the rollbacks and then re-execute the UAP. |
c700 |
Abnormal termination was detected on the client requesting SQL (JP1/AJS3 scheduler service process) during execution of SQL on the embedded database. |
c800 |
An attempt to send an SQL request has failed because a network failure occurred between the server and the system manager. |
c900 |
An attempt to receive a second or later SQL request has failed because a network failure occurred between the sender and the system manager. |
d000 |
The child process was killed because the parent process was killed during transaction processing. |
d100 |
Server processing was canceled because the UAP processing did not terminate within the monitoring period specified in PDSWAITTIME and PDSWATCHTIME in the client environment definitions. Alternatively, the related server processing was canceled because the pdcancel command was executed. |
d300 |
Although an error was detected, the system terminated processing without outputting troubleshooting information because the specification of the pd_dump_suppress_watch_time operand was valid. |
d500 |
An error occurred during determination of a transaction. |
000f ff00 |
The server process of the embedded database was forcibly terminated by the OS kill command. |
008b |
An OS stack overflow may have occurred while the embedded database was running. The following are the actions to be taken for the causes of the stack overflow. Cause 1 The probable cause is:
Action
Cause 2 An attempt to expand the stack failed due to insufficient OS memory. Action Terminate unnecessary programs to increase the amount of free space in memory. |
aa....aa: Name of the stopped server
bb....bb: Process ID of the stopped server
cc....cc: Service group name of the stopped server
- dd....dd: Run mode of the server immediately before it stopped
-
PDBSV: Embedded database server
PDBSYS: Embedded database being processed
- e:
-
N: Not a critical state
Y: Critical state
Since information on the embedded database is shared by multiple processes, the management table in the shared memory is referenced or updated. If a process that is updating the shared memory terminates abnormally, table information becomes inconsistent, disabling subsequent processing, which includes processing by other processes. As much as possible, the system prevents a forced termination from occurring in this processing period (called the critical period). If the system cannot prevent a forced termination in the critical period due to a failure, the embedded database terminates, and the integrity of the table information will be recovered when the embedded database is restarted.
ff....ff: Critical information
gg....gg: End status of the process returned by wait(2) (**** is displayed for an embedded database command.)
hhh: Server type (*** is displayed for a server other than an embedded database server)
- (S)
-
Terminates processing on the server on which an error occurred, and then restarts the server if necessary.
- Action
-
Determine the cause of the server stop according to the message output before this message or from the troubleshooting information (dump or trace), and then take action. If necessary, restart the server. Note that troubleshooting information is not output when gg....gg is c000, c100, c200, c300, c400, c500, c600, c700, c800, c900, d000, d100, d200, d300, or d500.