Siebel BI Publisher reporting environments should not be upgraded to the latest BI Publisher Patch #13399232 (Doc ID 1645512.1)

Last updated on JULY 20, 2016

Applies to:

Siebel Reports - Version 7.7.2.10 SIA [18385] to 8.1.1.5 SIA [21229] [Release V7 to V8]
Information in this document applies to any platform.

Symptoms

 As part of the installation and upgrade procedures for the Siebel BI Publisher reporting integration the recommendation exists to patch up to the latest available patch for BI Publisher 10.1.3.4.1 and customers are directed to review the following document :
< Document 797057.1> Overview of Available Update Patches for Oracle BI Publisher Enterprise 10g

Users following these instructions will find that their BI Publisher installation is upgraded to 10.1.3.4.2 which has not been certified for use with Siebel BI Publisher reporting on versions prior to 8.1.1.6. From the Siebel 8.1.1.6 FixPack and Siebel 8.2.2 FixPack onwards the Siebel BI Publisher integration has been certified against BI Publisher 10.1.3.4.2.


Users are likely to encounter errors following the application of BI Publisher Patch #13399232.


Following application of the patch the Siebel Reporting integration will fail with errors such as these which can be found within the BI Publisher log file :

11/10/07 08:33:17.483 xmlpserver: Servlet error
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (500)Internal Server Error
faultActor:
faultNode:
faultDetail:
{}:return code: 500
&lt;html&gt;&lt;head&gt;&lt;title&gt;Message:&lt;/title&gt;&lt;/head&gt;
&lt;body&gt;&lt;h1&gt;Message:&lt;/h1&gt;
&lt;p&gt;An error occurred while trying to process your request. This error indicates a problem with the configuration of this server and should be reported to the webmaster (along with any errors listed below). We apologize for the inconvenience&lt;/p&gt;
&lt;p&gt;Error(s):&lt;ol&gt;&lt;li&gt;Username and/or password not specified for EAI Request&lt;/ol&gt;&lt;/p&gt;
&lt;/body&gt;&lt;/html&gt;
{http://xml.apache.org/axis/}HttpErrorCode:500

(500)Internal Server Error
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.siebel.apps.shared.xmlp.security.BIPSiebelSecurityWSPortStub.authenticate(BIPSiebelSecurityWSPortStub.java:298)
at oracle.apps.xdo.security.SiebelValidator.validate(SiebelValidator.java:139)
at oracle.apps.xdo.servlet.ui.admin.security.SecurityAdminUtil.getDirectoryValidator(SecurityAdminUtil.java:320)
at oracle.apps.xdo.servlet.ui.admin.security.SecurityAdminUtil.getAllRoles(SecurityAdminUtil.java:424)
at oracle.apps.xdo.servlet.ui.admin.security.RoleHomeServlet.getRoles(RoleHomeServlet.java:367)
at oracle.apps.xdo.servlet.ui.admin.security.RoleHomeServlet.renderBody(RoleHomeServlet.java:259)
at oracle.apps.xdo.servlet.ui.admin.security.RoleHomeServlet.doPost(RoleHomeServlet.java:101)
at oracle.apps.xdo.servlet.ui.admin.security.RoleHomeServlet.doGet(RoleHomeServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:100)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)


Other, as yet undetermined, functionality errors may also occur following the upgrade.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms