I’ve been working with a couple of 4.0 upgrades lately and found that in many cases the Upgrade Management Tool can introduce some significant challenges. At this point SAP support seems to have very few people on board with any expertise with the tool and the challenges associated with using the tool for an upgrade to 4.0. I’ve had two messages open for more than a month each and despite numerous escalations can’t seem to get in touch with anyone at SAP that can help. I’m starting this thread hoping it can be a centralized location for any tips, tricks, and other discussions related to using the upgrade management tool to upgrade to 4.0.
I’ll start with one. Apparently when you use the Upgrade Management Tool you need more disk space available to your temp folder than the disk space consumed by the content you intend to move to 4.0 on both the source and target servers. For example, If you intend to perform a complete upgrade and the Filestore on your source server is 10 GB, then you need at least 10 GB free to the temp folder on both the source and target server. Actually, after speaking with several engineers at SAP I heard that it is recommended that there be free disk space available to the temp folder equal to 3x the size of the amount of content that you intend to move. Is this true? I don’t have a definitive answer.
Where is the temp folder located? In Windows go to Start -> Run and key in %TEMP% to find out. Most likely it will be located on the C: drive.
So what do you do if you don’t have 30 GB free on your C: drive? If you have virtual servers yo can grow the virtual disk. If not, you can change the location of the temp folder to a different drive. Do this in the Environment Variables. System Properties -> Environment Variables -> Change the value for TEMP to a new location. If virtualizing it may actually be easier to add a new virtual disk and then change the TEMP location to that new virtual disk. If you are using a physical box, hopefully you don’t have to add new physical disk.
If anyone can add/clarify/correct my understanding of this process it would be appreciated.
Here’s another one. It is recommended that you increase the amount of memory that you allocate to the Upgrade Management Tool by changing the command line parameter -Xmx. So what does that mean? By default the command for running the Upgrade Mangement Tool on Windows is as follows:
You can make this change by going to Start -> All Programs -> SAP BusinessObjects BI Platform 4.0 -> SAP BusinessObjects BI Platform. Right click on Upgrade Management Tool and select Properties. Look through “Target” until you find -Xmx2g. Change to -Xmx4g and close.
Again, if anyone can add to/clarify/correct that would be great.
One more. Are you getting this error when trying to move a folder full of objects to 4.0 using the Upgrade Management Tool?
A timeout occurred. Failed to update the object within 300 seconds.
What does that mean? In my case there were several Crystal Reports that were tied to old printer drivers on the source server. Those same printer drivers were not installed on the 4.0 server. As a result the Upgrade Management Tool was unable to move the report (as well as all instances tied to the report) to the new server.
I fixed things by going to the source server, opening the report using an older version of Crystal Reports, and saving the report to my network. I then opened the report with Crystal Reports 2011 and tried to save it out to the new 4.0 server. I was prompted to install a printer driver which was tied to the report before I could save the report. After I installed the printer driver I was able to successfully move that same folder full of reports to the new 4.0 server using the Upgrade Management Tool.
In this particular case I went from having 290 errors in the log file generated by the UMT to 0 errors generated by the UMT so something this small can have a huge impact.
Right 71 of kind Webi has been dropped. Install components on the destination system that can handle this kind of object to prevent rights from being dropped.
Right that existed in XI R2 does not exist in 4.0
Right 61 of kind Webi has been dropped. Install components on the destination system that can handle this kind of object to prevent rights from being dropped.
Right that existed in XI R2 does not exist in 4.0
Right 62 of kind Webi has been dropped. Install components on the destination system that can handle this kind of object to prevent rights from being dropped.
Right that existed in XI R2 does not exist in 4.0
According to support this means that there were rights setup on certain Web Intelligence documents in XI R2. The equivalent rights do not exist in the 4.0 system because the security model changed. Therefore the rights were dropped as the content was moved into 4.0. You will want to revisit security on the 4.0 system to ensure that the rights that were dropped don’t compromise the security of your system.
My issue with the tool is that I can’t seem to get all the objects to move to 4.0. I am moving from Crystal Enterprise 2008 (XI 3.1) and I need it to move everything especially the recurrences.
One of the problems I ran into recently was with a system that held only Crystal reports. There were several thousand repository objects set up in the Business View Manager (BVM) for dynamic prompts. The UMT does not like working with the objects from BVM and will throw an error if there are more than 500 - 700 of them selected for migration.
I ended up doing an incremental import using the following steps:
Import users and groups - UNCHECK the personal folders for the import.
Determine which personal folders contain reports.
Reimport the users whose personal folders contain reports in batches of 3-5 users, including their personal folders.
Import the public folders in batches of 3-5 folders, check the number of repository objects included after the UMT determines what all of the dependencies are. If the number is more than about 700, go back and remove something from the import.
I have been trying it with just one report and it won’t copy the report if there is a destination associated to it. It says that there are two destination property bags so it doesn’t create the object.
If i go with Incremental approach, i can bring all the public folders and associated objects… But when i select just 1 user group it is calculating around 400 K objects and then throwing errors, not sure what dependencies it is pulling…
I feel old Import Wizard was much more flexible and stable…
I come up with another issue while using Upgrade Management Tool
I have 500 Reports and 10’s of sub folders in One of the Public folder in 3.1. now i want 1 sub folder and 10 Reports out of them to be migrated to 4.0 SP5.
when i run Upgrade Management tool and Select Folders->Sub Folder and then right side the list of reports which i need and click on NEXT
in the next screen, it shows me all reports,folders, sub folders and everything. again, here i need to select my 10 reprots out of 500+ reports…
am i doing right? or is there anything that can be looked at?
did any one of you face similar issue?
We have a large repository of 48,000 users and over 100,000 reports and about 36,000 instances. Our Infoobject6 table has 437,000 rows. Following other posts, we increased the UMT timeout to 1200 then 3600 and the memory on the UMT server to 24GB and gave 16GB to the UMT. Also, allocated a lot of /TEMP space and pointed the Environment variable to it. We also made sure the FRS was not using the same drive. All services except the CMS, FRS and connection server were turned OFF on the source/dest including the Tomcats.
- Still, we were getting an Upgrade Management Tool or UMT Timeout During Receive after about 30-40 minutes into the migration (either all Users and Groups via incremental or Full Upgrade methods). We had our Oracle team capture the SQL it was sending on the source system and discovered it sends a huge SQL statement (for us it was over 21,000 lines) with a bunch of AND NOT IN (150 SI_IDs). I found these were all in the Temporary Storage folder. Running that SQL alone took over 3 hours. The really kool part was that after 5-6 minutes, it would resend the same SQL and it did that 5-6 times before it timed out.
REMEDY: In the source system CMC, go to Temporary Storage and set the limit on that folder to 100 or less BEFORE attempting the upgrade. I deleted them all. We used an off-line copy to do this because a live system will continue to create more instances in Temparary Storage. We got past the Timeout and are now testing how long it will run.
FULL CHECKLIST:There are some key things you need to do to improve your chances that the UMT will work:
Configure your 4.1 Servers for performance before you migrate (splitting the APS), especially your Event Server. The UMT will point any File Events to it, so if it’s moved later, they lose that and will not work until you edit each one and resave.
Clean up unneeded content
– Delete all content from Temporary Storage (causes Timeouts)
– Remove all DeskI reports if no plans to use the Viewer integration
– Script to clean out Inboxes of content older than 90 days
– Users with the most GBs of content in personal folders
– Large reports (BIAR files don’t handle big files well)
– Failed Schedules
– If you don’t use Crystal, delete any Crystal sample content
Run the Repository repair tool and make sure it actually worked
Update Windows AD/LDAP and disable on the source system (hopefully a staged copy of your repository and FRSes). Otherwise the UMT tries to authenticate any user it brings and causes more timeouts or failures if the user doesn’t exist.
On the machine where you run the UMT, Point %TEMP% to a Drive twice the size of your FRSes. We found it best to login with the Server User in an Admin Remote Session.
If you have lots of users, you may need to set BatchExpiry on both CMSes to 2000 or up to 9000
Turn off all unused Servers and tomcats (Keep CMS, FRS, & Connection and Crystal App Server if you have Crystal content).
If you can, turn off Virus scanning
On the UMT cmd line, increase its memory to -Xmx16g or more
HERE Is a UMT Cmd Line we used for our large deployment
On the destination 4.x server, turn off Search, Monitoring, and Auditing while the UMT runs.
We recently migrated from XIR3 to 4. After the migration it was found that no sub folders were migrated in the users personal folders. Users therefore lost their reports in the migration.
Is this a common issue? Does something special have to be done to migrate the subfolders?
If you’re a fan of backing up your content in BIAR files, this may be helpful:
Navigate to: Start > All Programs > SAP Business Intelligence > SAP BusinessObjects BI platform 4
Right click Upgrade Management Tool and click properties
Change the Target line as follows:
The -internal_use_only_noversioncheck switch addition stops the above error from happening and allows a user to restore content within a BI4.x to BI4.x environment using the Complete or Incremental options.
I have also another issue for using Upgrade Management Tool (BO3.1 to 4.1).
We used it on a Linux system and it works fine. All data are imported and upgraded.
But is it possible to run the tool a second time and overwrite or update the old data? Or is there an easy way to delete the old data (befor running the tool a second time)?
We are upgrading to BI 4.0 from 3.x and have LDAP setup on the 3.x server. However, we need to migrate the security, access levels and users from 3.x system. Do we need to setup LDAP authentication before we migrate or post the migration. What are the steps to setup LDAP authentication on the BI 4.0 platform. Any inputs are highly appreciated.
Upgrading from Edge 3.1 SP5 to Edge 4.1 SP2. Using the Upgrade Management Tool to move content from the 3.1 source to the 4.1 target I get the following error:
I get the error after I select a subset of content using an Incremental Upgrade. This happens as I am running through the settings in the UMT and I am never even able to kick off the content migration. I refined the upgrade to focus on a specific user. When I select the user and not their dependencies the user moves fine. When I select the users dependencies (most likely content in Personal Folder) I get the above error. Has anyone seen this?
I am trying to use UMT command line tool in Linux environment.But whenever I am giving the correct parameters I am getting error upgrademanagementtool.jar is not accessible.Is there any specific thing I am missing.The access to that jarfile has been checked and the folder access also been checked.
(BOB member since 2007-04-16)
(BOB member since 2007-09-17)
(BOB member since 2003-10-16)
(BOB member since 2007-07-04)