25 CLONE-20200 to CLONE-53030

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: The archive location is invalid.

Cause: There are five possible causes for an invalid path {0}: 1. The path was not provided. 2. The path was not an absolute path. 3. The path already existed. 4. The parent path did not exist. 5. The parent path did not have write permission.

Action: Provide an absolute path to a directory that does not exist and make sure that its parent location exists and has write permission.

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: Insufficient parameters for copyConfig.

Cause: Neither "-sourceMWHomeLoc", "-sourceInstanceHomeLoc and -sourceComponentName" nor "-sourceMWHomeLoc and -sourceDomainLoc" nor "-sourceNMHomeLoc" were provided.

Action: Provide either "-sourceMWHomeLoc", "-sourceInstanceHomeLoc and -sourceComponentName" or "-sourceMWHomeLoc and -sourceDomainLoc" or "-sourceNMHomeLoc".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20205: Arguments combination is invalid.

Cause: The -sourceInstanceHomeLoc and/or -sourceComponentName was provided along with -sourceMWHomeLoc.

Action: Provide either -sourceInstanceHomeLoc and/or -sourceComponentName or sourceMWHomeLoc.

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-20207: The clone option is not supported.

Cause: The option or argument "{0}" was not supported by {1} operation.

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-20208: Insufficient parameters.

Cause: At least one argument from these arguments "{0}", was not provided.

Action: Provide all the arguments.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20209: Unable to unregister all instances(which were present in source domain) from target domain.

Cause: An internal operation failed.

Action: Check the clone log and error file for more detail and unregister instances from target domain through admin console.

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-20211: Unable to update JRE_LOCATION in Oracle Home.

Cause: Unable to determine JRE_LOCATION.

Action: Update JRE_LOCATION attribute in {0} file present under Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20212: Target location is not provided.

Cause: Archive had Middleware Home and/or Oracle Home.

Action: Provide the target location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20213: Parameters are missing for component pasteConfig.

Cause: There are two possible causes: 1. Target component name was empty. 2. If target instance did not exist, then either target instance name or Oracle Home was empty or Oracle Home was not a directory.

Action: Provide a nonexistent component name and a target instance location. If the instance does not exist, provide the instance name and an existing Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20214: T2P of asinstance is not possible.

Cause: No movable component was found under the instance home.

Action: Make sure that the instance home has at least one movable component.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20215: T2P of asinstance failed.

Cause: Unable to archive all the movable components.

Action: Provide the clone log and error file for investigation.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20216: Instance home location "{0}" is invalid.

Cause: There are two possible causes: 1. Instance did not have the required configuration files. 2. Instance was not associated with a valid Oracle Home.

Action: Provide a valid instance home location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20217: Component does not exist.

Cause: The component "{0}" did not exist under the instance "{1}".

Action: Provide an existing component.

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-20224: T2P operation failed.

Cause: Unable to restore all movable components.

Action: Check the clone log and error file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20225: Invalid number of sourceid(s) and their restore locations.

Cause: There was a mismatch between the count of sourceids and restore locations specified in the command line. The number of sourceids was "{0}" and number of restore locations was "{1}".

Action: Provide the same number of sourceids and their corresponding restore locations.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20226: Duplicate target location.

Cause: An attempt was made to restore same or different sourceid at same location multiple times.

Action: Provide unique target location for each sourceid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20227: Invalid target location for Oracle Home.

Cause: Two Oracle Homes target location "{0}" and "{1}" were either equal or a parent or child of one another.

Action: Oracle Home(s) target location(s) should not be either equal or parent or child of one another.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20228: Invalid target location for Middleware Home.

Cause: Two Middleware Homes target locations "{0}" and "{1}" were either equal or the parent or child of one another.

Action: Middleware Home(s) target location(s) should not be either equal or a parent or child of each other.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20229: The archive file is invalid.

Cause: Internal id was absent in the archive.

Action: Make sure that the archive file is valid.

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: Middleware Home archive creation has failed.

Cause: The command "{0}" was not run successfully. The possible causes are: 1. All WebLogic product directories (like WebLogic Server, Coherence) were not installed inside this Middleware Home. 2. In case of Windows, some Java or WebLogic processes were running from this Middleware Home.

Action: Make sure all WebLogic products are installed inside, no process is running from the Middleware Home (in case of Windows), and check the clone log, clone error and "WebLogic error file at current location" for more details.

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 in the inventory for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20233: Restoring Middleware Home for sourceid "{0}" 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-20234: Unable to find Oracle Home "{0}" from inventory.

Cause: Missing entry for Oracle Home in the inventory.

Action: Make sure that the Oracle Inventory has an entry for this Oracle Home.

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-20238: Component name is invalid.

Cause: The instance "{0}" was already configured with component name "{1}".

Action: Provide a unique component name.

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-20241: Moveplan is invalid.

Cause: There was a mismatch between number of components specified in the moveplan and number of components present in the archive.

Action: Make sure that no component is removed from the moveplan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20242: Moveplan contains an invalid component type.

Cause: There are two possible causes :1. The component type was empty.2. The component type from moveplan "{0}" was not matching with the component type "{1}" present in the the archive.

Action: Make sure that component type is not changed in the moveplan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20243: Moveplan contains an invalid component name.

Cause: There are three possible causes for the component name {0} being invalid:1. It was empty.2. Length of the component name was either too short or too large.3. Component name had contained unsupported characters.

Action: Provide a valid component name in the moveplan.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20244: Moveplan is invalid.

Cause: The component names were not unique in the moveplan.

Action: Provide unique component names in the moveplan.

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-20246: Oracle Home is invalid.

Cause: Size of the Oracle Home "{0}" was zero.

Action: Uninstall the invalid Oracle Home and execute copyBinary again.

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: Invalid target location.

Cause: There are four possible causes for invalid location {0}: 1. The target location was not provided. 2. The target file path was not an absolute path. 3. The target file path did not exist. 4. The target file path did not have write permission.

Action: Provide an absolute path of an existing target location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20255: Invalid Middleware Home.

Cause: The "{0}" was not a valid Middleware Home.

Action: Make sure that it is a valid Middleware Home.

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 Oracle Inventory.

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 location file is invalid.

Cause: There are two possible causes for an invalid default invPtrLoc file "{0}": 1. The file did not exist. 2. It was a zero size file.

Action: Ensure that the default oraInst.loc file at "default location" is valid or provide a different, valid Inventory Pointer file using the -invPtrLoc 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-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-20270: Java home of the Middleware Home is invalid.

Cause: There are two possible causes: 1. Did not find either JAVA_HOME or JAVAHOME property in product.properties of WebLogic Server home. 2. The Java home did not exist.

Action: Make sure that the Middleware Home is installed with a valid Java home.

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-20273: Invalid instance location.

Cause: Path "{0}" was not absolute or did not exist or was an empty directory.

Action: Provide a valid absolute path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20274: Invalid Oracle Home.

Cause: Top component version validation failed.

Action: Make sure that the Oracle Home is valid.

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: Some files were missing.

Action: Check the clone log or error 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 or error 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 or error file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20279: Oracle Home configuration is unsuccessful.

Cause: Inventory was not updated properly.

Action: Check the clone log or error file for more details.

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-20281: Moveplan has incorrect SSL information for the asinstance

Cause: There were following causes: {0}

Action: The actions are: {0}

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20282: Parameter validation for component pasteConfig has failed.

Cause: Instance existed, but the provided instance name "{0}" was different from the instance name "{1}" found from the instance home.

Action: Either provide a valid instance name or do not provide a name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20283: Mismatch between domain parameters and Moveplan.

Cause: The provided admin port "{0}" correspond to non ssl port where as moveplan had SSL information.

Action: Provide ssl port.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20284: Parameter validation for component pasteConfig has failed.

Cause: Instance existed, but the provided Oracle Home "{0}" was different from the Oracle Home "{1}" used by the existing instance home.

Action: Either provide a valid Oracle Home or do not provide an Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20285: Unable to update WebLogic monitoring credential in EM agent.

Cause: Some internal operation failed.

Action: Check the clone log file and work around is : {0}

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20287: Domain connection validation has failed.

Cause: The possible causes were: 1. The domain details were not correct. 2. The domain was down. 3. If the port was ssl port, then moveplan did not have right ssl parameters.

Action: Make sure that the domain details are correctly provided and domain is running in the same admin port.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20291: Invalid target instance location.

Cause: Path {0} was either an empty string or was not an absolute path.

Action: Provide an absolute path for the target instance.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20292: Inventory pointer location file is not valid.

Cause: The inventory {0} found from the invPtrLoc File {1} was not absolute.

Action: Make sure that the inventory pointer location file is valid.

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 or error 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 or error file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20296: Invalid instance location for an existing instance name in the domain.

Cause: There are two possible causes for an invalid instance location {0}: 1. The instance location did not match the registered instance. 2. The instance home did not exist or was not valid.

Action: Provide correct instance name and location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20297: Invalid instance name for an existing instance location in the domain.

Cause: There are two possible causes for an invalid instance name {0}: 1. The instance name did not match the registered instance. 2. The instance home did not exist or was not valid.

Action: Provide correct instance name and location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20298: Invalid target location.

Cause: An attempt was made to restore multiple {0} Oracle Homes under same Middleware Home {1}.

Action: There can be only one SOA/WEBCENTER Oracle Home in a Middleware Home.

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 or error file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20300: Instance name is already registered with the domain.

Cause: Instance name was already registered with domain but no instance location was associated with it.

Action: Provide another instance name which is not registered with domain.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20301: Jre location update has failed.

Cause: Was unable to find the Java home from the Middleware Home "{0}".

Action: Make sure that the Middleware Home is installed properly.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20302: Invalid Java home.

Cause: The Java home {0} found from System property was not pointing to the Java home. It was pointing to the jre home and its parent was not Java home.

Action: Provide -javaHome <java home path> as command-line parameter to cloningclient.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20303: Invalid Java home.

Cause: The Java home {0} did not have the required files.

Action: Provide a correct Java home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20304: Invalid Java home.

Cause: Path {0} either was not absolute or did not exist.

Action: Provide an absolute path for the Java home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20306: Middleware Home cloning is not possible.

Cause: There are three possible causes for the failure of cloning this Middleware Home {0}: 1. WebLogic Server install path {1} was outside of Middleware Home. 2. Cloning script {2} was not present. 3. Cloning script {3} was not present.

Action: Make sure that cloning script is present and WebLogic Server is installed inside Middleware Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20307: Invalid path.

Cause: Path {0} was either not absolute or did not exist.

Action: Provide an absolute path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20312: Oracle instance name is invalid.

Cause: The instance name is already registered with domain.

Action: Provide an instance name which is not registered with domain.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20315: Unable to access Oracle Inventory.

Cause: An attempt was made to execute in silent mode. It was not possible to access the Oracle Inventory.

Action: Provide a valid Oracle Inventory pointer location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20316: Oracle Home(s) under the Middleware Home have not been included.

Cause: Oracle Home(s) registered with the Oracle Inventory were not present inside the Middleware Home.

Action: Ensure that the Oracle Home(s) present inside the Middleware Home are registered with the Oracle Inventory or provide the correct custom inventory.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20317: Oracle Home(s) under the Middleware Home have not been included.

Cause: Unable to find the Oracle Home(s) registered with the Oracle Inventory.

Action: Ensure that the Oracle Home(s) present inside the Middleware Home are registered with the Oracle Inventory or provide the correct custom Inventory.

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-20319: Invalid Oracle instance home location: {0}.

Cause: Either the directory location does not exist or it is corrupt.

Action: Provide a valid Oracle instance location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20320: The specified instance name "{0}" does not match calculated instance name "{1}".

Cause: The specified instance name did not match the instance name found from the specified instance home.

Action: Provide correct instance name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20321: Invalid Oracle Home location: {0}.

Cause: Either the directory location does not exist or it is corrupt.

Action: Provide a valid Oracle Home location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20322: The specified instance home "{0}" is not associated with specified Oracle Home, but associated with another Oracle Home "{1}".

Cause: The specified Oracle Home "{0}" was not matching with the Oracle Home used by the specified instance.

Action: Provide a correct Oracle Home location.

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-20325: Unsupported Instance home path length.

Cause: Length of Instance home path {0} was equal to {1} and it was exceeding the limit.

Action: Length of instance home path must be less than or equal to {0}

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20326: Domain parameters are missing.

Cause: Target instance did not exist; all domain parameters were not provided.

Action: Provide either all domain parameters or none.

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-20329: Unable to archive Oracle Home {0} and the dependent Oracle Home {1}.

Cause: The Oracle Home {1} was not clonable.

Action: Make sure that the dependent Oracle Home {1} is valid and clonable.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20330: Unsupported Middleware Home cloning.

Cause: Oracle Home {0} was associated with the Middleware Home {1}, but the Middleware Home was not cloneable.

Action: Provide a valid Middleware Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20331: Invalid Middleware Home.

Cause: Specified Middleware Home had neither clonable Weblogic binaries nor Oracle Homes.

Action: Provide a valid Middleware Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20332: Invalid Middleware Home location.

Cause: Path "{0}" was not absolute or did not exist or an empty directory.

Action: Provide a valid absolute path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20333: Invalid Domain home location.

Cause: Path "{0}" was not absolute or did not exist or an empty directory.

Action: Provide a valid absolute path.

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-20335: The move plan location is invalid.

Cause: There are five possible causes: 1. The path was not provided. 2. The path was not an absolute path. 3. The path already existed. 4. The parent path did not exist. 5. The parent path did not have write permission.

Action: Provide an absolute path to a directory that does not exist and make sure that its parent location exists and has write permission.

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-20339: Error in deploying adapters.

Cause: Adapter deployment failed.

Action: Make sure that all the specified values are correct and the domain configuration is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20340: The Plan Directory location is invalid.

Cause: There are four possible causes: 1. The path was not an absolute path. 2. The path already existed. 3. The parent path did not exist. 4. The parent path did not have write permission.

Action: Provide an absolute path to a directory that does not exist and make sure that its parent location exists and has write permission.

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-20345: Error in validating "SERVER_CONFIG".

Cause: Specified port is not valid.

Action: Make sure that valid port numbers are specified in 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-20358: Duplicate instance name.

Cause: Service for the given instance name {0} already existed.

Action: Choose a different instance name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20359: Values for all mandatory parameters are not provided.

Cause: {0} is empty.

Action: Provide a valid value for {0}

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20360: Could not connect to the AdminServer.

Cause: Specified AdminServer is down or the domain credentials are not correct.

Action: Make sure that specified AdminServer is started and the domain host, domain port, domain user and domain password values are correct.

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-20376: T2P operation is not possible.

Cause: T2P-specific binaries were missing from 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-20378: Invalid value entered.

Cause: The value of the parameter {0} was invalid.

Action: Provide a valid value for {0}.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20379: Target component information was missing for pasteConfig.

Cause: Either provide "targetComponentName(tcn)" or "targetDomainLoc(tdl)" or "targetNMHomeLoc(tnh)"parameter.

Action: Provide target component information.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20380: Invalid target Middleware Home location.

Cause: Path {0} was either an empty string or not an absolute path.

Action: Provide an absolute path for the target Middleware Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20381: Target component information was ambiguous.

Cause: Either provide "targetComponentName(tcn)" or "targetDomainLoc(tdl)" parameter.

Action: Provide target component information.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20382: Invalid domain home location.

Cause: Path {0} was either an empty string or not an absolute path.

Action: Provide an absolute path for the target domain home.

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: Oracle Home is not cloneable.

Cause: There are three possible causes for not being able to clone Oracle Home {0}: 1. Some component(s) were not cloneable. 2. Install.properties file did not have correct entries for cloning. 3. Required files needed for cloning were missing.

Action: Make sure that the Oracle Home is valid.

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: Invalid Domain home location.

Cause: Path "{0}" was not writeable.

Action: Provide a valid absolute path. For UNIX systems, make sure that the user executing the script is the same as the user who created the domain.

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: Error in examining OWSM policies.

Cause: OWSM policy examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20400: OWSM policy migration failed.

Cause: Either the managed servers targeted to OWSM application were down or the application was not in active state.

Action: Check the clone logs and managed server logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20401: Error in examining OWSM policies.

Cause: OWSM policy examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.

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-20411: Unable to update WebLogic monitoring credential in EM agent.

Cause: An internal operation failed.

Action: Check the clone log file for more details.

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: Required arguments are not provided.

Cause: An attempt was made to run pasteConfig operation by providing an non existing instance home. The following required arguments were missing :"{0}".

Action: Provide required arguments.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20428: Instance home location is invalid.

Cause: An attempt was made to run pasteConfig operation for the component by providing an existing instance home. There are two possible causes: 1. Instance did not have the required configuration files. 2. Instance was not associated with a valid Oracle Home.

Action: Provide a valid instance home location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20429: Middleware Home is invalid.

Cause: An attempt was made to run "{0}" operation of "{1}". The Middleware Home "{2}" was invalid.

Action: Provide a valid Middleware 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-20431: Component name in invalid.

Cause: The instance "{0}" was already configured with component name "{1}".

Action: Provide a unique component name.

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 component name.

Cause: There are two possible causes for the component name {0}:1. Length of the component name was either too short or too large.2. Component name had contained unsupported characters.

Action: Provide valid component name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20435: Some of the Oracle Homes are excluded during copy operation.

Cause: The following Oracle Homes will be excluded during copy operation. {0} and possible causes are:1. The Oracle Homes are registered with different inventory.2. The Oracle Homes are not clonable.

Action: Check the clone log and error file for more information.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20436: Moveplan is not correct.

Cause: The instance was registered with a non ssl domain where as moveplan had ssl information.

Action: Remove {0} config group from the moveplan and execute pasteConfig operation again.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20437: Moveplan is not correct.

Cause: The instance was registered with a ssl domain where as moveplan did not have ssl information.

Action: Provide a correct moveplan having ssl information.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20438: Instance does not have valid wls.connect.properties file.

Cause: There are two possible causes :1. Either file did not exist.2. File did not have correct entries to find out weblogic.home , keystore type and keystore location.

Action: Make sure that the wls.connect.properties file present at "{0}" is proper.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20439: MovePlan is not correct.

Cause: The config group {0} didn't have correct values for some or all of the following config properties {1}.

Action: Make sure that the moveplan has correct entry.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20440: MovePlan is not correct.

Cause: There was a mismatch betweeen moveplan and wls.connect.properties. The value of config property {0} was {1} where the corresponding value in wls.connect.properties was {2}.

Action: Make sure that the moveplan has correct entry.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20441: MovePlan is not correct.

Cause: The wls.connect.properties had no password where as moveplan's config property {0} had password or vice versa.

Action: The moveplan should have value for the password property if and only if wls.connect.properties has corresponding property.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20442: MovePlan is not correct.

Cause: The password from file mentioned in moveplan's config property {0} is not matching with the password mentioned in wls.connect.properties

Action: Make sue that the both passwords are same.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20443: Domain admin password is missing.

Cause: An attempt was made to execute pasteConfig operation in silent mode without providing domain password.

Action: In silent mode, provide domain password in command line argument.

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-20500: Arguments combination is invalid.

Cause: The -sourceNMHomeLoc was provided along with -sourceMWHomeLoc.

Action: Provide either -sourceNMHomeLoc or -sourceMWHomeLoc.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20501: Arguments combination is invalid.

Cause: The -sourceInstanceHomeLoc and/or -sourceComponentName was provided along with -sourceNMHomeLoc.

Action: Provide either -sourceInstanceHomeLoc and/or -sourceComponentName or -sourceNMHomeLoc.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20502: Arguments combination is invalid.

Cause: The -sourceDomainLoc was provided along with -sourceNMHomeLoc.

Action: Provide either -sourceDomainLoc or -sourceNMHomeLoc.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20503: Unable to resolve source Node Manager home.

Cause: The path provided with -sourceNMHomeLoc either did not exist or was not absolute.

Action: Provide an existing and absolute path with -sourceNMHomeLoc.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20504: Invalid Node Manager Home Location.

Cause: Path "{0}" was not absolute or did not exist or an empty directory.

Action: Provide a valid absolute path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20505: Target component information was ambiguous.

Cause: Either provide "targetComponentName(tcn)" or "targetNMHomeLoc(tnh)" parameter.

Action: Provide target component information.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20506: Target component information was ambiguous.

Cause: Either provide "targetDomainLoc(tdl)" or "targetNMHomeLoc(tnh)" parameter.

Action: Provide target component information.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20507: Invalid target Node Manager home location.

Cause: Path {0} was either an empty string or not an absolute path.

Action: Provide an absolute path for the target Node Manager home.

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: All managed servers were down in the provided source environment. The "copyConfig" operation requires all the managed servers to be up and running.

Action: Make sure that all managed servers are 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 Middleware Home and all Oracle Homes inside Middleware Home are 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 middleware home location validation failed.

Cause: Specified domain is not registered with the source middleware home.

Action: Make sure that specified domain home is registered in "domain-registry.xml" of source middleware 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 reassociation 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-20624: Unable to find any registered oracle home(s) in the provided middleware home.

Cause: Inventory might be corrupted or deleted.

Action: Make sure that the inventory with which the middleware home is registered is proper.

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 two possible causes: 1. Server might be down. 2. Credentials provided might be wrong.

Action: Make sure server is running and credentials are valid.

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: 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-20643: 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-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: Invalid value.

Cause: The {0} value is empty.

Action: Provide a valid value for {0} property.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20901: Unable to restore permission of a few files of the Oracle Home {0}. Check the log file {1} for details.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20902: An attempt was made to execute system prerequisites, but unable to load prerequisites jars.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20903: An attempt was made to execute system prerequisites, but unable to load OUI and engine jars.

Cause:

Action:

Level: 1

Type: UNKNOWN

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 reassociation from {0} to {1} is not supported. OPSS store will not be reassociated to {2}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20906: OPSS store reassociation 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. Reassociation 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-20912: WebLogic Server home is not valid. Make sure that Middleware Home location is valid.

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-20922: Error in starting 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-20928: OPSS policies are not migrated to target LDAP. Domain start might fail.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20929: Unable to find any valid plug-in(s) in the provided middleware home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20930: Error occurred while adding default realm data to archive.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20931: Error occurred while extracting default realm data from archive.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20932: 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-20933: At least one valid optimization flag has to be specified. Flag(s) provided are : {0}

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21001: As -sourceOracleHomeLoc has been provided, only the Oracle Home(s) specified along with this parameter will be honored.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21002: The sourceid was not provided, proceeding with default sourceid "{0}" to restore the archive.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21003: Unable to find Oracle Home(s), as inventory is not accessible.

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-21005: Cloning operation completed with warning.

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-21008: As "{0}" file does not exist, this Middleware Home will not be archived.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21009: The Middleware Home that will be included in the archive is {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21010: The Oracle Home "{0}" will be excluded as it is mentioned in exclude pattern.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21011: The archive will contain only Oracle Home(s) {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21012: The archive will be restored fully at {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21013: Trying to find Oracle Home(s) present under Middleware Home {0}...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21014: Adding specific files from Oracle Home {0} that will be required to execute system prerequisites during pasteBinary ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21015: Adding all required files for execution of system prerequisites finished.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21017: Adding Oracle Home {0} to the archive finished.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21018: Extracting at "{1}" location started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21019: Extracting at "{1}" location finished.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21020: Configuration for Oracle Home {0} is in progress ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21021: Configuration for Oracle Home {0} 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: Restoring Middleware Home at "{0}" from archive "{2}" started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21026: Restoring Middleware Home at "{0}" from archive "{2}" finished.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21027: Provided invPtrLoc was empty.

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-21033: Unable to find any Middleware Home or Oracle Home for archiving.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21034: The archive will contain only the Middleware Home {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-21038: The archive will contain both Middleware Home {0} and Oracle Home(s) {1}.

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-21041: Middleware 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-21043: J2EE component archive # {0}, sourceid {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-21055: In {1} seconds, {0}% has completed.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21057: Execution of system prerequisites for Oracle Home {0} 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-21062: The Java home {0} found from the system property was not pointing to a Java home, it might pointing to jre home, trying to check if its parent is a Java home

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21063: The {0} is not a valid Java home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21064: Updating Oracle Home information for Oracle Home {0} ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21065: Updating Oracle Home information completed for Oracle Home {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21066: Updating Oracle Home information failed for Oracle Home {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21067: Unregistering all instances(which were present in source domain) from target domain...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21068: Trying to unregister instances {0} from domain...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21069: All the instances are unregistered from domain successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21070: Unable to unregister following instances {0} from domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21071: Permission file created with warnings.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21072: Unregisteration of all instances(which were present in source domain) from target domain completed successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21073: INSTANCE archive # {0}, sourceid {1}

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21074: Trying to retrieve domain name ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21075: Domain name is {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21076: Trying to check whether Weblogic monitoring Credential for EM is already set in domain or not ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21077: Weblogic monitoring Credential for EM is already set.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21078: WLS credential is not set in EM, trying to set it ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21079: Updating Weblogic monitoring Credential for EM in the domain ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21080: Weblogic monitoring Credential is updated successfully.

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-21088: ASInstance {0} is configured with following components: {1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21089: Oracle Home {0} has following t2p plugins : {1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21090: Provide invPtrLoc:

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21091: Usage: <path to java> -jar <path to cloningclient.jar> <command> <command>: <Clone command> <Clone command>:

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-21096: Process complete in {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21097: Addition of the Oracle Home {0} to the archive started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21098: Enter domain Administrator password:

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21099: From instance {0}, the type and name of the components on which T2P will be performed are :{1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21100: From instance {0}, the name of the components on which T2P will be performed are :{1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21101: Under instance {0}, there are no movable components.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21102: T2P cannot be performed on all components present under instance {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21103: Log path "{0}" should be absolute and existing directory has write permission. This condition was not satisfied.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21104: The number of Oracle Homes and Middleware Homes present in the archive is {0} and {1} respectively.

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-21107: T2P cannot be performed on all components present under instance {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21108: Archiving movable components ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21109: Archiving of movable components completed successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21110: As the archive has only one Middleware Home and no Oracle Home, targetLocation should not exist, and its parent should exist.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21111: As the archive has no Middleware Home and one or more Oracle Home(s), targetLocation should exist, so that all the Oracle Home(s) will be restored under it.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21113: As the number of Oracle Home(s) {0} and Middleware Home {1}, the Middleware Home will be restored at nonexistent targetLocation, and all the Oracle Home(s) will be restored under it.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21114: Unable to find JDK JAVA Home from registry.xml file.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21115: Trying to find JRockit JAVA Home from registry.xml file.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21116: JAVA Home found from Middleware Home is {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21117: Path {0} is invalid. Either it is not absolute or does not have valid characters. The supported characters are "{1}" These three characters "_.-" are not allowed in the beginning.

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-21120: Adding all files detail to the archive started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21121: Adding all 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-21124: Oracle Inventory has updated successfully.

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: Oracle Home pasteBinary post validation, inventory validation started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21128: Oracle Home pasteBinary post validation, symbolic link validation started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21129: Under Middleware Home {0}, one {1} Oracle Home is already present and the Oracle Home path is {2}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21130: The component {0} under Oracle Home {1} is not cloneable.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21131: Updating Windows shortcut for Oracle Home {0} started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21132: Updating Windows shortcut for Oracle Home {0} finished.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21133: To archive only the Middleware Home provide "-excludeOracleHomes true" as command-line argument.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21134: Creating cloner objects for components ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21135: Cloner objects are created for components.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21136: Creating and starting ASInstance ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21137: ASInstance created and started successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21138: Executing all component cloner objects ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21139: Execution of all component cloner objects completed successfully.

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-21150: Shortcut name "{0}" will be used.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21151: Shortcut name "{0}" is already present.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21152: New Oracle Home folder name in shortcut will be "{0}".

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21154: Checking free space availability for copyBinary operation.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21155: Required free space is available for copyBinary operation.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21156: Extracting all the homes from the archive file. Extraction time will vary depending upon the archive size ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21157: The size of the all homes are {0} GB.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21161: In the domain the available instance name(s) and their corresponding location(s) are {0}.

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: Addition of the Middleware Home {0} to the archive started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21167: Creating archive of Middleware Home {0} started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21168: Creating archive of Middleware Home {0} finished.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21169: Adding archive of Middleware Home {0} to the main jar file started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21170: Adding archive of Middleware Home {0} to the main jar file finished.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21171: Extracting Middleware Home jar file from main jar ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21172: Extracting Middleware Home jar to the target location {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21178: The source Middleware Home was not installed with JDK or JRockit.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21179: The new Middleware Home will be restored using Java home {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21181: The instance is registered with the domain with following details: domainHost={0}, domainPort={1}, domainAdminUser={2} and protocol={3}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21182: Ignoring ssl information mentioned in the moveplan as either domain details were not provided in command line or instance was existing and not registered with the domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21183: Will try to use domainHost {0}, domainPort {1}, domainAdminUser {2} as used by instance.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21184: ASInstance will be configured without domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21185: ASInstance will be configured with domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21186: Validating domain connection.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21187: Connection obtained successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21188: Component will be configured without domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21189: Component will be configured with domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21190: Instance {0} is not registered with any domain, so the domain parameters are ignored.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21191: Instance "Create & Start" step failed.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21192: Target Instance Directory: {0} already exists. Skipping Instance Creation Step.

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-21194: Starting Instance Failed.

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-21202: Oracle Common home "{0}" exists, and is valid.

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-21207: There is an existing component with the same name: {0} under the instance: {1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21208: Setting the component name to: {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21209: Creating instance where the instance home location is {0} and the instance name is {1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21210: Instance {0} created and started successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21211: Registering instance with the domain where the host is {0} and the port is {1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21212: Instance is registered with domain successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21213: EMAgent creation started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21214: EMAgent creation finished.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21215: Middleware Home "{0}" has non clonable Weblogic binaries. Checking for Oracle Homes ...

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-21219: Validating whether service for the given instance name "{0}" already exists or not.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21220: Service for the given instance name "{0}" does not exist.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21221: SEVERE

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21222: System prerequisite specific files are not present in the Oracle Home, continuing...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21224: Starting Oracle instance {0}...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21225: Oracle instance {0} started successfully.

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-21244: Only unique {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-21265: Stopping AdminServer...

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-21272: {0} OPSS data...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21273: 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-21274: Warning: The following optimizationHints flag are not supported and hence ignoring - {0}

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21275: Warning: -domainAdminPassword argument has been deprecated. Use -domainAdminPasswordFile instead.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21290: Validating WLS connection and SSL information present in the moveplan ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21291: Validating SSL information present in the moveplan, if any ...

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-22006: As sourceMWHomeLoc and sourceOracleHomeLoc are empty, archive will not have any Middleware Home and Oracle Home.

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-22009: Middleware Home and/or Oracle Home unarchive location and user visible sourceid map: "{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-22011: Execution of the command "{0}" started at "{1}" and it will take approximately 4 minutes.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22012: Time taken to execute the command "{0}"="{1}".

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22013: Adding Middleware Home jar {0} to final jar with archive entry point={1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22014: Restoring Middleware Home using command "{0}" started ...

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22015: Restoring Middleware Home using command "{0}" finished.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22016: The javahome from Middleware Home 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-22031: Was unable to determine top component name from Oracle Home "{0}".

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22032: Parent of Oracle Home {0} is not a valid Middleware Home.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22038: The java home found from Middleware Home is={0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22039: The Weblogic server home found from Middleware Home 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-22059: Number of entries (each file and folder) that will be included in the archive is={0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22060: Number of entries whose permission could be handled in permission file={0}.

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-22068: The number of files whose permissions are written to permission file={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-22070: Unable to set permission of the following files.

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 Middleware Home "{0}" was invalid.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22080: The Middleware Home "{0}" was either dummy or invalid as the file {1} 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-22091: Either instanceHomeLocation or componentName or both are empty.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22092: The name and location of asinstances registered with the domain are={0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22093: The componentType is empty.

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-22095: The instanceHomeLocation {0} was not valid.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22096: The search string is empty.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22097: The instance.properties file {0} is invalid.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22098: While finding componentType for a componentName, all components found are: {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22099: Either componentName or componentType or instanceHomeLocation is empty.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22100: The specified parameters for component copyConfig are: componentName={0}, componentType {1}, instanceHomeLocation={2} and instanceName={3}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22110: As instanceHomeLoc is existing, and user has not provided instance name, so setting instance name to {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22112: As instanceHomeLoc is existing, and user has not provided Oracle Home, so setting Oracle Home to {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22117: Any one parameter from domainHost,domainPort,domainAdminUserName was not provided.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22118: The domain parameters are: domainHost={0}, domainPort={1}, domainAdminUserName={2}

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22119: Setting domain detail as domainHost={0}, domainPort={1}, domainAdminUserName={2} found from instance home.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22125: The domain password was empty.

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-22143: Parameter validation is complete. User visible sourceid is set to : "{0}".

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22144: Parameter validation is complete. Setting exclude Oracle Home to "{0}".

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22145: Unable to decide restore choice for default sourceid.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22146: In the archive, number of Middleware Home(s)={0} and number of Oracle Home(s)={1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22147: For sourceid {0}, the restore location {0} was either empty or already used by other sourceid. So existing restore location and sourceid map is={2}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22149: No of sourceid(s)="{0}" and correspond targetlocation(s)="{1}" are not same, but it should be same.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22152: path_upto_Scripts="{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-22155: After setting system environment property the environment values are: 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-22156: To run prerequisites, platform_directory under Scripts/prereq/ 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 Oracle Home {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22168: Status of adding oui jars to system classloader from Oracle Home {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-22173: Trying to validate Oracle Home {0} by validating its top component name and version.

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-22179: Extracting Middleware Home jar file from main jar under {0} location.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22180: Extracting Middleware Home jar {0} to the target location {1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22181: Before executing restore script, either javapath {0} or jrepath {1} did not exist.

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-22186: Invoking runConfigure for Oracle Home {0} with invPtrLoc "{1}".

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-22190: Taking backup of oraparam.ini where source path was {0} and new path was {1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22191: Restoring oraparam.ini where source path was {0} and new path was {1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22192: To update "JRE_LOCATION", Java home found from Middleware Home {0} 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-22197: Middleware Home install location is:{0}

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22198: Number of files from jar file entries for permission carrying: {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-22201: The oracle.installer.invPtrLoc after running prerequisites={0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

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

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22205: The oracle.installer.invPtrLoc before running runConfigure={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-22208: Required space is available for copyConfig operation.

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-22210: Number of entries in the file, which will contain all file paths={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-22215: Oracle Home {0} is valid as its top component name {1} and version {2} are valid.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22216: Source Oracle Home location 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-22233: For Oracle Home {0}, the name found from the inventory is={1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22234: Removing Oracle Home entry from shortcut list where folder Name="{0}" and item Name="{1}".

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22235: Source Oracle Home folder name in shortcut was="{0}".

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22236: Modified Oracle Home folder name pattern is="{0}".

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-22243: Restoring oraparam.ini where source path was {0} and new path was {1} status is={2}.

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-22256: Source jdk or jrockit home path {0} was not started with source Middleware Home path {1}.

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-22261: The final sourceid(s) "{0}" and their corresponding targetlocation(s) "{1}" will be taken care.

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-22272: Could not copy modified move plan with commented OPSS_SECURITY "configGroup" .

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22273: Listen Address of {0} Managed Server is {1}.

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-22276: Checking whether Oracle Home {0} can be archived or not.

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: Archive location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23002: Inventory location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23003: Flag to ignore free space check. Default value is false.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23005: Existing log directory location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23006: Source instance home location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23007: Source component name

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23008: Options(alias)

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23009: To create archive

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23010: Absolute path of archive location.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23011: Path should not exist and should have right privilege to create the file.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23013: Absolute path of Middleware Home location.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23014: Absolute path of inventory pointer (oraInst.loc file ) location to discover Oracle Homes present under the Middleware Home. This flag is supported in UNIX platforms only.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23020: Absolute path of a directory location with right privilege to create cloning log and error file. Default location is system temporary location.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23021: Flag to run the T2P operation in a non-interactive mode. Default value is false.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23022: Parameters for copyConfig of a component

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23023: Name of the existing component which will be archived.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23024: Absolute path of an existing instance which contains the component.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23025: Description:

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23027: Example:

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23028: Assumption:

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23029: Middleware Home

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23030: Oracle Home

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23031: Oracle inventory pointer location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23032: Instance home location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23033: Component name

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23034: To create an archive of a Middleware Home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23035: This archive will contain the Middleware Home and all the Oracle Home(s) under it, that is the archive will have

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23036: No Oracle Home is installed under this Middleware Home

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23037: This archive will contain only the Middleware Home as no Oracle Home is installed under it, that is the archive will have only

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23042: To create archive of oid1

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23043: To create archive of ovd1

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23044: Requirement

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23045: 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-23046: NOTE:

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23047: The parameter {0} will accept only one Middleware Home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23050: The parameter {0} can be accompanied with the {1} parameter only.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23055: CopyBinary of Middleware Home, Oracle Home and component at same time is not possible.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23057: In Windows, before creating archive of Middleware Home, make sure that no java or Weblogic processes are running from that Middleware Home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23060: Before creating archive of Middleware Home, make sure that the Weblogic product directories(like Weblogic server, coherence) are installed inside that Middleware Home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23061: If Operating System is {0}, then provide {1} as argument to Java.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23062: The target Middleware Home location cannot be inside another Middleware Home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23063: <Component specific>

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23064: Source Middleware Home location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23101: Absolute path of target location.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23102: Extra session variables for OUI runInstaller.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23103: Java home path.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23104: Absolute path of inventory pointer location.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23105: New name for the component to be restored.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23106: Absolute path of instance home under which component will be restored.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23107: Name of the instance under which component will be restored.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23108: Absolute path of Oracle Home associated with instance home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23109: Extra session variables to OUI runInstaller can be passed as key=value pairs. Multiple session variables can be passed as comma separated pairs.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23110: To restore from archive

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23111: Absolute path of the archive location. Make sure that the location exists.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23112: detail

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23113: Absolute path to restore Middleware Home. This absolute path can be either a non-existing or an existing empty directory.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23114: Flag to execute system prerequisites before restoring the Oracle Home(s). Default value is true.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23115: Absolute path of inventory pointer (oraInst.loc file ) location to register Oracle Homes with the central inventory. This flag is supported in UNIX platforms only.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23117: Java home to configure Middleware Home in the case when the archived Middleware Home does not contain a JDK or JRockit.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23118: New name for the component to be restored

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23119: Absolute path of instance home under which component will be restored. If instance does not exist, path can be either a non existing or an existing empty directory.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23120: Name of the instance under which component will be restored

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23121: Absolute path of the Oracle Home that will be used to configure the component.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23122: Absolute path of instance home under which component will be restored. Path can be either a non-existing or an existing empty directory.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23123: Domain host name

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23124: Domain port number

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23125: Domain Admin user name

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23126: Domain Admin password file

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23127: Database host name

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23128: Database listener port

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23129: Database service name

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23130: ODS schema password file

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23131: ODSSM schema password file

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23132: Namespace

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23133: OID admin password file

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23134: OID non SSL port

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23135: OID SSL port

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23140: OVD admin port

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23141: OVD http port for default listener

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23142: OVD ldap non ssl port default listener

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23143: OVD ldap ssl port default listener

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23144: To restore the full archive. To know the entities present in the archive, Execute "{0}" command.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23145: Middleware Home, Oracle Home pasteBinary

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23146: Archive has Weblogic binary and one or more Oracle Home. Restore full archive

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23147: Command:

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23148: Archive has one Middleware Home and two Oracle Homes(let {0} and {1})

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23149: Here {0} need to be either a non existing or an existing empty directory. {1} and {2} will be restored under {0}. Oracle Home folder name cannot be changed

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23150: Archive will be restored as follows: {0} {1} {2}

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23151: Absolute path of the Oracle Home that will be used to configure the instance home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23161: Archive has only one Middleware Home but no Oracle Home. Restore full archive

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23162: Here {0} need to be either a non existing or an existing empty directory.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23168: 1. All the entities present in the archive will be restored during pasteBinary operation. 2. When Oracle Home(s) is restored, make sure that the Oracle inventory has no entry for that target Oracle Home. 3. If targetInstanceHomeLoc exists, then targetInstanceName and targetOracleHomeLoc are optional. 4. If targetInstanceHomeLoc is already registered with domain, then domainHostName, domainPortNum and domainAdminUserName are optional.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23169: OID Specific NOTE: 1.If source and target database are different (if either host or port or service name is different) a) Then source oid and target oid name should be the same. b) Target database should have footprint of source OID Component. 2.If source and target database are same. a) Then source oid and target oid name should be different.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23201: List contents of an archive.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23202: List content of archive, that is, list all the entities present in the archive.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23203: Output:

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23204: Usage: <path to java> {0} <path to cloningclient.jar> <command> <command>:=<Clone command> <Clone command>:= | {1} | {2} | {3} For help on a particular command, use [ <path to java> {0} <path to cloningclient.jar> {4} <command>]

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23205: Usecase-{0}

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23206: <path to java> {0} <path to cloningclient.jar>

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23207: is inside

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23209: Middleware Home archive # {0}, home location={1}

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23210: Oracle home archive # {0}, home location={1}

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23211: For Component, if instance name is {0}, and component name is {1}

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23212: Component archive # {0}, instance name@component name={1}

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23213: Oracle Home path

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23214: Domain location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23215: Absolute path of the source Oracle Home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23216: Absolute path of the source Domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23217: Parameters for copyConfig of J2EE component.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23218: Absolute path of the Target domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23220: <J2EE Component specific>

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23221: To create archive of a soa domain

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23222: To restore an OID component

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23223: To restore an OVD component

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23224: To restore a SOA domain

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23225: Absolute path of the Target Oracle Home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23226: Oracle Process Manager ({0})

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23230: Absolute location of java home

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23235: To create archive of a Middleware Home (and all valid Oracle Home(s) under it).

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23240: To restore the full archive containing Middleware Home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23245: 1. All the entities present in the archive will be restored during paste binary operation. 2. When Oracle Home(s) is restored, make sure that the Oracle inventory has no entry for that target Oracle Home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23250: To create the archive of an Oracle system component or a WebLogic J2EE Domain or a Node Manager.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23255: To restore the full archive containing an Oracle system component or a WebLogic J2EE Domain or a Node Manager.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23260: 1. If targetInstanceHomeLoc exists, then targetInstanceName and targetOracleHomeLoc are optional. 2. If targetInstanceHomeLoc is already registered with domain, then domainHostName, domainPortNum and domainAdminUserName are optional.

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-23291: Paste Security Policy 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-23299: Migrating Policy and Credential store.

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-23318: Absolute path to directory where moveplan is to be extracted

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-23320: Absolute path to a non-existing directory where the t2p move plan will be extracted along with other J2EE Configuration Plans.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23321: To extract t2p move plan along with other J2EE Configuration Plans.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23322: Note: The t2p moveplan or multi archive moveplan contains the endpoint configuration for J2EE and System Component configuration. For details on how to modify the t2p moveplan or multi archive moveplan, refer to the Chapter "Cloning Oracle Fusion Middleware" of Fusion Middleware Guide

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23323: Source WebLogic Domain location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23324: Middleware Home location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23325: Source Domain Admin Server Host Name

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23326: Source Domain Admin Server Port

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23327: Source Domain Admin Server User Name

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23328: Source Domain Admin Server User Password File location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23329: Absolute path of Source J2EE Domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23330: Absolute path of Middleware Home location.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23331: Source Domain Admin Server Host Name.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23332: Source Domain Admin Server Port.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23333: Source Domain Admin Server User Name.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23334: Absolute Path to the file containing Domain Admin Server User Password.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23335: To create archive of ohs1

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23336: To create archive of WebLogic J2EE domain

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23337: Absolute path of target J2EE Domain. Path can be either a non existing or an existing empty directory.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23338: Absolute path of existing target Middleware Home location.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23339: Absolute path to the T2P Move Plan xml document extracted during extract plan operation. Refer to the Chapter "Cloning Oracle Fusion Middleware" of Fusion Middleware Guide for more details.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23340: Target WebLogic Domain location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23341: Target Middleware Home location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23342: Absolute path to the T2P Move Plan

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23343: Oracle System component specific parameters

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23344: WebLogic J2EE domain specific parameters

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23345: WebLogic domain location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23346: Source Middleware Home

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23347: Domain Admin Server Host Name where the system component will be registered

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23348: Domain Admin Server Port

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23349: Domain Admin Server User Name

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23350: Domain Admin Server User Password File location

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-23354: Target WebLogic Application Directory

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23355: Absolute path of target J2EE domain application directory. Path can be either a non existing or an existing empty directory.

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-23364: Archive(s) location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23365: Absolute path to directory where moveplan is to be extracted

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23366: Absolute path of the archive(s) location. Make sure that the location(s) exist(s). 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-23367: Absolute path of either a non existing or an existing empty directory where 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-23368: To extract moveplan or multi archive moveplan along with other J2EE configuration plans.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23369: Exporting OWSM policies...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23370: OWSM policies are not exported during "copyConfig". OWSM policies will not be migrated.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23371: Error in importing OWSM policies to target domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23372: Adding OWSM policies to archive.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23373: Importing OWSM policies...

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-23385: Flag for optimization while creating multi archive moveplan

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23386: Provide the flags as a comma separated list. (In Windows, provide the comma separated list within double quotes) The supported values are :{0} Based on flag, specific optimization of multi archive moveplan will take place. Flag description: fusionapps (fa) : You need to provide this hint always. This simplifies the move plan for Oracle Fusion Applications. sameSchemaNameSinglePassword (ssnsp) : The same password is used for all schemas associated with a particular database specified in DATASOURCE section of the moveplan. However, the passwords for APPID users are different. You are prompted to provide the password only once for each database. Therefore, you need to pass a separate password for each of the APPID users. rpdDataSource (rpdds) : The same password is used for all schemas associated with a particular database specified in RPD_CONFIG section of the moveplan. If ssnsp flag is provided, then automatically this flag will be set to true.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23387: Oracle ASInstance specific parameters

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23388: To create archive of asinstance

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23389: Flag to execute OPSS data export/import. Default value is true.

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-23501: Unable to create the directory {0}.

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 Middleware 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 Middleware Home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23505: Unable to derive Java Home from the target Middleware 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}. Make sure values provided are correct in moveplan. If "AdminServer Listen Port" is SSL port, provide value of "Custom Trust KeyStore File" of the domain if domain keystore type is Custom Trust.

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-23523: Node Manager specific parameters

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23524: Source nodemanager home location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23525: Absolute path of Source Node Manager home.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23526: To create archive of Node Manager

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23527: Target Node Manager Home location

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23528: Absolute path of target Node Manager home location. Path can be either a non existing or an existing empty directory.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23529: Additional parameters required for product specific operations. The additional parameters should be passed as key=value pairs. Multiple parameters may be passed by separating each key=value pair by a comma. i.e key1=value1,key2=value2,key3=value3

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23531: Flag to execute MDS export/import. Default value is true.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23532: Custom Trust KeyStore File location

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: Warning: Valid values are not provided for Custom Identity KeyStore configuration. Source configuration will be retained in the target.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24005: OVD cloning has failed.

Cause: OVD component pasteConfig parameter validation failed.

Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24006: OVD cloning has failed.

Cause: JPS file of the source OVD component is not available.

Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24007: OVD cloning has failed.

Cause: OVD creation failed.

Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24009: OVD cloning has failed.

Cause: Ports were not updated successfully.

Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24010: Port validation has failed.

Cause: Unable to assign port for {0}.

Action: Make sure that some ports are free.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24011: Oracle Home does not have supported binaries.

Cause: An attempt was made to use an incompatible top component based Oracle Home.

Action: Provide a valid Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24012: Oracle Home does not have supported binaries.

Cause: An attempt was made to use an incompatible component based Oracle Home.

Action: Provide a valid Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24301: Source OVD component listeners were configured with following details. {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24302: Listener {0} will be configured with port {1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24303: Updating configuration files.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24304: Updating configuration files completed.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24307: Validating OVD Admin port.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24308: Validating OVD LDAP port.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24309: Validating OVD LDAP SSL port.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24310: Validating OVD HTTP port.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24312: Creating OVD component.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24313: OVD component created successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24314: Stopping OVD component.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24315: OVD component stopped successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24316: Password file is either not provided or invalid for the adapter "{0}". Nothing will be changed for this adapter configuration.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24317: Null parameter(s) found during OVD parameters validation.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24318: Starting OVD component.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24319: OVD component started successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24320: Updating OVD component registration with admin server started...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24321: OVD component registration with admin server completed successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24322: Exporting OVD component server certificate into EMAGENT started...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24323: Exporting OVD component server certificate into EMAGENT completed successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24324: Restarting EMAGENT...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24325: EMAGENT restarted successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24326: Updating OVD certificate during cloning started...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24327: Updating OVD certificate during cloning completed successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24328: Stopping Oracle instance {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24329: Starting Oracle instance {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24330: Collecting OVD adapter information, if any ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24331: Performing OVD adapter parameter validation ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24332: Updating OVD adapters ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24333: Setting OVD server certificate in EMAGENT started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24601: Before updating listener_os.xml file {0}, the listener port details are : {1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24602: Updating listeners_os.xml file {0}...

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24603: Updating listeners_os.xml file is finished.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24604: Updating ovd-logging.xml file {0}...

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24605: Updating ovd-logging.xml file is finished.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24606: Building OracleASComponent object for OVD Component.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24607: OracleASComponent object for OVD Component is built successfully.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24608: Building OracleASComponentProperties object for OVD Component.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24609: OracleASComponentProperties object for OVD Component is built successfully.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24612: Source OVD component port information : {0} and instance information : {1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24613: Source OVD component version information : {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24614: Nothing to do in doPostCreateClone for OVD component during copyConfig operation.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24615: All ports detailed information from xml file {0} is : {1}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24616: OVD parameters for pasteConfig : {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24617: The {0} component version : {1}, but it should be within {2} and {3}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24618: The {0} component passed the version verification.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25001: Invalid component name.

Cause: Because source and target database are different, then target OID component name {0} should be the same as source OID component name {1}.

Action: Provide same component name as that of source OID component name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25002: Invalid Oracle directory server schema password.

Cause: Oracle directory server schema password was empty.

Action: Provide a valid Oracle directory server schema password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25003: Invalid ODSSM schema password.

Cause: Schema password for ODSSM was empty.

Action: Provide valid ODSSM schema password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25004: Invalid Oracle Internet Directory admin password.

Cause: Oracle Internet Directory admin password was empty.

Action: Provide valid Oracle Internet Directory admin password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25005: Database parameters validation has failed.

Cause: Either database host, port, or service name was incorrect.

Action: Provide correct database host, port, and service name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25006: Oracle directory server schema validation has failed.

Cause: Either database connection string or Oracle directory server schema username or password was not correct.

Action: Provide correct database connection string and Oracle directory server schema username or password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25007: Schema validation for ODSSM has failed.

Cause: Either database connection string or ODSSM schema username or password was not correct.

Action: Provide correct database connection string and ODSSM schema username and password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25008: Namespace value is missing.

Cause: The namespace value was empty.

Action: Provide namespace value.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25009: OID cloning has failed.

Cause: Wallet file of the source OID component is not available.

Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25010: Database connection has failed.

Cause: Either host name, port number, SID, Service Name, schema user, or schema password was empty.

Action: Make sure that all the parameters are valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25012: Invalid OID instance name.

Cause: An OID instance is already running with the same name.

Action: Provide different database details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25013: Invalid database.

Cause: The postStart is not performed in the database.

Action: Make sure that the database is already configured with an OID.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25014: Invalid target component name for OID.

Cause: Database is already configured with the name, "{0}".

Action: Provide different name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25015: Invalid target component name for OID.

Cause: During T2P scenario, database must contain the same OID entry, i.e. "{0}".

Action: Make sure that the database already has source information.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25016: Oracle directory server schema password missing.

Cause: An attempt was made to clone OID component in silent mode without providing valid ODS schema password.

Action: Provide ODS schema password in a secured file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25017: ODSSM schema password missing.

Cause: An attempt was made to clone OID component in silent mode without providing a valid ODSSM schema password.

Action: Provide ODSSM schema password in a secured file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25018: OID admin password missing.

Cause: An attempt was made to clone OID component in silent mode without providing valid OID admin password.

Action: Provide OID admin password in a secured file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25019: Oracle Home does not contain the supported binaries.

Cause: An attempt was made to use an incompatible top component based Oracle Home.

Action: Provide a valid Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25020: Oracle Home does not contain the supported binaries.

Cause: An attempt was made to use an incompatible component based Oracle Home.

Action: Provide a valid Oracle Home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25301: Enter ODS schema password :

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25302: Enter ODSSM schema password :

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25303: Enter OID Admin password :

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25304: Database parameter(s) are empty.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25305: Database details from tnsfile is empty and provided database detail(s) are also empty.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25306: Database details from tnsfile is not empty but provided database detail(s) is empty.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25307: Database details from tnsfile and provided database details are different.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25308: Setting database details as follows: DB_HOST {0}, DB_PORT {1}, DB_SERVICE {2}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25309: Source OID was configured with following database details, database host {0}, database port {1}, database service name {2}. To use the same database, provide these values as argument.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25310: The postStart has already been performed in the database.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25312: Source OID component was configured with following details. non-SSL port {0}, SSL port {1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25313: Validating Oracle Internet Directory ldapSSLPort.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25314: Validating Oracle Internet Directory nonSSLPort.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25315: Source OID {0} was associated with database host {1} and service name {2}, and port number {3}. An attempt is made to associate target OID with same database and service name. The target OID component name is the same as the source OID component name. So source OID will not work properly but target OID will work. If you provide a unique name (database should not be configured with this name) for target OID component, then other installed OIDs will work properly.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25316: Starting OID component...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25317: OID component started successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25318: Stopping OID component.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25319: OID component stopped successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25320: Null parameter(s) found during OID parameters validation.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25321: Creating OID component...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25322: OID component created successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25323: The port "{0}" is free for use.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25324: The port "{0}" is not free for use.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25325: The provided port "{0}" was either empty or not free, trying to use port "{1}".

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25327: Unable to calculate new port.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25328: New value for port is "{0}".

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25330: Database is already configured with following OID instance(s) {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25331: Post-create configuration for OID component started...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25332: Post-create configuration for OID component completed successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25333: ODS schema validation completed successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25334: ODSSM schema validation completed successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25601: Source OID component port information : {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25602: Source OID component version information : {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25603: Nothing to do in doPostCreateClone for OID component during copyConfig operation.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25604: OID parameters for pasteconfig : {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25605: Building OracleASComponent object for OID component.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25606: OracleASComponent object for OID component is built successfully.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25607: Building OracleASComponentProperties object for OID component.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25608: OracleASComponentProperties object for OID component it built successfully.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25609: The {0} component version is : {1}, but it should be within {2} and {3}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25610: The {0} component passed the version verification.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-26001: OHS T2P property file is invalid.

Cause: Either property file did not exist or had invalid inputs.

Action: Make sure that the property file {0} has a valid entry.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-26002: OHS cloning has failed.

Cause: OHS creation failed.

Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-26003: Error in validating listen host and port.

Cause: The causes were:{0}

Action: Make sure the listen host and port values provided are correct and the ports are free on the corresponding host.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-26004: Unable to obfuscate plsql database password.

Cause: An internal operation failed.

Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-26005: Unable to update and obfuscate oradav password.

Cause: An internal operation failed.

Action: Check the clone log file for more details and update and obfuscate oradav password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-26007: Unable to update webgate configuration.

Cause: Update of webgate configuration details in webgate conf file failed.

Action: Check the clone log file for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-26008: Primary OAM server update has not happened.

Cause: Unable to calculate httpd.conf file path.

Action: Update primary OAM server details webgate configuration file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-26009: OHS T2P failed.

Cause: Unable to start OS component.

Action: Check clone log and error file and ohs log file {0} for root cause.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-26101: Null parameter(s) are found during OHS parameters validation.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26102: Creating OHS component...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26103: OHS component created successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26104: Stopping OHS component...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26105: OHS component stopped successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26106: Capturing WebGate configuration, if any ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26107: Webgate install directory updated successfully in configuration files.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26108: Starting OHS component...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26109: OHS component started successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26110: Validating config properties of config group {0}...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26111: Config properties of config group {0} are validated and updated.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26113: Virtual port {0} is not in listen port list.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26114: Setting virtual port to {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26115: Virtual port is not in the new listen port list. Leaving this virtual host port as it is.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26116: Updating webgate specific configuration, if any ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26117: The port {0} is not free. Assigning new port {1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26118: Archive of {0} files started, if any...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26119: Archive of {0} files finished.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26120: Restoring {0} files from the archive started ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26121: Restoring {0} files from the archive completed.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26122: Updating instance location, component name and Oracle Home ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26123: Instance location, component name and Oracle Home updated successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26124: Updating directive and container...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26125: Directive and container are updated successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26127: Trying to validate move plan and updating, if required...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26128: Updating all xml files under {0}...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26129: All xml files under {0} are updated successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26130: Updating all configuration files ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26131: All configuration files are updated successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26133: Configuration file {0} does not exist. Unable to run file fixer.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26134: In source environment, configuration file {0} was outside of the instance home. In target environment, trying to restore to same location.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26135: An attempt was made to restore configuration file at {0}, but this path already exists. So configuration file will not be restored again.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26136: Extracting configuration file under {0}...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26137: Configuration file {0} is restored successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26138: An attempt was made to restore {0} directive at {1}, but this path already exists. So directive will not be restored again.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26139: Extracting directive files under {0}...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26143: Obfuscating PLSQL database password, if exists.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26144: No configuration file carries PLSQL database password.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26145: Obfuscation of PLSQL database password did not happen.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26146: Configuration file {0} was not restored from the archive. Obfuscate will not be performed.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26147: Configuration file {0} does not exist. Obfuscate will not be performed.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26148: Updating password field in the configuration file {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26149: Unable to retrieve password for {0} from file {1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26150: Unable to update password field in the configuration file {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26151: Password field is updated in the configuration file {0} successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26152: Obfuscating PLSQL database password...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26153: PLSQL database password obfuscated successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26154: Unable to obfuscate PLSQL database password.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26155: Restoring permission of configuration files...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26156: Permission of configuration files are restored successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26157: Unable to restore permission of configuration files.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26158: Unable to update password field in the configuration file {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26159: Validating move plan...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26160: From move plan, the name of the property is {0}, and its value is empty. Value cannot be empty.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26161: From move plan, the name of the property is {0}, and its value {1} is not a valid integer. It should be a valid integer.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26162: Updating oradav configuration file, if exists ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26163: Updating oradav configuration file ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26164: Obfuscating oradav password...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26165: Oradav password is obfuscated successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26166: Unable to obfuscate oradav password.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26167: Oradav configuration file is updated successfully.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26168: Unable to update oradav configuration file.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26169: Updating webgate install directory, if present ...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26170: Webgate install directory is updated successfully in configuration files.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26171: Validating config properties of config group {0}...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26172: Config properties of config group {0} are validated.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26301: Building OracleASComponent object for OHS component...

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-26302: OracleASComponent object is created successfully.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-26303: Building OracleASComponentProperties object for OHS component ...

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-26304: OracleASComponentProperties object is created successfully.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-26305: OHS parameters for pasteConfig operation are : {0}.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-26306: Printing {0} move plan ...

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-26307: Updating configuration file {0} through file fixer ...

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

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

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

CLONE-32010: One or more ADF Connection types for {0} are not supported and will not be included in the moveplan.xml.

Cause: One or more ADF Connection MBean does not provide the movableProperty annotation for at least one attribute.

Action: Validate that all ADF Connection MBean in your application have at least one property with movableProperty annotation with a value of "true".

Level: 1

Type: WARNING

Impact: Other

CLONE-32020: ADF Connection MBean {0}.{1} is read only. Changes for this ADF Connection will not be applied.

Cause: The ADF Connection MBean is read only.

Action: Validate that your application is configured with a writable Oracle MDS.

Level: 1

Type: WARNING

Impact: Other

CLONE-32100: Application {0} does not have ADF Connection MBean properties.

Cause: Application {0} does not have ADF Connection MBeans.

Action: Validate that the ADF web application module's web.xml was configured for ADF Connection MBeans or if the application does not have any ADF Connections.

Level: 1

Type: WARNING

Impact: Other

CLONE-32110: No ADF Domain Config MBeans were detected in the source domain, and therefore no ADF domain config information will be included in your move Plan.

Cause: ADF domain does not have ADF domain config MBeans.

Action: Validate that the ADF web application module's web.xml was configured for ADF domain config MBeans or if the application does not have any ADF domain configuration.

Level: 1

Type: TRACE

Impact: Other

CLONE-32500: No Move Plan available.

Cause: Either ADF T2P plugin copy command failed, or the file is missing or corrupted.

Action: Validate that the Move Plan is valid after extraction from the copy command result.

Level: 1

Type: WARNING

Impact: Other

CLONE-33000: Unable to apply ADF Connection properties for Application "{0}"

Cause: This could be caused by an invalid Oracle MDS configuration in your application or a failure while attempting to apply attributes using JMX.

Action: Please validate that the application is configured with writable Oracle MDS.

Level: 1

Type: ERROR

Impact: Other

CLONE-33010: Start to run T2P ADF Connection Plugins.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33020: Finish running T2P ADF Connection Plugins.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33100: Starting WLS managed server {0}@{1}:{2}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33200: Stopping WLS managed server {0}@{1}:{2}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33300: Processing {0} ADF Connection MBean attributes at server {1}

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33400: No ADF Connectioin MBean with name {0}

Cause: OBJECT_NAME_PROPERTY field for mbean object name might be changed accidently.

Action: Use the value of OBJECT_NAME_PROPERTY from other attributes under the same ADF Connection MBean in Move Plan to correct the wrong one.

Level: 1

Type: WARNING

Impact: Other

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

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

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

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

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

Cause:

Action:

Level: 1

Type: TRACE

Impact: Other

CLONE-51000: Is SOA Domain = {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51001: Executing "Post-Copy Configuration" operation of the SOA plugin.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51002: Executing "copyConfig Validation" operation of the SOA plugin.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51003: Executing "Copy Configuration" operation of the SOA plugin.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51004: SOA Oracle Home Location is {0}

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51005: Not valid SOA Domain. Skipping SOA-specific copy configuration steps.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51006: Exporting {0} composite to {1}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51007: Exporting Human WorkFlow Attribute Labels Info.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51008: Exporting Human WorkFlow TPFF Attributes.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51009: Exporting Human WorkFlow Approval Groups.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51010: Exporting Human WorkFlow Rules for Users.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51011: Exporting Human WorkFlow Rules for Groups.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51012: Exporting Human WorkFlow Views for Users.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51013: Exporting Human WorkFlow Standard Views.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51014: Exporting SOA Composites.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51015: No SOA Composite found in the specified domain. Composite details will not be added to the move plan.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51016: Exporting B2B Channel Info.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51017: No B2B Channels found in the specified domain. B2B details will not be added to the move plan.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51018: Adding B2B export file {0} to archive.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51019: Adding B2B Channel {0} to the move plan.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51020: Adding Composite {0} to the move plan.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51023: Exporting OWSM Policies...

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51024: Executing "Post-Paste Configuration" operation of the SOA plugin.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51025: Executing "pasteConfig Validation" operation of the SOA plugin.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51026: Executing "Pre-Paste Configuration" operation of the SOA plugin.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51027: Executing "Paste Configuration" operation of the SOA plugin.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51028: Extracting soat2p folder from archive.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51029: Importing OWSM Policies to target domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51030: Error in importing OWSM Policies to target domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51031: Importing Human WorkFlow Migration XML to target domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51032: Importing Human WorkFlow Attribute Labels Info.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51033: Importing Human WorkFlow TPFF Attributes.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51034: Importing Human WorkFlow Approval Groups.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51035: Importing Human WorkFlow Rules for Users.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51036: Importing Human WorkFlow Rules for Groups.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51037: Importing Human WorkFlow Views for Users.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51038: Importing Human WorkFlow Standard Views.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51039: Importing B2B Delivery Channels to target domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51040: Importing SOA Composites to target domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51041: Composite information is not available in the move plan. No Composites will be deployed to the target domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51042: B2B Information is not available in the move plan. No B2B channel details will be applied to the target domain.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51044: SEVERE: Specified composite config plan {0} is not a valid file. Using the default composite from archive.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51045: Adding OWSM policies to archive.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51046: "dataImport" is set as false. Skipping SOA import configurations.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51047: "mdsDataExport" flag is set to false. Skipping MDS migration for B2B, Human WorkFlow and OWSM

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51048: OWSM Policies are not exported during "copyConfig". OWSM policies will not be migrated.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51049: Human WorkFlow MDS data is not exported during "copyConfig".Human WorkFlow data will not be migrated.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51050: B2B data is not exported during "copyConfig".B2B MDS data will not be migrated.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51051: Exporting BPM Organizations and Dashboard data.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51052: Importing BPM Organizations and Dashboard data.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51053: BPM data migration file is not present in archive, skipping BPM import.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51054: Is BPM Domain {0}.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51055: Exporting BPM Organizations.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51056: Exporting Dashboard data of users.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51057: Importing BPM Organizations.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51058: Importing Dashboard data of users.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51059: BPM data not exported during "copyConfig".BPM data will not be migrated.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51060: Export of {0} composite failed.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51061: Exporting SOA configuration from MDS.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51062: MDS export for "soa-infra" application failed.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51063: Importing SOA configuration from MDS.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51064: MDS import for "soa-infra" application failed.

Cause:

Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-52000: "soa-infra" is targeted to AdminServer.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-52001: "OracleBPMWorkspace" is targeted to AdminServer.

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-52002: Not valid BPM Domain. Skipping BPM specific copy configuration steps .

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-52003: Determining if SOA platform is available...

Cause:

Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-53000: Error in finding SOA Oracle Home.

Cause: Specified Middleware Home did not have a valid SOA Oracle Home. Skipping SOA-specific configurations.

Action: Make sure that a valid SOA Oracle Home is present in the specified Middleware Home

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53001: Error in connecting to SOA Managed Server.

Cause: SOA Managed Server was down.

Action: Make sure that all managed servers in the specified domain are started.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53002: Error in examining Composites.

Cause: Composite examination failed.

Action: Make sure that all the specified values are correct. Check managed server logs and clone logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53003: Error in examining B2B.

Cause: B2B examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53004: Error in examining Human WorkFlow.

Cause: Human WorkFlow examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53005: Error in examining OWSM Policies.

Cause: OWSM Policy examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53007: Error in generating composite config plans.

Cause: Composite examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53008: Error in importing Human Workflow migration data.

Cause: Human WorkFlow migration failed.

Action: Make sure that all the specified values in the move plan are correct and the archive is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53009: 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: ERROR

Impact: Cloning

CLONE-53010: Error in deploying adapters.

Cause: Adapter deployment failed.

Action: Make sure that all the specified values are correct and domain configuration is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53011: Error in deploying Composites.

Cause: Composite deployment failed.

Action: Make sure that the config plan for {0} is valid or exists in archive.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53012: "soa-infra" is down.

Cause: Application "soa-infra" was not in active state. SOA specific "Paste Configuration" operations cannot be executed.

Action: Make sure that all the specified values in the move plan are correct.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53013: SOA Plugin examination failed.

Cause: Execution of "Copy Configuration" of SOA failed.

Action: Make sure that the SOA managed server is started and all the applications targeted to the SOA managed server are in active state.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53014: Plugin "Pre-Paste Configuration" execution failed.

Cause: Execution of "Paste Configuration" of SOA failed.

Action: Check the clone logs and SOA managed server logs. Make sure that all the specified values in the move plan are correct and none of the "READ_ONLY" properties are modified.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53015: Error in deploying Composites.

Cause: Composite deployment failed.

Action: Make sure that the config plans are valid and end points are configured correctly in composite config plans.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53016: Error in stopping SOA managed server.

Cause: Could not stop SOA managed server.

Action: Check the managed server logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53017: Error in examining B2B delivery channels from the move plan.

Cause: B2B delivery channel configuration failed.

Action: Make sure that values specified in the move plan are correct and none of the "READ_ONLY" properties are modified.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53018: Error in deploying Composites.

Cause: Composite deployment failed.

Action: Make sure that the config plans are configured correctly. Check managed server and t2p logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53019: OWSM Policy migration failed.

Cause: Make sure that the SOA managed server is started and applications targeted to the SOA managed server are in active state.

Action: Check the clone logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53020: Error in connecting to BPM Managed Server.

Cause: BPM Managed Server was down.

Action: Make sure that all managed servers in specified domain are started.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53021: SOA Plugin examination failed.

Cause: Execution of "Copy Configuration" of SOA failed.

Action: Make sure that the BPM managed server is started and all the applications targeted to the BPM managed server are in active state.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53022: Error in examining BPM.

Cause: BPM examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53023: Error in importing B2B Application data.

Cause: B2B Application data migration failed.

Action: Make sure that all the specified values in the move plan are correct and archive is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53024: Error in importing BPM Application data.

Cause: BPM Application data migration failed.

Action: Make sure that all the specified values in the move plan are correct and archive is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53025: Error in validating SOA domain.

Cause: The domain is not ready for deploying composites.

Action: Make sure that all the specified values in the move plan are correct. Check server logs for more details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53026: Error copying the MDM URL Resolver configuration file.

Cause: Unable to copy the updated "{0}" file to "{1}".

Action: Make sure that the file exists and has the required permissions.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53027: Error in importing MDS data.

Cause: MDS import for "soa-infra" application failed.

Action: Check SOA server logs for details.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53028: 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-53029: An internal error occurred.

Cause: Could not create the B2B Callout Directory, {0}.

Action: Move the B2B Callout Directory from source to target post "pasteConfig" operation.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-53030: An internal error occurred.

Cause: Could not create the B2B Large Payload Directory, {0}.

Action: Move the B2B Large Payload Directory from source to target post "pasteConfig" operation.

Level: 1

Type: ERROR

Impact: Cloning