cancel
Showing results for 
Search instead for 
Did you mean: 

WIS 10901 error while refreshing report in rich client

Former Member
0 Kudos

I'm facing a strange issue while refreshing a report from Rich client. Here are details

Environment: BO XI 3.1 SP3, Oracle application DB. Weu2019ve 2 BO servers (S1 and S2) on cluster and load balancer (common URL) in front.

While login to S1 with 6400 port, I can refresh report in rich client.

While login to S2 on 6400 port or using common url, during refresh gives below error u2013

u201CA database error occurred. Database error text is: (CS) u201CDBDriver failed to load: C:\Program Files\.....\dbd_oci.dllu201D (The specified procedure canu2019t be found) (WIS 10901)u201D

Iu2019ve installed oracle8i client on my system. Any idea what causing this issue?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

"While logging into S2 or Common URL...."

Where do you enter the s2 or common url info?

Former Member
0 Kudos

Mentioned S2 or URL in System name box like

@Server Name.domain controller:6400

amrsalem1983
Active Contributor
0 Kudos

do you have the oracle client installed on the S2?

Former Member
0 Kudos

Yes. Oracle 10g client installed on both application server. I've teste the universe connection from server, it's working fine.

Any idea what could be probable causes of "DBDriver failed to load: C:\Program Files\.....\dbd_oci.dllu201D error?

One observation, the path of dbd_oci.dll is the BO installation directory of my local machine (on server BO is not installed on C drive). Why it's referring dbd_oci.dll from local client even in 3 tier mode?

amrsalem1983
Active Contributor
0 Kudos

i think its all related to the Oracle client on your server

check the report queries, is it all from Universes? and what are the connection for those universes?

check it step by step from the report level (Queries -> Universes ->Universes Connections)

good luck

Former Member
0 Kudos

But why those reports are working fine from other machine? also it's working when I 'm connecting to S1 in 3 tier mode. I think something wrong in my local system, but can't figure out the exact cause.