nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iwcmp across different stores?

mart2001

Hi,

Env: Teamsite 6.7.2, SP2
Windows 2003 EE Server

I am wondering if iwcmp work across different content stores or does it work only on the same content store?

After running iwmigrate from a 6.5 content store and created a a new 6.7.2 content store, I want to make sure that the files are copied over correctly.

When I try to run the following command:

iwcmp y:\default\main\branch1\WORKAREA\work1 y:\672new\main\branch1\WORKAREA\work1

I get the following error message:
Error locating area 2.

Should I use a third party tool to compare the directories and files in default and 672new?

Find more posts tagged with

Comments

Adam Stoller

Hi,

Env: Teamsite 6.7.2, SP2
Windows 2003 EE Server

I am wondering if iwcmp work across different content stores or does it work only on the same content store?

After running iwmigrate from a 6.5 content store and created a a new 6.7.2 content store, I want to make sure that the files are copied over correctly.

When I try to run the following command:

iwcmp y:\default\main\branch1\WORKAREA\work1 y:\672new\main\branch1\WORKAREA\work1

I get the following error message:
Error locating area 2.

Should I use a third party tool to compare the directories and files in default and 672new?

Contact Support and ask them about the Feature Request that was filed in regards to case number 705880. It was my case, and they supposedly opened an FR for it, but I was never provided the FR# (which seems to be SOP for Autonomy, judging by the 7.0 Release Notes).

The response I got was that despite the documentation not saying anything about such a limitation, that it was the way the CLT was designed so making it work across stores would be an enhancement.

A 3rd party tool (like diff on Unix or Beyond Compare on Windows) will give you much of the same information, eventually, but won't be able to tell you about differences in terms of files being marked private (which is what I was trying to achieve at the time)

mart2001

Thanks Fish. I ended up writing a simple and quick perl script to compare the files between the two directories.

mart2001

Quick might not be the correct adjective... Using Dirwalk or File::Find going through 46 gigs of the content store is anything, but quick....

Adam Stoller

Quick might not be the correct adjective... Using Dirwalk or File::Find going through 46 gigs of the content store is anything, but quick....

Is your TS server Windows or Unix?
Are you just trying to get a list of files that differ (either orphaned or actually differ) - or do you want a complete listing of the line-by-line differences in those files that differ?

On Unix - I'd recommend using the diff utility (perhaps gnu-diff / gdiff if available).

On Windows (or Unix) - I'd recommend checking out Beyond Compare

I'm curious though, how did you code your comparison routine? Traversing 46 gigs is going to take some time regardless, but there are both good and bad ways to perform the comparison - especially depending on what you are looking to achieve as an end-result.

Did you make sure that you only compared files in staging and avoid traversing through workareas and editions? If not, that kind of thing could make a big difference in the amount of time it takes to perform the operation.

piechart.rptdesign

mart2001

I was going through all the workareas, STAGING, and EDITION.... That's probably why it is taking so long. This is on a Windows system. I was only comparing if the file exist in the old store and exist on the new store, and if the sizes are the same or different.

Adam Stoller

I was going through all the workareas, STAGING, and EDITION.... That's probably why it is taking so long. This is on a Windows system. I was only comparing if the file exist in the old store and exist on the new store, and if the sizes are the same or different.

Okay - well, fix your code to only examine STAGING and skip EDITION and WORKAREA directory traversal - and that should help immensely.

Are you doing one-by-one comparisons or storing information in a hash and then comparing the contents of the hash?

mart2001

One by one comparison and just prints to stdout... Then redirect it to a file.

If there is a file in STAGING on the old store, and the file does not exist in STAGING in the new store, what would be the reason?

When I looked at the latest EDITION, I can see that the file does not exist on the new and old store. Would that be the reason?

Adam Stoller

One by one comparison and just prints to stdout... Then redirect it to a file.

If there is a file in STAGING on the old store, and the file does not exist in STAGING in the new store, what would be the reason?

When I looked at the latest EDITION, I can see that the file does not exist on the new and old store. Would that be the reason?

That sounds right, but I'm a little short of gray-cells right now to really consider it in detail - sorry.