question on clone

classic Classic list List threaded Threaded
7 messages Options
Sri
Reply | Threaded
Open this post in threaded view
|

question on clone

Sri
Hi Erman,

Today we faced an issue while cloning from prod to test instance.

in prod we have run port pool as 10 and patch port pool as 7
in test we ran adcfgclone with run port pool as 11 and patch as 17

But adcfgclone failed with attached error.we have ran adcfgclone again with run port pool as 0 and patch as 17 and this time it completed successfully

From notes,it was as below

This problem is happening due to very less port pool difference chosen between source and target instance and there are multiple same type of managed server exist on source. But i wanted to know where exactly we get the issue while running adcfgclone on target if the selected port pool is less

Thank you for your support
Sri
Reply | Threaded
Open this post in threaded view
|

Re: question on clone

Sri
Reply | Threaded
Open this post in threaded view
|

Re: question on clone

ErmanArslansOracleBlog
Administrator
Did you check this note?

12.2 Creating New WLS Domain Fails On Adcfgclone.pl With "oracle.as.t2p.exceptions.FMWT2PPasteConfigException: PasteConfig failed. Make sure that the move plan and the values specified in moveplan are correct." (Doc ID 2215729.1)

Read the cause and the solution.
Sri
Reply | Threaded
Open this post in threaded view
|

Re: question on clone

Sri
Thanks erman for your timely help.our issue was fixed with running adcfgclone with higher port pool
Sri
Reply | Threaded
Open this post in threaded view
|

Re: question on clone

Sri
Erman,

can you give some idea why it was failing when we choose lesser port range

Thanks
Reply | Threaded
Open this post in threaded view
|

Re: question on clone

ErmanArslansOracleBlog
Administrator
As the note that I sent you, suggests;

The problem is resolved by running a adcfgclone.pl with a correct port pool value, which is higher range than SOURCE instance.

The note also gives you the cause:

Here -> "the port value that you give for a managed server of yours was not within the correct port pool range." It may be the case where the port may already be assigned to another tier on the source or target.

The note also gives you the related bug number ( Bug 22840524. ).

I believe it is related with the port ranges defined in context files.
The port number you use for a managed server is somehow not aligned with the port range defined for that managed server.

Check your context files with that in mind..


Sri
Reply | Threaded
Open this post in threaded view
|

Re: question on clone

Sri
Thanks erman,you are right.Port which we gave in target is in source as well