Skip Headers
Oracle® Database Error Messages
12c Release 1 (12.1)

E49325-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

85 PRCN-02018 to PRCN-03087

PRCN-02018: Current user {0} is not a privileged user
Cause: Current user did not have sufficient privileges to perform this operation.
Action: Make sure that the user has root privileges on Linux/Unix's and Administrator on Windows.
PRCN-02030: Subnet does not exist for resource {0}
Cause: An attempt was made to query subnet for a network resource configured with Oracle clusterware and it was not found.
Action: Internal error. Contact Oracle Support.
PRCN-02031: Unknown DHCP server name {0} found for resource {1}
Cause: The DHCP server type obtained for the network resource is not a valid server type.
Action: Internal error. Contact Oracle Support.
PRCN-02032: Failed to retrieve DHCP server type {0}
Cause: An attempt to query the DHCP server type for the network resource failed because its value could not be retrieved from the Oracle clusterware resource attributes.
Action: make sure Oracle clusterware is up and running. and also look at the help for the accompanying CRS error message.
PRCN-02033: Failed to update DHCP server type to {0} {1}
Cause: An attempt to update the DHCP server type for the network resource failed because its value could not be updated in the Oracle Clusterware resource attribute.
Action: Make sure that the Clusterware stack is up. Make sure that the user has enough permission to modify node applications. Examine the accompanying message for additional details.
PRCN-02034: Could not find dependent resource {0} for resource {1}: {2}
Cause: Could not get the resource associated with a given resource. Could not get the ASM resource associated with a given ASM disk group resource.
Action: Make sure that clusterware stack is up. Make sure that the network resource associated with this resource has not been removed. Make sure that the user has permission to perform this operation.
PRCN-02035: Port {0} is not available on node(s) or virtual host(s): {1}
Cause: The port specified is already being used by some other applications on the nodes or virtual hosts given.
Action: Stop the applications that are using these ports or specify a different port and try the command again.
PRCN-02036: Failed to retrieve port number(s) for {0}
Cause: An attempt to retrieve the port number(s) for the cluster resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the resource you are querying has been configured. Also take a look at the help for the accompanying error message(s).
PRCN-02037: Failed to retrieve Oracle home for {0}
Cause: An attempt to retrieve Oracle home value for the listener resource failed.
Action: Make sure that the clusterware stack is up. Make sure that listener is configured. If node name is being specified in the command line make sure that the node name is a valid node name. Also look at help for the accompanying error message(s).
PRCN-02038: Failed to update Oracle home {0} for listener {1}
Cause: An attempt to update the Oracle home value for the listener resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the listener is configured. If node name is being specified in the command line make sure that the node name is a valid node name. Make sure that user is a owner or has write permissions to modify the listener resource. Also look at the help for other errors listed in error stack.
PRCN-02039: Failed to retrieve Oracle home for {0} on node {1}
Cause: An attempt to retrieve Oracle home value for the listener resource on a the specified node failed.
Action: Make sure that the clusterware stack is up. Make sure that the listener is configured on the node. Make sure that the node name being passed in the command line is a valid node name. Also look at the help for the accompanying error message(s).
PRCN-02040: Failed to update Oracle home {0} for {1} on node {2}
Cause: Attempt to update value of attribute Oracle home for listener resource on the specified node failed.
Action: Make sure that the clusterware stack is up. Make sure that the listener is configured on the node. Make sure that the user has enough permission to modify the listener. Make sure that the node name being passed in the command line is a valid node name. Also look at the help for other errors listed in error stack.
PRCN-02041: Failed to retrieve properties of {0}
Cause: Failed to retrieve properties of the given entity.
Action: Make sure that user has permission to read resource attribute.
PRCN-02042: Failed to set properties {0} of {1}
Cause: Failed to update properties of the given entity.
Action: Make sure that user has permission to update resource attribute.
PRCN-02043: Multiple network resources {0} exist on the cluster
Cause: More than one network resource has been configured and the one to be used for creating this resource has not been specified.
Action: Use the '-netnum <net_num>' option to specify the network to be used and retry the command again.
PRCN-02044: No listener exists
Cause: No listener has been configured.
Action: Use netca or srvctl to add/configure a listener.
PRCN-02045: No network exists
Cause: No network has been configured.
Action: Use 'srvctl add nodeapps' to add/configure network resource.
PRCN-02046: Netmask does not exist for resource {0}
Cause: An attempt to retrieve the subnet information for the network resource resulted in not finding subnet mask.
Action: Internal error. Contact Oracle Support.
PRCN-02047: VIP {0} exists
Cause: The VIP with specified name has been registered in CRS.
Action: Remove the existing VIP before registering it again.
PRCN-02048: The network number {0} is already registered for subnet ''{3}'' and adapters ''{4}''. Can not add network number {0} for the specified subnet ''{1}'' and adapters ''{2}''.
Cause: The network number is taken by a registered network resource.
Action: Use a different network number to add a new network resource with the specified subnet and adapters, or modify existing network using the command 'srvctl modify nodeapps'.
PRCN-02049: The network attributes specified (network number: {0}, subnet: {1}, adapters: {2}) conflict with an already registered network (network number: {3}, subnet: {4}, adapters: {5})
Cause: The network resource is registered with different network number
Action: Use the registered network resource with the registered network number or provide different subnet or adapters.
PRCN-02050: The requested VIP (nodename: {0}, VIP name: {1}, network number: {2}) has the same VIP name but different network number or preferred node than the registered VIP (nodename: {3}, VIP name: {4}, network number: {5}).
Cause: One VIP name (and IP address) can only be used by one VIP with the same network number on the same node.
Action: Use a different VIP name or IP address.
PRCN-02051: The requested VIP (nodename: {0}, VIP name: {1}, network number: {2}) has the same network number and the same preferred node but different VIP name with the registered VIP (nodename: {3}, VIP name: {4}, network number: {5}).
Cause: One network resource on one preferred node can have only one cluster VIP.
Action: Use different network number or preferred node to register different VIP.
PRCN-02052: Failed to modify network number {0} to use subnet "{1}" with subnet mask "{2}", adapters "{3}" and address type "{4}"
Cause: CRS was unable to modify the network resource to use new subnet/netmask/interface/address type.
Action: Check accompanying error message(s) for details, then ensure that:

- The clusterware stack is up.

- The subnet, netmask, address type and adapters values are correct.

- The network interface referred to is running.

- The user trying to modify the network resource has root privileges.

PRCN-02053: Failed to modify ONS listening port for local client connections to {0}
Cause: CRS unable to modify the ONS listening port for local connections
Action: Make sure that clusterware stack is up. If the port is in use by another application, try using a different port.
PRCN-02054: Failed to modify ONS listening port for remote client connections to {0}
Cause: CRS unable to modify the ONS listening port for remote client connections
Action: Make sure that clusterware stack is up. If the port is in use by another application, try using a different port.
PRCN-02055: Failed to update port number(s) to {0} for {1}
Cause: An attempt to update the listener port failed for the nodes of the cluster.
Action: The port could be in use. Try using different port. If node name was specified in the command line make sure that the node name is a valid node name. Also look at the help for the accompanying error message(s).
PRCN-02056: Invalid listener protocol type {0}
Cause: The specified listener protocol type is invalid.
Action: Provide a valid listener protocol type. It can be TCP, TCPS, IPC, NMP, or SDP.
PRCN-02057: Invalid listener protocol value {0}
Cause: The specified listener protocol value is invalid.
Action: Provide a valid listener protocol value. It cannot contain special characters ':,/'
PRCN-02058: Invalid listener protocol ENDPOINTS {0}. Delimiter is "{1}", invalid part is "{2}".
Cause: The specified listener ENDPOINTS are invalid.
Action: Provide valid listener protocol ENDPOINTS. It cannot contain invalid part.
PRCN-02059: Invalid listener port number {0}
Cause: The specified listener port number is invalid.
Action: Provide a valid listener port number.
PRCN-02060: Duplicated listener protocol value {0}
Cause: The specified listener protocol value is a duplication of another one.
Action: Remove duplicated listener protocol value.
PRCN-02061: Failed to add listener {0}
Cause: An attempt to add listener failed because endpoints were not specified correctly or other reasons.
Action: Review the underlying error messages that provide the details of which resources failed to create. Check the cause and action for the individual resource creation failure. If the endpoints were not specified correctly, correct endpoints.
PRCN-02062: The specified hostname or address {0} cannot be resolved.
Cause: An invalid IP address or unresolvable hostname was specified.
Action: If IP address is specified then make sure that it is of legal length. If a host name is specified than make sure that the host name resolves to an IP address.
PRCN-02063: Failed to modify OC4J listening port to {0}
Cause: CRS unable to modify the OC4J instances listening port.
Action: Make sure that clusterware stack is up. If the port is in use by another application, try using a different port.
PRCN-02064: Found {0} VIPs for {1}
Cause: A conflict was found in VIP resource definition: either more than one VIP is using the same name or address, or a VIP is using the same name or address as a real host.
Action: Ensure that each VIP is defined with a distinct name and address relative to other VIPs and hosts in the network.
PRCN-02065: Ports {0} are not available on the nodes given
Cause: The ports specified are already being used by some other applications in one or more of the specified nodes.
Action: Stop the applications that are using these ports or specify different ports.
PRCN-02066: Failed to retrieve cluster listener for {0} because it has the type of Single Client Access Name Listener
Cause: Failed to use cluster listener APIs or srvctl commands for specified listener.
Action: Use Single Client Access Name Listener (SCAN listener) APIs or srvctl commands (srvctl <verb> scan_listener) for specified listener name.
PRCN-02067: Port {0} is not available on nodes: {1}
Cause: The port specified is already being used by other application.
Action: Stop the application that is using this port or specify a different port.
PRCN-02068: Failed to check the port availability
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRCN-02069: Unable to retrieve the list of nodes
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRCN-02070: Failed to validate network. No interface matches required network (subnet: {0}, netmask: {1} adapters: {2}).
Cause: No intefaces were found that match the specified network.
Action: Specify a subnet that exists on all nodes, or reconfigure the nodes to ensure that the specified subnet exists on all nodes.
PRCN-02071: Failed to update attribute USE_EVM to {0}
Cause: An attempt to update the attribute value of USE_EVM for ONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-02072: Failed to get multicast port for events from EONS
Cause: An attempt to get multicast port for events from EONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-02073: Failed to remove EONS
Cause: An attempt to remove EONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-02074: Specified check interval of {0} minutes is below the minimum check interval {1} minutes
Cause: The CVU resource check interval specified was less than the minimum check interval.
Action: Retry the operation with a interval greater than or equal to the minimum check interval.
PRCN-02075: Failed to modify the CVU RUN_INTERVAL attribute to {0}
Cause: CRS was unable to modify the CVU RUN_INTERVAL attribute.
Action: Make sure that the Clusterware stack is up. Make sure that the user is an owner or has write permissions to modify the CVU resource. Check for and respond to any accompanying error messages.
PRCN-02076: failed to retrieve the CVU RUN_INTERVAL attribute for resource "{0}"
Cause: An attempt to retrieve the RUN_INTERVAL attribute for the Cluster Verification Utility cluster resource failed.
Action: Make sure that the Clusterware stack is up. Make sure that the CVU resource has been configured. Check for and respond to any accompanying error messages.
PRCN-02077: Failed to modify the CVU CHECK_RESULTS attribute to "{0}"
Cause: CRS was unable to modify the CVU CHECK_RESULTS attribute.
Action: Make sure that Clusterware stack is up. Make sure that the CVU resource has been configured. Check for and respond to any accompanying error messages.
PRCN-02078: Failed to retrieve the CVU CHECK_RESULTS for "{0}"
Cause: An attempt to retrieve the CHECK_RESULTS attribute for the CVU cluster resource failed.
Action: Make sure that the Clusterware stack is up. Make sure that the CVU resource has been configured. Check for and respond to any accompanying error messages.
PRCN-02079: Port {0} is out of the valid range, between 1 and 65535 and cannot be used on any of the nodes given
Cause: The port number that was provided was either less than 1 or greater than 65535.
Action: Make sure the port provided has a value between 1 and 65535.
PRCN-02080: Address type does not exist for resource {0}
Cause: An attempt was made to query address type for a network resource configured with Oracle clusterware and it was not found.
Action: Contact Oracle Support Services.
PRCN-02081: Failed to modify network number {0} to use subnet "{1}" with prefix length "{2}", adapters "{3}" and address type "{4}"
Cause: CRS was unable to modify the network resource to use new subnet/prefix length/interface/address type.
Action: Check accompanying error message(s) for details, then ensure that:

- The clusterware stack is up.

- The subnet, prefix legth, address type and adapters values are correct.

- The network interface referred to is running.

- The user trying to modify the network resource has root privileges.

PRCN-02082: Setting the server type to "{0}" is not allowed for an {1} network
Cause: An attempt was made to set the IPv4 network server type to 'autoconfig' or to set the IPv6 network server type to 'static' .
Action: Make sure that the network is IPv4 or IPv6 when trying to set the server type to 'dchp' or 'autoconfig' respectively.
PRCN-02083: Modifying the server type from "{0}" to "{1}" directly is not allowed
Cause: An attempt was made to change the network server type from 'static' to a dynamic type (or the reverse) without the required intermediate setting of 'mixed'.
Action: First change the server type to 'mixed', then retry the command.
PRCN-02084: Failed to update the {0} server type to "{1}" {2}
Cause: An attempt to update the server type for the network resource failed because its value could not be updated in the Oracle Clusterware resource attribute.
Action: Make sure that the Clusterware stack is up. Make sure that the user has enough permission to modify node applications. Examine the accompanying message for additional details.
PRCN-02085: There exists already another network ("{0}") with the same IPv6 link-local subnet
Cause: Already registered another nework with the same IPv6 link-local subnet.
Action: Make sure that the IPv6 link-local subnet is unique among the existing networks.
PRCN-02086: Failed to modify the CRSHOME_SPACE_ALERT_MODE attribute of the CVU resource to "{0}"
Cause: Cluster Ready Service (CRS) was unable to modify the CRSHOME_SPACE_ALERT_MODE attribute of the Cluster Verification Utility (CVU) CRS resource.
Action: Make sure that the Oracle Clusterware stack is up. Make sure that the CVU resource has been configured. Examine and respond to any accompanying error messages.
PRCN-02087: Failed to retrieve the CRSHOME_SPACE_ALERT_MODE attribute of the CVU resource
Cause: An attempt to retrieve the CRSHOME_SPACE_ALERT_MODE attribute of the Cluster Verificiation Utility (CVU) cluster resource failed.
Action: Make sure that the Oracle Clusterware stack is up. Make sure that the CVU resource has been configured. Examine and respond to any accompanying error messages.
PRCN-03000: The IPMI configuration failed on all nodes
Cause: The node names were invalid or were valid but had no IPMI device present.
Action: Make sure that all nodes are reachable and the IPMI device exists on those nodes.
PRCN-03001: The IPMI configuration failed on one or more nodes
Cause: There was at least one node with invalid name or with no IPMI device.
Action: Make sure that all nodes are reachable and the IPMI device exists on those nodes.
PRCN-03002: There is no network resource configured for the cluster
Cause: A request to add a listener was rejected due to the lack of a network resource.
Action: Use the command 'srvctl add network' to configure the network first, then retry the command.
PRCN-03003: Failed to unregister EONS resource type
Cause: A request to unregister the EONS resource type failed because of the reason provided by an accompanying exception message.
Action: Examine the accompanying error message for details.
PRCN-03004: Listener {0} already exists
Cause: The specified listener was already created.
Action: Use the command 'srvctl modify listener' to modify attributes if needed.
PRCN-03005: Failed to add or use registered network {0} with network interfaces ''{1}'' because the network was already registered for network interfaces ''{2}''
Cause: The network resource was already registered with different interfaces.
Action: Use the same network interfaces as the one registered with network resource.
PRCN-03006: Failed to add or use registered network {0} with network interfaces ''{1}'' because the network was already registered with no interface specified
Cause: The network resource was already registered with no user specified interface.
Action: Do not specify network interface as the system decides the network interface.
PRCN-03007: Failed to add or use registered network {0} with network mask ''{1}'' because the network was already registered for network mask ''{2}''
Cause: The network resource was already registered with a different network mask.
Action: Use the same network mask as the one registered with network resource.
PRCN-03008: Failed to add or use registered network {0} with network subnet ''{1}'' because the network was already registered for network subnet ''{2}''
Cause: The network resource was already registered with a different network subnet.
Action: Use the same network subnet as the one registered with network resource.
PRCN-03009: Failed to retrieve log file attribute for {0} resource
Cause: An attempt to retrieve the log file attribute for the cluster resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the resource you are querying has been configured. Refer also to any accompanying error messages for details.
PRCN-03010: Failed to retrieve log component attribute for {0} resource
Cause: An attempt to retrieve the log component attribute for the cluster resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the resource you are querying has been configured. Refer also to any accompanying error messages for details.
PRCN-03011: Failed to retrieve debug file attribute for {0} resource
Cause: An attempt to retrieve the debug file attribute for the cluster resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the resource you are querying has been configured. Refer also to any accompanying error messages for details.
PRCN-03012: Failed to retrieve debug component attribute for {0} resource
Cause: An attempt to retrieve the debug component attribute for the cluster resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the resource you are querying has been configured. Refer also to any accompanying error messages for details.
PRCN-03013: Failed to update log file attribute of {0} resource
Cause: An attempt to update the attribute value of LOG_FILE for ONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-03014: Failed to update log component attribute of {0} resource
Cause: An attempt to update the attribute value of LOG_COMP for ONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-03015: Failed to update debug file attribute of {0} resource
Cause: An attempt to update the attribute value of DEBUG_FILE for ONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-03016: Failed to update debug component attribute of {0} resource
Cause: An attempt to update the attribute value of DEBUG_COMP for ONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-03017: Specified check interval of {0} minutes exceeds the maximum check interval {1} minutes
Cause: The CVU resource check interval specified was more than the maximum check interval.
Action: Retry the operation with an interval smaller than or equal to the maximum check interval.
PRCN-03018: Addition of listener version {0} is not allowed using srvctl version {1}
Cause: The versions of srvctl used and listener to be created did not match.
Action: Use the same version of srvctl as listener.
PRCN-03019: Not allowed to modify the network address type from {0} to {1}
Cause: An attempt was made to change the network address type directly from "IPv4" to "IPv6" or vice versa.
Action: Ensure that transitions between IPv4 and IPv6 first set an intermediate address type of 'both'.
PRCN-03020: Invalid LISTENER type {0}
Cause: The LISTENER type supplied is not valid.
Action: This is an internal error; contact Oracle Support Services.
PRCN-03021: No ASM listener exists
Cause: No ASM listener was configured for cluster ASM.
Action: Use the command 'srvctl add listener -asm' to configure an ASM listener.
PRCN-03022: Leaf ASM listener does not exist
Cause: Leaf ASM listener was not configured for leaf ASM.
Action: Use the command 'srvctl add listener -leaf' to configure an ASM listener.
PRCN-03023: Unable to retrieve information about the network subnet mask
Cause: An error occurred while obtaining information about the network subnet mask.
Action: Examine the accompanying error messages for details.
PRCN-03024: Mismatch between the subnet mask of the VIP ({0}) and that of the associated network ({1})
Cause: The subnet mask of the VIP address did not match the one of the associated network resource.
Action: Make sure the VIP address has the same subnet mask as the network it belongs to.
PRCN-03025: Mismatch between the prefix length of the VIP ({0}) and that of the associated network ({1})
Cause: The prefix length of VIP address did not match the one of the associated network resource.
Action: Make sure the VIP address has the same prefix length as the network it belongs to.
PRCN-03026: "{0}" is not a valid IPv4 network mask or IPv6 prefix length
Cause: The provided string was neither a valid IPv4 network mask nor a valid IPv6 prefix length.
Action: Contact Oracle Support.
PRCN-03027: Unable to determine the network type
Cause: An error occured while retrieving the USR_ORA_AUTO network attribute value.
Action: Examine the accompanying error messages for details.
PRCN-03028: VIP {0} address modification is not allowed because the network type is "{1}"
Cause: An attempt was made to change the USR_ORA_VIP value for a VIP on an IPv4 network with 'dhcp' network type or on an IPv6 network with 'autoconfig' network type.
Action: Make sure that the network type is either 'static' or 'mixed' for the IPv4 or IPv6 type of the VIP address that you try to modify.
PRCN-03029: Transition for a network that contains both IPv4 and IPv6 addresses to an {0} network of network type 'mixed' is not allowed
Cause: An attempt was made to transiton from a network with both IPv4 and IPv6 addresses to a network that has only one type of addresses and is of network type 'mixed'.
Action: Finish the transition from 'DHCP' or 'autoconfig' to 'static' or vice versa and retry.
PRCN-03030: Unable to retrieve the list of VIPs for network with number {0}
Cause: An error occurred while obtaining information about the VIPs that depend on the given network.
Action: Examine the accompanying error messages for details.
PRCN-03031: Unable to retrieve information about the address of VIP resource "{0}"
Cause: An error occurred while obtaining information about the address of the given VIP resource.
Action: Examine the accompanying error messages for details.
PRCN-03032: The VIP for hosting node "{0}" on network number {1} does not contain an {2} address or a VIP name that resolves to an {2} address
Cause: The given VIP did not contain an IP address or a VIP name that resovled to an IP address of the displayed address type.
Action: Make sure that the VIP contains an IP address or a VIP name that resolves to an IP address of the displayed address type.
PRCN-03033: Unable to retrieve the SCAN name for network {0}
Cause: An error occurred while obtaining the Single Client Access Name (SCAN) name for the specified network.
Action: Examine the accompanying error messages for details.
PRCN-03034: SCAN name "{0}" resolves to one or more {1} addresses
Cause: The given SCAN name resolved to the given type (IPv4 or IPv6) of addresses.
Action: Make sure that the SCAN name does not resolve to addresses of the given address type.
PRCN-03035: SCAN name "{0}" resolves to {1} addresses instead of {2}
Cause: The given SCAN name resolved to a wrong number of addresses.
Action: Make sure that the SCAN name resolves to the same number of addresses as the existing SCAN VIPs by using the 'srvctl modfiy scan -scanname <scan_name>' command.
PRCN-03036: Unable to retrieve the list of SCAN VIPs that depend on network with network number {0}
Cause: An error occurred while obtaining information about the SCAN VIPs that depend on the given network.
Action: Examine the accompanying error messages for details.
PRCN-03037: Unable to retrieve information about the address of SCAN VIP resource "{0}"
Cause: An error occurred while obtaining information about the address of the given SCAN VIP resource.
Action: Examine the accompanying error messages for details.
PRCN-03038: SCAN name "{0}" resolves to different addresses than those of the existing SCAN VIPs
Cause: While attempting to change the network address type, it was found that the given SCAN name resolved to a set of addresses that are different from the ones of the existing SCAN VIPs.
Action: Make sure that the SCAN name resolves to the same addresses as those of the existing SCAN VIPs by using the command 'srvctl modifiy scan -scanname <scan_name>'.
PRCN-03039: Unable to remove the {0} address from the VIP resource "{1}"
Cause: An error occurred while trying to remove either the IPv4 or the IPv6 address from all the VIPs on the network.
Action: Examine the accompanying error messages for details.
PRCN-03040: Unable to remove the {0} address from the SCAN VIP resource "{1}"
Cause: An error occurred while trying to remove either the IPv4 or the IPv6 address from all the SCAN VIPs on the network.
Action: Examine the accompanying error messages for details.
PRCN-03041: Failed to modify the network address type
Cause: An error occurred while trying to modify the network address type.
Action: Examine the accompanying error messages for details.
PRCN-03042: Subnet "{0}" is already in use by a network on the cluster
Cause: The specified subnet was already registered with another network on the cluster.
Action: Use a unique subnet and retry the operation.
PRCN-03043: Failed to verify the uniqueness of subnet "{0}" among the networks of the cluster
Cause: An error occurred while trying to verify the uniqueness of the subnet.
Action: Examine the accompanying error messages for details.
PRCN-03044: There is no {0} subnet for network with number {1}
Cause: No subnet of the given address type was found for the specified network.
Action: Modify the network to include a subnet of the specified address type and retry.
PRCN-03045: Management listener is not running in the cluster
Cause: An attempt to retrieve the IP address failed because the management listener was not running.
Action: Start the management listener using the command 'srvctl start mgmtlsnr'.
PRCN-03046: Failed to retrieve the IP address of the management listener
Cause: An attempt to retrieve the IP address of the management listener failed in querying the management listener resource.
Action: Stop and restart the management listener using the commands 'srvctl stop mgmtlsnr' and 'srvctl start mgmtlsnr', then retry the command. If the problem persists, contact Oracle Support Services.
PRCN-03047: Failed to set or get the subnet of the listener resource
Cause: An attempt to set or retrieve the subnet of the listener failed because the operation is not allowed for this resource.
Action: Use the 'srvctl' commands on the underlying network resource to set or get the subnet value or create a different listener.
PRCN-03048: Listener subnet "{0}" is not a subnet classified {1}
Cause: While adding a management listener, the specified subnet was not classified as a subnet of the required type.
Action: Specify a subnet that is classified as required as reported by using the command 'oifcfg getif', or change the subnet classification to the required type using the command 'oifcfg setif'.
PRCN-03049: Cannot change the network subnet address type to 'both' because it has only an {0} subnet address
Cause: An attempt to modify the network address type failed because the network had only one type of subnet address instead of both IPv4 and IPv6 subnet addresses.
Action: Make sure that the network has been configured with both IPv4 and IPv6 subnets using the command 'srvctl modify network -subnet'.
PRCN-03050: SCAN name "{0}" resolves to different number of IPv4 ({1}) and IPv6 ({2}) addresses
Cause: An attempt to change subnet address type to 'both' was rejected because the given SCAN name resolved to a different number of IPv4 and IPv6 addresses.
Action: Make sure that the SCAN name resolves to the same number of IPv4 and IPv6 addresses.
PRCN-03051: Unable to retrieve a list of the hub nodes
Cause: While attempting to change the subnet address type, an error occured while retrieveing a list of the hub nodes.
Action: Examine the accompanying message for details.
PRCN-03052: The following nodes do not have VIPs configured for network: {0}
Cause: While attempting to change the subnet, some nodes were found to be missing VIP addresses.
Action: Configure VIP addresses for the given nodes using the command 'srvctl add VIP'.
PRCN-03053: The following nodes do not have configured VIPs with IPv4 addresses on network {0}: {1}
Cause: A request to change the subnet address type was rejected because the specified nodes had VIPs which did not have any configured IPv4 address or a name that resolved to an IPv4 address.
Action: Make sure that the given nodes have configured VIPs with IPv4 address or name that resolved to an IPv4 address.
PRCN-03054: The following nodes do not have configured VIPs with IPv6 addresses on network {0}: {1}
Cause: A request to change the subnet address type was rejected because the specified nodes had VIPs which did not have any configured IPv6 address or a name that resolved to an IPv6 address.
Action: Make sure that the given nodes have configured VIPs with IPv6 address or name that resolved to an IPv6 address.
PRCN-03055: Cannot change the network subnet address type to 'both' for the following VIP related issues: {0}
Cause: An attempt to modify the network address type was rejected because the network either had no VIPs on one or more nodes or the VIPs did not have the expected address type.
Action: Examine the accompanying message for details.
PRCN-03056: The VIP address "{0}" is an {1} address, while network {2} has no {3} subnet
Cause: The VIP with the given address had a different address type than the network subnet address type.
Action: Either modify the network via the command 'srvctl modify network -subnet' to include the missing type or make sure that the VIP address type matches the address type of the network subnet.
PRCN-03057: The VIP name "{0}" resolves to one or more {1} addresses ("{2}"), while network {3} has no {1} subnet
Cause: The VIP name mapped to an address with different address type than the network subnet address type.
Action: Either modify the network via the command 'srvctl modify network -subnet' to include the missing type or make sure that the VIP name resolves to addresses that matche the address type of the network subnet.
PRCN-03058: Cannot update listener that is not an ASM listener
Cause: An attempt was made to update a non-ASM listener.
Action: Specify the name of an ASM listener on the command line. Use the command 'srvctl config listener -asmlistener' to display ASM listener names.
PRCN-03059: Unable to retrieve the network number
Cause: An error occurred while attempting to retrieve the network number.
Action: Examine the accompanying error messages for details.
PRCN-03060: Unable to retrieve the list of configured networks on the cluster
Cause: An error occurred while attempting to retrieve the set of configured network resources 'ora.net*.network'.
Action: Examine the accompanying error messages for details.
PRCN-03061: The specified network server type "{0}" is invalid for an "IPv4" network.
Cause: The network server type was specified as 'autoconfig' which is not valid for an IPv4 network.
Action: The network server type must be 'static' or 'dhcp' or 'mixed'.
PRCN-03062: The specified network server type "{0}" is invalid for an "IPv6" network.
Cause: The network server type was specified as 'dhcp' which is not valid for an IPv6 network.
Action: The network server type must be 'static' or 'autoconfig' or 'mixed'.
PRCN-03063: Failed to find an available port in the default TCP port range {0} - {1} among nodes: {2}
Cause: An attempt to find an available default TCP port failed because all default TCP ports were used by some other applications in at least one node in the cluster.
Action: Specify a port to be used outside the default TCP port range using 'srvctl add listener -endpoints'
PRCN-03064: The user "{0}" could not be found on the cluster
Cause: The user specified as the listener owner was not a known OS user name.
Action: Enter the name of an existing OS user as the owner of the specified listener.
PRCN-03065: Cannot configure the default network as leaf.
Cause: An attempt was made to configure the default network with the leaf category.
Action: Provide a non-default network when using SRVCTL to add a network resource with the '-leaf' flag.
PRCN-03066: Cannot configure network resource as leaf because cluster is not configured as Flex Cluster.
Cause: An attempt was made to add a network resource with the leaf category in a cluster not configured as Flex Cluster.
Action: Use SRVCTL without the '-leaf' flag when adding a network resource in a non-Flex Cluster system. Or, convert the cluster to a Flex Cluster before doing this operation.
PRCN-03067: Unable to modify the owner for an ASM or leaf listener.
Cause: An attempt was made to modify the owner of a ASM or leaf listener resource.
Action: Repeat the operation specifying a node listener.
PRCN-03068: Unable to determine whether the VIP address "{0}" belongs to network with number {1}
Cause: An error occurred while trying to determine whether the VIP address matches the network subnet.
Action: Examine the accompanying error messages for details.
PRCN-03069: Unable to determine whether the VIP address "{0}" belongs to network with number {1} and subnet number {2}
Cause: An error occurred while trying to determine whether the VIP address matches the network subnet.
Action: Examine the accompanying error messages for details.
PRCN-03070: The VIP address "{0}" does not belong to network with number {1} and subnet number {2}
Cause: The VIP address did not match the subnet of the specified network.
Action: Make sure that the VIP address or the address the VIP name resolves to matches the network subnet.
PRCN-03071: Invalid address or unknown host "{0}"
Cause: An attempt was made to configure a network resource with an invalid address or host name.
Action: Specify a resolvable host name or an IP address of legal length.
PRCN-03072: Unable to modify the home node of the HAVIP.
Cause: An attempt to modify the home node of the HAVIP failed because there was an export file system registered with the same path, export options and HAVIP home node.
Action: Provide a different home node or examine the accompanying error messages for details.
PRCN-03073: Invalid node name: {0}
Cause: The home node name was invalid. The home node name must contain alphanumeric characters and hyphens only. It cannot be a fully qualified domain name.
Action: Check the home node name and try again.
PRCN-03074: The specified ping target list contains duplicate addresses.
Cause: The specified ping target list was invalid. It contained duplicate IP addresses or host names that resolve to duplicate IP addresses.
Action: Reissue the command without elements that are or resolve to the same
PRCN-03075: The specified TCP ports ({0}) are configured for another ASM or management listener.
Cause: An attempt to add an ASM or management listener failed because one or more of the specified ports were already configured for another ASM or management listener.
Action: Retry the command specifying a port not in use by another ASM or management listener.
PRCN-03076: Unable to find an available port in the default TCP port range {0} - {1}
Cause: An attempt to find an available default TCP port failed because all default TCP ports were configured for other ASM or management listeners.
Action: Retry the command specifying a port outside the default TCP port range.
PRCN-03077: The specified ports {0} are in the privileged ports range.
Cause: The specified ports were in the privileged ports range (0-1023) which can only be used by daemons running as user 'root'.
Action: Specify port numbers greater than 1023.
PRCN-03078: Setting the address type to "ipv4" is not allowed because the existing network address type is "ipv6".
Cause: An attempt to change the address type from 'ipv6' to 'ipv4' directly was rejected because the address type must first be changed to 'both' then to 'ipv4'.
Action: Use the command 'srvctl modify network' to change the network type to 'both' by adding an IPv4 subnet and retry the command.
PRCN-03079: Setting the address type to "ipv6" is not allowed because the existing network address type is "ipv4".
Cause: An attempt to change the address type from 'ipv4' to 'ipv6' directly was rejected because the address type must first be changed to 'both' then to 'ipv6'.
Action: Use the command 'srvctl modify network' to change the network type to 'both' by adding an IPv6 subnet and then retry the command.
PRCN-03080: The network configuration cannot be modified when the network type is 'mixed'.
Cause: An attempt to modify a network configuration was rejected because either the IPv4 or IPv6 subnet is configured with 'mixed' network type.
Action: Change the network type to 'static' or 'dhcp' or 'autoconfig' before proceeding with the configuration change.
PRCN-03081: The specified subnet ({0}) is already configured for ASM listener "{1}".
Cause: An attempt to add or modify an ASM listener was rejected because the specified subnet was already used for another ASM listener.
Action: Retry the command specifying a subnet that is not in use by another ASM listener.
PRCN-03082: An attempt to modify the OC4J port failed because OC4J is running. Use -force to force stop and restart of OC4J.
Cause: A request to modify the port number of OC4J was rejected because such modification requires OC4J to be stopped and restarted.
Action: Use '-force' option to force restart of OC4J.
PRCN-03083: failed to modify OC4J when trying to set the HTTP port and Remote Method Invocation (RMI) port to the same number {0}
Cause: A request to modify the OC4J port numbers was rejected because the HTTP port number was the same as the Remote Method Invocation (RMI) port number.
Action: Choose a different port that is not in use.
PRCN-03084: failed to modify RMI port for OC4J to use the port number {0} that is used by the listener {1}
Cause: A request to modify the OC4J Remote Method Invocation (RMI) port number was rejected because the specified port was already used by a node listener.
Action: Choose a different port number that is not used as an HTTP port or a node listener port.
PRCN-03085: failed to modify HTTP port for OC4J to use the port number {0} that is used by the listener {1}
Cause: A request to modify the OC4J HTTP port number was rejected because the specified port was already used by a node listener.
Action: Choose a different port number that is not used as an RMI port or a node listener port.
PRCN-03086: failed to merge files "{0}" and "{1}"
Cause: An attempt to merge the two indicated network configuration files failed.
Action: Examine the accompanying error messages for details, resolve issues and retry.
PRCN-03087: An attempt to extract the DNS name server IP address from file "{0}" failed.
Cause: No DNS name server IP address was specified in the specified file.
Action: Make sure that there is a line in the specified file that starts with 'nameserver' followed by the GNS name server IP address.