Post Migration Issue

Hi all,

We are facing an issue post migration from TS 6.1 to TS 6.7. Actually we have some programs which executes iwcmp programatically and after migration when we ran the same and getting results as f+ for source and f+ for target as well, which is a conflict as per our business requirements.

Overview of migration we did:
1. Submit and published all workareas
2. Create the backing store.
3. Migrate the backing store
4. Re-create the workareas with original name, we had earllier (instead of temp_workarea)

Can anyone provide any pointer / suggestion / resolution as how to get rid of f+ status from both as there is no difference in the file. It comes in to picture only after step 4 of migration.

Thanks in advance. Much appreciated.

Find more posts tagged with

Comments

chicka

Could you please clear my doubt. Are you referring f+ as the working version???

kaalraa

Could you please clear my doubt. Are you referring f+ as the working version???

Try running iwcmp command and you will get to know the status. Also for more info read the manuals, please.

Pawan

Could you please clear my doubt. Are you referring f+ as the working version???

This is not any working version, this is the result of the iwcmp comparison for the files.
The issue which Kaalraa has mentioned seems worth checking, may be checking all the attributes of the conflicting files may help in tracking the real cause.

Adam Stoller

Hi all,

We are facing an issue post migration from TS 6.1 to TS 6.7. Actually we have some programs which executes iwcmp programatically and after migration when we ran the same and getting results as f+ for source and f+ for target as well, which is a conflict as per our business requirements.

Overview of migration we did:
1. Submit and published all workareas
2. Create the backing store.
3. Migrate the backing store
4. Re-create the workareas with original name, we had earllier (instead of temp_workarea)

Can anyone provide any pointer / suggestion / resolution as how to get rid of f+ status from both as there is no difference in the file. It comes in to picture only after step 4 of migration.

Thanks in advance. Much appreciated.

Are you re-creating the workareas - or re-naming the temp_workarea?
If the latter - don't! That's intended for maintaining state in between runs of iwmigrate (incremental updates and such) and should not be used as a real workarea. If you're done migrating, remove it and create a new one.

Whether or not the above has anything to do with the issues you are seeing - I don't know.

You did not indicate what areas you are using as parameters for iwcmp - that might help shed some light on the issue.

kaalraa

Thanks for a reply, Adam!!

Are you re-creating the workareas - or re-naming the temp_workarea?
If the latter - don't! That's intended for maintaining state in between runs of iwmigrate (incremental updates and such) and should not be used as a real workarea. If you're done migrating, remove it and create a new one.
Whether or not the above has anything to do with the issues you are seeing - I don't know.

We are creating new workareas using the last edition. Not touching temp_workarea at all.

You did not indicate what areas you are using as parameters for iwcmp - that might help shed some light on the issue.

We are not comparing the workareas, however we are using iwcmp for each and every file, chosen by the user from the workarea of 2 different branches with same work area content.

/iw-home/bin/iwcmp "/default/main/BRANCH_1/WORKAREA/filename" "/default/main/BRANCH_2/WORKAREA/filename"

In the above representation, filename is similar in both branches.

Adam Stoller

Thanks for a reply, Adam!!
We are creating new workareas using the last edition. Not touching temp_workarea at all.
We are not comparing the workareas, however we are using iwcmp for each and every file, chosen by the user from the workarea of 2 different branches with same work area content.

/iw-home/bin/iwcmp "/default/main/BRANCH_1/WORKAREA/filename" "/default/main/BRANCH_2/WORKAREA/filename"

In the above representation, filename is similar in both branches.

The files in two different workareas on two different branches are bound to be different - plus if you're comparing files in workareas - if the files are submitted, they'll both be indicated as modified.

If you're on Unix - I suggest you use

diff -w -r /iwmnt/default/main/branch_1/WORKAREA/wa_name_1 /iwmnt/default/main/branch_2/WORKAREA/wa_name_2

you'll get much better results in terms of differences.

If you just want to spot-check certain files - then:

diff -w /iwmnt/default/main/branch_1/WORKAREA/wa_name_1/path-to-file /iwmnt/default/main/branch_2/WORKAREA/wa_name_2/path-to-file

If you're on Windows (or can map a drive to your //IWSERVER share from your Windows desktop) - you might look into Beyond Compare or similar