Sunday, October 16, 2011

BI Publisher 10.1.3.3.3 jdbc connection failed t connect to RAC Database

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem: BI Publisher 10.1.3.3.3 jdbc connection failed t connect to RAC Database

Symptoms:
When using BI Publisher 10.1.3.3.3 and configure Connection Pool with RAC database by using "oracle.jdbc.driver.OracleDriver" as driver class. when we are providing RAC Db details, it is failing to connect. So are forced to connect to one specific node of the RAC database.

Log files:
OC4J container log file

[031710_073542788][][EXCEPTION] jdbc:oracle:thin:@172.29.128.52:1630:USBL
[031710_073542788][][EXCEPTION] biuser
[031710_073542788][][EXCEPTION] oracle.jdbc.xa.client.OracleXADataSource
[031710_073542789][][EXCEPTION] java.sql.SQLException: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
HPUX-ia64 Error: 2: No such file or directory

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:277)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:272)
at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOsesskey(T4CTTIoauthenticate.java:243)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:304)
at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.java:430)
at oracle.jdbc.driver.T4CConnection.(T4CConnection.java:151)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:608)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at oracle.apps.xdo.servlet.data.JDBCDataSource.testConnection(JDBCDataSource.java:198)
at oracle.apps.xdo.servlet.ui.admin.datasource.UpdateConnectionServlet.doConnectionTest(UpdateConnectionServlet.java:341)
at oracle.apps.xdo.servlet.ui.admin.datasource.UpdateConnectionServlet.doPost(UpdateConnectionServlet.java:129)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:80)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)


Solution:


The JDBC drivers used by default for Oracle RDBMS is not RAC enabled.
So it only connects to a specific instance rather than the RAC instance.
See JDBC Driver Support for Oracle Application Server (Fusion Middleware)
(Doc ID 365120.1). You could try a RAC enabled JDBC driver.

Bug 9500202 - BI PUBLISHER CP NOT WORKING ON RAC DATABASE logged for this issue.
References:
Bug 9500202 - BI PUBLISHER CP NOT WORKING ON RAC DATABASE logged for this issue.
Get Oracle Certifications for all Exams
Free Online Exams.com

No comments: