Hello Anuprai,
I suspect you hand-edited your $ODBCINI file, possibly by extrapolating what the entries would look like based on a connection string, because if you had used the Ingres ODBC Administrator (iiodbcadmin), the DSN entry would look like this:
[evalkit_Ingres2006]
Driver=Ingres
Description=Ingres
Vendor=Ingres Corporation
DriverType=Ingres
Server=test
Database=bobd01
ServerType=Ingres
PromptUIDPWD=
WithOption=
RoleName=
RolePWD=
DisableCatUnderscore=N
AllowProcedureUpdate=N
UseSysTables=N
BlankDate=N
Date1582=N
CatConnect=N
Numeric_overflow=Y
SupportIIDECIMAL=N
CatSchemaNULL=N
ReadOnly=N
SelectLoops=Y
You may be able to connect if you substitute the keyword "server" for "vnode".
If you are using a version of Ingres later than 2.6, You may use the iiodbdcadmin utility as Dave recommended. Early versions of Ingres name the utility as iiodbdcadmn (no "i" in 'admin').
Before using iiodbcadmin, be sure to configure the ODBC for Ingres by running iisuodbc.
Note that if your $ODBCINI file contains connection information about other drivers, iiodbcadmin will ignore the information for those drivers, but you can add, modify or delete Ingres driver entries as required.
You will find more information about using the Ingres ODBC driver in an Ingres environment in the Connectivity Guide at
http://esd.ingres.com/product/docs/Ingres_2006/docs.
Regards,
Ralph Loen