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