R12.2

[Sri]

Hi,

How are you?

Need favour again.

We are adding a new node to our existing system to meet the demand.In Doc ID 1383621.1,it was updated as below and we need the clarification on below statement.

"Note: Ensure that the port pool provided for the Run Edition File System is different from the port pool of the Patch Edition File System of the primary node. Otherwise, it will result in errors during execution of fs_clone."

Thanks,
Anwar

[ErmanArslansOracleBlog]

It is basically  a restiction of fs_clone on multi-node environments.
You can give any port pools when adding a node and that's why there is a note there.
Consider it..

[ErmanArslansOracleBlog]

As i said, this seems to be an adop restriction.
there are similar bugs in the lower code levels.
Look at this:

In code level AD 7 or lower, ADOP requires unique ports across RUN/PATCH filesystems on all nodes (primary and slave). This is a known issue identified in Bug 24362054 .

This one is different than yours and it has a patch, but I just wanted to show you that , there can be  restricitons like this and maybe in the near future, that restriction may go away, as the one above.
But for now, you need to consider it.

[satish]

Thanks for the update.But in general when adding the node,we will be giving the same ports as they are for primary node right.(for load balancing)

primary portpool
RUN 0
PATCH 1

Secondary
RUN 0
PATCH 1

[ErmanArslansOracleBlog]

You are talking about the Oracle Http Server/the Apache right?
Then you are right..

but, consider what the document says, anyways..