Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 1 (11.1.1)

Part Number E10113-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

23 CLONE-27010 to CLONE-28400

CLONE-27010: One or more ADF Connection types for {0} are not supported and will not be included in the moveplan.xml.
Cause: One or more ADF Connection MBean does not provide the movableProperty annotation for at least one attribute.
Action: Validate that all ADF Connection MBean in your application have at least one property with movableProperty annotation with a value of "true".

Level: 1

Type: WARNING

Impact: Other

CLONE-27020: ADF Connection MBean {0}.{1} is read only. Changes for this ADF Connection will not be applied.
Cause: The ADF Connection MBean is read only.
Action: Validate that your application is configured with a writable Oracle MDS.

Level: 1

Type: WARNING

Impact: Other

CLONE-27100: Application {0} does not have ADF Connection MBean properties.
Cause: Application {0} does not have ADF Connection MBeans.
Action: Validate that the ADF web application module's web.xml was configured for ADF Connection MBeans or if the application does not have any ADF Connections.

Level: 1

Type: WARNING

Impact: Other

CLONE-27500: No Move Plan available.
Cause: Either ADF T2P plugin copy command failed, or the file is missing or corrupted.
Action: Validate that the Move Plan is valid after extraction from the copy command result.

Level: 1

Type: WARNING

Impact: Other

CLONE-28000: Unable to apply ADF Connection properties for Application "{0}"
Cause: This could be caused by an invalid Oracle MDS configuration in your application or a failure while attempting to apply attributes using JMX.
Action: Please validate that the application is configured with writable Oracle MDS.

Level: 1

Type: ERROR

Impact: Other

CLONE-28400: No ADF Connectioin MBean with name {0}
Cause: OBJECT_NAME_PROPERTY field for mbean object name might be changed accidently.
Action: Use the value of OBJECT_NAME_PROPERTY from other attributes under the same ADF Connection MBean in Move Plan to correct the wrong one.

Level: 1

Type: WARNING

Impact: Other