Hi Mats, In my example, the scan host (prodscan.local) resolves to 3 ips that are cycled by the RAC nodes. The second server is strictly the dataguard failover.. So yes, this is using the preferred method of 1 scan_host, resolving to all rac nodes. We've extensively tested rac failover, dataguard failover, and even scan dns failure.
Another example of the connectstring using the OpenBD api: <datasource name="prod_db"> <displayname>prod_db</displayname> <password>xxxxxxxxxxx</password> <connectionretries>2</connectionretries> <sqldelete>false</sqldelete> <sqlupdate>false</sqlupdate> <username>myapp</username> <drivername>oracle.jdbc.OracleDriver</drivername> <sqlstoredprocedures>true</sqlstoredprocedures> <perrequestconnections>false</perrequestconnections> <sqlinsert>false</sqlinsert> <sqlselect>false</sqlselect> <connectiontimeout>60</connectiontimeout> <port>1521</port> <server>prodscan.local</server> <databasename>prod_db</databasename> <description></description> <connectstring></connectstring> <logintimeout>60</logintimeout> <initstring></initstring> <hoststring>jdbc:oracle:thin:@prodscan.local:1521/ myrac_servicename</hoststring> <maxconnections>20</maxconnections> <name>prod_db</name> </datasource> Where 'prodscan.local' is the SCAN host name. You'll have to manually edit the bluedragon.xml file because the admin console doesn't let you create the hoststring with service_name notation. Maybe try using the ojdbc14.jar file and see if the problem persists? Hopefully it'll work for you. -chris -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en
