cancel
Showing results for 
Search instead for 
Did you mean: 

Database error: (CORBA) "Error on Fetch" . (IES 10901)

Former Member
0 Kudos

Hi Folks - I'm getting "Database error; (CORBA) "Error on Fetch".(IES 10901)" or "Database error: (CORBA) "Error on Describe" . (IES 10901)" when scheduling a webi report.

The reports complete, albeit usually long when refreshing, but when attempting to schedule, either one the error above is show. I doesn't seem like there's any action in particular that causes one or the other - in fact i've been mostly getting the "Database error: (CORBA) "Error on Describe" . (IES 10901)" but recently started getting the "error on Fetch"

The only pattern we have noticed is that it only occurs against SQL Server data sources. We reports that run against oracle db data sources but we do not encounter the error when scheduling against those sources.

I haven't been able to find much on the error out there on the error. I've reviewed KBA's 1402451, 1500465, and 1347906, but to no avail.

Any recommendations will be greatly appreciated.

Thanks!!


OUR ENVIRONMENT

___________________

Product Version - BI 4.1 SP 02

Operating system - (OS/SP Level):  AIX 6.1 PL9 SP1

CMS Database :Oracle 11g

Problomatic Report - reporting Database : MS 2012 Web Server :

Problomatic Report - Database Connection: JDBC

Windows 2003 64Bit - Apache tomcat 7.0

Type of environment :Stand Alone

Accepted Solutions (1)

Accepted Solutions (1)

sateesh_kumar1
Active Contributor
0 Kudos

Hi Marlon ,

I'm not sure if it helps  .Check below KBA

1920700 - Error:"CORBA error while communicating with the SL Service(WIS 00000)"

Try by changing WebIContainer_ServerDescriptor.xml in win64_x64\config properties file.

Try changing Time out parameters of webi processing server in CMC also.

Former Member
0 Kudos

Hi Sathish, thanks for the response - worked with SAP support a bit and added command "-RequestTimeout 18000000" to the properties of the  all the webintelligence server, the APS servers, the CMS server and the job servers we had configured. So far the reports have been running and no error is being produced.

Thanks!

Answers (0)