BO XI 3.1 SP3 Full Install supports Windows 7 and Windows 2008. The Supported Platforms document also states that the highest Oracle data connector that is supported is “Oracle Net Client (11.1.0.6)”.
So the problem is that Oracle states clearly that 11.2 is the only version which is supported on Windows Server 2008 R2 (emphasis on the R2).
In other words, as I read it, if I follow the BO XI 3.1 SP3 Support Platforms guide and the corresponding Oracle document completely there is no way that I can run Business Objects Enterprise (BOE) or even BO XI 3.1 SP3 Designer on a Windows Server 2008 R2 and connect to any Oracle data sources.
HI,
At this moment, i’m testing BOE XI R3 installation over W2008, accessing to oracle DB Server 11g with Oracle Client 10g.
With Client oracle 10g, you may be sure, it is working fine.
However, i couldn’t use an oracle instance as repository DB.
So the respository have currently been installed in Mysql DB.
It might be due to values of nls characterset and language parameters of DB instance
Yes with Windows 2008 R2 and Oracle you get stuck. You can either go with an unsupported stack or downgrade Oracle to 11g R1.
I’m currently on a project where in Dev we’re unsupported and expecting that by the time we go live there will be sp’s that offer support. Or failing that we’ll have a reference stack on which we’ll have a supported platform on which we can reproduce an issue and obtain support. Bit of a risk but that’s the plan!
So for the record, we currently have in our dev environment,
An Oracle DB server running on 64bit Windows 2008 R2, Oracle version is 10.2.0.4 which although not supported by Oracle does work.
This DB server hosts repositories for both BOE and BO Data Services and our source, target and reporting schemas. We set DB Charset to AL32UTF8 and National Charset to UTF-8 - is that what you are using tietiebob?
In your case I’m sure you can use the 11.1.0.6 client to connect to the 11.2 database. Check Oracle forums on this but i’d be suprised if there are any show stoppers
Either you run a build that is unsupported by Oracle or unsupported by SAP BO.
The truth is that SAP BO Support is not as strict as Oracle Support. I mean to say that Oracle support will wash their hands of me if I ever complain about running Oracle client 11.1 on my Win Server 2008 R2, because it is explicitly unsupported. BO on the otherhand… well I am not quite sure what they would do. They could say to me if I run 11.2 that this is not supported as their doc says, or if I run 11.1 they could say that is not supported because Oracle says Win Server 2008 R2 is an unsupported platform for it.
OK, I think I found a solution. There is an Oracle Note called “How to Install Oracle 10.2.0.5 on MS Windows 7 / Windows 2008R2”, its number is 1173433.1.
So it would seem that Oracle does support 10.2.0.5 on Win Server 2008 R2. I was told by an Oracle Support person that “I can’t really speak on their requirements or any potential issues you may have using 11gR2 vs 11gR1. What I can tell you is that it is much easier to install 11gR2 vice 10.2.0.5.”
I just verfied this with Statement of Direction: Oracle Database 10g Release 2 Client (10.2.0.5) with Microsoft Windows 7 and Windows Server 2008 R2 [ID 1061272.1], which states:
And so, it seems that to answer my original question the only way to remain 100% compliant with BO and Oracle when running BOE on a Windows Server 2008 R2 box that must connect to Oracle is to install Oracle 10.2.0.3 and patch it to Oracle 10.2.0.5.[/b]
I spoke with a VERY senior BO Engineer and he told me that Oracle 11.2 client was supported by reference (since 11.2 is the only 11 client supported by Oracle on Win Server 2008 R2) and that I would not be denied support by SAP BO if I had trouble with my system running BO XI 3.1 SP3 and Oracle 11.2 32-bit client. He also confirmed that BO is testing 11.2 client presently for certification.
INSTALLATION NOTE:
I should add that I had trouble putting Oracle 11.2 32-bit client on my 64-bit server. Ultimately the solution was simply to right click “setup.exe” and select “Run as administrator” (even though my user is a member of the Administrator’s group). I thought this was quirky because the 64-bit client ran fine with just a double click of “setup.exe”.
We have run into similar issues with the new “BOE-3.1 package with SP3” which is a complete install for Windows 2008 Server that only installs in the 64-bit mode.
We had a 32-bit Oracle 10g client installed, that BOE did not recognize for the CMS and have had trouble installing the 64-bit Oracle 10g client that we downloaded.
Anyone know which specific 64-bit Oracle 10g client should be used with the “BOE-3.1 package with SP3” 64-bit package…?
As far as I know, SAP BOE 3.1 offers a native support for 64bit architecture, but is a 32-bit application (for Windows, there is a true 64bit app for Linux). You need to install Oracle 32bit client to communicate with the BOXI3.1. Also, Oracle 10.2 client (32bit) works well with BO only and ONLY if you install BO in a folder which has no “(x86)” in its name. This goes for server and client installations on Win7/Win2008.
We installed it (BO XI 3.1 SP3 + FP3.2) in c:\BOXI31 folder (Run as Administrator), used Oracle 10.2.0.1 32bit client (install it as Run as Admin) and our OS is Win 2008 Server SP2, 64bit, and it all works.
If you have access to the SAP Knowledge Base check out note 1429999. It will point you to a document that, for me, was very informative.
As far as its relevance to this thread, it states that the 10.2.0.5 client on Windows 2008 R2 x64 would be supported when connecting to an 11g CMS database because Oracle states that it is a valid and supported configuration. SAP supports the 10.2.0.5 client, Oracle supports that client connecting to an 11g instance.
The Oracle 11.2 client will show on the supported platforms doc with 3.1 SP4.
My installation failed a lot of time (Oracle CMS) when I tried to install in D:\Program Files (X86)\Business Objects…, but it succeeded when I installed it in D:\Apps\BO31\
(BOB member since 2004-03-17)
(BOB member since 2007-03-23)
(BOB member since 2009-04-24)
(BOB member since 2006-07-28)