For anyone interested: Been fighting for quite some time now with my OTR project after running into a somewhat wierd setup using Oracle Cloud Control (Enterprise Manager) which is still the basis for the Oracle Tablespace Report. I run into several issues on OTR since it was not really working properly when there was Target RAC instances to be monitored. One issue that I run into was that I couldn't connect at all to a RAC Instance and also not directly to one of the nodes. Finally figured out that if the DBA, who setup the RAC, activated a Banner in the DB... (displaying some Text info/security info on every connect) the ojdbc14.jar which is shipped with OpenBD won't work.
To solve this issue one need to download the latest oracle driver from OTN in my case ojdbc6.jar since I'm using JDK6 on my Jetty setup. Drop the old jar file and replace it with the newly downloaded jar in the WEB-INF/lib directory What this solves besides the bug on Banners is that one now can connect using the SCAN hostname instead the more complex version using all node hosts and the load_balance=ON Typical old way jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=on) (ADDRESS=(PROTOCOL=TCP)(HOST=host1) (PORT=1521)) (ADDRESS=(PROTOCOL=TCP)(HOST=host2) (PORT=1521)) (CONNECT_DATA=(SERVICE_NAME=service))) With he new driver from oracle the connect string will be more simple.... almost like when connecting to a single instance jdbc:oracle:thin:@scan-host-address:scan-port/service_name It's almost identical to a single instance connect. Instead of the " / " used above the normal connect string have a " : " between port and the SID or Service Name I hope this will be helpful whenever one of you run into this Banner problem on an Oracle DB and also this simplified JDBC connect for RAC -- online documentation: http://openbd.org/manual/ google+ hints/tips: https://plus.google.com/115990347459711259462 http://groups.google.com/group/openbd?hl=en
