My Oracle Support Banner

Can't Start Part of The ISP Node Services After Cloning (Doc ID 2482464.1)

Last updated on JUNE 18, 2019

Applies to:

Oracle Applications Manager - Version 12.2 and later
Information in this document applies to any platform.

Symptoms

On : 12.2, Rapidclone

When attempting to start a new cloned ISP node,
the following error occurs.

ERROR
-----------------------

ERROR: Skipping startup of <DOMAIN_NAME> since the AdminServer is down. AdminServer needs to be up before starting/stopping the managed servers.

ERROR: Skipping startup of <HOST> since the AdminServer is down. AdminServer needs to be up before starting/stopping the managed servers.

ERROR: Skipping startup of <HOST> since the AdminServer is down. AdminServer needs to be up before starting/stopping the managed servers.

ERROR: Skipping startup of <HOST> since the AdminServer is down. AdminServer needs to be up before starting/stopping the managed servers.

ERROR: Skipping startup of <HOST> since the AdminServer is down. AdminServer needs to be up before starting/stopping the managed servers.

adstrtal.sh: Exiting with status 1


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Start the application of the ISP node.

Changes

This is a new cloned instance and customer is adding the ISP node. They changed the ISP context file

<wls_admin_host oa_var="s_wls_admin_host">PRIMARY_NODE</wls_admin_host>

 

Cause

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
Symptoms
Changes
Cause
Solution


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