Posts

BI 4 Error - QTJ 00519 Refecence @select could not be resolved

After migrating an Universe from XI R3.1 SP 4 to BI 4 SP 8 and converting it in UNX format for a filter object the following error was erased  Riferimenti non risolti:  : @Select(OGGETTI SPECIALI\Cod Anno) it missed the root folder of the object Riferimenti non risolti:  :  @Select( ORDERS \OGGETTI SPECIALI\Cod Anno) so the solution was to replace the first string with the second! See also Sap BI 4.0 errors list

Information Design Tool - How to create a Native filter

Image
How to create a object filter in Information Design Tool Go in th Business Layer an click on insert object button selecting filter object Assign it a name flag the check 'Native' filter select it as Active object and select the where condition in SQL Assistant (check the prompt syntax on the bottom of image behind) Properties See also Bublish unx universe from IDT

Error WIS 10901 - A database error occured. The database error text is: (CS) "DBDriver failed to load : C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32x_x86\dataAccess\connectionServer\dbd_oci.dll (The specified module could not be found)

WebI Error WIS 10901 A database error occured. The database error text is: (CS) "DBDriver failed to load : C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32x_x86\dataAccess\connectionServer\dbd_oci.dll (The specified module could not be found) Environment BO XI 3.1 SP 4 We get this error when  to create a  Rich Client  report from a user's machine, against a universe with a connection to an oracle database . Solution This usually due to  incorrect ODBC configuration so in order to solve this issue try the following steps: 1.      Stop all the services from BO Central configuration Manager. 2.      Open odbc.sbo file located at "Program Files\Business Objects\BusinessObjects Enterprise    11.5\win32_x86\dataAccess\connectionServer\odbc" 3.     Go to parameter setting for "Generic ODBC datasource ". 4.     Change the value of "Transactional Available" parameter to No. 5.     Add this new parameter settin

Error ERR_WIS_30285 -The Web Intelligent server is running out of memory, your document has been closed. If the problem persists, contact your BusinessObjects administrator. (Error ERR_WIS_30285) while refreshing a large Webi report.

Error ERR_WIS_30285 -The Web Intelligent server is running out of memory, your document has been closed. If the problem persists, contact your BusinessObjects administrator. (Error ERR_WIS_30285)  while refreshing a large Webi report. Envirnonement BO XI R3.1 SP 4 This error was erased while scheduling or refreshing  a large Webi report. The cause is connections  timed out. Resolution File Repository Servers:- Input Server: Maximum Idle Time : 60 Minutes (CMC-->servers-->Input File Repository Server)                                                 Output Server: Maximum Idle Time : 60 Minutes (CMC-->servers-->Output File Repository Server) Universe - Timeout parameter limit in the Universe - set this in Designer Open the designer > import the universe. Click File > Parameters, select the controls tab, increase the Limit execution time to 60 minutes. WebIntelligenceProcessingServer Connection Timeout - This is set in the CMC > Servers > WebInte

BusinessObjects Environment Cleanup activity using Query builder

BusinessObjects Environment assessment using Query builder This includes identifying unused BI content (Users, Universes, reports,etc.). We are going to see more in detail about identification of unused objects using Query Builder in this document.   Let us see how to identify unused objects in each category listed below     1. User Community          a. Users not logged in for the past 6 months             SELECT TOP 1000 SI_NAME, SI_LASTLOGONTIME FROM CI_SYSTEMOBJECTS            WHERE SI_NAME NOT IN ('ADMINISTRATOR','GUEST') AND SI_KIND='USER'           AND SI_LASTLOGONTIME < '2013.06.30' ORDER BY SI_NAME          b. Users who never logged in to system              SELECT TOP 1000 SI_NAME, SI_LASTLOGONTIME FROM CI_SYSTEMOBJECTS            WHERE SI_NAME NOT IN ('ADMINISTRATOR','GUEST') AND SI_KIND='USER'             AND SI_LASTLOGONTIME IS NULL ORDER BY SI_NAME          c. Users not in any gr

SAP Business Objects Query Builder

Business Objects Query Builder Among Business Objects tools there is an application named Query Builder which can be used to query the Business Objects Meta Data repository in order to collect more information and details about your  Business Objects reporting system. Its url is: http://BOserver:port/AdminTools/ How to create a query Queries are created in a language SQL like. Unlike Sql language there are not a lot of functions supported (like nesting SQL statements, the GROUP BY clause or the DISTINCT function). Below the possible functions in Query Builder within the different clauses of a query are described: (SELECT, FROM, WHERE, ORDER BY). Some examples behind: A list of the Id and Name of all universes SELECT SI _ID, SI _NAME FROM CI _APPOBJECTS WHERE SI _KIND = 'UNIVERSE' Total num ber of Web Intelligence Reports SELECT COUNT(SI _ID) FROM CI _I NFOOBJECTS WHERE SI _KIND = 'WEBI ' A list of 10 0  Crystal Reports with all properties SELE

BI 4 - IDT error: ambiguous object path - Checking integrity from Information Design Tool shows an error parsing expression: ambiguous object path

On converting a unv universe in unx format in Indormation Design Tool with a generic error after tracing IDT we found the following error and solution: Checking integrity from Information Design Tool shows an error parsing expression: ambiguous object path Environment:  BI.4 - Information Design Tool - SP 5 on Windows Server 2008 R2 Cases: When a dimension and a filter has the same name in Information Design Tool, the Check Integrity returns an Ambiguous Object Path error. Or After converting the universe from UNV to UNX the check integrity gives Ambiguous Object path error. The issue is resolved on Support Package 5 with Patch 1 or Support Package 6. See Also: http://businessobjectsbi4.blogspot.it/2013/09/sap-bi-40-errors-list.html