Kbase P130169: 10.1C ODBC/JDBC connection to the database are case sensitive in regards to database name
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/04/2011 |
|
Status: Verified
SYMPTOM(s):
ODBC connection fails with error message "Server rejects connection on attach"
Error attempting to connect to database via ODBC fail
[DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OpenEdge] Server rejects connection on attach
Error attempting to connect to database via JDBC fail
[DataDirect][OpenEdge JDBC Driver][OpenEdge] Remote Database Name not valid
FACT(s) (Environment):
Identical connection parameters worked in previous OpenEdge 10.1x database connections.
Database is being started via a parameter file.
Database name is lower case from Operating System level.
Database name is listed as Upper Case in parameter file.
OpenEdge 10.1C
Windows
CAUSE:
This is expected behavior, in 10.1C SQL-92 connections to the database are case sensitive. 10.1C introduced this new feature. It is designed as additional insurance to make sure the user is connecting to the expected database. It is case sensitive to the way the database name was specified when started. On Windows, the proserve command is not cases sensitive.
FIX:
To fix the issue, simply make sure the database name matches spelling and case used when starting the database. This can be confirmed by looking at the dbname.lg file and looking at the line with the following information:
(4235) Physical Database Name (-db) <dbname>.
For example, if database name is SPORTS2000, the database name in the connection parameters must be SPORTS2000 or SPORTS2000.db. If the name is changed to sports2000 on startup of the database, then the ODBC/JDBC connection will fail with the above errors unless the database name being specified on connection is consistent with the database name used to start the database.
Example: If the physical name of the database is SPORTS2000 and you proserve the db as sports2000:
proserve sports2000 -S <port>
You must use the lower case version for the database name in the DSN Admin tool to avoid errors.