1 (ADF) CLONE-32000 to CLONE-33700

CLONE-32000: No ADF Connection MBeans were detected in the source domain, and therefore no ADF Connection information will be included in the moveplan.xml.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Other

CLONE-32010: 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-32020: 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-32030: ADF Connection MBean {0}.isEditable() return false, no moveplan content generated for this MBean.
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-32040: ADF Connection MBean {0}.isEditable() return false, any updates in source moveplan will not be saved in target domain.
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-32100: 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-32110: No ADF Domain Config MBeans were detected in the source domain, and therefore no ADF domain config information will be included in your move Plan.
Cause: ADF domain does not have ADF domain config MBeans.
Action: Validate that the ADF web application module's web.xml was configured for ADF domain config MBeans or if the application does not have any ADF domain configuration.

Level: 1

Type: TRACE

Impact: Other

CLONE-32500: 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-33000: 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-33010: Start to run T2P ADF Connection Plugins.
Cause: Start to run T2P ADF Connection Plugins.
Action: No Action.

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33020: Finish running T2P ADF Connection Plugins.
Cause: Finish running T2P ADF Connection Plugins.
Action: No Action.

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33100: Starting WLS managed server {0}@{1}:{2}
Cause: Starting WLS managed server.
Action: No Action.

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33200: Stopping WLS managed server {0}@{1}:{2}
Cause: Stopping WLS managed server.
Action: No Action.

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33300: Processing {0} ADF Connection MBean attributes at server {1}
Cause: Processing ADF Connection MBean attributes at server.
Action: No Action.

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33400: 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

CLONE-33500: Successfully saved ADF Connection MBean attributes update for application {0}
Cause: Successfully saved ADF Connection MBean attributes update for application.
Action: No Action.

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33600: No ADF Connection MBean attributes changed for application {0}
Cause: No ADF Connection MBean attributes changed for application.
Action: No Action.

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33700: MBean attribute {0} old value {1} new value {2} changed? {3}
Cause:
Action:

Level: 1

Type: TRACE

Impact: Other