Problems with Tools Startup

The following flow chart helps you isolate a problem when starting an Ingres tool:

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.
   1. 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.
   2. 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.
   1. 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

      UNIX:

      C Shell:

      setenv II_DBMS_LOG $II_SYSTEM/ingres/files/dbms_%p.trace

      Bourne Shell:

      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 others logs (or the recovery process log)

      VMS:

      define /system/exec II_DBMS_LOG -
      II_SYSTEM:[INGRES.FILES]DBMS.LOG (for a system level installation)

      define/group/exec II_DBMS_LOG - II_SYSTEM:[INGRES.FILES]DBMS.LOG (for a group level installation)

   2. When the DBMS Server shuts down, information is dumped to the DBMS log file. You must rename the file before restarting Ingres 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.

Database Connection Problems

Database connection problems occur in the following scenarios:

• If you cannot connect to any database
• If you encounter errors while connecting to individual databases

No Database Connections

If you cannot connect to any database, follow these steps:

1. Check the errlog.log to see if there are any associated messages. These messages are often more informative than the message displayed on your screen and can quickly identify the source of failure. Check for associate messages in the errlog.log by using their timestamps.
2. Ensure that all your installation's processes are running, as described in Check Ingres Installation on Windows, Check Ingres Installation on UNIX, and Check Ingres Installation on VMS.
3. Run logstat to insure that the logging system status is ONLINE and not LOGFULL. If the status is not ONLINE, see How to Log System Issues.
4. Use iinamu to interrogate the Name Server. (For additional information, see iinamu in the Command Reference Guide). Type show ingres to verify that the DBMS Server has registered with the Name Server.
5. Use the iimonitor utility to see if you can connect to the DBMS Server. See iimonitor in the Command Reference Guide.

   If you can connect, at the "IIMONITOR>" prompt type show sessions to examine DBMS server activity.

   If you cannot connect to the DBMS Server, see How to Log System Issues.

   Check the Ingres environment variable/logical II_DBMS_SERVER:

   Windows:

   Use ingprenv and your system's echo command to verify that II_DBMS_SERVER is not set, either in the Ingres symbol table or your local environment.

   UNIX:

   Use ingprenv and your system's env or printenv command to verify that II_DBMS_SERVER is not set, either in the Ingres symbol table or your local environment.

   VMS:

   Use II_DBMS_SERVER to bypass the Name Server process. Issue the following command at the operating system prompt:

   define II_DBMS_SERVER II_DBMS_pid

6. Restart the Name Server if II_DBMS_SERVER works.
7. If the error condition persists, contact technical support, as described in What You Need Before Contacting Technical Support.

Individual Database Connection Failure

If you can connect to some databases but not others:

1. Check the errlog.log for database connection error messages. These messages can quickly identify the source of the failure.
2. Check that the database is not exclusively locked by another user.
3. Check database permissions and ownership, as described in Check Ingres Installation on Windows, Check Ingres Installation on UNIX, and Check Ingres Installation on VMS.

   Verify that your database still exists and is not being recovered by the recovery system.

4. Type catalogdb and choose "catalog" / "databases" or run VDBA to check if the database is listed.

   If the database does not exist, a corresponding error message is sent.

   Using VDBA:

5. Select a server and click Connect DOM.
6. Select Database from the drop down menu and choose infodb. Make sure the database is not listed as inconsistent and that the status indicated is "VALID."