Forum Discussion

Jessica_42876's avatar
Jessica_42876
Icon for Nimbostratus rankNimbostratus
Sep 28, 2011

Health Monitor

Hi, guys!

 

 

I have a problem with an F5 Health Monitor for Oracle with an OracleRac 11gR2 environment. We checked the next manual http://www.f5.com/pdf/deployment-guides/oracle-rac-database-dg.pdf to deploy the health monitor but it doesn't work. We make a trace and get the next error in the Oracle Listener:

 

ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

 

Also, we checked the F5 logs in /var/log/ and we get the next message:

 

9/13/11 2:29 PM: jdbc:oracle:thin:@10.0.3.202:1522:oraculo(Thread-9070): getConnection (Io exception: The Network Adapter could not establish the connection)

 

9/13/11 2:29 PM: jdbc:oracle:thin:@10.0.3.206:1522:oraculo(Thread-9072): getConnection (Io exception: The Network Adapter could not establish the connection)

 

9/13/11 2:29 PM: jdbc:oracle:thin:@10.0.3.204:1521:oraculo(Thread-9068): getConnection (Listener refused the connection with the following error:

 

ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

 

The Connection descriptor used by the client was:

 

10.0.3.204:1521:oraculo

 

)

 

 

The conclusion is: The F5 use the Oracle SID in the connection string but, with an OracleRAC enviroment, the SERVICE_NAME must be used instead the SID. Also, these connection string is an old fashion of the Oracle JDBC. So,what can we do?

 

 

and

 

can we use ". ", like such as an oracle.example.com in the Database?

 

 

 

 

Jessy

 

    • Mike_Dayton_108's avatar
      Mike_Dayton_108
      Icon for Nimbostratus rankNimbostratus
      What did you end up using for your connection string? How did you address the SERVICE_NAME= issue? Version 11.5 I tried to cheat by manually editing bigip.conf with: database (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=%node_ip%)(PORT=%node_port%))(CONNECT_DATA=(SERVICE_NAME=my_name))(SERVER=dedicated)) ... Syntax Error unknown property
  • Ojp,

     

     

    BIG-IP 11.0 has been updated to the latest JDBC available from Oracle as of it's release. This is what allowed us to retool the monitor in v11 to support the new Connection Strings, among other things.

     

     

     

    Cheers.