8 CLONE-20200 to CLONE-92302

CLONE-20200: The clone option or argument is invalid.
Cause: The option or argument "{0}" was not supported by cloning.
Action: Provide a valid option or argument. Use the "-help" option for more information about cloning options and arguments.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20201: The value for the argument is missing.
Cause: The argument "{0}" was provided, but its value was not provided.
Action: Provide the corresponding value.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20202: Oracle Home is invalid.
Cause: This Oracle home was not registered with the OraInventory. Unable to find any Oracle home from the OraInventory.
Action: Provide valid Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20203: Invalid archive location.
Cause: There are six possible causes: 1. Archive path was not provided. 2. Archive path was not an absolute path. 3. Archive path did not exist. 4. Archive path did not point to a file. 5. Archive path did not have read permission. 6. Archive was a zero size file.
Action: Provide the absolute path of a valid archive file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20204: Oracle Home is invalid.
Cause: This Oracle home was not registered with the OraInventory. The Oracle homes registered with the OraInventory were : {0} .
Action: Provide valid Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20205: Oracle Home is invalid.
Cause: This Oracle home was not registered with the OraInventory specified in inventory pointer location file {0}. The Oracle homes registered with that OraInventory were : {1}
Action: Provide valid Oracle Home and make sure that Oracle Home is registered with the OraInventory.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20206: Invalid value for "{0}" option.
Cause: The provided value was not a Boolean value.
Action: Supported Boolean values are "true" or "false".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20210: The archive file is invalid.
Cause: The archive file failed an internal consistency check.
Action: Make sure that the archive file is created using T2P operation.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20218: Cloning is not successful.
Cause: An internal operation failed.
Action: Provide the clone log and error file for investigation.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20219: Clone type is invalid.
Cause: Clone type was either empty or not supported.
Action: The clone type is either "{0}" or "{1}" or "{2}".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20220: Parameters are missing.
Cause: Either archiveLocation or cloneType was empty. The values provided were archiveLocation : "{0}" cloneType : "{1}".
Action: Make sure that the correct values are provided.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20221: Invalid clone type.
Cause: The clone type "{0}" did not match "{1}" or "{2}".
Action: The clone type should be either "{0}" or "{1}".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20222: Parameters validation has failed.
Cause: Primary parameters validation for "{0}" failed.
Action: Check the clone log and error file and provide correct value.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20223: Invalid Oracle Home.
Cause: There are four possible causes for an invalid Oracle Home "{0}": 1. It did not exist. 2. It was an empty directory. 3. It had invalid inventory pointer file (if operating system is other than Windows). 4. It had no top component or invalid top component version.
Action: Provide a valid Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20225: Some configuration files have incorrect entry.
Cause: Following files have still reference to source Oracle Home {0} {1}
Action: Update those files with target Oracle Home path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20227: Error in validating T2P binary..
Cause: T2P binary had been compromised.
Action: Make sure that the T2P binaries are valid. Check the T2P documentation for more information.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20228: Error in validating archive file.
Cause: Unable to find internal version pertaining to T2P operation from the archive.
Action: Make sure that archive file is valid and correct T2P binaries are used during copy and paste operation.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20229: Error in validating archive file.
Cause: Archive file had been compromised.
Action: Make sure that the archive file is valid. Check the T2P documentation for more information.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20230: Primary validation prior to clone operation has failed for {0}.
Cause: Parameter(s) were missing or some validation(s) failed.
Action: Check the clone log and error file for information about which parameter is missing or why validation failed.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20231: Error in validating archive file.
Cause: The version of of archive file and T2P binary were "{0}" and "{1}" respectively. The possible causes were: 1. The major version was mismatched. 2. The minor version of archive file is higher than the minor version of T2P binary used for paste operation.
Action: Make sure that correct T2P binary is used during copy and paste operation.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20232: Oracle Home configuration has failed.
Cause: Exception occurred while configuring Oracle Home.
Action: Check the installer log and cloneAction log at following location {0} for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20235: Adding "{0}" to the archive has failed.
Cause: An internal operation failed.
Action: Check the clone log and error file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20236: Archive creation has failed.
Cause: An internal operation failed.
Action: Check the clone log and error file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20237: Restoring the sourceid "{0}" has failed.
Cause: An internal operation failed.
Action: Check the clone log for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20239: Invalid archive file.
Cause: Either archive did not have sourceid file, or a sourceid was a zero size file.
Action: Make sure the correct archive file is provided, and check the extracted sourceid file whose path is "{0}".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20240: Invalid archive file.
Cause: Either archive did not have "{0}" file, or archive was not created through copyConfig operation.
Action: Make sure that the correct archive file is provided.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20245: Unable to include permission file to the archive.
Cause: Permission file creation failed.
Action: Check the clone log and error file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20247: Not all file permission operations are successful.
Cause: Some files were missing from the Oracle Home {0}.
Action: Check the clone log file and permission restore log file {0} for more details about the missing files.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20248: Execution of system prerequisites have failed.
Cause: The following system prerequisites failed : {0}.
Action: Check clone log for more details on prerequisites output and result.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20249: Execution of system prerequisites have completed with warnings.
Cause: The following system prerequisites completed with warnings : {0}.
Action: Check clone log for more details on prerequisites output and result.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20250: Execution of system prerequisites has completed without verifying some of the prerequisites.
Cause: The following system prerequisites were not verified : {0}.
Action: Check clone log for more details on prerequisites output and result.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20251: Execution of system prerequisites failed for some or all of the Oracle Homes.
Cause: Some of the system prerequisites were not completed successfully.
Action: Check the clone logs for more details on the prerequisite output and results. Re-execute the pasteBinary command after either fixing the failing prerequisites or by adding the '-executeSysPrereqs false' parameter to the command line.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20252: Invalid T2P action type.
Cause: The provided action type was "{0}". This action type was either empty or unsupported.
Action: The supported action types are "{0}".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20254: Cloning is not possible..
Cause: The Oracle Home {0} did not have supported binaries. The root causes were :{1}.
Action: Make sure that the Oracle has correct binaries.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20255: Cloning is not possible.
Cause: The Oracle Home name {0} provided in -ouiparam argument was already registered with the Oracle Inventory.
Action: Either provide a different inventory location or provide a different Oracle Home name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20256: Unable to capture permission of all the files present under the Oracle Home.
Cause: Some of the files did not have proper permission.
Action: Check clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20261: Invalid Oracle Inventory.
Cause: There are six possible causes for an invalid inventory pointer file "{0}": 1. File did not exist. 2. File did not have read permission. 3. It was a zero size file. 4. File did not have any pointer to OraInventory. 5. Oracle Inventory found from file was not absolute. 6. Oracle Inventory specified in the inventory pointer file did not have write permission.
Action: Provide a valid inventory pointer file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20262: Cloning is not possible.
Cause: The Oracle Home {0} was already registered with the Oracle Inventory.
Action: Either provide a different inventory location or provide a different location for the new Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20263: Invalid Oracle Inventory.
Cause: There are two possible causes for an invalid OraInventory "{0}". 1. Inventory was empty. 2. It did not have valid inventory.xml file.
Action: Provide a valid Oracle Inventory.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20264: Default inventory pointer file is invalid.
Cause: There are six possible causes for an default inventory pointer file "{0}": 1. File did not exist. 2. File did not have read permission. 3. It was a zero size file. 4. File did not have any pointer to OraInventory. 5. Oracle Inventory found from file was not absolute. 6. Oracle Inventory specified in the inventory pointer file did not have write permission.
Action: Ensure that the default inventory pointer file is valid or provide a different, valid inventory Pointer file using the {0} argument.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20265: Invalid argument.
Cause: Either argument was an empty string or "null".
Action: Provide a valid argument.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20266: Loading of OUI and engine jar to system class loader was unsuccessful.
Cause: The possible causes are : {0}
Action: Check clone log and error file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20269: Setting Java library path has failed.
Cause: There are four possible causes: 1. The OUI library path {0} was empty. 2. Unable to find OUI library directory name. 3. The oraInstaller library path {1} was empty. 4. The oraInstaller library path {1} was corrupted.
Action: Make sure that OUI and the oraInstaller library are available.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20271: Invalid characters.
Cause: Command-line input {0} had some unsupported characters.
Action: Supported characters are "{0}" but these three characters "_.-" are not allowed in the beginning of a string.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20272: Invalid path.
Cause: Path "{0}" was either not absolute or did not have valid characters.
Action: Supported characters are "{0}" but these three characters "_.-" are not allowed in the beginning of a string.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20275: Insufficient space to create {0}.
Cause: Minimum required space was at least "{0}" MB, but only "{1}" MB was available for use.
Action: Make sure that the minimum required space is available for use.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20276: Extracting is unsuccessful.
Cause: Either there was no space available or no write permission.
Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20277: Some files are missing.
Cause: After configuration, some files were removed.
Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20278: Oracle Home configuration is unsuccessful.
Cause: Some symbolic link(s) were either mismatching or were not present.
Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20279: Some of the files present under Oracle Home did not have proper permission.
Cause: Some of the files did not have proper permission.
Action: Check the file {0} which has expected and actual permission. Then update permission of those files.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20280: Oracle Home is not cloneable.
Cause: Some component(s) under the Oracle Home {0} were not cloneable.
Action: Make sure that all components in the Oracle Home are cloneable.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20293: Oracle Home configuration is unsuccessful.
Cause: The OraInventory {0} from invPtrLoc file {1} did not match with OraInventory {2} from reference invPtrLoc file {3}.
Action: Check the clone log file and install CloneAction file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20294: Oracle Home configuration is unsuccessful.
Cause: Unable to find Oracle Home name from the inventory.xml file.
Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20299: Oracle Home configuration is unsuccessful.
Cause: Some "no read permission" files were not present.
Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20305: Extracting is unsuccessful.
Cause: Some files were missing.
Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20318: Missing argument: {0}.
Cause: Required argument was not provided at command line or in the argument file.
Action: Provide a valid argument.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20324: Unsupported character sequence.
Cause: Input value "{0}" had some unsupported characters.
Action: Name must begin with an alphanumeric character; may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters; and must be 4 to 30 characters long.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20327: Invalid password file.
Cause: The {0} password file {1} did not exist or first line did not contain password.
Action: Provide a valid password file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20328: Invalid domain port.
Cause: The domain port was invalid.
Action: Provide a valid port.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20334: Invalid Domain home location.
Cause: Path "{0}" was not writable.
Action: Provide valid absolute writable path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20336: The move plan location is invalid.
Cause: There are three possible causes: 1. The path was not provided. 2. The move plan was not readable. 3. The path was not an absolute path.
Action: Provide a valid absolute path for the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20337: Unable to persist the move plan.
Cause: Make sure that the move plan location is writable. {0}
Action: Check the logs for details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20338: Error in examining Adapters.
Cause: Adapter examination failed.
Action: Make sure that all the specified values are correct and the domain configuration is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20341: Error in copyConfig.
Cause: The AdminServer is down.
Action: Make sure that the AdminServer of the specified domain is started.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20342: Error in deploying Adapters.
Cause: Adapter deployment failed.
Action: Make sure that the deployment plan for {0} is valid or that it exists in the archive.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20343: Error in validating "SERVER_CONFIG".
Cause: Specified move plan has more servers than in the source domain.
Action: Make sure that no new servers are added to the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20344: Error in validating "SERVER_CONFIG".
Cause: Specified server {0} does not exist in the source domain.
Action: Make sure that no new servers are added to the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20346: Error in validating "SERVER_CONFIG".
Cause: Specified {0} {1} is not valid.
Action: Make sure that valid port numbers are specified in the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20347: Error in validating "DATASOURCE".
Cause: Specified move plan has more data sources than in the source domain.
Action: Make sure that no new data sources are added to the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20348: Error in validating "DATASOURCE".
Cause: Specified data source {0} does not exist in the source domain.
Action: Make sure that no new data sources are added to the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20349: Error in validating "DATASOURCE".
Cause: Some of the required parameters of data source {0} are missing in the move plan.
Action: Make sure that valid values are provided in the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20350: Error in validating "MACHINE_CONFIG".
Cause: Specified move plan has more machines than in the source domain.
Action: Make sure that no new machines are added to the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20351: Error in validating "MACHINE_CONFIG".
Cause: Specified machine id {0} does not exist in the source move plan.
Action: Make sure that no new machines are added to the move plan and also make sure that "configProperty" id is not modified.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20352: Error in validating "MACHINE_CONFIG".
Cause: Specified port {0} is not valid.
Action: Make sure that valid port numbers are specified in the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20353: Error in exporting metadata.
Cause: MDS Metadata export failed.
Action: Make sure all the servers are started in the specified domain.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20354: Server start failed.
Cause: MDS Metadata import failed. Could not start the server {0}
Action: Make sure that valid values are provided in the move plan and the archive is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20355: Error in importing metadata.
Cause: MDS Metadata import failed.
Action: Make sure that valid values are provided in the move plan and the archive is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20357: Command-line parameters did not match the script.
Cause: The parameters used for this command were invoked by the wrong script.
Action: Use the '-help' option to see the allowed parameters.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20361: Error in executing WebLogic script for configuring adapter and application deployments.
Cause: Either the values specified in the moveplan are not correct or the end points are not configured correctly in adapter or application deployment plans.
Action: Check the t2P logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20362: Connection to AdminServer failed.
Cause: AdminServer start failed. Make sure that AdminServer parameters specified in the move plan are correct.
Action: Check the AdminServer logs.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20363: Adapter deployment failed.
Cause: Adapter redeployment failed. Make sure that all values are specified correctly in the move plans and "READ_ONLY" properties are not changed.
Action: Check the t2p logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20364: OPSS data {0} failed.
Cause: OPSS data migration script execution failed.
Action: Check the t2p logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20365: Error in executing WebLogic script for configuring server, cluster , datasource and authenticator.
Cause: Either the values specified in the move plan are not correct or some "READ_ONLY" properties in the move plans are modified or some internal error happened.
Action: Check the t2p logs for more details. Make sure that values in the move plans are correct.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20366: Domain unpack failed.
Cause: Make sure that values specified are correct.
Action: Check the t2p logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20367: Move plan parsing failed.
Cause: Specified file is not a valid move plan or the move plan is corrupted.
Action: Make sure that the move plan is a valid xml file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20368: Domain pack failed.
Cause: Make sure that values specified are correct.
Action: Check the t2p logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20369: Invalid domain application directory.
Cause: Path "{0}" was not writable.
Action: Provide valid absolute writable path and make sure that the user executing the tool and the owner of the domain home directory is the same, for UNIX.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20370: Invalid domain application directory.
Cause: Directory "{0}" is not empty.
Action: Provide a valid non-existing or an empty directory.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20371: Invalid domain location.
Cause: Directory "{0}" is not empty.
Action: Provide a valid non-existing or an empty directory.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20372: Server port validation failed.
Cause: Ports of following servers - {0} - are not available.
Action: Provide valid free ports.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20373: The system temporary directory is inaccessible.
Cause: The system temporary directory "{0}" did not have write permission.
Action: Make sure that system temporary directory has write permission.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20375: Invalid Oracle Home.
Cause: Required files needed for cloning were not found in the Oracle Home {0}.
Action: Make sure that the Oracle Home has the required files for cloning.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20377: Error in stopping {0} managed server.
Cause: Either the credentials were not correct or the managed server was not running.
Action: Check the server logs for details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20383: Invalid move plan directory location.
Cause: Path {0} was either an empty string or not an absolute path.
Action: Provide an absolute path for the move plan directory.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20384: Mandatory parameter missing.
Cause: Parameter "planDirLoc(pdl)" missing for the extractMovePlan command.
Action: Provide parameter "planDirLoc(pdl)" for the extractMovePlan command.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20385: Error in validating "MACHINE_CONFIG".
Cause: Specified name {0} for machine {1} is not valid.
Action: Provide valid machine name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20386: Oracle Home is not cloneable.
Cause: Install.properties file from Oracle Home {0} did not have correct entries for cloning.
Action: Make sure that the install.properties has correct entries.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20387: Error in validating "CLUSTER_CONFIG".
Cause: Specified move plan had more clusters than in source domain.
Action: Make sure that no new clusters are added to the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20388: Error in validating "CLUSTER_CONFIG".
Cause: Specified cluster {0} did not exist in source move plan.
Action: Make sure that no new clusters are added to the move plan and "READ_ONLY" properties are not changed..

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20389: Error in validating "CLUSTER_CONFIG".
Cause: Specified name {0} for cluster was not valid.
Action: Provide valid machine name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20390: Error in validating "CLUSTER_CONFIG".
Cause: Specified cluster type "{0}" for cluster {1} was not valid.
Action: Valid values are "unicast" and "multicast".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20391: Error in validating "CLUSTER_CONFIG".
Cause: Specified port {0} was not valid.
Action: Make sure that valid port numbers are specified in the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20392: The domain home validation failed.
Cause: The following file {0} did not present under domain home.
Action: Provide a valid domain location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20393: Error in validating command-line parameter "{0}".
Cause: Path {0} was either not absolute or did not exist.
Action: Provide an absolute path for the command-line parameter "{0}"

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20394: Invalid Domain home location.
Cause: Path "{0}" was not absolute or an empty directory.
Action: Provide a valid absolute path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20395: Invalid Domain home location.
Cause: Path "{0}" was not readable.
Action: Provide a valid absolute path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20396: The domain home validation failed.
Cause: An attempt was made to perform T2P of "{0}" domain. The specified domain home "{1}" was not a "{0}" domain.
Action: Provide a valid domain location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20397: Error in validating "RDBMS Security Store".
Cause: RDBMS Security Store was not enabled in source domain
Action: Make sure that no new sections are added to the move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20398: Error in validating "RDBMS Security Store".
Cause: {0} for RDBMS Security Store was not valid.
Action: Provide valid value for {0}.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20399: Unable to determine Oracle Home used by the domain home.
Cause: Oracle Home information was missing in "{0}" file present under domain home.
Action: Make sue that the specified domain home is associated with a valid Oracle home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20400: Source Oracle Home location validation failed.
Cause: The source Oracle Home "{0}" is not matching with the Oracle Home "{1}" used by the domain home "{2}" .
Action: Provide the Oracle home specified in "{0}" file present under domain home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20402: The move plan file is invalid.
Cause: The xml file was not a valid multi archive moveplan.
Action: Provide a valid xml file for multi archive moveplan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20403: Unable to complete application deployment plan export.
Cause: Error in examining applications for custom deployment plan.
Action: Check logs for details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20404: Error in deploying applications with custom deployment plan.
Cause: Application deployment failed.
Action: Make sure that the deployment plan for {0} is valid or exists in archive.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20405: Application deployment failed.
Cause: Application redeployment failed. Make sure that all values are specified correctly in the move plans and "READ_ONLY" properties are not changed.
Action: Check the t2p logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20406: Invalid move plan directory location.
Cause: Path {0} was either an empty string or not an absolute path.
Action: Provide an absolute path for the move plan directory.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20407: Invalid move plan directory location.
Cause: Move plan directory location was empty.
Action: Provide an absolute path for the move plan directory.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20409: OPSS Configuration failed.
Cause: Specified LDAP details were either wrong or LDAP was not running.
Action: Make sure that LDAP details are correct and LDAP is up and running.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20410: The move plan file is invalid.
Cause: The provided file was not a valid xml moveplan file.
Action: Provide a valid xml moveplan file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20412: Insufficient arguments.
Cause: An attempt was made to perform "{0}" operation. No argument was provided from the following supported arguments : "{1}".
Action: Provide valid arguments.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20413: Unsupported command argument(s).
Cause: An attempt was made to perform "{0}" operation. Some of the arguments are not supported by this operation on this OS platform. The supported arguments are: "{1}".
Action: Provide valid arguments.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20414: Unsupported command argument(s).
Cause: An attempt was made to perform "{0}" operation of "{1}". Some of the arguments are not supported by this operation. The supported arguments are :"{2}".
Action: Provide valid arguments.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20415: Insufficient arguments.
Cause: An attempt was made to perform "{0}" operation of "{1}". Following required arguments were missing: "{2}".
Action: Provide required arguments.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20416: Arguments combination is invalid.
Cause: An attempt was made to perform "{0}" operation of "{1}" type.
Action: Provide valid arguments for a particular type.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20417: Insufficient arguments to decide exact operation.
Cause: An attempt was made to perform "{0}" operation. Unable to decide type of operation from provided arguments. The supported arguments for this operation are: "{1}".
Action: Provide valid arguments.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20418: Invalid path.
Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a file. 4. The file did not have read permission. 5. The file size was zero.
Action: Provide a valid path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20419: Invalid path.
Cause: The value provided for argument "{0}" was "{1}". There are six possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a directory. 4. It was an empty directory. 5. The directory represented by the path did not have read permission. 6. If environment is UNIX, the directory represented by the path did not have executable permission.
Action: Provide a valid path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20420: Invalid path.
Cause: The value provided for argument "{0}" was "{1}". There are four possible causes: 1. The path was not an absolute path. 2. The path was already existing. 3. The parent directory did not have write permission. 4. If environment is UNIX, there was no executable permission on the existing directory.
Action: Provide absolute path and make sure that it does not exist and its parent directoy is writable.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20421: Invalid integer value.
Cause: The value provided for argument "{0}" was "{1}" and it was not a valid positive integer.
Action: Provide a valid positive integer.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20422: Invalid boolean value.
Cause: The value provided for argument "{0}" was "{1}" and it was not a boolean value.
Action: Provide either "true" or "false".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20423: Invalid password file.
Cause: The value provided for argument "{0}" was "{1}". There are six possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a file. 4. The file did not have read permission. 5. The file size was zero. 6. The file did not carry first line as password.
Action: Provide a valid password file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20424: Invalid path.
Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path was existing. It was not an empty directory. 3. The path was not existing. Unable to create all the non existing directories. 4. The path was existing. It did not have write permission. 5. If environment is UNIX, there was no executable permission on the existing directory.
Action: Provide absolute path of either a non existing or an existing empty directory and make sure that it is writable

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20425: Archive file is not provided.
Cause: An attempt was made to perform "{0}" operation. Archive file is a mandatory argument.
Action: Provide valid archive file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20426: Archive file is invalid.
Cause: This file was invalid for "{0}" operation. This archive was not created using T2P "{1}" operation.
Action: Provide valid archive file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20427: Oracle Home is invalid.
Cause: An attempt was made to run "{0}" operation of "{1}" domain. The following file {2} did not present under target Oracle Home.
Action: Provide a valid Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20429: Oracle Home is invalid.
Cause: An attempt was made to run "{0}" operation of "{1}". The Oracle Home "{2}" was invalid.
Action: Provide a valid Oracle Home location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20430: Invalid string value.
Cause: The value provided for argument "{0}" was "{1}" and it was not a valid string value.
Action: Provide a non-empty value.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20432: Invalid path.
Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path was existing. It was not a directory. 3. The path was not existing. Unable to create all the directories. 4. The path was existing. It did not have write permission. 5. If environment is UNIX, there was no executable permission on the existing directory.
Action: Provide absolute path of a directory and make sure that it is writable.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20434: Invalid target Oracle home name.
Cause: There are two possible causes for the target Oracle home name {0}:1. Length of the target Oracle home name was {1} and it was either too short or too large.2. target Oracle home name had contained unsupported characters.
Action: Provide valid target Oracle home name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20444: Mismatch between archive file and multi archive moveplan.
Cause: The archive file used during this pasteConfig operation was not provided during execution of extractMovePlan command.
Action: Execute extractMovePlan command again by providing the archive file {0} along with other archive files created during copyConfig process.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20508: Invalid target Node Manager home location.
Cause: Path {0} exists but is not a directory.
Action: Provide an empty or non-existing directory location for the target Node Manager home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20509: Invalid target Node Manager home location.
Cause: Path {0} exists but is not an empty directory.
Action: Provide an empty or non-existing directory location for the target Node Manager home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20510: Move Plan does not contain any domain information.
Cause: Source Node Manager may not have been registered with any domain.
Action: Register source Node Manager with the available domains on the machine and run the t2p utility again.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20511: Unable to retrieve AdminServer Password for domain{0}.
Cause: Either the password file {0} did not exist, or the AdminServer password was empty.
Action: Provide a valid password file for AdminServer Password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20512: Unable to determine AdminServer credentials for domain {0} from Move Plan.
Cause: Either one of AdminServer Listen Address, AdminServer Listen Port, AdminServer User Name or AdminServer Password for domain {0} was not provided in the MovePlan.
Action: Provide valid AdminServer credentials in the Move Plan and run the t2p utility again.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20513: Unable to determine NodeManager credentials for domain {0} from Move Plan.
Cause: Either one of NodeManager User Name or NodeManager Password for domain {0} was not provided in the MovePlan.
Action: Provide valid NodeManager credentials in the Move Plan and run the t2p utility again.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20514: Unable to retrieve NodeManager Password for domain{0}.
Cause: Either the password file {0} did not exist, or the NodeManager password was empty.
Action: Provide a valid password file for NodeManager Password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20515: Unable to connect to AdminServer for domain(s) {0}.
Cause: The AdminServer for domains(s) {0} was not running.
Action: Bring up the AdminServer for each domain before running the t2p utility.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20516: Error while checking the available port for Node Manager.
Cause: The port {0} was not available for the Node Manager.
Action: Provide an available port for Node Manager in nodemanager.properties.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20517: Error while trying to start the Node Manager.
Cause: Operation timed out while trying to start the Node Manager.
Action: Check the nodemanager.log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20518: Error in trying to read password from file {0} .
Cause: File {0} does not exists.
Action: Provide an existing password file in which the first line is the password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20519: Error in retrieving password from file {0} .
Cause: The first line of file {0} does not contain a valid password.
Action: Provide an existing password file in which the first line is the password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20600: Unable to derive value of all config properties.
Cause: Could not derive values for some properties that had reference to other config properties.
Action: Check clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20601: Unable to derive frontend host.
Cause: The Listen address from OHS was not in proper format.
Action: The frontend host can be updated later from Weblogic console.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20602: Unable to derive frontend port.
Cause: The Listen address from OHS was not in proper format.
Action: The frontend port can be updated later from Weblogic console.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20603: Error in validating "SERVER_CONFIG".
Cause: Specified "{0}" file for server "{1}" was not valid.
Action: Make sure that "{0}" file is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20604: Error in validating command line parameters.
Cause: Some command line arguments may be missing or invalid or the archive provided may not be proper or valid
Action: Make sure that valid values are provided for all the required arguments and the archive is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20605: Invalid target domain directory name.
Cause: Provided target domain directory name "{0}" did not match with source domain directory name "{1}".
Action: Make sure target domain directory name is not changed.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20606: Error in validating source environment.
Cause: Adminserver was down in the provided source environment. The "copyConfig" operation requires adminserver to be up and running.
Action: Make sure that adminserver is up and running.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20607: Error validating source environment.
Cause: Provided source domain is in edit mode.
Action: Activate all unsaved changes in source domain and re-run "copyConfig".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20608: Error reading composites.
Cause: Composite configuration plan "{0}" could not be read.
Action: Make sure that the file exists and has read permission.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20609: Error updating composites.
Cause: Composite configuration plan "{0}" could not be updated.
Action: Make sure that the file exists and has write permission.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20610: Error validating source NodeManager Home.
Cause: Specified source NodeManager Home location is not valid. "nodemanager.properties" file is not present under NodeManager Home location.
Action: Make sure that source NodeManager Home location is correct and all required files are present.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20611: Error validating source NodeManager Home.
Cause: Specified source NodeManager Home location is not valid. "nodemanager.domains" file is not present under NodeManager Home location.
Action: Make sure that source NodeManager Home location is correct and all required files are present.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20612: Error in executing wlst script.
Cause: {0} did not exist.
Action: Make sure that specified Oracle Home is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20613: Listen port validation failed.
Cause: Specified port, {0} is either not valid or not available.
Action: Provide valid free port.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20614: NodeManager listen address validation failed.
Cause: Specified listen address was not configured on a local network interface.
Action: Provide a valid local listen address on which the NodeManager should come up.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20615: Source Oracle home location validation failed.
Cause: Specified domain is not registered with the source Oracle home.
Action: Make sure that specified domain home is registered in "domain-registry.xml" of source Oracle home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20616: Domain credentials validation failed.
Cause: Specified domain credentials were not of the source domain location.
Action: Make sure that specified source domain location and domain credentials are valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20617: Error reading MDM URL Resolver configuration.
Cause: MDM URL Resolver configuration file "{0}" could not be read.
Action: Make sure that the file exists and has read permission.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20618: Error updating MDM URL Resolver configuration.
Cause: MDM URL Resolver configuration file "{0}" could not be updated.
Action: Make sure that the file exists and has write permission.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20619: OPSS re-association failed.
Cause: Execution of reassociateSecurityStore to target environment failed.
Action: Check the T2P logs for details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20620: AdminServer restart failed.
Cause: Could not restart AdminServer.
Action: Check the T2P logs and AdminServer logs for details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20621: Data source creation failed.
Cause: Error in creating OPSS datasource.
Action: Check T2P logs for details. Make sure values provided in moveplan for "OPSS_CONFIG" are correct.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20622: OPSS Store is not migrated.
Cause: OPSS store is not migrated to target LDAP.
Action: Move LDAP data from source to target before running "pasteConfig".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20623: OPSS store configuration failed.
Cause: Modification of bootstrap credential failed.
Action: Check clone log file for error details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20625: Unable to find Node Manager configuration.
Cause: Node Manager home location is empty.
Action: Make sure that the Node Manager configuration is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20626: Unable to find Node Manager configuration.
Cause: Node Manager type is empty.
Action: Make sure that the Node Manager configuration is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20627: Error in finding Node Manager configuration.
Cause: Node Manager is not configured correctly for the source domain.
Action: Make sure that the Node Manager configuration is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20628: Error in validating Node Manager home.
Cause: Node Manager home location is empty.
Action: Provide valid location for Node Manager home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20629: Error in validating Custom Location Node Manager home.
Cause: Node Manager home location is not empty.
Action: Provide valid location for Node Manager home. It should be empty or non-existing directory

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20631: Error in starting node manager.
Cause: Node Manager start failed.
Action: Check node manager log file, {0} for details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20632: Error in retrieving Node Manager configuration.
Cause: Internal error happened while validating Node Manager configuration.
Action: Make sure the archive provided is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20633: Error in validating "Node Manager Config".
Cause: {0} for Node Manager Config was not valid.
Action: Provide valid value for {0}.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20634: Error in validating "Node Manager Config".
Cause: {0} was not valid config property for Node Manager.
Action: Make sure config property names are not modified in move plan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20635: OPSS data {0} failed.
Cause: Unable to find "{0} / {1} / {2}" at "{3}".
Action: Make sure these files exist and are accessible.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20636: OPSS data import failed.
Cause: Unable to seed the schema.
Action: Check clone logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20637: OPSS data import failed.
Cause: Unable to add ldap container.
Action: Check clone logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20638: OPSS data {0} failed.
Cause: Unable to update {0}.
Action: Check clone logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20639: Connection to {0} failed.
Cause: There are three possible causes: 1. Server might be down. 2. Credentials provided might be wrong. 3. If only SSL mode is enabled, provide value of "trustKeyStoreLoc" parameter.
Action: Make sure server is running and credentials are valid. If SSL port is used, provide value of "trustKeyStoreLoc" and re-run "copyConfig".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20640: OPSS data {0} failed.
Cause: Unable to find "{0}" at "{1}".
Action: Make sure this file exist and is accessible.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20641: An internal operation failed.
Cause: Component registration xml, {0} is not a valid xml file.
Action: Make sure that {0} is a valid component registration xml file and is not corrupted.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20642: Move plan comparison failed.
Cause: The move plan xml passed in the argument does not contain the same meta data as the one present in archiveMeta data property "{0}" from argument move plan is "{1}" Meta data property "{0}" from archive move plan is "{2}"
Action: Make sure the move plan is actually generated from the archive passed in the argument.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20643: Additional parameter format not valid. The value provided for argument "{0}" was "{1}"
Cause: There are three possible causes: 1. Parameter value may be null. 2. Parameter value is not a key-value pair. 3. If more than one key-value pair is passed, they may have not been seperated using ,(comma).
Action: Make sure additional parameter is following a proper syntax. Syntax : -additionalParams property1=value1,property2=value2 Example: -additionalParams server=orclSv1,port=8888 Note:','(comma) and '='(equal) characters cannot be directly used within the key or value. They can be used by replacing them with the escape character as mentioned below ','(comma) -> %2C '='(equal) -> %3D Example: -additionalParams server=srv1%2CfailoverServer%3Dsrv2,ports=8888%2C8881

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20644: Invalid passphrase file.
Cause: The {0} passphrase file {1} did not exist or first line did not contain passphrase.
Action: Provide a valid passphrase file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20645: Mismatch between domain credentials and domain location.
Cause: The provided domain location "{0}" was different from the domain location "{1}" found from domain by using domain credentials.
Action: Make sure that specified source domain location and domain credentials are in sync.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20646: Target domain location validation failed.
Cause: Target domain directory name, {0} contain invalid characters.
Action: The specified domain directory name must include only alphanumeric characters, hyphens ('-') or underscore characters ('_'). The domain directory name must contain at least one letter or digit.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20647: {0} listen address validation failed.
Cause: Specified listen address, {0} is not a local machine address.
Action: "pasteConfig" is run on domain AdminServer machine. Specify valid local ip address for {0} listen address.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20648: Java vendor and version validation failed
Cause: The Java used in target location is different from the one being used on source location.
Action: Make sure the Java used on target machine is from the same vendor and has the same major version. Example: 1.6 or 1.7

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20904: Error happened while shutting down the managed servers. Check the t2p logs for details.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20905: OPSS store re-association from {0} to {1} is not supported. OPSS store will not be re-associated to {2}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20906: OPSS store re-association values are not provided. Source Domain OPSS store will be used for unpacked domain.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20907: {0} Details provided for OPSS configuration is same as source domain. Re-association will not be executed.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20908: Deployment plan ({0}) specified for {1} does not exist. {2} will not be added to the move plan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20909: Application deployment plan ({0}) specified for {1} does not exist. {2} will not be added to the move plan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20910: Default Authenticator data export failed.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20911: Default Authenticator data import failed.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20913: {0} is not a valid configProperty for {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20914: Exception caught while creating Move Plan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20915: Exception occurred while trying to write FMWClonerBean to File.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20916: Exception occurred while trying to write CopyArgBean to File.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20917: Exception occurred while deserializing FMWClonerBean from File.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20918: Exception occurred while deserializing CopyArgumentBean from File.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20919: Error in enrolling NodeManager with domain {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20920: NodeManager default startup script {0} does not exists.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20921: Unable to start the Node Manager.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20923: Error in examining OWSM targets. Verify that OWSM targeting is fine post paste config.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20924: Unable to establish a connection to the MBean server to verify an active edit session. Make sure that an edit session is not active in the domain.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20925: Error in validating RDBMS security store properties. Could not establish connection to the RDBMS security store.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20930: Found invalid "configProperty", {0} for {1} configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20931: Error occurred while adding default realm data to archive.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20932: Error occurred while extracting default realm data from archive.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20933: optimizationHints argument is required during extract move plan for multi archive mode. Use -optimizationHints (-opth) option to specify optimization hints.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20934: At least one valid optimization flag has to be specified. Flag(s) provided are : {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20935: "pasteConfig" operation of Node Manager failed. Correct the error before running the utility again. Also target Node Manager Home, {0} will be in an unusable state, so delete the directory before re-running "pasteConfig".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20937: "pasteConfig" operation of J2EE domain failed. Check log and error files for more details.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20938: Error occurred while handling component plan validation event handler. Message: {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20939: Error at column {0}, line {1}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20940: Error occurred while handling move plan validation event handler. Message: {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20941: Unable to validate domain connection , and exception is = {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21004: Some files are missing. Check clone log file to see all the missing files.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21006: Total time taken by T2P process was {0} seconds.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21007: Cloning operation completed successfully.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21016: Adding Oracle Home "{0}" binaries to the archive started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21017: Adding Oracle Home binaries to the archive finished.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21018: Extracting Oracle Home binaries from the archive at "{0}" location started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21019: Extracting Oracle Home binaries from the archive finished.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21020: Configuration of Oracle Home is in progress ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21021: Configuration of Oracle Home completed successfully.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21022: Applying permission for {0} started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21023: Applying permission for {0} finished. Operation complete in "{1}" seconds.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21024: A configuration script needs to be run as root at the end of clone operation. Run "{0}/oracleRoot.sh" as root.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21025: Validating permission of all files in new Oracle Home ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21026: Permission of all files in new Oracle Home are correct.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21028: Unable to find component detail from Oracle Home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21029: Unable to find top component detail from Oracle Home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21030: Adding "{0}" to the archive is successful.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21031: Time taken to add all the cloners to archive was "{0}" seconds.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21032: Archive created successfully at {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21035: Restoring the home finished successfully at {1}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21036: Restoring the component finished successfully.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21037: Time taken to restore all cloners from archive was "{0}" seconds.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21039: Gathering all sourceid(s) present in the archive.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21040: Oracle Home archive # {0}, home location {2}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21042: Component archive # {0}, instanceName@componentName {1}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21044: Unable to find JRockit JAVA HOME from registry.xml file.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21045: Permission file created successfully.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21046: Permission file creation failed.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21047: Permission for new Oracle Home {0} is not set properly, and permissionFilePath relative to Oracle Home is {1}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21048: Adding all required files to the main archive started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21049: Canonical path of the following files did not exist, and their absolute path is:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21050: List of files without read permission:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21051: Adding permission file to the archive started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21052: Adding permission file to the archive finished. Operation completed in "{0}" milliseconds.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21053: Total size of the file(s), to be included in the main jar from source location {0}={1} GB.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21054: Unable to read "{0}" file while adding files to the jar file.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21056: Time taken for adding files to archive was {0} seconds.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21057: Execution of system prerequisites started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21058: Execution of system prerequisites finished.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21059: Output of the process can be checked in the file {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21060: No system prerequisites will be executed for the Oracle Home {0} as it is set to false.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21061: No system prerequisites will be executed for the Oracle Home {0} as no system prerequisites files are available for this Oracle Home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21071: Permission file created with warnings.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21081: Parsing moveplan to get component name and component type ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21082: Parsing multi archive moveplan ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21083: Creating updated moveplan for component name "{0}" and component type "{1}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21084: Checking whether any config property has still reference to other config property or not.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21085: Updating component specific moveplan from multi archive moveplan ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21086: Updating component specific moveplan from multi archive moveplan for "{0}" ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21087: No config property has any reference to other config property.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21092: For help on a particular command, use [ <path to java> -jar <path to cloningclient.jar> -help <command>]
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21093: To proceed enter "yes", or any other text to abort:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21094: Clone operation was aborted.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21095: Create archive for {0} started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21105: Archive is invalid as it has home(s) and component(s).
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21106: Execution of system prerequisites has completed with warnings and/or to be verified. To proceed enter "yes", or any other text to abort:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21118: Adding symbolic link files detail to the archive started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21119: Adding symbolic link files detail to the archive finished. Operation complete in "{0}" milliseconds.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21122: File "{0}" is missing.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21123: Symbolic link file is not present or not properly linked, where absolute path should be "{0}" and canonical path should be "{1}", but canonical path found is "{2}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21125: All the symbolic link files are present in the Oracle Home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21126: Operation is {0}% complete, in "{1}" seconds.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21127: Performing inventory validation ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21128: Performing symbolic link files validation...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21129: Performing source Oracle Home reference validation ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21141: CloningClient build label is "{0}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21142: CloningClient version is "{0}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21143: Log File: "{0}". Error File: "{1}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21144: Unable to create log directory {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21145: The message id "{0}" is invalid for message type {1}, It did not start with "CLONE", or it did not end with "-INFO" where message type=INFO or it did not end with "-TRC" where message type=TRACE or it did not end with "-SVR" where message type=SEVERE or it did not end with "-ERR" or "-CAUSE" or "-ACTION" where message type=ERROR or its length was not be equal to "{2}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21146: Oracle Home {0} is registered with the Oracle Inventory {1}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21147: Oracle Home {0} is registered by the name {1} with the Oracle Inventory.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21148: Oracle Home {0} passed post validation.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21149: Oracle Home {0} failed post validation.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21154: Checking for availability of {0} MB free space at {1}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21155: Required free space is available.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21163: Adding details regarding files without read permission to the archive, started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21164: Adding details regarding files without read permission to the archive, finished. Operation complete in "{0}" milliseconds.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21165: In the source Oracle Home, some files have no read permission. Those files are not present in the cloned Oracle Home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21166: Permission of all files in new Oracle Home is not correct and details can be found at {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21193: Error while parsing "{0}" password file: "{1}" for password.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21196: The port "{0}" is free for use.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21197: The port "{0}" is not free for use.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21198: Trying to use source port "{0}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21199: Trying to get a new port between lower port {0} and higher port {1}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21200: Unable to calculate new port.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21201: New value for port "{0}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21203: The {0} password file: "{1}", either does not exist or is zero size.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21204: ERROR
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21205: CAUSE
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21206: ACTION
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21216: Performing post operation, if any ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21217: Post operation completed.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21218: Post operation failed.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21221: SEVERE
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21223: Deleting half-created archive file...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21226: Creating Move Plan...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21227: Extracting move plan and configplan(s) from archive(s)...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21228: Extracting plans from archive {0} under {1}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21229: Creating move plan by merging move plan(s)...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21230: Trying to derive OHS configuration from J2EE configuration...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21231: Trying to derive WebLogicCluster of OHS from J2EE configuration...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21232: Trying to derive OHS configuration within itself...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21233: Trying to find out component name and component type from archive ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21234: Laying down move plan(s) and other plan(s) from archive...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21235: Updating location of composite, MDM url resolver and adapter in move plan, if any...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21236: Move plan created successfully.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21237: Creating component specific updated move plan from move plan {0}...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21238: Trying to derive nodemanager configuration properties...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21239: Optimizing J2EE domain configuration ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21240: Optimizing J2EE domain configuration for {0} ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21241: Optimizing J2EE domain configuration for DataSource driverclass, jdbc url, schema name and password for all DB schema based on optimization hints ssn={0} ssp={1} sdt={2}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21242: Flag {0} is provided to perform more optimization.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21243: No {0} config property will be populated in moveplan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21245: Source domain had file based OPSS_SECURITY configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21246: Trying to find out whether user has changed OPSS configuration from file based to LDAP or DB based in move plan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21247: User has updated the OPSS configuration from file based to LDAP or DB based.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21248: User has not changed the OPSS file based configuration, so OPSS configuration will be same as source.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21249: IN the archive, component name is "{0}" and component type is "{1}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21250: Updating composite configuration plans ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21251: ERROR: There is a reference for host and port to tpid "{0}", but unable to find values for these tpid.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21252: ERROR: Config property having tpid "{0}" and value "{1}" is not in host:port pattern, but some other config properties depends upon it.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21253: ERROR: There is a reference to tpid "{0}", but unable to find values for these tpid.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21254: ERROR: There is a reference for host to tpid "{0}" and for port to tpid "{1}", but unable to find values for these tpid.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21255: ERROR: The reference tpid "{0}" is not in proper format.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21256: ERROR: Config property having tpid "{0}" and value "{1}" has no domain name, but some other config properties depends upon it.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21257: Unable to derive value for T2P unique id "{0}"
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21258: Updating application deployment plans ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21259: Unable to optimize host port value in composite configuration plan "{0}". Update this file before pasteConfig operation.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21260: All the host port values present in composite configuration plans of all the domains are optimized.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21261: Unable to optimize host port value in MDM URL Resolver file "{0}". Update this file before pasteConfig operation.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21262: All the host port values present in MDM URL Resolver file of all the domains are optimized.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21263: Updating MDM URL Resolver configuration ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21264: OPSS configuration complete. AdminServer will now be restarted.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21266: {0} does not appear to contain an obfuscated password. Assuming plaintext...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21267: Failed to create the deployment plan file at specified location for application "{0}". Copying the deployment plan file to "{1}"
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21268: Examining Node Manager configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21269: Validating Node Manager config properties.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21270: Configuring Node Manager.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21271: Validation of node manager config properties failed.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21272: {0} OPSS data...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21273: Examining Coherence Server configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21274: Examining Coherence Cluster configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21275: Pasting Coherence Server configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21276: Pasting Coherence Cluster configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21277: Failed to create the deployment plan file at specified location for adapter "{0}". Copying the deployment plan file to "{1}"
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21278: Warning: optimizationHints argument is not required during extract move plan for single archive mode. Ignoring the argument.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21279: Warning: The following optimizationHints flag are not supported and hence ignoring - {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21280: Warning: -domainAdminPassword argument has been deprecated. Use -domainAdminPasswordFile instead.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21281: Ignoring the argument {0} for this operation
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21282: Warning: MDS Import of following applications failed. {0}. Check managed server and clone logs for details.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21283: Warning: MDS export of some applications failed. Check the following list of applications and verify that MDS data is not associated with these applications. {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21284: Warning: Java vendor information is missing from product.properties.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21285: Warning: Java version information is missing from product.properties.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21286: Warning: Unable to save Java vendor and version information into manifest file.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21287: Warning: Exception occured while fixing file {0} SRC : {1} TAR : {2}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21288: Warning: Invalid Oracle home as unable to find Oracle home name from inventory.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21289: Warning: OUI major version is not 13.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21290: Warning: File {0} will not be archived as it is locked by other process.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21291: Warning: File {0} will not be archived as unable to read.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-22001: CreateClonerInfo object should not be empty at this point.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22002: Source type "{0}" was either empty or was not supported.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22003: The provided cloneType="{0}", is not matching with required clone type "{1}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22004: ApplyClonerInfo object should not be empty at this point.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22005: Either cloneType="{0}" or visible sourceid="{1}" or actual sourceid="{2}" is empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22008: During apply cloner object(s) build, all the sourceid(s) in the archive are {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22010: The archive entry point in the jar is="{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22017: No cloner object was found.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22018: Setting actual sourceid for all cloner objects.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22019: Adding all sourceid(s) to the jar file started ...
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22020: Adding all sourceid(s) to the jar file finished.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22025: The content of the sourceid file is {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22040: The jar file path={0} is invalid.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22041: Path represented by "{0}" was not a directory.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22042: Path represented by "{0}" did not exist.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22043: Path is empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22044: Unable to create file "{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22045: Directory {0} was not empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22046: File object is empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22047: The specified path "{0}" is not a file.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22048: The file "{0}" is of zero size.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22049: The file "{0}" is not a directory.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22052: Target location {0} is empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22053: The jar output stream is empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22054: The exclude pattern of the files which will not be included in archive={0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22055: Generating exclude file pattern list, if any pattern is provided.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22057: Generating list of files to be included.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22058: The statistics of the files are: Total number of files={0}. Non-readable files={1}. symbolic link files={2}. Exclude pattern={3}. Exclude pattern actual={4}. Included files only={5}. Included empty folders only={6}. Nonempty folders={7}. Invalid absolute path whose canonical path does not exist={8}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22061: The archive entry point={0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22062: Counter={0}, and excluded file through file pattern is {1}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22063: The time taken for unarchiving the entry from main jar={0} milliseconds.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22064: Either jar file path or entryNameToBeExtracted or target location is empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22065: The statistics of files whose permission will be handled:
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22066: The number of files with root privilege={0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22067: The number of symbolic link files={0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22069: The root privilege files are:
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22071: File permission is invalid where visible permission is={0} and its calculated permission is={1}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22072: Permission file {0} was already existing, so it will be deleted.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22073: The command "ls -alR" is executed properly, and temporary file was {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22074: The command "ls -alR" is not executed properly, and temporary file was {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22075: Unable to generate document object from the xml file {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22076: The domainHost={0}, domainPort={1}, domainAdminUserName={2}, domainAdminPassword={3}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22077: The Weblogic home "{0}" was invalid.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22078: The Weblogic jar "{0}" was invalid.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22079: The Oracle Home "{0}" was invalid.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22085: No parameter(s) should be empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22088: The jmx_connector is valid.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22089: Connection obtained successfully.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22090: Unable to get server connection.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22094: Under instance home {0}, the components present are {1}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22140: Parameter validation is complete. Sourceid is set to : "{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22141: Parameter validation is complete. TargetLocation is set to : "{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22142: Parameter validation is complete. Sourceid map is set to : "{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22152: parent_of_prereq="{0}", path_upto_oui="{1}", libDir_for_oui="{2}", platform_for_prereq="{3}", oui_lib_dir="{4}", sPrereqDir="{5}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22153: Before setting system environment property, prereq_bootstrap_dir="{0}", bootstrap_dir="{1}", prereq_config_loc="{2}", prereq_log_dir="{3}", oracle_install_scratch_path="{4}", oracle_install_lib_loc="{5}", oracle_install_engine_mode="{6}", java_lib_path="{7}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22154: To run prerequisites, oui lib directory is "{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22156: To run prerequisites, platform_directory under prereq folder is "{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22157: Operating system name="{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22158: No jar will be added to system class loader as jarlist is empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22159: Checking whether the following classes are already available in classpath or not. {0}
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22160: Status of the availability of all above classes in classpath is "{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22161: The following jars will be added to System class loader. {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22162: All jars added to System class loader successfully.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22163: All jars added to System class loader failed.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22164: After loading jars to classpath, checking whether the following classes are available or not {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22165: Adding engine jars to system classloader from Oracle Home {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22166: Status of adding engine jars to system classloader from Oracle Home {0} is="{1}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22167: Adding oui jars to system classloader from {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22168: Status of adding oui jars to system classloader from {0} is="{1}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22169: Adding both engine and oui jars to system classloader.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22170: Status of adding both engine and oui jars to system classloader is="{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22171: Adding oui jars from Oracle Home {0} to system class loader to know Oracle Home details.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22172: Trying to retrieve the top component name from Oracle Home {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22174: Extracting prerequisites jars under {0} location.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22175: Invoking engine prerequisites launcher.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22176: Status of parsing command-line argument="{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22177: Status of first validation of command-line argument="{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22178: Status of second validation of command-line argument="{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22183: Invalid entry for inventory_loc in inventory pointer file, and entry was {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22184: List of all valid symbolic link files is as follows.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22185: In file description "{0}", the first character is not "l", but has String "->"; assume it is symbolic link file.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22188: Adding jars from {0} to system class loader.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22189: Status of adding jars from {0} to system class loader is "{1}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22193: Updating file {0} where key={1} and value={2}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22194: Status of updating file {0} where key={1} and value={2}, is {3}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22195: All inputs from command-line are: {0}
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22199: List of all symbolic link files is as follows.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22200: Setting invPtrLoc with InventoryManager with user input value {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22204: OraInstaller library path={0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22206: Size of the home {0}={1} byte or "{2}" MB.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22207: For location {0}, free space required="{1}" MB, and the available free usable space="{2}" MB.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22209: Number of entries in the file, which will contain all valid symbolic link files detail={0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22211: Validating existence of symbolic link file by checking absolute path and canonical path.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22212: The command "{0}" is not executed properly, and temporary file was {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22217: {0}, file "{1}" is missing.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22218: During file existence check, number of files present={0} and number of file absent={1}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22224: For sourceid="{0}", the target location="{1}", and space required="{2}" MB.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22238: Rename status of source file {0} to target file {1} is {2}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22239: Delete status for file {0} is {1}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22240: Before updating file, sourcefile="{0}", old value="{1}", new value="{2}" and temporary file="{3}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22241: Trying to overwrite the content of source file "{0}" into the target file "{1}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22242: All the Oracle Home location and corresponding name present in the inventory {0} is as follows: {1}
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22244: Directory "{0}" was empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22245: Prereq execution result as follows: AllPrereqChecksCount ="{0}", prereqSuccessCount ="{1}", prereqFailedCount ="{2}", WarningsCount ="{3}", UserVerifyCount ="{4}", List of All Checks ="{5}", List of checks passed ="{6}", List of checks failed ="{7}", List of Warning checks ="{8}", List of checks to verify="{9}", List of checks to Retry ="{10}", Prereq Summery ="{11}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22247: Number of files with "no read access permission"={0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22248: The file "{0}" was non-readable in the source Oracle Home, and now it is available in the cloned Oracle Home.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22249: ERROR, for the symbolic link path "{0}", the required canonical file {1} is not present.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22250: ERROR, the symbolic link path "{0}", did not exist.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22251: ERROR, for the symbolic link path "{0}", the absolute path {1} and canonical path {2} are same, which is incorrect.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22252: ERROR, for the symbolic link path "{0}", the canonical path {1} and required canonical path {2} are different, but should be same.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22253: Counter={0}, absolute path="{1}" and required canonical path="{2}"
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22254: The input from the user was="{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22257: Unable to set the permission of the file {0} to {1}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22260: Executing following command: {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22262: Primary validation prior to clone operation is successful for {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22263: Restoring for the sourceid "{0}" started at {1}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22264: Time taken to restore sourceid "{0}" is "{1}" milliseconds.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22265: Adding cloningclient.jar to Archive.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22266: "StartupMode" is not set in move plan. Assuming PRODUCTION Mode.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22267: Extracted MDS metadata to {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22268: No MDS data found in archive. Skipping metadata import.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22269: Adapter deployment plan location is {0}. Make sure that configurable parameters specified in {1} deployment plan are correct.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22270: Commented OPSS_SECURITY "configGroup".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22271: OPSS_SECURITY "configGroup" commenting failed.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22274: Setting Listen Address of {0} to localhost to start it locally.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22275: Setting Listen Address of {0} to {1}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22277: Removing frond end url setting for {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22278: Setting frond end url setting for {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22279: Failed to remove frontend host and port settings for {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22280: Failed to set frontend host and port settings for {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22281: {0} start failed. Checked managed server logs for details.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22282: {0} start failed due to time out. Try again.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22283: Application deployment plan location is {0}. Make sure that configurable parameters specified in {1} deployment plan are correct.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22284: Adding Default Authenticator data to archive.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22285: Adding Node Manager files to archive.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22286: Derived WebLogic Server home to be {0} and Java Home to be {1}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22287: Loading Jar {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22288: Move Plan has no Node Manager movable component.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22289: Number of Node Manager Movable Components is {0}
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22290: Mismatch in number of Movable Components of node manager from derived and visible.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22291: Deriving node manager properties of {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22292: Retargeting owsm application and data sources.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22293: Detected CommonDomain. Exporting Fusion Apps Global Partition MDS docs..
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22294: Not detected as CommonDomain. Fusion Apps Global Partition MDS docs will not be exported..
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22295: Detected CommonDomain. Exporting ESS Global Partition MDS docs..
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22296: Not detected as CommonDomain. ESS Global Partition MDS docs will not be exported..
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22297: Detected CommonDomain. Exporting ESS Internal Partition MDS docs..
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22298: Not detected as CommonDomain. ESS Internal Partition MDS docs will not be exported..
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22299: Export location for embedded LDAP data = {0}
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-23001: Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23002: Usage: Run {0} script with following parameters:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23003: Options(alias) with multiple names separated by comma:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23004: Absolute path of java home directory
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23005: T2P process cannot be executed without this.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23006: Absolute path of archive file
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23007: The archive file should not exist.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23008: Absolute path of Oracle Home
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23009: To create archive of this Oracle Home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23010: Absolute path of inventory pointer loc i.e. oraInst.loc
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23011: This argument is ignored from 12.1.2.0.0. It is used to validate source Oracle Home. Internally it is calculated. In case of unix, it is ORACLE_HOME/oraInst.loc. In case of Windows this argument is not required.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23012: Absolute path of a directory
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23013: Cloning log and error file will be created under this directory. Default location is system temporary location.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23014: Flag to run the T2P operation in a non-interactive mode. Default value is true.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23015: Flag for ignoring the results of free space check. Default value is false.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23016: Description:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23017: To create an archive of Oracle Home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23018: Example:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23019: Usecase-{0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23021: Command:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23022: Requirement
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23023: The movement scripts require a minimum of Java version of 1.6 However, for the exact JRE version certified for the product, please refer to the System Requirements and Supported Platforms document, which is located at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23024: Assumption:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23025: NOTE:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23030: Absolute path of the target Oracle Home
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23031: Absolute path of an existing archive file.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23032: This argument is mutually exclusive with "{0}" argument.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23033: Flag to execute system prerequisites before restoring the Oracle Home. Default value is true.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23034: Absolute path of inventory pointer file
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23035: This flag is supported in UNIX platforms only. Default value is {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23036: This file has pointer to central inventory. Oracle Home will be registered with that central inventory.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23037: The invPtrLoc should point to a file which contains the following information.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23038: Additional session variable for OUI runInstaller. Variables need to be passed as key=value pair.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23039: More than one session variable should be separated using comma (,).
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23040: In Windows, provide whole value within double quote("").
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23041: Oracle Home name that will be used to register Oracle Home with the central inventory.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23042: Flag to reconfigure an already existing Oracle Home(created using flexClone mechanism). Default value is false.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23043: Either to restore and configure the Oracle Home using an archive or reconfigure an Oracle Home created via flexClone mechanism.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23044: Make sure that the Oracle inventory has no entry for the target Oracle Home and target Oracle Home name.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23045: Restore Oracle Home from an archive
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23046: Archive was created using copyBinary script. Path specified for target Oracle Home need to be either a non existing or an existing empty directory.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23047: Reconfigure an already existing Oracle Home created using flexClone mechanism
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23048: The target Oracle Home is existing. Binaries are moved from source to target via flexClone mechanism.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23049: The target Oracle Home location cannot be inside another Oracle Home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23060: WebLogic managed domain specific parameters
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23061: Absolute path of source WebLogic Domain
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23062: To capture configuration of this domain.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23063: Source Domain Admin Server Host Name
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23064: Source Domain Admin Server Port
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23065: Source Domain Admin Server User Name
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23066: Absolute path of source domain Admin server user password file
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23067: Absolute path of Custom Trust KeyStore File
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23068: Additional parameters required for product specific operations. It need to be passed as key=value pairs.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23069: Mutiple parameters should be passed by separating each key=value pair by a comma (,).
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23070: In Windows, provide whole value within double quote("").
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23071: Standalone domain specific parameters
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23072: Absolute path of source standalone Domain
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23073: Node Manager specific parameters
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23074: Absolute path of source nodemanager home
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23075: If this argument is not provided, copyConfig utility will try to calculate the same.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23076: In case of failure to compute the argument, provide the argument explicitly.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23077: To create archive of a Weblogic managed domain or a standalone domain or a NodeManager.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23078: This Oracle Home need to be associated with the domain specified via argument {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23081: To create archive of {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23085: Absolute path of an existing target Oracle Home
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23086: Absolute path of the T2P MovePlan
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23087: Absolute path of the updated T2P MovePlan xml document (extracted during {0} operation).
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23088: Refer to the Chapter "Cloning Oracle Fusion Middleware" of Fusion Middleware Guide for more details.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23089: Absolute path of target WebLogic managed domain
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23090: Path can be either a non existing or an existing empty directory.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23091: Absolute path of target domain Admin server user password file
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23092: Absolute path of target J2EE domain application directory
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23093: Absolute path of target Node Manager home
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23094: To restore the full archive containing a WebLogic managed domain or a standalone domain or a Node Manager.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23095: To restore archive of {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23096: Absolute path of target Standalone domain
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23101: Absolute path of the existing archive files.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23102: If multiple archives are provided, provide them as a comma separated list. (In Windows, provide the comma separated list within double quotes)
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23103: Absolute path to directory where moveplan is to be extracted
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23104: The moveplan and/or multi archive moveplan will be extracted along with other J2EE Configuration Plans.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23105: Flags for optimization while creating multi archive moveplan
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23106: Provide the flags as a comma separated list. (In case of Windows, provide the comma separated list within double quotes)
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23107: The supported values are :{0} and the aliases for these flags are {1} respectively.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23108: Based on flag, specific optimization of multi archive moveplan will take place.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23109: Flag description:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23110: You need to provide this hint always. This simplifies the move plans by setting other flags internally.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23111: The same password is used for all schemas associated with a particular database specified in {0} section of the moveplan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23112: However, the passwords for APPID users are different. You are prompted to provide the password only once for each database.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23113: Therefore, you need to pass a separate password for each of the APPID users.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23114: The same password is used for all schemas associated with a particular database specified in {0} section of the moveplan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23115: If {0} flag is provided, then automatically this flag will be set to true.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23116: To extract moveplan or multi archive moveplan along with other J2EE configuration plans.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23117: The t2p moveplan or multi archive moveplan contains the endpoint configuration for J2EE and CAM Component configuration
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23118: For details on how to modify the t2p moveplan or multi archive moveplan, refer to T2P document.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23120: Updating machine, datasource configuration changes in the extracted domain template ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23170: Invoking all CAM components which supports T2P.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23171: Following system components are configured in the domain: "{0}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23172: No system components are configured in the domain.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23173: Following types system components support T2P : "{0}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23174: There are no system components which support T2P.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23175: Following types of sytem components {0} are configured in domain. T2P is not possible for following components types {1} as there is no T2P support for them.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23176: Following system components (COMPTYPE_COMPNAME Vs machineName) are configured in the domain "{0}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23190: Find all CAM plugin PasteConfig implementations and apply the configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23265: Use the "-help" option for more information about cloning options and arguments.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23267: Pack Domain - {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23268: Adding Packed Domain to archive
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23269: Error in examining J2EE Domain. Check the logs for more details
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23270: Connecting to domain runtime...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23271: Trying to connect to {0}:{1}...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23272: Successfully connected to the Domain Runtime ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23273: Examining Servers.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23274: Examining Machines.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23275: Examining Clusters.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23276: Examining Datasources.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23277: Examining Security Policy.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23278: Examining all J2EE plugin implementations.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23279: Credential and Policy Store is LDAP type.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23280: Credential and Policy Store is File based.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23281: Extract the packed domain from archive to temp location.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23282: Reading the extracted domain template and pasting server, machine, cluster, datasource configuration changes...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23283: Unpack Domain.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23284: Starting AdminServer and pasting security policy configuration changes...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23285: Find all J2EE plugin PasteConfig implementations and apply the configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23286: Pasting security policy configuration changes....
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23287: Paste Server Configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23288: Paste Cluster Configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23289: Paste DataSource Configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23290: Paste Machine Configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23292: Examining Adapters.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23293: Examining Resource Adapters. The Resource Adapters with deployment plan will be added to move plan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23294: Adding Adapter {0} to move plan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23295: Warning: Found invalid attribute in Adapter "ConfigGroup". Valid Attributes are "Name" and "Deployment Plan".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23296: Paste Adapter Configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23297: Warning: Neither LDAP nor DB details are specified in move plan for the OPSS Security Store. Default Store will be used at the target.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23298: Re-associate security store with provided LDAP : {0}, {1}, {2}, {3}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23300: Configplans have been extracted at "{0}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23301: ExtractMovePlan operation completed successfully.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23302: Serialize and write bean to a temp file, then add that temp file to jar.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23303: Write archive file list to a temp file , then add that temp file to jar.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23304: ****************** PACK ******************
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23305: Details for Packing Domain...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23306: Oracle Home Source Location: {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23307: Source Domain Location: {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23308: Packed jar Location: {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23309: Command to execute for pack: {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23311: SEVERE: Specified adapter deployment plan {0} is not a valid file. Using the default plan from archive.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23312: Examining LDAP Authenticators.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23313: Paste LDAP Authenticator Configuration
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23314: Exporting metadata of applications. Make sure that all managed servers in the specified domain are started.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23315: Importing metadata of applications.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23316: Starting {0} to import MDS data.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23317: Importing metadata of application {0} from archive.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23319: Exporting metadata may take several minutes. Check the logs for monitoring the progress....
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23351: MDS data export flag is set to false. Skipping MDS configurations.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23352: [Deprecated - As of release 11.1.1.7.0, replaced by "-mdsDataExport|-mde"] Flag to execute MDS export/import. Default value is true.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23353: Error in validating "pasteConfig" parameters.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23356: Error in validating "SERVER_CONFIG" parameters in "moveplan".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23357: {0} is already running on port {1}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23358: Stopping all managed servers.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23359: Credential and Policy Store is database based.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23360: Values for re-associating and migrating "OPSS_SECURITY" are not provided. Assuming File store for OPSS.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23361: Re-associate security store to database : {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23362: Examining RDBMS Security Store.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23363: Paste RDBMS Security Store Configuration
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23374: Examining applications with custom deployment plans.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23375: Examining applications with custom deployment plans. The applications with a deployment plan will be added to the move plan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23376: Adding application {0} deployment plan to the move plan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23377: Pasting application deployment plan configuration.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23378: Warning: Found invalid attribute in DEPLOYMENT_PLAN_CONFIG "ConfigGroup". Valid attributes are "Application Name" and "Deployment Plan".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23379: SEVERE: Specified application deployment plan {0} is not a valid file. Using the default plan from archive.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23380: Exporting Default Authenticator data.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23381: Importing Default Authenticator data.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23382: MDS export of some applications failed. Check the logs for details.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23383: MDS import of some applications deployed on {0} failed. Check the logs for details.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23384: Stopping {0}...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23500: Error while archiving Node Manager. Check log for more details.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23502: Unarchiving Node Manager files at location {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23503: Target Oracle Home Location is either null or an empty string.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23504: Unable to derive target WebLogic Server Home from the Oracle Home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23505: Unable to derive Java Home from the target Oracle Home .
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23506: The file {0} does not exist.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23507: Updating file {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23508: Examining each domain to enroll Node Manager.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23509: Unable to retrieve properties of the domain from Move Plan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23510: Domain Name is either null or an empty string in the Move Plan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23511: Domain Location is either null or an empty string in the Move Plan.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23512: Incorrect format of AdminServer Listen Port for domain {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23513: Checking if the AdminServer for domain {0} is up...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23514: Could not connect to AdminServer for domain {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23515: Enrolling NodeManager with domain {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23516: Successfully enrolled NodeManager with domain {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23517: WebLogic Server Home value is either null or empty string.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23518: Starting Node Manager from location {0}...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23519: Node Manager ListenPort mentioned in nodemanager.properties is not valid.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23520: Checking if port {0} is available for Node Manager...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23521: Port is available.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23522: -targetNMHomeLoc is either null or an empty string.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23530: Re-associating security store...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23533: Absolute path of Custom Trust KeyStore File Location. Specify this property to specify the "CustomKeyStore" if SSL port is specified for AdminServer.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23534: The move plan - {0} was not extracted using the archive - {1}. Please extract the move plan once again using the archive - {1} and re-run the script.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23535: Warning: Starting of {0} is taking longer than expected. Check the server logs to make sure {1} start is in progress.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23536: Warning: Stopping of {0} is taking longer than expected. Check the server logs to make sure {1} shutdown is in progress.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23537: [Deprecated - As of release 11.1.1.7.0, replaced by"-domainAdminPasswordFile"]
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23538: Starting AdminServer...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23539: Stopping AdminServer...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23540: Starting managed server {0}...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23541: Stopping managed server {0}...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23542: Archive file {0} is either not a file or of zero size.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23543: No archive file is provided..
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23544: Number of moveplans and number of archives are not same.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23545: Unable to load prerequisites jars, proceeding without executing system prerequisites.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23546: The sameDBTopology flag is false. No optimization will happen for data source.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23547: Prereq will not be executed.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-27000: 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-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-28010: Start to run T2P ADF Connection Plugins.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-28100: Starting WLS managed server {0}@{1}:{2}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-28200: Stopping WLS managed server {0}@{1}:{2}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: NOTIFICATION

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

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

Level: 1

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-40001: OWSM Plug-in Copy Config Operation Started. Validating source environment.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40002: WSM-PM is not installed in domain. Repository data will not be moved.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40003: Reading bootstrap configuration file.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40004: Bootstrap configuration file modified on source environment. \"bootstrap.configmanager\" movable component will be added to move plan.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40005: Bootstrap configuration file \"wsm-config.xml\" is not modified on source environment.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40006: Reading WSM repository data.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40007: WSM repository data modified on source environment. \"wsm.repository\" movable component will be added to move plan.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40008: WSM repository data is not modified on source environment.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40009: OWSM plug-in movable component of type \"{0}\" will be added to move plan.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40010: WSM specific artifacts are not modified on source environment. Nothing will be added to move plan.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40011: OWSM Plug-in Copy Config operation finished.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40020: Unable to retrieve repository timestamp. Validation will not be performed.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40021: OWSM Plug-in Paste Config operation started. Validating target environment.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40022: WSM-PM is not installed in target domain. Repository data will not be updated.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40023: Updating repository data using move plan values. Extracting configuration groups from movable component.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40024: Repository movable component is not present in move plan. Repository data will not be updated
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40025: Updating bootstrap configuration using move plan values.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40026: Bootstrap movable component is not present in move plan. Bootstrap configurations will not be updated.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40027: OWSM Plug-in Paste Config Operation Finished.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40028: Map file does not exist at {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40029: WSM repository archive file does not exist at {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40030: Error in importing repository data at target environment.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40031: Bootstrap file updated successfully, deleting original file.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40032: Error in updating bootstrap file, restoring original file.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40033: Repository timestamp updated successfully.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40034: Repository timestamp not updated.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40035: OWSM Plug-in Paste Config Operation Finished.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40036: Domain name \"{0}\" will be changed to \"{1}\".
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40037: WSM Policy Manager is in active state.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42000: OWSM Plug-in source environment validation failed.
Cause: The method which checks if wsm-pm application is installed in domain failed.
Action: Make sure that admin server is up and wsm-pm applications is in active state, if installed.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42001: OWSM Plug-in copyConfig operation failed.
Cause: Execution of \"doCopyConfig\" failed.
Action: Check clone logs and server logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42002: Error in generating map file for WSM Repository archive.
Cause: The map file for WSM repository archive could not be created.
Action: Check the clone logs and server logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42003: OWSM plug-in target environment validation failed.
Cause: The method which checks if wsm-pm application is installed in domain failed.
Action: Make sure that admin server is up and wsm-pm applications is in active state, if installed.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42004: Error in reading wsm repository timestamp.
Cause: Either wsm-pm application is not active or connection credentials are incorrect.
Action: Make sure wsm-pm application is up and credentials are correct. Check clone logs and server logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42005: Error in parsing move plan.
Cause: Specified move plan was not valid.
Action: Make sure that all the specified values in the move plan are correct.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42006: Error in extracting OWSM t2p directory.
Cause: Execution of \"extractWsmT2PFromRepository\" failed.
Action: Make sure that archive location is correct and is not corrupted. Check clone logs for details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42007: WSM repository import failed.
Cause: WSM Repository data could not be imported.
Action: Make sure wsm-pm application is active. Check the clone logs and server logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42008: Export WSM repository failed.
Cause: WSM Repository data could not be exported.
Action: Check the clone logs and server logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42009: Error in adding file \"{0}\" to T2P archive.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42010: Error in reading bootstrap configuration file at source environment.
Cause: Either the file path is invalid or bootstrap file is of invalid format.
Action: Check the clone logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42011: Error in reading bootstrap configuration file at target environment.
Cause: Either the file path is invalid or bootstrap file is of invalid format.
Action: Check the clone logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42012: Error in reading map file generated by import repository command.
Cause: The location of the map file is invalid or map file does not exist.
Action: Check clone logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42013: Error in reading map file generated by import repository command.
Cause: Generated map file is not of correct format.
Action: Check clone logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42014: Error in retrieving the status of wsm-pm application.
Cause: The wsm-pm application is not up or the server on which wsm-pm is targeted is not up.
Action: Make sure server on which wsm-pm is targeted is not down and correct admin server credentials have been provided.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42015: Invalid map file location - {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42016: Invalid map file pattern - {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42017: Error in reading map file - {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42020: Invalid bootstrap configuration file location - {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42021: Error in updating bootstrap configuration file - {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42022: Unable to parse bootstrap configuration file {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42023: Error in connecting to domain runtime.
Cause: Domain runtime connection to admin server could not be established.
Action: Make sure admin server is up and credentials are correct. Check clone logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42024: Unable to retrieve information about listen (non-ssl) port.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42025: Unable to retrieve server bean object for admin server.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42026: Error is encountered in starting managed server.
Cause: The server where wsm-pm application is targeted could not be started.
Action: Check server logs and clone logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42027: Error is encountered in stopping managed server.
Cause: The server where wsm-pm application is targeted could not be stopped.
Action: Check server logs and clone logs for more details.

Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-92100: In method doCopyConfigValidation.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92101: In method doCopyConfig.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92102: In method doPostCopyConfig..
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92103: In method doPasteConfigValidation.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92104: In method doPrePasteConfig.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92105: In method doPasteConfig.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92106: In method doPostPasteConfig.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92107: Download data for User Preferences.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92109: Extract driver configuration.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92110: Extract configuration from {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92111: Value was null for property {0}. Skip.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92112: No UMS config found. Skip driver configuration.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92113: Update configuration on {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92114: Upload data for User Preferences.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92115: UMS application not present in domain. Skip doCopyConfig (no-op).
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92116: UMS application not present in domain. Skip doPasteConfig (no-op).
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92117: Starting server {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92118: Stopping server {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92119: Handle User Preferences.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92120: Found User Preferences on {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92130: No DriverConfigExtractor found for driver type {0}. Skip.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92300: doCopyConfig failed. msg={0} stackTrace={1}
Cause: Failure during copyConfig.
Action: See log for details.

Level: 1

Type: ERROR

Impact: Process

CLONE-92301: doPasteConfig failed. msg={0} stackTrace={1}
Cause: Failure during pasteConfig.
Action: See log for details.

Level: 1

Type: ERROR

Impact: Process

CLONE-92302: Skipped corrupted ConfigGroup for {0}
Cause: Expected one ConfigProperty within ConfigGroup.
Action: Edit moveplan.xml or configure manually in the production system.

Level: 1

Type: ERROR

Impact: Process