ADOP fs_clone failing with ERROR: Managed Server's are not in sync between file system context and DB context
adop fs_clone failing with below error.
+++++++++++++++++++++++++
configProperty id = Server11
Count for NodeIterator nextNode = 3
ERROR: Managed Server's are not in sync between file system context and DB context
ERROR: Update Moveplan Fail
START: Inside exitClone....
Updating status INCOMPLETE for ApplywlsTechStack
START: Updating status INCOMPLETE for action ApplywlsTechStack
END: Updated status INCOMPLETE for action ApplywlsTechStack
SOLUTION
Please follow the solution in Doc ID 2232990.1 and advise accordingly
To resolve the issue test the following steps in a development instance and then migrate accordingly:
1. Unlock the configuration in the weblogic console via the following steps:
A. Open a browser and enter the weblogic console URL eg: https ://localhost:port/console as the administrator.
B. Navigate to the weblogic server administration Applications Configuration console.
C. Unlock the weblogic server configuration by clicking 'Release Configuration' option.
D. If the Configuration is not locked, you can also attempt to lock and then release the configuration.
2. Run fs_clone again using the force option.
>adop phase=fs_clone force=yes
To resolve the issue test the following steps in a development instance and then migrate accordingly:
1. Unlock the configuration in the weblogic console via the following steps:
A. Open a browser and enter the weblogic console URL eg: https ://localhost:port/console as the administrator.
B. Navigate to the weblogic server administration Applications Configuration console.
C. Unlock the weblogic server configuration by clicking 'Release Configuration' option.
D. If the Configuration is not locked, you can also attempt to lock and then release the configuration.
2. Run fs_clone again using the force option.
>adop phase=fs_clone force=yes
Comments
Post a Comment