System Administrator Guide > System Administrator Guide > Troubleshooting Ingres > Problems with Tools Startup > Database Connection Problems
Was this helpful?
Database Connection Problems
Database connection problems occur in the following scenarios:
• If you cannot connect to any database, including iidbdb
• 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 Diagnose Logging System Problems.
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 Diagnose Logging System Problems.
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 Actian 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. Check if the database is listed:
Type catalogdb and choose Databases.
Using Actian Director: Select the database from the Instance Explorer, and then select Properties, Information. Make sure the database is not listed as inconsistent.
Using VDBA: Select a server and click Connect DOM. 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.”
Last modified date: 08/29/2024