SAP BusinessObjects XIr2 to r3.

1 upgrade experiences - Document Transcript

1.
2.

3.

4.

5.

6.

Business Objects R3.1 Upgrade Experiences BUSINESS OBJECTS R3.1 UPGRADE EXPERIENCES
STARSCHEMA LTD., 2009 www.starschema.net
Business Objects R3.1 Upgrade Experiences Contents 1. Install
..................................................................................................................................................... 3 Issue Description:
.................................................................................................................................. 3 Solution:
................................................................................................................................................ 3 2. Federation
............................................................................................................................................. 4 Issue Description:
.................................................................................................................................. 4 Solution:
................................................................................................................................................ 4 Issue Description:
.................................................................................................................................. 4 Solution:
................................................................................................................................................ 4 3. Top level rights
...................................................................................................................................... 4 Issue Description:
.................................................................................................................................. 4 Solution:
................................................................................................................................................ 4 4. Scheduling Reports
in InfoView ............................................................................................................ 5 Issue Description:
.................................................................................................................................. 5 Solution:
................................................................................................................................................ 5 5. Instance names in
report History.......................................................................................................... 5 Issue Description:
.................................................................................................................................. 5 Solution:
................................................................................................................................................ 6 6. Issues reported by
users ....................................................................................................................... 6 Issue Description:
.................................................................................................................................. 6 Solution:
................................................................................................................................................ 6 STARSCHEMA LTD.,
2009 www.starschema.net
Business Objects R3.1 Upgrade Experiences 1. Install Issue Description: During BO install, CMS database stops
abnormally, the installer raises the popup below: Error description in the Event Viewer: The installation fails. Solution:
The rootcause of this issue is related to the CHAR parameter setting of the nls_length_semantics database
parameter (Oracle 9.2). STARSCHEMA LTD., 2009 www.starschema.net
4 Business Objects R3.1 Upgrade Experiences This can not be resolved by setting the nls_length_semantics
parameter to BYTE on the existing database instance. A new temporary database needs to be created with initial
nls_length_semantics parameter set to BYTE, to temporarily host the CMS database. 2. Federation Issue
Description: Client fails to connect to Federation server, unable to create replication job. Solution: Pocket level
analisys of client-server communication (using Packetyzer utility) revealed the true error string: invalid argument:
en_HU. Modifiyng regional settings of the user whose account BO services and Tomcat were running on to
English resolves this issue. Issue Description: The replication job fails. Solution: Federation service is based on BIAR
files. BIAR files are assembled in the temporary folder of the user running the BO services. It may be necessary to
move the temp folder to another partition using environmental variables. 3. Top level rights Issue Description: Users
can not see folders assigned to their groups. Solution: The rootcause of this problem is the slight difference between
R2 and R3.1 right management system. One workaround is to define a custom Access Level (defining custom
Access Levels is a new feature in R3) which includes non inheriting view right on Content > Folder. This newly
created Access Level (eg. View on Folder) needs to be associated with Everyone user at Root Folder level (in CMC
go to Folders, click on Manage, choose Top-Level Security > All Folders). STARSCHEMA LTD., 2009
www.starschema.net
5 Business Objects R3.1 Upgrade Experiences 4. Scheduling Reports in InfoView Issue Description: When
scheduling a report to run once eventually, the scheduled instance instantly enters running state. Solution: This is a
regional setting dependent issue. Packet analisys revealed that the client side JavaScript does not assemble the
entered date in a format acceptable by the report server. Editing the files below PlatformservicesjspjsYUICalendar.js,
Platformservicesjspshared_recurrencerecurrence.jsp, Platformservicesjspshared_recurrence_schedule.jsp solves
this issue. 5. Instance names in report History Issue Description: After performing an upgrade style installation of BO
R3.1 on XI R2, instance names in reports history become incorrect. All report instances are renamed to the time of
the migration. Instance names reference to SI_UPDATE_TS timestamp, which is determined by the LASTMODIFY
column at CMS level. STARSCHEMA LTD., 2009 www.starschema.net
6 Business Objects R3.1 Upgrade Experiences Solution: Adjusting the value of the LASTMODIFY column related to
the report instances to SI_ENDTIME property solves this issue. 6. Issues reported by users Issue Description: After
logging into InfoView, nothing can be seen but a black (or white) sheet in the browser. Solution: Resetting font size to
default resolves this issue. Copyright 2009, Starschema, All Rights Reserved. This document is provided for
information purposes only, and the contents hereof are subject to change without notice. This document is not
warranted to be error-free, nor is it subject to any other warranties or conditions, whether expressed orally or implied

in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We
specifically disclaim any liability with respect to this document, and no contractual obligations are formed either
directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
means, electronic or mechanical, for any purpose, without our prior written permission. Starschema is a registered
trademark of Starschema Limited. Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Web Intelligence and Xcelsius
are trademarks or registered trademarks in the United States and/or other countries of SAP AG and/or affiliated
companies