since updating from SAP BODS 4.0 to SAP DS 4.2 SP02 (14.2.2.446) we are experiencing massive and continuous problems with our (non-secure) central repository.
First of all most of the time it is not shown in designer anymore by which local repository an object is checked out (see screenshot). This is especially very annoying since we are quite a number of people (>10) working on the same objects and therefore have to ask everybody to checkin each time someone wants checkout an object which is already checked out by someone else.
Secondly, which is also quite confusing, for some objects the central repository is shown as the checkout repository
After the update the overall performance during checkin/checkout/get latest version of objects has dramatically decreased. It now takes at least 3-4 times longer to conduct these actions than before the update.
Since we are such a large group of people in the project we are very dependent on a correct and fast working central repository and thefore would be very thankful for any advise.
Yes, this is the annoying thing even if it will be a 3 person team :(. You cannot keep going to 2 others in team and ask “Can you check them in…?” either one is going to yell at us telling I have not! There was a known bug, but I had stopped tracking of it as write a piece of query to produce a “Checked Out Object - Report”
This was a known issue I had faced in 4.1 SP1 and we had to upgrade our client install to 4.1 SP3. The check-out/check-in will be superfast. But now I fear this just got sneaked in again. There will be a topic for this in BOB I have posted a SAP Note Number I suppose. Central Repo - Updating Dependency Info
My SAP Incident says ADAPT01703084 was for Central Repo Performance when you will have upgraded. Actually, I had tested a process by creating a new Central Repo and had reported that the performance isn’t that bad. They say, it is fixed in 4.2 SP1. I additionally followed a note 1798375 - Best Practices for Data Services Designer and Central repository and it has certain index definition.
@Jim: What exactly do you mean by an “in-place upgrade”? The incremental update didn’t work so we had to complety deinstall the old version of IPS/DS and install the new version by using the full install packages for IPS and DS.
@Ganesh:
You wrote to 1.) that this is a known bug. Do you know if there already exists an Incidient No. for it?
Regarding 3): We will try the steps mentioned in the SAP note but it really feels like as there is something going wrong when the designer is accessing the Central Repo DB. Since you said it actually was fixed in an earlier upgrade the newest upgrade to SP2 is actually more a downgrade from that perspective. :-/ We will open an incident for it.
[quote:221ba33567=“Jan-P”]@Jim: What exactly do you mean by an “in-place upgrade”? The incremental update didn’t work so we had to complety deinstall the old version of IPS/DS and install the new version by using the full install packages for IPS and DS.
[/quote]
I think that’s the problem. When you deinstalled the old version you may have lost information about users.
An in-place upgrade would have left all the existing software and repositories (especially the repository used by IPS ) there so they could still be used.
(BOB member since 2011-07-18)
(BOB member since 2007-01-10)
(BOB member since 2011-07-18)
(BOB member since 2014-07-10)