Removing broken parent associations for pages

Hi

I localized a site and I got broken parent association for pages.
i.e. It is expecting a DCR for a component which no longer exists.

Is there a way to remove broken associations? I have uploaded the related files report for the page which shows a broken parent association.

Find more posts tagged with

Comments

Pawan

I know this is a year old post but I have bumped into this problem and looking for solution. Anyone can shed some light here would be great.

My problem is with dcr files, they throw an error on save.

TS 7.2
RHEL

Rick Poulin

In 7.2.0, you can't save anything with a broken dependency. You need to recreate a dummy file with the same name to 'unbreak' the dependency, then save your file so the dependency is removed, then delete the dummy file. This is fixed in 7.2.1 or 7.2.1 sp1, can't remember which.

Pawan

In 7.2.0, you can't save anything with a broken dependency. You need to recreate a dummy file with the same name to 'unbreak' the dependency, then save your file so the dependency is removed, then delete the dummy file. This is fixed in 7.2.1 or 7.2.1 sp1, can't remember which.

Thanks for the workaround, however, it didn't work in my case as the broken dependency is showing a non-existing edition path and doesn't delete it even creating a new file. The new file with same name shows valid dependency however, the renamed one shows both the valid as well as the broken dependency.

Attaching the dependency image

Adam Stoller

Thanks for the workaround, however, it didn't work in my case as the broken dependency is showing a non-existing edition path and doesn't delete it even creating a new file. The new file with same name shows valid dependency however, the renamed one shows both the valid as well as the broken dependency.

Attaching the dependency image

Just to make sure (I believe you know this well enough, but ...) - edition names that begin with a '#' are "hidden" editions - and will not show up when you list the contents of the EDITION directory on the file system interface or when you ask to list editions within the TeamSite UI.

You should be able to list the contents of that edition in the command line (but you won't be able to use path completion) - e.g.: /bin/ls /default/main/mybranch/EDITION/#38282

You should also be able to verify if the hidden edition exists by doing something like this (also from the command line): iwlist -k /default/main/mybranch/EDITION | grep 38282

You want to make sure that the issue is that the edition isn't there - because it's possible that it is there and the issue is something else.

Rick Poulin

Whether the edition exists or not won't help you here, because you can't go creating a temp file in an edition anyway. What I've done in the past for things like this is to write a simple Java servlet that allows you to remove dependencies like this. That's really the only option, since there aren't any CLTs to work with the dependency manager.

Pawan

Whether the edition exists or not won't help you here, because you can't go creating a temp file in an edition anyway. What I've done in the past for things like this is to write a simple Java servlet that allows you to remove dependencies like this. That's really the only option, since there aren't any CLTs to work with the dependency manager.

Support responded to me asking to use the CLT iwdepfixup, but I couldn't find this CLT in TS7.2, can anyone please check and confirm whether this CLT is present in TS7.2.1 SP1 or later.

Pawan

....You should also be able to verify if the hidden edition exists by doing something like this (also from the command line): iwlist -k /default/main/mybranch/EDITION | grep 38282

You want to make sure that the issue is that the edition isn't there - because it's possible that it is there and the issue is something else.

Thanks Adam.

The edition isin't there inside the new sub-branch, the new sub-branch has only 3 hidden editions as of now. The missing edition which shows as the broken dependency is in the parent branch where this file originally exists.

My understanding on the hidden editions is they are created to keep track of the delta and should be deleted once a real edition is created and merge all the changes into this new edition. I see huge number of hidden editions existing in one of the most active branch in TeamSite.

Can anyone please let me know what should be the normal value for number of hidden editions under a branch.

nipper

Support responded to me asking to use the CLT iwdepfixup, but I couldn't find this CLT in TS7.2, can anyone please check and confirm whether this CLT is present in TS7.2.1 SP1 or later.

Not on 7.2.1 on RHEL either. There is not a SP1 but there is a major patch for 721. Having fought with that recently I am pretty certain it is on on the patch either.

But I do see it on 731, both as an exe and as a bat file (which is quite helpful on Linux I might add). Smiley Very Happy

nipper

Thanks Adam.

Can anyone please let me know what should be the normal value for number of hidden editions under a branch.

Hidden Editions are created for each submit, so 10s of thousands is not uncommon. I have also never deleted a hidden edition, not certain if you can, besides running iw_migrate

Pawan

Hidden Editions are created for each submit, so 10s of thousands is not uncommon. I have also never deleted a hidden edition, not certain if you can, besides running iw_migrate

Thanks Andy.
I was worried as I have over 100s of thousands of hidden edition and increasing as a faster rate. Not sure if that has anything to do with the performance of TeamSite in general and submit operations in specifc. I am still waiting on support to provide me a workaround until we upgrade to TS7.3.1 or later.

Adam Stoller

Thanks Andy.
I was worried as I have over 100s of thousands of hidden edition and increasing as a faster rate. Not sure if that has anything to do with the performance of TeamSite in general and submit operations in specifc. I am still waiting on support to provide me a workaround until we upgrade to TS7.3.1 or later.

The number of editions on a branch has not been the source for performance problems since before TeamSite 5.5.2 - so I wouldn't worry too much about that (and if member serves correctly, it was sometime after 5.5.2 - perhaps 6.7x? - when submit operations started getting recorded as hidden editions specifically because they had done away with the performance issues from have large numbers of editions on a branch)