ADOP Prepare Phase is running long
Root cause of FS_CLONE failure:
===============================
Checked the
FS_CLONE log files. FS_CLONE is failing on 3 nodes apdba07, apdba08, apdba09
during port validation.
This is happening
because the OAEA Managed Servers are wrongly configured.
Node Name FS1 -
OAEA Port FS2 - OAEA Port
---------
--------------- ---------------
apdba02 6811 6801
apdba07 6821 6811
<-----
apdba08 6821 6811
<-----
apdba09 6821 6811
<-----
apdba14 ---- ----
apdba15 ---- ----
apdba22 6811 6801
apdba23 6811 6801
Ports 6801 and
6811 are used on apdba02, apdba22 and apdba23
Ports 6811 and
6821 are used on apdba07, apdba08 and apdba09
6811 port is used
on PATCH on some nodes and on RUN on some nodes which is causing the issue.
You need to
re-create the OAEA managed servers on apdba07, apdba08 and apdba09 so that all
of them are in SYNC.
Action Plan:
- Delete the OAEA Managed
Servers on apdba07, apdba08 and apdba09
- Correct the OAEA
Managed Servers ports (6811 --> 6801) in RUN file System of apdba07, apdba08
and apdba09
- Execute
AutoConfig on apdba07, apdba08 and apdba09
- Correct the OAEA
Managed Servers ports (6821 --> 6811) in PATCH file System of apdba07, apdba08
and apdba09
- Upload the
context file using below command:
java -cp
$CLASSPATH oracle.apps.ad.autoconfig.oam.CtxSynchronizer action=upload contextfile=<PATCH
CONTEXT FILE PATH>
- Create the OAEA
Managed Servers on apdba07, apdba08 and apdba09
- Run FS_CLONE
using below command
adop
phase=fs_clone force=yes
Subscribe to:
Post Comments
(
Atom
)
No comments :
Post a Comment
Note: only a member of this blog may post a comment.