20 OAB-00015 to OAB-960018
- OAB-05021: Error downloading assembly archive from EM Software Library.
-
Cause: (See message)
-
Action: Check the connection to EM Software Library and, if the remote directory is /tmp, specify another directory. Also verify that the permissions of the remote directory allow the EM Software Library user access.
Level: 1
Type: ERROR
Impact: Other
- OAB-05023: Error downloading the assembly archive.
-
Cause: (See message)
-
Action: Check the connection to EM Software Library and, if the remote directory is /tmp, specify another directory. Also, verify that the permissions of the remote directory allow the EM Software Library user access.
Level: 1
Type: ERROR
Impact: Other
- OAB-07306: Encrypts one or more values that are obtained by securely prompting without echoing. The encrypted values can either be printed to the screen or appended to a specified file. This command is intended for use when constructing property files used in conjunction with script-based facilities.
-
Cause:
-
Action:
Level: 1
Type: NOTIFICATION
Impact: Other
- OAB-07309: The output file where the specified properties and encrypted values should be written. If the file does not exist then it will be created. If the file exists then all new properties will be appended to the file and any pre-existing properties will be updated.
-
Cause:
-
Action:
Level: 1
Type: NOTIFICATION
Impact: Other
- OAB-23484: Cannot create template for {0} because it belongs to the following assemblies for which assembly archives exist: {1}.
-
Cause: Cannot recreate templates for a member of any assembly that has an existing assembly archive.
-
Action: Delete assembly archive for any assemblies that contain the specified element.
Level: 1
Type: ERROR
Impact: User Input
- OAB-23496: There are not enough loop devices present to create a template for this appliance.
-
Cause: {0} loop devices are needed to create a template for this appliance, but only {1} loop devices are present on this system.
-
Action: Configure additional system loop devices. Contact Oracle support if necessary.
Level: 1
Type: ERROR
Impact: Other
- OAB-40202: Aborting operation due to previous failure during deployment.
-
Cause: Cannot proceed due to prior error during configuration (rehydrate) phase.
-
Action: Investigate cause of original error and redeploy, reset all state and manually re-attempt configuration, or set the state to CONFIGURED and reattempt the desired operation.
Level: 1
Type: ERROR
Impact: Other
- OAB-42736: The assembly archive does not contain a disk image matching expected pattern <capture_id>{0}.
-
Cause: The archive is corrupted, or is not compatible with this version of Oracle Virtual Assembly Builder.
-
Action: Contact Oracle Support Services if necessary.
Level: 1
Type: ERROR
Impact: Data
- OAB-43032: Cannot modify element {0} because it belongs to the following assemblies that have assembly archives: {1}.
-
Cause: Cannot modify a member of any assembly that has an assembly archive.
-
Action: Delete the assembly archives for all assemblies that contain the specified element.
Level: 1
Type: SET_AT_RUNTIME
Impact: User Input
- OAB-44008: The appliance {0} has ovm-template-config version {1}, whereas appliance {2} has conflicting version {3}.OVF generation must specify a single version.
-
Cause: (See message)
-
Action: Re-template appliances using base images with matching ovm-template-config packages.
Level: 1
Type: ERROR
Impact: Other
- OAB-45231: Cannot capture file sets for assembly {0} because it contains appliances with non-uniform file set definitions.
-
Cause: The assembly members are divided into {0} groups, each of which shares file set definitions: {1}.
-
Action: Capture file sets individually for one member of each of the above groups.
Level: 1
Type: ERROR
Impact: User Input
- OAB-45232: Cannot capture file sets for {0} because it belongs to the following assemblies that have assembly archives: {1}.
-
Cause: Cannot capture file sets for a member of any assembly that has an assembly archive.
-
Action: Delete the assembly archives for all assemblies that contain the specified element.
Level: 1
Type: ERROR
Impact: User Input
- OAB-90061: Unable to create connection to remote server.
-
Cause: Timed out trying to connect to IPV4 and IPV6 sockets. Remote process is not up or there are network connection issues.
-
Action: Verify port forwarding is enabled on remote machine. If sudoUser option is used, verify the remote user has sudo permissions.
Level: 1
Type: ERROR
Impact: Network
- OAB-111001: Configuration is not valid.
-
Cause: The configuration has the following problems: {0}.
-
Action: The configuration information may be in assembly metadata, appliance metadata or the deployment plan. Locate and either update or delete the configuration artifacts associated with the listed problems.
Level: 1
Type: WARNING
Impact: User Input
- OAB-111477: Appliance instance %s is in the invalid state %s. It is expected to be in the state %s
-
Cause: The specified appliance instance in the invalid state for the operation initiated
-
Action: Check the initiated operation in conjunction with the specified current state of the appliance instance
Level: 1
Type: ERROR
Impact: Deployment
- OAB-111492: Failed to configure the vNets on the appliance instance %s
-
Cause: Specified appliance instance did not receive vNet configured message in %d seconds
-
Action: Check to see if the appliance instance is reachable by SSH. If not, check and correct your vNet configuration and retry. For static IP networking, check gateway, netmask, DNS settings and IP address settings in the deployment plan. For DHCP networking, check your network router to insure DHCP is enabled and addresses are available for lease. If the appliance is reachable by SSH, then check the log files in /assemblybuilder and the instance home for errors that may have occurred during rehydration. If all seems well, the phone home timeout may need to be increased.
Level: 1
Type: ERROR
Impact: Deployment
- OAB-111493: Appliance instance %s reported an error while configuring the network interfaces: %s
-
Cause: One or more required network interface configuration parameters was missing or incorrect
-
Action: Ensure that all required network interface configuration parameters were specified. Check assemblybuilder.log file and ab.out files on the appliance for details
Level: 1
Type: ERROR
Impact: Deployment
- OAB-111550: Create vNet is not supported in the target environment
-
Cause: A request has been initiated to create a private vNet, but the target environment does not support this capability
-
Action: Do not declare private vNets while using the specified target environment
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112031: The assembly instance %s is not in any of the states %s. So, it cannot be removed
-
Cause: The assembly instance for the supplied identifier is not in any valid state for the delete operation
-
Action: Check the status and try a valid assembly instance
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112035: Assembly instance %s is not currently deployed. Appliance %s cannot be scaled
-
Cause: An attempt was made to scale the assembly instance that is currently undeployed
-
Action: Deploy or start the assembly instance before attempting to perform the scale operation
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112038: Cannot scale the appliance. Supplied target %s for the appliance %s is above its maximum scalability requirement %s
-
Cause: The target count specified for the supplied appliance is above its maximum scalability requirement.
-
Action: No action required
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112039: Cannot scale the appliance. Supplied target %s for the appliance %s is below its minimum scalability requirement %s
-
Cause: The target count specified for the supplied appliance is below its minimum scalability requirement.
-
Action: No action required
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112049: Assembly instance %s is in intermediate state %s while being restored from the persistence
-
Cause: The previous operation was terminated prior to the completion of the operation
-
Action: Undeploy and/or remove the assembly instance and create and deploy it again
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112088: Appliance instance with the identifier %s does not belong to the assembly instance %s
-
Cause: Appliance instance with the supplied identifier does not belong to the supplied assembly instance
-
Action: Provide a valid appliance instance identifier that belong to the supplied assembly instance
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112090: Assembly instance %s is not in any expected states %s. Its current state is %s
-
Cause: The assembly instance for the supplied identifier is not in any valid state for the requested deployer operation
-
Action: Check the status and try a valid assembly instance
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112091: Appliance instance %s is not in any expected states %s. Its current state is %s
-
Cause: The appliance instance for the supplied identifier is not in any valid state for the requested deployer operation
-
Action: Check the status and try a valid appliance instance identifier
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112133: Cannot unregister the assembly %s:%s from the resource pool %s. It has assembly instances %s
-
Cause: It cannot be unregistered when there are assembly instances
-
Action: Delete the specified assembly instances prior to attempting to unregister the assembly
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112144: Phone home request timed out for the phonehome type %s uid %s
-
Cause: A phone home call from the deployed VM was not received in %d seconds
-
Action: Check to see if the appliance instance is reachable by SSH. If not, check and correct your vNet configuration and retry. For static IP networking, check gateway, netmask, DNS settings and IP address settings in the deployment plan. For DHCP networking, check your network router to insure DHCP is enabled and addresses are available for lease. If the appliance is reachable by SSH, then check the log files in /assemblybuilder and the instance home for errors that may have occurred during rehydration. If all seems well, the phone home timeout may need to be increased.
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112162: Cannot add or delete tags to the appliance instance %s. The assembly instance object for the specified appliance instance is in FAILED stage
-
Cause: The assembly instance object for the specified appliance instance is in FAILED stage
-
Action: Supply a valid appliance instance identifier
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112175: Cleanup operation on the process %s timed out after %s seconds
-
Cause: Look at the target environment log files for the possible root causes or timeout value is too short for this operation
-
Action: Look at the target environment log files and take appropriate action or increase the timeout value
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112934: Operation not allowed for ExaLogic: %s. Target configuration for Exalogic is performed at installation time.
-
Cause: On Exalogic systems, the target configuration is defined at installation time and may not be changed.
-
Action: None. Dynamic configuration of targets is not necessary on Exalogic systems.
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112950: Specified target %s cannot be set as a default target because it is not a deployment target.
-
Cause: Specified target is not a deployment target and cannot be used as a default deployment target.
-
Action: Specify a deployment target to be used by default instead.
Level: 1
Type: ERROR
Impact: Deployment
- OAB-112951: Cannot connect to the target %s using specified connection properties.
-
Cause: Specified target connection properties are invalid, the target is down, or secure connection cannot be established because of deployer or target SSL configuration.
-
Action: Make sure the target connection properties are valid, the target is running and that deployer and target SSL configurations would allow for secure connection.
Level: 1
Type: ERROR
Impact: Deployment
- OAB-113547: Assembly archive already exists at: {0}
-
Cause: An assembly archive with the same name already exists at the location specified.
-
Action: Please choose a different name and/or location to download the assembly archive to using the 'fileName' parameter.
Level: 1
Type: ERROR
Impact: Deployment
- OAB-114603: Cannot find a repository shared by pool servers.
-
Cause: No single repository was found that is presented to all the servers in the pool {0}
-
Action: Configure OVM environment so that at least one repository is presented to all the servers in the pool {0}
Level: 1
Type: ERROR
Impact: Deployment
- OAB-114615: Cannot find another server for VM {0} in the pool {1}. Minimum {2} servers are required for this VM anti-affinity group and only {3} servers are used.
-
Cause: Not enough servers are available in the pool to satisfy VM anti-affinity group minimum servers requirement.
-
Action: Increase the number of servers in the pool {0}, deploy to a different pool or lower minimum servers requirement of VM the anti-affinity group and try again.
Level: 1
Type: ERROR
Impact: Deployment
- OAB-114630: Failed to import virtual cdrom {0} from URL {1}.
-
Cause: Download of virtual cdrom to the repository failed, possibly due to the OVS host connection isues.
-
Action: Make sure OVS hosts have access to the virtual disk file at the specified URL and try again.
Level: 1
Type: ERROR
Impact: Deployment
- OAB-114639: SSL handshake failed while trying to establish secure connection to OVM manager at {0}.
-
Cause: The client was not able to establish secure connection.
-
Action: Check deployer and OVM manager SSL configuration. Make sure OVM manager certificate is trusted by deployer.
Level: 1
Type: ERROR
Impact: Deployment
- OAB-114822: Invalid operation attempted. Cannot perform delete failed appliance instances operation since the assembly instance {0} is currently deployed
-
Cause: The corresponding deployment is not running
-
Action: This operation is only meant for deleting the failed instances resulted by the scale operation
Level: 1
Type: ERROR
Impact: Deployment
- OAB-114831: Invalid network properties. Errors are %s
-
Cause: Network configured for the specified appliances are static but does not defined required properties for the static network or specified properties are invalid
-
Action: Fix the errors specified in the error message
Level: 1
Type: ERROR
Impact: Deployment
- OAB-114833: Assembly instance %s does not contain deployment requirement instances after restoration
-
Cause: Some or all appliance instances of the assembly instance in the corresponding target environment are either managed by the external tools or could not be recovered
-
Action: Delete the assembly instance and create it again
Level: 1
Type: ERROR
Impact: Deployment
- OAB-114839: Deployer must always be executed by the same user '%s', while the current user is '%s'
-
Cause: WebLogic and its applications are now executed by a different OS user, which can cause problems with Deployer file based store and is not allowed.
-
Action: Restart WebLogic as the original user, or reinstall Deployer.
Level: 1
Type: ERROR
Impact: Deployment
- OAB-114866: Cannot use storage target %s with the deployment target %s
-
Cause: The supplied storage target is not configured in the allowed storage targets list for the specified deployment target
-
Action: Provide a valid and configured allowed storage target for the specified deployment target
Level: 1
Type: ERROR
Impact: Deployment
- OAB-114887: Assembly instance {0} does not meet the deployment requirement
-
Cause: One or more instances of the assembly instance in the corresponding target environment are either managed by the external tools or would have gone down
-
Action: Delete the assembly instance and create it again
Level: 1
Type: WARNING
Impact: Deployment
- OAB-114893: Either parameter {0} or {1} must be specified for action {2}, but not both
-
Cause: Both {0} and {1} parameters were specified for action {2} while only one can be set.
-
Action: Update rule definition to specify only {0} or {1} parameter for action {2}.
Level: 1
Type: ERROR
Impact: Deployment
- OAB-114903: {0} operation request {1} for the appliance {2} in the assembly instance {3} is cancelled
-
Cause: The deployer server handling the specified request is either crashed or has been shutdown
-
Action: Look at the logs for corresponding appliance and perform any cleanup if necessary
Level: 1
Type: WARNING
Impact: Deployment
- OAB-114906: {0} operation request {1} for the assembly instance {2} is cancelled
-
Cause: The deployer server handling the specified request is either crashed or has been shutdown
-
Action: 1. Look at the logs for corresponding assembly instance and perform any cleanup if necessary 2. Delete the specified deployment
Level: 1
Type: WARNING
Impact: Deployment
- OAB-114907: {0} operation request {1} for the assembly archive {2}:{3} on the target {4} cancelled
-
Cause: The deployer server handling the specified request is either crashed or has been shutdown
-
Action: Look at the logs for corresponding registration and perform any cleanup if necessary
Level: 1
Type: WARNING
Impact: Deployment
- OAB-114913: Cannot find disk {0} in the appliance instance {1}
-
Cause: Disk with the supplied name isn't a valid disk for the supplied appliance instance
-
Action: Check the specified disk is a valid disk attached to the supplied appliance instance against the ovf descriptor of the assembly and try again with the valid disk name
Level: 1
Type: WARNING
Impact: Deployment
- OAB-114914: Cannot find disk {0} in the assembly instance {1}
-
Cause: Disk with the supplied name isn't a valid disk in the assembly instance
-
Action: Check the specified disk is a valid disk the ovf descriptor of the assembly and try again with the valid disk name
Level: 1
Type: WARNING
Impact: Deployment
- OAB-114915: Invalid disk {0} for the snapshot generation. Its not attached to the appliance instances in the assembly instance {1}
-
Cause: The disk with the supplied name isn't configured to attach any appliance instance
-
Action: Check the specified disk is a valid disk the ovf descriptor of the assembly and it is configured to attach to one or more appliances
Level: 1
Type: WARNING
Impact: Deployment
- OAB-114916: Invalid snapshot generation request. The appliance instance {0} doesn't have any disks attached
-
Cause: The supplied applaince instance doesn't have any disks attached
-
Action: Check the specified appliance instance against the ovf descriptor of the assembly and try again with the valid appliance instance
Level: 1
Type: WARNING
Impact: Deployment
- OAB-114917: Cannot generate snapshot to the appliance instance {0}. It has shared disks {1}
-
Cause: The supplied appliance instance has shared disks. The appliance alone cannot be snapshotted when it has shared disks.
-
Action: Generate snapshot to the assembly instance when there are shared disks
Level: 1
Type: WARNING
Impact: Deployment
- OAB-114920: No snapshot disks found in the snapshot {0} for the appliance instance {1}. The appliance instance is new after the snapshot is generated. This appliance instance cannot be restored to the snapshot. Continuing the assembly restoration of rest of the appliance instances.
-
Cause:
-
Action:
Level: 1
Type: WARNING
Impact: Deployment
- OAB-115157: Assembly resources file already exists at: {0}
-
Cause: An assembly resources file with the same name already exists at the location specified.
-
Action: Please choose a different name and/or location to download the assembly archive to using the 'fileName' parameter
Level: 1
Type: ERROR
Impact: Deployment
- OAB-118107: The Elastic IP address %s assigned to %s is not available because it is assigned to another instance.
-
Cause: The Elastic IP address is already assigned to another instance.
-
Action: Ensure that an available Elastic IP address is assigned to the appliance.
Level: 1
Type: ERROR
Impact: Deployment