8 ASCRS-00001 to ASCRS-00143

ASCRS-00001: {0} of {1} completed successfully.

Cause: Operation is completed successfully.

Action: Informational, no further action is needed.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00002: {0} of {1} canceled.

Cause: Operation is canceled.

Action: Informational, no further action is needed.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00003: {0} of {1} failed.

Cause: Operation failed.

Action: Inspect the log files for the detailed cause.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00004: UP state of CRS with CRS HOME {0} could not be verified.

Cause: CRS could be down.

Action: Try to restart CRS. Refer to CRS documentation if it persists.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00006: Please run the following as root to complete this operation. {0}

Cause: Root privilege is needed for some resource task.

Action: Do as instructed.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00007: Cluster nodes specified {1} is different from cluster nodes - {2} - for dependent resource {0}

Cause: Not matching cluster nodes between this resource and its dependents.

Action: Please ensure the same set of cluster nodes for this resource and its dependents.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00008: Resource {0} cannot be deleted since dependent resources exist.

Cause: Named resource cannot be deleted since other resources depend on it.

Action: Delete all the dependent resources first.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00009: Resource {0} already manages same object as {1} wants to manage: {2}.

Cause: One physical resource shouldn't be managed twice by CRS.

Action: Delete and re-create the existing resource or update it.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00012: Invalid cluster node: {0}.

Cause: The named node is not in the cluster.

Action: Specify the correct node name. Refer to CRS command olsnodes for listing node names.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00013: Invalid policy type: {0}.

Cause: Invalid policy type specification.

Action: Refer to ASCRS online help for this operation and read about policy values.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00016: Malformed IP address or invalid host name : {0}.

Cause: Malformed IP address or invalid host name

Action: Supply a valid IP or host name.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00017: Invalid file or directory: {0}.

Cause: The named file or directory doesn't exist.

Action: Specify a valid file or directory for this argument.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00019: Resource not found: {0}.

Cause: Named resource doesn't exist.

Action: Please provide correct resource name.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00020: CRS error while calling {0}. Return code {1}.

Cause: Failure of CRS command as indicated.

Action: Refer to CRS troubleshooting documentation.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00021: Resource of type {0} and name {1} already exists.

Cause: Named resource was already created.

Action: Create a different resource or delete this one and try again.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00022: File {0} cannot be read.

Cause: Unreadable file.

Action: Change the file permission to make it readable for the ASCRS user.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00026: Error trying to retrieve require resources for {0}.

Cause: CRS cs_stat has failed to return complete information for named resource.

Action: Ensure CRS is running, diagnose CRS cs_stat. Refer to CRS troubleshooting documentation.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00028: Error writing or creating file {0}.

Cause: The file cannot be opened or created for writing.

Action: Ensure the file directory exists and the user has write permission on the named file.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00030: VIP {0} provided is up but not on this node.

Cause: The named VIP is already in use on this network.

Action: Forfeit the use of this VIP on the other host, or select a different VIP.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00031: Resource {0} is already down.

Cause: The named resource is already down.

Action: None.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00032: Resource {0} is already up on the node {1}.

Cause: The named resource is already up on the node when trying to start it.

Action: None.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00033: Resource {0} is not in state to switch.

Cause: Resource is not in good state for switch operation.

Action: Please refer to the CRS documentation for resource switchover.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00034: Specified node {1} is not in hosting members for {0}.

Cause: Invalid node member name for the names resource.

Action: Specify the correct node name.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00035: Permissions and/or ownership on resource {0} are not correct for this operation.

Cause: The user is not qualified to perform this operation.

Action: Delegate this task to the owner of this resource.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00036: No parameters to update.

Cause: No updatable information is specified for update operation.

Action: Specify updatable parameter/value. Refer to the online help.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00037: Network Interface {0} is invalid.

Cause: Network Interface is invalid.

Action: Specify a valid network interface that is in working state.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00038: VIP {0} is up on this node but not on the provided interface.

Cause: The named vip is in use by another interface on this node.

Action: Please make sure the vip is used for one interface.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00039: Update operation not allowed if either the target or resource state is not in offline state.

Cause: Resource is not in good state for update operation.

Action: Stop and take the resource offline.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00040: Are you sure you want to delete {0} (y/n) ?

Cause: Need user confirmation for resource deletion.

Action: Answer "y" for yes or "n" for no.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00041: Are you sure you want to stop {0} (y/n) ?

Cause: Need user confirmation for resource stop.

Action: Answer "y" for yes or "n" for no.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00042: Are you sure you want to switch over {0} (y/n) ?

Cause: Need user confirmation for resource switchover.

Action: Answer "y" for yes or "n" for no.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00043: Unrecognized ASCRS resource name {0}.

Cause: Without type information, this name cannot be resolved to a canonical ASCRS resource name.

Action: Use a canonical name, or specify resource type.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00044: ASCRS resource name {0} is not of type {1}.

Cause: The resource name and type are not consistent.

Action: When the name is canonical, ensure its type is consistent if it is specified.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00045: Malformed CRS parameter specification: {0}.

Cause: Syntax error in CRS resource "-o" parameter.

Action: Refer to CRS documentation or ASCRS online help for this operation.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00046: Invalid parameter name "{0}" for this resource.

Cause: This is not an ASCRS parameter or it is not applicable to this resource.

Action: Avoid using this parameter for this resource.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00047: Parameter "{0}" can only assume integer values.

Cause: This argument doesn't accept non-integer values.

Action: Supply a valid integer value for this argument.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00048: Value is out of range for parameter: {0}.

Cause: Integer value is out of valid range.

Action: Follow ASCRS online help for this command for correct value.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00049: "{0}" is not a valid value for parameter "{1}".

Cause: The value for the command-line switch is not valid.

Action: Follow ASCRS online help for this command for the correct value.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00050: No disk is mounted at "{0}".

Cause: No shared disk is mounted on the named mount point.

Action: Mount the shared disk.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00051: No signature found on shared disk at "{0}".

Cause: Signature file is missing on the root of the shared disk.

Action: Create the .ascrssf file on the root of the shared disk.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00052: Value must be an absolute path name for argument: "{0}".

Cause: The path name is not an absolute path.

Action: Use a valid absolute path name.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00053: Path does not exist: "{0}".

Cause: The named path doesn't exist as a disk mount point.

Action: Create the path name if it is intended, or use a different valid path.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00054: Unrecognized AS component name: "{0}".

Cause: User has supplied an invalid AS component name.

Action: Supply the correct WebLogic server name if this is WebLogic resource, or the OPMN component id if it is OPMN resource.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00055: Not a valid AS config file: "{0}".

Cause: The AS config file in the component home is damaged, or this is not an AS component home.

Action: Correct the configuration file and make sure this is a valid AS component home.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00056: Not recognized as an AS component home: "{0}".

Cause: User has supplied an invalid AS component home.

Action: Follow the ASCRS online help to identify the component home correctly.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00057: Node manager is not reachable at "{0}:{1}".

Cause: AS node manager is down.

Action: Make sure node manager is running on the specified host and port.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00058: Managed server "{0}" is not reachable.

Cause: The named AS server is down or invalid as user input.

Action: Make sure the server name is correct and running.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00059: Please run ascrsctl prepare command.

Cause: AS environment is not ready for CRS management.

Action: Run ascrsctl prepare command to set it up.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00060: Please run ascrsctl check command for details.

Cause: AS environment preparation failed.

Action: Run ascrsctl check command for details.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00061: Cannot write on the shared disk mounted at {0}.

Cause: The user doesn't have write permission on the name disk.

Action: Make sure this is the right user for this operation, or grant this user write permission on this disk.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00062: Cannot connect to the node manager with the existing saved credential.

Cause: Cannot log in to AS node manager due to invalid login credential file.

Action: Follow the Oracle Fusion Middleware High Availability Guide to re-create the node manager login credential files.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00063: Cannot connect to server {0} with the existing saved credential.

Cause: Cannot log in to the named AS server due to invalid login credential file.

Action: Follow the Oracle Fusion Middleware High Availability Guide to re-create the WebLogic server login credential files.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00064: CRS command {0} execution encountered I/O errors.

Cause: This command could be missing, corrupted, or other I/O issue.

Action: Ensure this CRS command can be executed manually. Check CRS logs.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00065: Stop of this resource will also stop these dependent resources:

Cause: Other resources are or will be running and it depends on this resource.

Action: Confirm or cancel when this message is prompted.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00066: Start of resource {0} on node {1} completed successfully.

Cause: Another resource is running and it depends on this resource.

Action: Either stop avoid this operation or use -f option.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00067: The current user is not the CRS home owner.

Cause: The current user is not the CRS home owner.

Action: Run this command as CRS home owner.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00068: Circular ASCRS resource dependency is detected.

Cause: The specified dependency resources depends on the updated resource.

Action: Choose different required resources.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00069: Switch of this resource will also switch these related resources:

Cause: Other resources are running that depend on or are required by this resource.

Action: Confirm or cancel when this message is prompted.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00070: Command {0} finished with errors. Refer to ASCRS log files for details.

Cause: The named ASCRS command has failed for some unknown reason.

Action: Refer to ASCRS ascrsctl.log or the ASCRS agent log for this resource.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00071: The number of cluster nodes should be more than one.

Cause: Too few cluster nodes are specified for hosting the resource.

Action: Use default or specify at least two cluster nodes

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00072: Type {0} dependencies cannot be empty for this resource.

Cause: The specified type of dependencies are not allowed to be all removed.

Action: Update the dependencies with other resource names of the desired type

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00073: Not a valid XML file: "{0}".

Cause: The XML file is damaged.

Action: Correct the file and try again.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00074: Value is not a number or out of bound for {0} in configuration for policy {1} and resource type {2}.

Cause: The specified value for the named CRS property is either a non-number or out of range.

Action: Choose a number in range. Consult ASCRS configuration for property ranges.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00075: Invalid monitor name: "{0}".

Cause: The monitor name is not found in ASCRS monitor configuration.

Action: Select a valid monitor name.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00102: ASCRS command is missing or invalid.

Cause: ASCRS command is missing or invalid.

Action: Supply correct ASCRS command, or run "ascrsctl help" for details.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00103: Value is missing or empty for argument -{0}.

Cause: The named argument cannot have an empty value.

Action: Supply the correct value for the argument. Run "ascrsctl help" for details

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00104: No value is needed for argument -{0}.

Cause: The named argument cannot have a value.

Action: Remove the value for the argument. Run "ascrsctl help" for details.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00105: Invalid ASCRS command-line syntax: {0}.

Cause: Invalid ASCRS command-line syntax.

Action: Run "ascrsctl help" for details.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00106: Required argument is missing: -{0}.

Cause: The named argument is mandatory for this operation.

Action: Refer to ascrsctl online help for details about this operation.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00107: Multiple occurrence of the same argument or its aliases not allowed: {0}.

Cause: This argument cannot be followed with multiple values.

Action: Supply a single value or refer to the ascrsctl online help for details.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00108: Invalid database component id: {0}.

Cause: Invalid database component id is specified.

Action: If componentID is specified, it should be dbinstance, dbconsole, jobscheduler (Windows only) or vsswriter (Windows only).

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00140: Online help does not exist for this request.

Cause: Invalid ascrsctl help specification.

Action: Run "ascrsctl help" for details.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00141: Invalid ASCRS resource type {0}.

Cause: Invalid ASCRS resource type.

Action: Run "ascrsctl help" for details.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00142: Invalid ASCRS command-line keyword {0}.

Cause: Invalid ASCRS argument name for ASCRS online help.

Action: Run "ascrsctl help" for details.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00143: Invalid ASCRS resource name: "{0}".

Cause: An ASCRS resource name must start with an English alphabet or number and it can only contain English alphabets, numbers and the dot character. It cannot be called "nil".

Action: Check for invalid special characters in the name.

Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability