DBMS Server Stopped
Once started with ingstart, the DBMS Server process must continue running until the ingstop or iimonitor command is issued to stop it. If the DBMS Server stops running (“dies”) for any other reason, report it to technical support along with the associated error log messages and, if possible, the cause of the DBMS Server stopping.
1. Document error log entries associated with the process death
. Details on reading the log files are described in
Check the Error Log Files. Save all errors for technical support.
2. Isolate the reason your DBMS Server process died.
a. Isolate which operations, application, query, and tables are needed to duplicate the problems. See the copyapp and unloaddb command descriptions in the Command Reference Guide.
b. Save this to make a test case for technical support.
3. If the immediate cause cannot be isolated, perform long-term diagnostics with II_DBMS_LOG. This diagnostic tool is especially valuable for fatal DMF errors.
a. Set II_DBMS_LOG to capture a “snapshot” of the DBMS Server when it stops by setting it to the full path name of a file before starting the DBMS Server. For example:
Windows:
SET II_DBMS_LOG=%II_SYSTEM%\ingres\files\dbms.log
Linux:
II_DBMS_LOG = $II_SYSTEM/ingres/files/dbms_%p.trace
EXPORT II_DBMS_LOG
At startup, the %p in the II_DBMS_LOG specification is replaced by the Process Identifier (PID) of the server process. This prevents DBMS servers from clobbering each other's logs (or the recovery process log)
b. When the DBMS Server shuts down, information is dumped to the DBMS log file. You must rename the file before restarting Actian X or the new server overwrites the file. Prepare to send this file along with associated errors from the error log files to technical support for analysis.
Last modified date: 04/03/2024