Information Technology Reference
In-Depth Information
Table24-4 Process Features
Essentials Desktop
Command-line Equivalents
Start Process
pdexec
Stop Process
pdterm
For a complete description of the desktop interface processes, refer to the RME online help.
Several events can cause a process to fail. For example, the database engine might fail for one of the
following reasons:
On UNIX systems, the database uses a small amount of space in the /tmp file system. If this space
fills up, the database can no longer accept connections from client code and fails.
The file system containing the database file is full.
If an application process fails, examine your system to see whether either of these conditions or any
others has occurred, and attempt to correct them.
Troubleshooting a Process Problem
The Process Failures table gives you information about potential process failures. It tells you that the
process has failed or that an administrator has shut down the process.
If a process behaves in an unexpected way and you want to know the possible cause, to troubleshoot a
process, perform the following steps:
Select Admin; Troubleshooting; Process Failures.
Step 1
Click on the process name to display the Process Details table.
Step 2
Click Back to return to the Process Failures table.
Step 3
Click any process state to display the System Log.
Step 4
Click Back to return to the Process Failures table.
Step 5
Click Update at any time to refresh the fields.
Step 6
Starting a Process
Scenario : You check process status and notice that the DbServer process in the Process Status table
shows a state of “Failed to run.” You attempt to restart the process.
For the desktop interface, to attempt a process restart using the navigation tree, perform the following
steps:
Step 1
Select Admin; System Admin; Start Process.
The Start Process dialog box appears.
Step 2
Click Process, select DbServer in the Process Name drop-down list box, and then click Finish .
The Process Status table appears. If the status now reads “Running normally,” you have solved the
problem.
If the process is still not running normally, you may need collect more server and process information
to further troubleshooting.
Search WWH ::




Custom Search