20 CLONE-20200 to CLONE-25610

CLONE-20200: The clone option or argument is invalid.
Cause: The option or argument "{0}" was not supported by cloning.
Action: Provide valid option or argument. Use the "-help" command to know more 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 path {0}: 1. The path was not provided. 2. The path was not an absolute path. 3. The path was already existing. 4. The parent path did not exist. 5. The parent path did not have write permission.
Action: Provide a nonexistent absolute path 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 five possible causes for the file {0}: 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 have read permission. 5. Archive was a zero size file.
Action: Provide absolute path of a valid archive file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20204: Insufficient parameters for createClone.
Cause: Neither "-sourceMWHomeLoc" nor "-sourceInstanceHomeLoc and -sourceComponentName" were provided.
Action: Provide either "-sourceMWHomeLoc" or "-sourceInstanceHomeLoc and -sourceComponentName".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20205: Arguments combination is invalid.
Cause: The -sourceInstanceHomeLoc and/or -sourceComponentName was provided along with -sourceMWHomeLoc.
Action: Do not provide above argument combination as mentioned in the "CAUSE".

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: Mandatory parameter is missing.
Cause: Argument "{0}" was not provided.
Action: Argument "{0}" is mandatory for "{1}", so provide both arguments.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20208: Insufficient parameters.
Cause: Any one argument from these arguments "{0}", was not provided.
Action: Provide all the arguments.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20209: Sourceid is invalid.
Cause: There are three possible causes: 1. The individual sourceid "{0}" was either empty or did not present in the archive. 2. The provided sourceid was not present in the archive. 3. Multiple sourceids were provided along with default sourceid. The provided sourceid was: "{1}".
Action: Provide a valid sourceid. Do not mix default sourceid with other sourceid(s). Use "{0}" command to discover all the sourceid present in the archive.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20210: The archive file is invalid.
Cause: No sourceid(s) was present in the archive.
Action: Make sure that archive file is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20211: Archive is invalid.
Cause: Archive had multiple Middleware homes.
Action: Make sure that the archive is created using correct cloningClient.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20212: Targetlocation is not provided.
Cause: Archive had Middleware home and/or Oracle home.
Action: Provide targetlocation.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20213: Parameters are missing for component apply cloning.
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 nonexistent component name, and target instance location. If instance does not exist, provide instance name and existing Oracle home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20214: ApplyClone does not support multiple component at a time.
Cause: An attempt was made to restore multiple sourceids at a time.
Action: The number of sourceids should be one.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20215: Oracle home {0} configuration is unsuccessful.
Cause: Some files were missing.
Action: Check the clone log or error file for more detail.

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 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 did 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}" was not matching with "{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 this Oracle home "{0}": 1. It did not exist. 2. It was an empty directory. 3. It had no inventory pointer file(if operating system is other than Windows). 4. It had no top component or invalid top component version.
Action: Provide valid Oracle home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20224: Unsupported component cloning.
Cause: The "{0}" component cloning is not supported.
Action: The supported component cloning are "{0}".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20225: Invalid number of sourceid(s) and their restore locations.
Cause: There was a mismatch between number of sourceids and their restore locations. The number of sourceids is "{0}" and restore location is "{1}".
Action: Provide the same number of sourceids and their corresponding restore location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20226: Duplicate unarchive 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 unarchive location for Oracle home.
Cause: Two Oracle homes unarchive location "{0}" and "{1}" were either equal or parent child of one another.
Action: Oracle home(s) unarchive location(s) should not be either equal or parent child of one other.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20228: Invalid unarchive location for Middleware home.
Cause: Two Middleware homes unarchive location "{0}" and "{1}" were either equal or parent child of one another.
Action: Middleware home(s) unarchive location(s) should not be either equal or parent child of each other.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20229: Preparation for apply clone has failed.
Cause: Parameter(s) were missing or some validation failed.
Action: Check the clone log and error file to know which parameter is missing or validation has failed.

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 to know which parameter is missing or validation failed.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20231: Middleware home archive creation has failed.
Cause: The command "{0}" was not run successfully.
Action: Check the clone log and error file for more detail.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20232: ASInstall configuration has failed.
Cause: Exception occurred while configuring Oracle home.
Action: Check the installer log and cloneAction log in the inventory for more detail.

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 detail.

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 inventory has 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 detail.

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 detail.

Level: 1

Type: ERROR

Impact: Cloning

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

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20238: Oracle Internet Directory parameters validation has failed before restoring it.
Cause: Any one parameter was invalid.
Action: Check the clone log and error file for more detail.

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 correct archive file is provided, and check the extracted sourceid file whose path is "{0}".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20240: Invalid instance location.
Cause: Oracle Internet Directory component already existed under the specified instance.
Action: Provide an instance where no Oracle Internet Directory component is installed.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20241: 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-20242: Invalid odssm schema password.
Cause: Schema password for odssm was empty.
Action: Provide valid odssm schema password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20243: 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-20244: Database connection has failed.
Cause: Either database host or port or service name was incorrect.
Action: Provide correct database host, port and service name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20245: 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-20246: 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-20247: Namespace is missing.
Cause: The nameSpace was empty.
Action: Provide namespace.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20248: Oracle Internet Directory admin Password validation has failed.
Cause: Oracle Internet Directory admin Password was incorrect.
Action: Provide correct Oracle Internet Directory admin password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20249: Invalid instance location.
Cause: Oracle Virtual Directory component already existed under the specified instance.
Action: Provide an instance where Oracle Virtual Directory component is not installed.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20250: Oracle Virtual Directory admin password validation has failed.
Cause: Oracle Virtual Directory admin password was incorrect.
Action: Provide correct Oracle Virtual Directory admin password.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20251: Validation for nameSpace has failed.
Cause: The nameSpace was empty.
Action: Provide correct nameSpace.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20252: Database connection has failed.
Cause: Either hostname or port number or sidOrServiceName or schema user or schema password was empty.
Action: Make sure that all the parameters are valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20253: Invalid target location.
Cause: There are two possible causes for the specified path: 1. The parent path did not exist. 2. The parent path did not have write permission.
Action: Provide a nonexistent absolute path and make sure that its parent location exists and has write permission.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20254: Invalid target location.
Cause: There are four possible causes for file {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 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-20257: Invalid target location.
Cause: There are three possible causes for the specified file: 1. The target location was not provided. 2. The target file path was not an absolute path. 3. The target file path was already existing.
Action: Provide a nonexistent absolute path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20258: Invalid value for HTTP/DSML gateway SSL enable.
Cause: The provided value was invalid.
Action: The supported value is "true".

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20259: Invalid restore location for Oracle home.
Cause: The Oracle home parent location="{0}", was neither an existing Middleware home nor present in Middleware home restore path list.
Action: Provide valid Oracle home location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20260: Execution of system prerequisites has failed.
Cause: An internal operation failed.
Action: Check the clone log and error file for more detail.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20261: Invalid inventory.
Cause: There are six possible causes for 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 an OraInventory. 5. OraInventory found from file was not absolute. 6. OraInventory specified in the inventory pointer file "{1}" did not have write permission.
Action: Provide valid 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 different inventory or provide different location for new Oracle home.

Level: 1

Type: ERROR

Impact: Cloning

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

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20264: Default invPtrLoc is invalid.
Cause: There are two possible causes for default invPtrLoc "{0}": 1. The file did not exist. 2. It was a zero size file.
Action: Provide valid invPtrLoc or make sure that default invPtrLoc is proper.

Level: 1

Type: ERROR

Impact: Cloning

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

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20266: Invalid Oracle home location.
Cause: An attempt was made to restore "{0}" Oracle home using sourceid {1} at new location {2}. But the parent of new location was not a valid Middleware home.
Action: Before restoring either SOA, WEBCENTER or CLASSIC Oracle home, make sure that its parent is a valid Middleware home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20267: Invalid Oracle home location.
Cause: An attempt was made to restore Oracle home using sourceid {0} at new location {1}. Parent of new location was not a valid Middleware home.
Action: There are two possible actions: 1. Make sure that the parent of Oracle home is a valid Middleware home. 2. To restore IM or WEBTIER Oracle home without Middleware home, provide "-mwHomeValidation false" as command-line argument.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20268: Invalid Oracle home location.
Cause: Parent of Oracle home {0} was not a valid Middleware home.
Action: There are two possible actions: 1. Make sure that the parent of Oracle home is a valid Middleware home. 2. To create archive of Oracle home where its parent is not a Middleware home, provide "-mwHomeValidation false" as command-line argument.

Level: 1

Type: ERROR

Impact: Cloning

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

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20270: JAVA HOME not found.
Cause: Did not find JAVA HOME from product.properties of Weblogic server home.
Action: Make sure that Middleware home is installed with proper 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}" out of which these three characters "_.-" are not allowed in the beginning.

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}" out of which these three characters "_.-" are not allowed in the beginning.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20273: Invalid instance location.
Cause: Path "{0}" was not absolute or did not exist or an empty directory.
Action: Provide valid absolute path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20274: Invalid Oracle home.
Cause: Top component version validation failed.
Action: Make sure that Oracle home is valid.

Level: 1

Type: ERROR

Impact: Cloning

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

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20276: Unarchive is unsuccessful.
Cause: Some files were missing.
Action: Check the clone log or error file for more detail.

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 detail.

Level: 1

Type: ERROR

Impact: Cloning

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

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 detail.

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: Parameter validation for component applyClone has failed.
Cause: Either component name or instance location was empty.
Action: Provide component name and instance location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20282: Parameter validation for component applyClone has failed.
Cause: Instance was existing. But provided instance name "{0}" was different from the instance name "{1}" found from instance home.
Action: Either provide valid instance name or do not provide.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20283: Parameter validation for component applyClone has failed.
Cause: There was an existing component with same name under the specified instance.
Action: Make sure that the instance has no component with this name.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20284: Parameter validation for component applyClone has failed.
Cause: Instance was existing. But provided Oracle home "{0}" was different from Oracle home "{1}" used by existing instance home.
Action: Either provide valid Oracle home or do not provide.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20285: Parameter validation for component applyClone has failed.
Cause: Oracle home {0} had not supported files for {1}.
Action: Provide valid Oracle home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20286: Parameter validation for component applyClone has failed.
Cause: Middleware home {0} and parent of Oracle home {1} were different.
Action: Middleware home should be parent to the Oracle home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20287: Domain connection validation has failed.
Cause: Either domain detail was not correct or domain was down.
Action: Make sure that the domain details are correct and domain is up.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20288: Oracle home has not supported files.
Cause: Either component or top component was not present or version was mismatched.
Action: Check the clone log or error file for more detail.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20289: Oracle home has not supported files.
Cause: An attempt was made to use an incompatible top component based Oracle home.
Action: Make sure that the Oracle home is valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20290: Validation for ovdAdmin has failed.
Cause: ovdAdmin was empty.
Action: Provide correct ovdAdmin.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20291: Invalid target instance location.
Cause: Path {0} was either empty or did not absolute.
Action: Provide absolute path for target instance.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20292: Inventory pointer location file is not proper.
Cause: The inventory {0} found from the invPtrLoc File {1} was not absolute.
Action: Make sure that inventory pointer location file is proper.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20293: Oracle home configuration is unsuccessful.
Cause: The OraInventory {0} from invPtrLoc file {1} was not matching with OraInventory {2} from reference invPtrLoc file {3}.
Action: Check the clone log or error file and install CloneAction file for more detail.

Level: 1

Type: ERROR

Impact: Cloning

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

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20295: Execution of system prerequisites has failed.
Cause: The number of checks="{0}" and the number of success check="{1}" were mismatched. The unsuccessful checks were="{2}".
Action: Check clone log for more detail on prerequisites output and result.

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 instance {0}: 1. The instance location did not match the registered instance. 2. The instance home did not exist or did 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 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 an 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 detail.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20300: Instance home is corrupted.
Cause: Was unable to start the instance "{0}".
Action: Check the clone log or error file for more detail.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20301: Jre location update has failed.
Cause: Was unable to find java home from Middleware home "{0}".
Action: Make sure that Middleware 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 java home, it was pointing to 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} had not required files.
Action: Provide correct java home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20304: Invalid java home.
Cause: Path {0} was either not absolute or did not exist.
Action: Provide absolute path for java home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20305: Invalid Oracle home location.
Cause: The sourceMWHomeLoc and sourceOracleHomeLoc were provided. The Oracle home {0} was not present under sourceMWHomeLoc {1}.
Action: If both sourceMWHomeLoc and sourceOracleHomeLoc are provided, then all the Oracle home(s) mentioned in sourceOracleHomeLoc should be present under sourceMWHomeLoc.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20306: Middleware home cloning is not possible.
Cause: There are three possible causes for 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 absolute path.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20308: Middleware home is not provided.
Cause: Instance was registered with domain. Parent of Oracle home was not a Middleware home.
Action: Provide Middleware home, and make sure it is parent to the Oracle home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20309: Invalid usecase.
Cause: An attempt was made to create archive of both Middleware home and Oracle home.
Action: Provide either Middleware home or Oracle home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20310: Invalid usecase.
Cause: An attempt was made to create archive of an Oracle home which is inside a Middleware home.
Action: It is not possible to create archive of an Oracle home which is inside a Middleware home. The supported usecases are:1. Create full archive of the Middleware home by providing -smw <Middleware home location>.2. Create archive of only Middleware home by providing -smw <Middleware home location> 3. Create archive of standalone Oracle home(the Oracle home, whose parent is not a Middleware home) by providing -smw <parent of Oracle home location>.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20311: Invalid usecase.
Cause: An attempt was made to create archive of a common Oracle home.
Action: It is not allowed to create archive of a common Oracle home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20312: Invalid sourceid.
Cause: As archive has Middleware home, either provide default sourceid or Middleware home sourceid or do not provide sourceid.
Action: Use -listCloneArchive command to know sourceids present in the archive.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20313: Duplicate sourceid.
Cause: An attempt was made to restore same sourceid for multiple times.
Action: While providing sourceid as comma separated, make sure that all are unique.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20314: Invalid target location.
Cause: An attempt was made to restore standalone Oracle home archive under a Middleware home.
Action: It is not possible to restore a standalone Oracle home under a Middleware home.

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

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20318: Invalid argument: {0}.
Cause: Required argument wasn't provided at command line and also in the argument file.
Action: Provide valid argument.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20319: Invalid instance home location: {0}.
Cause: Either the directory location doesn't exist or it is corrupt.
Action: Provide valid instance location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20320: The specified instance name "{0}" is mismatching with calculated instance name "{1}".
Cause: The specified instance name was not matching with 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 doesn't exist or it is corrupt.
Action: Provide 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 correct Oracle home location.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20323: Invalid archive file.
Cause: The archive has Oracle home but no Middleware home.
Action: Make sure that archive was created using proper cloningclient jar.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20324: Unsupported character sequence.
Cause: Input {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 has to be less than or equal to {0}

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20326: Domain parameters are missing.
Cause: There are three possible causes: Target instance did not exist, and 1. All domain parameters were not provided. 2. Or domain host, port, user name were provided but port was not a positive integer one. 3. Or domain host, port, user name were provided but domain password file was not provided in silent mode.
Action: Provide either all domain parameters or not a single one.

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: Invalid dependent home.
Cause: Oracle home {0} has dependency on {1}, but unable to include dependent home.
Action: The dependent home is invalid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20330: Unsupported Middleware home cloning.
Cause: Oracle home {0} was associated with middleware home {1}, but Middleware home was not clonable.
Action: Provide a valid Middleware home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20331: Invalid Middleware home.
Cause: Specified Middleware home was not clonable and did not have any Oracle home.
Action: Provide a valid Middleware home.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-20332: Invalid Oracle home location.
Cause: Path "{0}" was not absolute or did not exist or an empty directory.
Action: Provide valid absolute path.

Level: 1

Type: ERROR

Impact: Cloning

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

Level: 1

Type: ERROR

Impact: Cloning

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

Level: 1

Type: ERROR

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: The sourceid(s) available in the archive is "{0}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21005: The cloneplan has been extracted, and present at "{0}" location.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21006: Total time taken by cloningclient="{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 list of Oracle home(s) that will be included in the archive is={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: Primary validation prior to clone operation is successful for {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21014: Adding all required files for execution of system prerequisites during applyClone ...
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: Unarchiving started at "{1}" location.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21019: Unarchiving at "{1}" location, finished.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21020: ASInstall configuration for Oracle home {0} is in progress ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21021: ASInstall 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, and time taken="{1}" milliseconds.
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="{0}" milliseconds.
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: Restoring for the sourceid "{0}" started ... at {1}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21034: Time taken to restore sourceid "{0}" is="{1}" milliseconds.
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="{0}" milliseconds.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21038: Oracle home {0} has required files for {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: J2EEComponent 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 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 and time taken was="{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={0} milliseconds.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21057: Execution of system prerequisites started for Oracle home ...
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: The postStart has already performed in the database.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21061: Validating Oracle Internet Directory LdapSSlPort.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21062: The java home {0} found from System property was not pointing to 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: Validating Oracle Internet Directory nonSSlPort.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21066: Setting isOVDHttpSSL to "{0}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21067: Database is already configured with Oracle Internet Directory Component named {0}, so provide different name for Oracle Internet Directory Component.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21068: Provided database details is empty and also database detail from tnsfile is empty.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21069: Provided database details and found from tnsnames.ora file are different.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21070: Database parameters should not be empty.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21071: Adding permission file to the archive failed.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21084: The cn=orcladmin password verified successfully.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21085: The cn=orcladmin password verification is postponed.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21086: Error occurred while binding OID with database.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21088: Null parameter(s) found during OID parameters validation.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21089: Null parameter(s) found during OVD parameters validation.
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, type "yes":
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: Time taken for this process={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: Enter ods schema password:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21100: Enter odssm schema password:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21101: Enter oid Admin password:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21102: Enter ovd admin password:
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21103: Log path "{0}" should be absolute and existing directory with write permission. But this condition was not satisfied.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21104: The number of Oracle home(s) and Middleware home 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 failed for sourceid {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21107: The final sourceid(s) which will be taken care of="{0}" and their corresponding targetlocation(s)="{1}".
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21108: As Middleware home validation is set to false. It will not check whether parent is a Middleware home or not.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21109: As the archive has only one Oracle home and no Middleware home, targetLocation should not exist, and its parent should exist.
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}" out of which 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 and time taken was="{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 and time taken was="{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 canonicalpath should be "{1}", but canonicalpath 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: In "{1}" seconds, {0}% has completed.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21127: Oracle home applyClone post validation, inventory validation started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21128: Oracle home applyClone 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 window shortcut for Oracle home {0} started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21132: Updating window shortcut for Oracle home {0} finished.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21133: Archive of only Middleware home could be achieved by providing "-excludeOracleHomes true" as command-line argument.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21134: Source OVD Component was configured with following detail. httpPort={0}, ldapPort={1}, ldap ssl Port={2}, ovdAdminPort={3}, isHttpSSl={4}, isAdminSSL={5}, isSrcHttpActive={6}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21139: Setting isOVDAdminSSL to "{0}" as source ovd component was configured like this.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21140: Setting isOVDHttpSSL to "{0}" as source ovd component was configured like this.
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 may not be started with "CLONE", or it may not be ended with "-INFO" where message type=INFO or it may not be ended with "-TRC" where message type=TRACE or it may be ended with "-ERR" or "-CAUSE" or "-ACTION" where message type=ERROR or its length may 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-21153: Source OID Component was configured with following detail. non ssl port={0}, ssl port={1}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21154: Checking free space availability for createClone operation.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21158: The port "{0}" was either empty or did not free, trying to get new port.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21161: In the domain the available instance name and their corresponding locations are={0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21162: Component configuration started ... Output has logged to clone log and error file.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21163: Adding no read permission files detail to the archive started ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21164: Adding no read permission files detail to the archive finished and time taken was="{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} ...
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-21173: Restarting component ... Output has logged to clone log and error file.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21174: Instance "{0}" is down, trying to start the instance ...
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21175: Instance "{0}" started successfully.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21176: Instance "{0}" is in running state.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21177: Component started successfully.
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 configured with new java home {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21180: From httpPort and isHttpSSL, either both will be empty or both will be present, but any one argument is empty.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21181: The instance is registered with domain with following details: domainHost={0}, domainPort={1}, domainAdminUser={2}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21182: Either provided domain parameter is empty or mismatching with the domain parameters used by the existing instance.
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: Middleware home is not provided. {0} will be used as Middleware home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21185: Domain details are provided, but Middleware home is not provided.
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-21195: Cloning for Component Type: "{0}" is not supported.
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 within 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: 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 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 instance home location={0} and instance name={1}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21211: Instance will be registered with domain where host={0} and port={1}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21212: Instance will not be registered with domain.
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}, was either not valid or did not cloneable, but still continuing ...
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-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 did 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-22007: Building cloner object where componentName="{0}", componentType="{1}", instanceLocation="{2}", instanceName="{3}" and Oracle home location="{4}".
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-22023: Adding cloneplan to the jar file started ...
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22024: Adding cloneplan 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-22026: Either cloneplan or objectforClonePlan is empty, before adding to cloneplan.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22027: Adding oidComponentObject to clonePlan.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22028: Adding ovdComponentObject to clonePlan.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22029: Got cloneplan from archive.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22030: Archive does not have component detail.
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-22035: Unable to find installed components detail from Oracle home {0}.
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-22056: Generating exclude path list if any.
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}. Nonreadable 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 taken care 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 taken care:
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: Permission of the following files are not taken care.
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 -lQR" is executed properly, and temporary file was {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22074: The command "ls -lQR" 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 invalid as the file {1} was invalid.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22081: The instance name was empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22082: The instanceHomeLocation {0} was invalid.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22083: The instanceHomeLocation {0} exists in domain.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22084: The instanceName {0} already exists in domain.
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-22086: The domain parameters are as follows: domainHost={0}, domainPort={1}, domainAdminUserName={2} and Weblogic home={4}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22087: The Weblogic home={0} was not valid.
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 instance name and its location is={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 createClone are: componentName={0}, componentType {1}, instanceHomeLocation={2} and instanceName={3}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22101: CreateClone for "{0}" is not supported.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22102: The instance home "{0}" is not valid.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22103: The instanceName provide and calculated were different and they were "{0}" and "{1}" respectively.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22104: Wallet file was not present under oid component.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22105: The tnsnames.ora file {0} is invalid.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22106: The ports.prop file {0} is invalid.
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} and Middleware home={3}.
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-22128: Adding ojdbc6.jar to SystemClassloader failed.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22129: Adding ldapjclnt11.jar to SystemClassloader failed.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22130: No domainConnection.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22131: Invoking config to create oid.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22132: Building oid parameters failed.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22133: Status of adding vde.jar to SystemClassLoader is={0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22134: Invoking config to create ovd.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22135: Building ovd parameters failed.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22136: The value of isOvdAdminSSL parameter should be true or false, but found "{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22137: The value of isOvdHttpSSL parameter should be true or false, but found "{0}".
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22138: The value of ovdAdminName parameter was empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22139: The value of ovdAdminPassword parameter was empty.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

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

Level: 1

Type: TRACE

Impact: Cloning

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

Level: 1

Type: TRACE

Impact: Cloning

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

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22143: Parameter validation is complete. Setting user visible sourceid 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-22150: Restore location {1} is invalid for sourceid="{0}", where provided restore location(s)="{2}", sourceid(s)="{3}" and restoreLoc_uvSrcid="{4}"
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22151: All Middleware home(s) restore path list="{0}", provided restoreLocation="{1}", sourceid="{2}" and restoreLoc_uvSrcid="{3}".
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 from Oracle home {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22170: Status of adding both engine and oui jars to system classloader from Oracle home {0} is="{1}".
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-22196: All inputs for cloning 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-22202: The oracle.installer.invPtrLoc after running runConfigure={0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22203: For restoreWallet, archive location is={0} and actual sourceid={1} and instance location={2}.
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 createClone 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-22219: As no files is present under ovd component, nothing to archive.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22220: As no files is present under config for ovd component, nothing to archive.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22221: For restore ovd component files, archive location is={0} and actual sourceid={1} and instance location={2}, component name={3}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22222: Unarchiving files under {0} using entry id {1}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22223: As no files are present under instanceHome-config-JPS, nothing to archive.
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-22225: OVD parameters for apply clone={0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22226: OID parameters for apply clone={0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22227: The "{0}" component cloning is unsupported.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22228: Component detail from archive is: Top component name={0}, top component version={1}, Component name={2} and component version={3}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22229: Component detail from Oracle home is: Top component name={0}, top component version={1}, Component name={2} and component version={3}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22230: Validating whether component version {0} is within {1} and {2} or not.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22231: Validation for Component version {0}, within {1} and {2} is successful.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22232: Loading vde jar from Oracle home {0} to class loader before validating domain connection.
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}", UserVerifyCount ="{3}", WarningsCount ="{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-22246: Updating ovd listen file {0}, with ovdAdminPort={1}, ovdLdapPort={2}, ovdLdapSSLPort={3}, ovdHttpPort={4}, isOvdAdminSSL={5} and isOvdHttpSSL={6}.
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 nonreadable 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-22255: Status of adding optic.jar to SystemClassLoader is={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-22258: After creation of cloned OVD Component, port informations are as follows: httpPort={0}, ldapPort={1}, ldap ssl Port={2}, ovdAdminPort={3}, isHttpSSl={4}, isAdminSSL={5}, isHttpActive={6}, isOvdAdminActive={7}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-22259: All Ports detailed information from xml file {0} is: {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-23001: Archive location
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23002: Inventory location
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: Archivelocation should not exist and its parent should exist and have write permission
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23012: Parameters for createClone of Middleware home
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 location(oraInst.loc file location), to discover Oracle home(s) present under Middleware home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23016: Absolute path of the standalone Oracle home to be included in the archive.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23020: Existing log directory location, where cloning log and error file will be generated. Default location is system temporary location.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23021: Flag to run the cloning client in a noninteractive mode. Default value is false.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23022: Parameters for createClone 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-23026: To create archive of either Middleware home( and all valid Oracle home(s) under it) or component.Use "{0}" command to know all the entities present in the archive.
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 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: Java version should be at least
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-23048: The parameter {0} will accept only one standalone Oracle 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-23051: Either {0} or {1} can be provided, but not both arguments at same time.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23052: If only {0} is provided, only that Oracle home will be included in the archive, subject to condition that it is a standalone Oracle home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23055: CreateClone 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 Weblogic processes are running.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23058: While creating the archive of Middleware home, make sure that Weblogic server is installed inside the Middleware home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23059: Copyright (c) 2004, 2009, 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 server is 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: only weblogic binaries from
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: Sourceid of the entity to be restored.
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-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 or Oracle home(s).
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: Inventory pointer location
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
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 associated with the instance home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23122: Absolute path of Middleware home for domain configuration
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 apply clone
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} should not exist but its parent should exist and has write permission {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: Archive has only one standalone Oracle home. Restore full archive
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23152: Archive has one Oracle home(let {0})
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23153: Here {0} should not exist but its parent should exist and has write permission and its parent should not be a Middleware home.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23154: Archive will be restored at {0}
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23155: Archive has only Oracle homes. Restore full archive
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} should not exist but {1} should exist and has write permission
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23163: Restore single entity from archive by providing single sourceid
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23164: First find out sourceid from archive using "{0}" command
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23168: 1. All the entities present in the archive will be restored during applyClone operation.2. When ever Oracle home(s) will be restored, make sure that the Oracle inventory has no entry for that target Oracle home.3. If targetInstanceHomeLoc exist, then targetInstanceName and targetOracleHomeLoc are optional.4. If targetInstanceHomeLoc is already registered with domain, then domainHostName, domainPortNo 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 createClone 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-23219: Parameters for applyClone of J2EE Component.
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 JDK.
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 ever Oracle home(s) will be 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 a component.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23255: To restore the full archive containing an Oracle Component.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23260: 1. If targetInstanceHomeLoc exist, then targetInstanceName and targetOracleHomeLoc are optional.2. If targetInstanceHomeLoc is already registered with domain, then domainHostName, domainPortNo and domainAdminUserName are optional.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23265: Invalid Command line options. Please use the '-help' option to see full help.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24000: Unable to set source component properties.
Cause: Component properties object from bean is null.
Action: Check the log file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24005: OVDCloning has failed.
Cause: Ovd Component applyClone parameter validation failed.
Action: Check the clone log file for more detail.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24006: OVDCloning has failed.
Cause: JPS file of the source OVD Component is not available.
Action: Check the clone log file for more detail.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24007: OVDCloning has failed.
Cause: OVD creation failed.
Action: Check the clone log file for more detail.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24008: OVDCloning has failed.
Cause: Collection of ports for new OVDComponent failed.
Action: Check the clone log file for more detail.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24009: OVDCloning has failed.
Cause: Port updation for OVDComponent failed.
Action: Check the clone log file for more detail.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24010: Port validation has failed.
Cause: Ubale to assign port for {0}.
Action: Make sure that some ports are free.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24011: Oracle home has not supported binaries.
Cause: An attempt was made to use an incompatible top component based Oracle home.
Action: Make sure that the Oracle home is a valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24012: Oracle home has not supported binaries.
Cause: An attempt was made to use an incompatible component based Oracle home.
Action: Make sure that the Oracle home is a valid.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-24301: Source OVD Component listeners were configured with following detail. {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-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 asinstance {0}.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24329: Starting asinstance {0}.
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 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 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 builded 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 builded successfully.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24610: Collecting port informations after OVD component is created.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24611: Collecting port informations completed.
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 createClone operation.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24615: All Ports detailed info from xml file {0} is : {1}
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24616: OVD parameters for apply clone = {0}.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-24617: The {0} component version is = {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 verfication.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25000: Unable to set source component properties.
Cause: Component properties object from bean is null.
Action: Check the log file.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25001: Invalid component name.
Cause: As source and target database are different,then target OID component name {0} should 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 or 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 is missing .
Cause: The nameSpace was empty.
Action: Provide namespace.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25009: OIDCloning has failed.
Cause: Wallet file of the source OID Component is not available.
Action: Check the clone log file for more detail.

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25010: Database connection has failed.
Cause: Either hostname or port number or sidOrServiceName or 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 same name.
Action: Provide different database detail.

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 any oid .

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25014: Invalid target component name for OID.
Cause: Database is alreday 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 same oid entry, i.e. "{0}" .
Action: Make sure that database has already 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 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 has not supported binaries.
Cause: An attempt was made to use an incompatible top component based Oracle home.
Action: Make sure that the Oracle home is a valid .

Level: 1

Type: ERROR

Impact: Cloning

CLONE-25020: Oracle home has not supported binaries.
Cause: An attempt was made to use an incompatible component based Oracle home.
Action: Make sure that the Oracle home is a valid .

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 detail from tnsfile is empty and provided database detail(s) are also empty.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25308: Setting database db detail 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 detail, database host ={0} database port ={1} database service name = {2}. To use same database , provide these values as argument.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

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

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25311: The postStart is not performed in the database, i.e database is vanila.
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25312: Source OID Component was configured with following detail. 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 component {0} was associated with database host {1} and service name {2} , and port number {3}. And an attempt is made to associate target oid component with same database and service name. And target oid component name is same to that of source oid component. As a result source oid will not work properly, but target will work. If you provide a unique name (i.e. database is not configured with this name)for target oid component , Then other installed oid(s) 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 within loweport {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 = "{0}" .
Cause:
Action:

Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25330: Database is 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-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 createClone operation.
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning

CLONE-25604: OID parameters for apply clone = {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 builded 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 builded 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 verfication .
Cause:
Action:

Level: 1

Type: TRACE

Impact: Cloning