My Oracle Support Banner

ORDeploy Fails to Restart the Server While Re-deploying RMS After Dynamic Hierarchy Changes (Doc ID 2482438.1)

Last updated on DECEMBER 05, 2019

Applies to:

Oracle Retail Merchandising System - Version 16.0.1 and later
Information in this document applies to any platform.


When attempting to re-deploy the RMS after the Dynamic Hierarchy changes, the ORDEPLOY command fails to restart the server as part of its routine.


<PATH_TO_ORPATH>/orpatch/deploy/xml/javaapp_rms.xml:600: The following error occurred while executing this line:
 <PATH_TO_ORPATH>/orpatch/deploy/xml/common/weblogic_scripts/weblogic.xml:1535: Restart server script failed. The following error occurred while executing this line:
<PATH_TO_ORPATH>/orpatch/deploy/xml/common/weblogic_scripts/weblogic.xml:1849: exec returned: 1

 Total time: 2 minutes 23 seconds
 Error while executing!
 Child process 23005 completed with status 1 (errors)
 Error while executing!
 Failure in deploy method!
 Removing: <PATH_TO_ORPATH>/orpatch/logs/ordeploy_restart.state
 ordeploy session complete

The issue can be reproduced at will with the following steps:

1. As part of the Dynamic Hierarchy changes, re-deploy the RMS application.
2. Run the script "ordeploy -a RMS -t JAVA"
3. This command should stop and start the Managed-Server as part of its routine.
4. However, the command does not stop the server.
4a. Stop the server manually.
5. Notice that the command fails to restart the server.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.