Catalogue Copy problem - Urgent help required

Hi I am copying piping catalogues (basically 2 cata elements) from one DB to another DB using the Catalog copy utility.

I am keeping the same name and not adding any prefixes to the copied elements.

However after copying is completed I have notice that the PTREF, GMREF etc for all the SCOM elements is undefined and error appears on opening MODIFY->Category regarding undefined reference.

What could be the problem? Why references do not get automatically set after copying?

Is there any other way apart from DB Listing to copy CATA & SPWL from one DB to another DB?

PTREF and GMREF is kept in other place in the hierarchy.

Find PTREF and GMREF hierarchy from existing catalogue and copy these also into the destination.

Then Ref will fix automatically.

Yes they are under different CATAs but I am copying both the CATAs to the new DB. So all PTSE, GMSE and related CATE, SCOM are present in the new DB after copying.

That is why I am not able to understand why is this happening?

[QUOTE=pratikkr;111734]Yes they are under different CATAs but I am copying both the CATAs to the new DB. So all PTSE, GMSE and related CATE, SCOM are present in the new DB after copying.

That is why I am not able to understand why is this happening?

First you copy REF Elements, which is independent i.e. elements which doesn't have any ref.
Later you copy dependent elements which have some ref.

First GMSE PTSE
LATER CATE

Yes it should be done in order and this time I carefully followed the sequence. First I copied CATA containing PTSE & GMSE etc. then I copied CATA containing SCOMs. Till this step everything was fine.

Then I copied SPWL and when I checked the CATREFs in the SPECs they were all pointing to the SCOMs in the original database and not the copied database.

If I remove the original foreign databases then the SPEC references turn to nulref. Why is this happening?

Ref numbers issue,we need to link SPCO SCOM ref with ref number from Copied database.

Do you mean we have to manually again set the references?

Do you mean we have to manually again set the references?

Through reports we can achieve this.

Yes, but is this a normal procedure to do this thing?

What I suspect is that in catalog copy utility if you do not copy with prefixes then this problem will occur. Due to same name of elements in two different databases the software gets confused and refers to the original database only.

But again copying with prefixes is not always an option especially in case of specs where you want spec name to be exactly the same.

What procedue do you follow while copying catalogues from some another project to a new project. Do you copy the complete databases or transfer elements to the new database using catalog cppy utility?

[QUOTE=pratikkr;111758]Yes, but is this a normal procedure to do this thing?

What I suspect is that in catalog copy utility if you do not copy with prefixes then this problem will occur. Due to same name of elements in two different databases the software gets confused and refers to the original database only.

But again copying with prefixes is not always an option especially in case of specs where you want spec name to be exactly the same.

What procedue do you follow while copying catalogues from some another project to a new project. Do you copy the complete databases or transfer elements to the new database using catalog cppy utility?

They are two options with copying database from one project to another.

1. Include Foreign
2. Copy Foreign.

E.g My catalogue database is exists with ACP Project, usually ACP Catalogue database update with the project fixes frequently.

1. If you want updates from Fixes for your project also then go for Include Foreign, But changes in catalogue database you should perform in ACP Project Only

2. If you don't want any updates from Fixes then you can go with Copy Foreign, Copy Foreign DB Editable in your project itself.