I did find other sources that 11g is supported.
Here are some suggestions:
Try troubleshooting with the ODBC Administrator first, once the connection is working there, the settings can be added to the "Other Connection Settings" in the Monarch Personal Oracle connector.
Use an IP address instead of a host name.
The connect option "Query Timeout" sets number of seconds for the default query timeout for all statements that are created by a connection. If the error is occurring when the server takes a long time to respond to queries, this could resolve your issue.
- If set to -1, the query does not time out. The driver silently ignores the SQL_ATTR_QUERY_TIMEOUT attribute.
- If set to 0, the query does not time out, but the driver responds to the
- If set to x (x is the value in seconds), all queries time out after the specified number of seconds unless the application overrides this value by setting the SQL_ATTR_QUERY_TIMEOUT attribute.
The connect option "Failover Mode" may also be useful.
You will need to configure the connect option "AlternateServers" to the same connection if you are not currently using AlternateServers.
For example, let's say the Oracle listener service is configured on the host "MyServer", port "1521" and ServiceName=ORC_ABC.
The AlternateServers property can be configured as follows:
Then set Failover Mode to 1 or 2.
If set to 1 (Extended Connection), the driver provides failover protection for new and lost
connections, but not any work in progress.
If set to 2 (Select), the driver provides failover protection for new and lost connections. In addition,
it preserves the state of work performed by the last Select statement executed.
Let us know if any of these suggestions help.