Actian Ingres Non-Spatial Troubleshooting
Problems sometimes arise when attempting to connect to an Ingres database. This is almost always due to a misconfiguration in the user’s environment.
The following suggestions can often help detect and overcome such problems.
- Ensure you can connect to the database with the host, port, database, user name, and password using VDBA on Windows or SQL Terminal monitor.
- Ensure that the port is the two Instance Identifiers followed by the digit 7. We are connecting using the JDBC driver and the Data Access Server.
- If you try to list the tables and nothing happens, check the log file. There may have been an underlying error that didn’t generate a dialog. Usually this means a parameter does not exist or permissions are not sufficient to access the requested resource.
- If your data ends up looking garbled using a given encoding, or you get an encoding error, there might be a system and server encoding mismatch. Try using nchar/nvarchar/longnvarchar types instead.