8 CLONE-20200 to CLONE-92302
- 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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-28000: Unable to apply ADF Connection properties for Application "{0}"
-
Cause: This could be caused by an invalid Oracle MDS configuration in your application or a failure while attempting to apply attributes using JMX.
-
Action: Please validate that the application is configured with writable Oracle MDS.
Level: 1
Type: ERROR
Impact: Other
- CLONE-28400: No ADF Connectioin MBean with name {0}
-
Cause: OBJECT_NAME_PROPERTY field for mbean object name might be changed accidently.
-
Action: Use the value of OBJECT_NAME_PROPERTY from other attributes under the same ADF Connection MBean in Move Plan to correct the wrong one.
Level: 1
Type: WARNING
Impact: Other
- 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-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