Re: Adop Prepare Has Failed With adclone.pl Error

Posted by Berke on
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/Adop-Prepare-Has-Failed-With-adclone-pl-Error-tp292p296.html

Hello Erman,

When I ran your command, it started like the the log below. However when I ran the adop phase=prepare while the adadminsrvctl was started forcefully in the patch fs, I see the following error.
-----
04/28/15-16:13:08 :: adadminsrvctl.sh version 120.10.12020000.9
04/28/15-16:29:18 :: adadminsrvctl.sh version 120.10.12020000.9
Validated the passed arguments for the option ebs-get-serverstatus
AdminServer is currently not running.

Validated the passed arguments for the option ebs-nmstart-adminsrv
Checking if the Admin Server is already up.
The Admin Server is not already up.
Checking if the Node Manager is already up..
Traceback (innermost last):
  File "<string>", line 1, in ?
  File "<iostream>", line 123, in nmConnect
  File "<iostream>", line 653, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Unexpected end of stream
Use dumpStack() to view the full stacktrace

Connecting to Node Manager ...

ERROR: Cannot connect to Node Manager. Check if port 5557 is correct
ERROR: Unable to connect to the Node Manager. The Admin Server cannot be started up.
Successfully disconnected from Node Manager.


04/28/15-16:29:29 :: adadminsrvctl.sh: exiting with status 1
--

Do you think that it might be due to the faulty run of the adop syncronization(patch fs creation step) that is run while adop prepare phase?

Should I run with an option like skipsyncerror?