2.7.2 The action to be taken if the embedded database is unable to start
This subsection describes the action to be taken if the embedded database is unable to start.
- Organization of this subsection
(1) Action to be taken if the embedded database is unable to start normally
The following table describes the possible causes of a failure of the embedded database to start normally and the actions to be taken.
|
Possible cause |
Action to be taken |
|---|---|
|
The embedded database is not installed or set up correctly. |
Install or set up the embedded database again. |
|
The system definition contains an error. |
A message reporting that the system definition contains an error is output. Correct the error in the system definition based on the information in the message. |
|
Memory or file capacity is insufficient. |
A message reporting that system memory or file capacity is insufficient is output. Either stop unnecessary processes, or delete unnecessary files. If the message is related to shared memory, review the system definition. If the message is related to process-specific memory, stop all unnecessary processes. In UNIX, if necessary, check the settings of the operating system parameters related to shared memory of the OS. For details about the operating system parameters, see the Release Notes. |
|
Files required to start the embedded database are missing. |
A message reporting that a file or files required to start the embedded database are missing. Create the required file or files based on the information in that message. |
|
A problem has occurred in a file required to start the embedded database. |
Refer to the messages, and check the file where the problem occurred. Eliminate the cause of the problem, and then restart the embedded database. |
|
The OS is not properly configured to act as the execution environment for the embedded database. |
Reconfigure the OS. |
|
The current system log file cannot be allocated. |
Use the ajsembdbaddlog command to add a system log file. |
(2) Action to be taken if the embedded database is unable to restart
When the embedded database cannot be restarted, review the messages that are output during the restart processing. The following table lists the possible causes of a failure of the embedded database to restart and the actions to be taken.
|
Possible cause |
Action to be taken |
|---|---|
|
The embedded database is unable to restart because a problem occurred in the RD area used by the master directory. |
See (3) Action to be taken if a problem occurs in the system area. |
|
The embedded database failed to restart after a log was added and the single server definition was edited (the KFPS00715-E message is output). |
Execute the ajsembdbstart command with the -R option specified. |
|
The embedded database cannot be restarted in UNIX due to a problem other than the above. |
See (4) Action to be taken if another type of problem occurs (in UNIX). |
(3) Action to be taken if a problem occurs in the system area
The embedded database cannot be restarted if a problem has occurred in the system area. In this case, you must restore the system area by using the procedure below. The system area contains internal information about the embedded database system. For details about the commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
To restore the system area:
-
Use the ajsembdbstart command with the -r option specified to start the embedded database.
-
Use the ajsembdbrstr command to restore the system area.
-
Use the ajsembdbstop command to terminate the embedded database.
-
Use the ajsembdbstart command to start the embedded database.
-
Use the ajsembdbrstr command to restore the RD area where the problem occurred.
We recommend that you check the execution results after each command is executed to ensure that the command was executed successfully.
(4) Action to be taken if another type of problem occurs (in UNIX)
The following describes the action to be taken if a problem other than those described above occurs in UNIX. For details about the commands used for this purpose, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference or 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
(a) If the embedded database process registered in the OS has not started
Sometimes, an embedded database process registered in the OS might not start due to a fault of some kind. The OS will make several attempts to start the process before giving up, after which you will be unable to start the embedded database by using the ajsembdbstart command. At this point, take action by using the following procedure.
To correct the problem:
-
Execute the ajsembdbinstl command.
Note that if power is shut off and the server that hosts the embedded database stops while the database is running, the same problem might occur immediately after you turn the power back on and start the OS. This is because the status of the disk that contains the embedded database practical directory is the failed status. Take the same recovery action as described above.
(b) If the embedded database process registered in the OS has started
If the embedded database process registered in the OS has started, take action by using to the following procedure.
To correct the problem:
-
When you execute the ajsembdbstart command, a message is output. Use the information in the message to resolve the problem.