PRCS-01000 to PRCS-01172

115 PRCS-01000 to PRCS-01172

PRCS-01000: Failed to get enabled status of {0}: Cause: An attempt to check whether a server is enabled failed.; Action: Examine the accompanying error messages for details.
PRCS-01001: Failed to enable {0}: Cause: An attempt to enable the specified server failed.; Action: Examine the accompanying error messages for details.
PRCS-01002: Failed to disable {0}: Cause: An attempt to disable the specified server failed.; Action: Examine the accompanying error messages for details.
PRCS-01005: Failed to create server {0}: Cause: An attempt to create the specified server failed.; Action: Examine the accompanying error messages for details.
PRCS-01006: Failed to get server for node {0}: Cause: An attempt to get server for the specified node failed.; Action: Examine the accompanying error messages for details.
PRCS-01007: Server pool {0} already exists: Cause: The specified server pool already exists.; Action: Examine the accompanying error messages for details.
PRCS-01008: Server pool {0} does not exist: Cause: The specified server pool does not exist.; Action: Use the srvctl command to create server pool.
PRCS-01009: Failed to create server pool {0}: Cause: An attempt to create specified server pool failed.; Action: Examine the accompanying error messages for details.
PRCS-01010: Failed to get {0} of server pool {1}: Cause: An attempt to get the attribute value of the specified server pool failed.; Action: Examine the accompanying error messages for details.
PRCS-01011: Failed to modify server pool {0}: Cause: An attempt to modify the specified server pool failed.; Action: Examine the accompanying error messages for details.
PRCS-01012: Failed to remove server pool {0}: Cause: Failed to unregister server pool. This message is followed by the reason for failure.; Action: Retry after resolving the issue reported in the failure message.
PRCS-01013: Failed to look up server pool {0}: Cause: An attempt to get the specified server pool failed.; Action: Examine the accompanying error messages for details.
PRCS-01014: Server {0} is already part of server pool {1}: Cause: An attempt to add the server as a candidate for the specified server pool failed because the server is already in the pool's SERVER_NAME attribute.; Action: No action is needed.
PRCS-01015: Server {0} is not part of server pool {1}: Cause: An attempt to remove the server from the SERVER_NAMES attribute of the server pool failed because the specified server is not in the pool's SERVER_NAME attribute.; Action: Add the server to the server pool.
PRCS-01016: Failed to resolve Single Client Access Name {0}: Cause: An attempt to resolve specified Single Client Access Name to a list of IP addresses failed because Single Client Access Name could not be resolved in DNS using nslookup or using other lookup methods.; Action: Check whether the specified Single Client Access Name is correct. Review the underlying error messages that provide the details of which resource failed to resolve. Check the cause and action for the individual error. If Single Client Access Name should be resolved in DNS, check the configuration of Single Client Access Name in DNS.
PRCS-01017: Failed to configure Single Client Access Name {0}: Cause: An attempt to add cluster configuration for Single Client Access Name failed.; 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.
PRCS-01018: Failed to add cluster configuration for Single Client Access Name listener {0}: Cause: An attempt to configure Single Client Access Name 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.
PRCS-01019: Failed to remove the configuration for Single Client Access Name listener {0}: Cause: An attempt to remove the configuration of Single Client Access Name listener failed because other resources depended on it or other reasons.; Action: Review the underlying error messages that provide the details of which resources failed to remove. Stop Single Client Access Name listener resource before removing it. Can consider using force flag to remove Single Client Access Name listener resources if no other resources depend on it.
PRCS-01020: Failed to enable Single Client Access Name resources {0}: Cause: An attempt to enable Single Client Access Name resources failed.; Action: Review the underlying error messages that provide the details of which resources failed to enable. Check the cause and action for the individual resource creation failure.
PRCS-01021: Failed to disable Single Client Access Name resources {0}: Cause: An attempt to disable Single Client Access Name resources failed because current user did not have sufficient privileges to perform this operation or other reasons.; Action: Review the underlying error messages that provide the details of which resources failed to disable. Check the cause and action for the individual resource failure. Make sure that the user has root privileges on Linux/Unix's and Administrator on Windows.
PRCS-01022: Failed to start Single Client Access Name resources {0}: Cause: An attempt to start Single Client Access Name resources failed.; Action: Review the underlying error messages that provides the details of which resources failed to start.
PRCS-01023: Failed to stop Single Client Access Name resources {0}: Cause: An attempt to stop Single Client Access Name resources failed because Single Client Access Name listeners were not stopped/relocated or other reasons.; Action: Review the underlying error messages that provides the details of which resources failed to stop. Check the cause and action for the individual resource creation failure. Stop Single Client Access Name listeners first or use force flag to stop Single Client Access Name Virtual Internet Protocol(VIP) resources if no other resources depend on them.
PRCS-01024: Failed to remove Single Client Access Name Virtual Internet Protocol(VIP) resources {0}: Cause: Could not remove Single Client Access Name Virtual Internet Protocol(VIP) resources because the resources are running or Single Client Access Name listeners depend on or other reasons.; Action: Review the underlying error messages that provides the details of which resources failed to remove. Stop the Single Client Access Name VIPs and Single Client Access Name listeners, then remove Single Client Access Name listeners. Or use force flag to remove Single Client Access Name Virtual Internet Protocol(VIP) resources if no other resources depend on them.
PRCS-01025: Could not find any Single Client Access Name (SCAN) Virtual Internet Protocol (VIP) resources using filter {0}: Cause: An attempt to retrieve the SCAN VIP resources failed.; Action: Ensure that the resource name supplied is correct. Examine the accompanying error messages for additional details.
PRCS-01026: Could not find any Single Client Access Name (SCAN) listener resources using filter {0}: Cause: An attempt to retrieve the SCAN listener resources failed.; Action: Ensure that the resource name supplied is correct. Examine the accompanying error messages for additional details.
PRCS-01027: Could not find any Single Client Access Name listener with ordinal number {0}: Cause: Could not find the Single Client Access Name listener for specified ordinal number.; Action: Use the command 'srvctl config scan_listener' to check available ordinal number.
PRCS-01028: Single Client Access Name (SCAN) listener resources already exist on network {0}: Cause: Single Client Access Name listeners were already created on the specified network.; Action: Use the command 'srvctl modify scan_listener' to modify attributes if needed.
PRCS-01031: Failed to modify Single Client Access Name listeners using endpoints {0}: Cause: An attempt to modify Single Client Access Name listeners failed.; Action: Check if the endpoints specified are valid.
PRCS-01032: No server pool was found that matches the query {0}: Cause: An attempt to find server pools that match the given query found no matching server pool.; Action: Either configure a server pool via the command 'srvctl add srvpool' or modify existing a server pool via the command 'srvctl modify srvpool' to match the query and retry the request.
PRCS-01034: Failed to modify Single Client Access Name {0}: Cause: Failed to modify the configuration of Single Client Access Name because the endpoints were not specified correctly or extra Single Client Access Name VIPs could not be removed or other reasons.; Action: Review the underlying error messages that provides the details of which resources failed to modify. Resolve the reported problem and retry. If to modify the endpoints, specify correct endpoints. If to update the number of Single Client Access Name VIPs, stop the Single Client Access Name listeners that depend on.
PRCS-01035: Invalid number of TCP ports ({0}) for SCAN Listener: Cause: Either no port was specified, or more than one port was specified.; Action: Specify only one port number for TCP protocol for SCAN listener.
PRCS-01037: Single Client Access Name (SCAN) Virtual Internet Protocol (VIP) resources already exist on network {0}: Cause: An attempt was made to add SCAN VIPs when SCAN VIPs were already configured. Only one SCAN per cluster network can be configured.; Action: Remove the existing SCAN on the given network and add a new SCAN. Or, modify the SCAN to use a new SCAN name or have the existing SCAN name map to different SCAN VIPs.
PRCS-01038: Failed to find Single Client Access Name Virtual Internet Protocol(VIP) associated with listener {0}: Cause: Cannot find Single Client Access Name Virtual Internet Protocol(VIP) associated with the given listener.; Action: Examine the accompanying error messages to determine how to respond.
PRCS-01039: Failed to find Single Client Access Name listener associated with the given Virtual Internet Protocol(VIP) {0}: Cause: Cannot find Single Client Access Name listener associated with the given Virtual Internet Protocol(VIP).; Action: Examine the accompanying error messages to determine how to respond.
PRCS-01040: User {0} does not have CRS administrator role: Cause: The specified user did not have CRS administrator role.; Action: Grant CRS administrator role to the user by using the command 'crsctl add crs administrator -u <user_name>' and retry.
PRCS-01041: Invalid builtin server pool name {0}: Cause: The specified builtin server pool name is invalid.; Action: Provide a valid builtin server pool name. It can be Generic or Free.
PRCS-01042: Server pool {0} is not hosting any database currently: Cause: A database could not be found referencing the given server pool.; Action: Create the database configuration using the command 'srvctl add database ... -serverpool <server_pool>' and retry.
PRCS-01043: Server pool {0} is not hosting any database service currently: Cause: A service could not be found referencing the given server pool.; Action: Create the service configuration using the command 'srvctl add service ... -serverpool <server_pool>' and retry.
PRCS-01046: Name {0} is not valid: Cause: Specified name was not valid.; Action: Specify a valid string name, and retry.
PRCS-01047: Minimum size of {0} is not valid: Cause: Specified minimum size was not valid.; Action: Specify minimum size to be an integer equal to or greater than zero and less than the maximum size (other than -1), and retry.
PRCS-01048: Maximum size of {0} is not valid: Cause: Specified maximum size was not valid.; Action: Specify maximum size to be an integer greater than or equal to -1 and retry.
PRCS-01049: Importance of {0} is not valid: Cause: Specified importance was not valid.; Action: Specify importance value to be an integer greater than or equal to 0 and retry.
PRCS-01050: Could not add GNS VIP {0} because another one with name {1} already exists: Cause: The name of the GNS VIP to be added matches one that already existed.; Action: Specify another name.
PRCS-01051: Could not add GNS VIP using network {0} because registered another one using network {1} already exists: Cause: The network specified for the GNS VIP to be added matches one that already existed.; Action: Specify another network.
PRCS-01053: failed to resolve address for Grid Naming Service VIP {0}:\n{1}: Cause: The address specified for the GNS VIP could not be resolved.; Action: Specify a valid address.
PRCS-01054: Failed to configure VIP for Grid Naming Service VIP {0}: Cause: The creation of the GNS VIP failed.; Action: Examine the accompanying error message for details.
PRCS-01055: Failed to modify Grid Naming Service VIP {0}: Cause: The modification of the GNS VIP failed.; Action: Examine the accompanying error message for details.
PRCS-01056: Could not find resources for Grid Naming Service Virtual Internet Protocol(VIP) {0}: Cause: The specified GNS VIP did not exist.; Action: Specify a valid GNS VIP name.
PRCS-01057: INTERNAL ERROR: no attributes specified.: Cause: No attributes to modify GNS with were passed to a method.; Action: This is an internal error. Please contact Oracle Customer Support.
PRCS-01058: INTERNAL ERROR: unsupported query type: "${0}": Cause: The type of query to be made to GNS is unrecognized.; Action: This is an internal error and should not be visible. Please contact Oracle Customer Support.
PRCS-01059: Failed to get sub-server pools of server pool {0}: Cause: Failed to look up PARENT_POOLS attribute of server pools containing the given server pool name. Ensure that current user has read permissions on the given server pool and its sub-server pools.; Action: Grant read permissions on the given server pool and its sub-server pools.
PRCS-01060: Failed to relocate servers {0} into server pool {1}: Cause: Failed to relocate servers into the given server pool. This message may be accompanied by others providing additional details. A likely cause is violation of defined configuration attributes such as pool MIN_SIZE, SERVER_NAMES etc.; Action: If the problem stems from violating configuration attributes, either modify the attributes or reformulate the request. Otherwise, contact Oracle Support Services.
PRCS-01061: Failed to find running database instances hosted by server pool {0}: Cause: Failed to find running database instances hosted by the servers in the given server pool. This message is accompanied by others providing additional details. A likely cause is that current user may not have permissions to query profiles of databases hosted by the given server pool.; Action: If lack of permissions is the cause of this failure, then use the command 'srvctl config object -a' to find the current owner of entity and retry the query as that owner user. Otherwise, contact Oracle Support Services.
PRCS-01062: Failed to determine whether server pool {0} has any parents or children: Cause: Failed to find parents or children of the given server pool. A likely cause is that current user may not have permissions to query profile of given server pool or profiles of other server pools whose PARENT_POOLS attribute contains this server pool name.; Action: If lack of permissions is the cause of this failure, then use the command 'srvctl config serverpool serverpool -a' to find the current owner of the server pool and retry the query as that owner user. Otherwise, contact Oracle Support Services.
PRCS-01063: Server pool {0} with minimum size {1}, maximum size {2}, importance {3} and server list ({4}) can not be created: Cause: Specified server pool cannot be created because of the reason provided by an accompanying exception message.; Action: Respond based on the accompanying exception message.
PRCS-01064: Failed to find server pools using filter {0}: Cause: Attempt to look up server pool entitites using given filter failed. A likely cause is that current user does not have permissions to query server pool entities; Action: If lack of permissions is the cause of this failure, then use the command 'srvctl config serverpool -a' to find the current owner of the server pools and retry the query as that owner user. Otherwise, contact Oracle Support Services.
PRCS-01065: GNS server is not configured in this cluster.: Cause: A command that applies only to a GNS server cluster was rejected because this cluster has not been configured as a GNS server.; Action: If GNS server is to run in this cluster, use the 'srvctl add gns' command to configure it.
PRCS-01066: Server group {0} with server list ({1}) can not be created: Cause: Specified server group cannot be created because of the reason provided by an accompanying exception message.; Action: Respond based on the accompanying exception message.
PRCS-01067: Failed to find online database instances hosted by server pool {0}: Cause: Failed to find online database instances hosted by the servers in the given server pool. This message is accompanied by others providing additional details. A likely cause is that current user may not have permissions to query profiles of databases hosted by the given server pool.; Action: If lack of permissions is the cause of this failure, then use the command 'srvctl config object -a' to find the current owner of the entity and retry the query as that owner user. Otherwise, contact Oracle Support Services.
PRCS-01068: Oracle Clusterware server entity for node {0} does not exist: Cause: The server entity for the specified node does not exist.; Action: Start Oracle Clusterware on the given node and retry.
PRCS-01069: Label {0} in GNS domain name {1} does not follow RFC-1035 convention: Cause: The specified portion of the GNS domain name does not follow RFC-1035 label conventions.; Action: Specify a domain name that follows RFC-1035 conventions. According to RFC-1035 conventions, the domain name consists of a set of labels separated by ".". A label must begin with an alphabetic character and can contain only alphanumerics and "-" (dash or minus character), end with an alphanumeric, and be no more than 63 characters long.
PRCS-01070: Label {0} part of GNS domain name {1} is too long: Cause: The specified portion of the GNS domain name does not follow RFC-1035 label conventions, as it is longer than 63 characters.; Action: Specify a domain name that follows RFC-1035 conventions. The domain name consists of a set of labels separated by ".". Label must begin with an alphabetic character and can contain only alphanumeric characters and "-" (dash or minus character), end with an alphanumeric and be no more than 63 characters long.
PRCS-01071: An error occurred while trying to look up IP address for "{0}".: Cause: A requested operation failed because an error occurred when it attempted to resolve the indicated fully qualified domain name (FQDN) for the GNS server.; Action: Ensure that the local node has name servers properly configured. If the domain in the FQDN is a GNS domain name, ensure that DNS has been set up to forward requests to GNS and that the GNS resource is online. Ensure that there are no firewalls between the local node and the name servers.
PRCS-01072: Failed to create server pool with reserved name {0}: Cause: Request to create the specified server pool was rejected because specified server pool name is the name of builtin server pool of Oracle Clusterware.; Action: Supply a server pool name other than the builtin server pool name (Generic or Free) of Oracle Clusterware and retry.
PRCS-01073: The specified GNS logging level {0} was outside the expected range of {1} to {2}: Cause: The 'log_level' value in the 'srvctl start gns -loglevel <log_level>' command was less than the minimum limit.; Action: Ensure that the 'log_level' value is within the valid range.
PRCS-01074: The specified GNS logging level {0} was outside the expected range of {1} to {2}: Cause: The 'log_level' value in the 'srvctl start gns -loglevel <log_level>' command was greater than the maximum limit.; Action: Ensure that the 'log_level' value is within the valid range.
PRCS-01075: GNS Domain name {0} ends with invalid character {1}: Cause: The specified GNS domain name ends with an invalid character and does not follow RFC-1035 label conventions.; Action: Specify a domain name that follows RFC-1035 conventions. According to RFC-1035 conventions, the domain name consists of a set of labels separated by ".". A label must begin with an alphabetic character and can contain only alphanumeric characters or "-" (dash or minus character), end with an alphanumeric, and be no more than 63 characters long.
PRCS-01076: Invalid Single Client Access Name {0}. The subnet {1} of SCAN VIP {2} differs from the subnet {3} of network {4}: Cause: The SCAN VIPs resolved from the specified Single Client Access Name are in a subnet that differs from the network's subnet.; Action: Use the SCAN name that can be resolved to the SCAN VIPs in the same subnet of network resource.
PRCS-01077: The specified trace level {0} was outside the expected range of {1} to {2}: Cause: The trace level value was less than the minimum limit or greater than the maximum limit.; Action: Ensure that the trace level value is within the valid range.
PRCS-01078: Failed to update the invited nodes {0} for service registration with Scan Listener {1}: Cause: An attempt to update the invited nodes attribute failed.; Action: Retry the request after ensuring that the CRS stack is running, the SCAN listener resource has been configured, and the user has update permission on the SCAN listener resource.
PRCS-01079: Failed to retrieve the invited nodes for service registration with Scan Listener {0}: Cause: An attempt to retrieve the invited nodes attribute value of scan listener failed.; Action: Retry the request after ensuring that the CRS stack is running, the SCAN listener resource has been configured, and the user has update permission on the SCAN listener resource.
PRCS-01080: Failed to update the invited subnets {0} for service registration with Scan Listener {1}: Cause: An attempt to update the invited subnets attribute of scan listener failed.; Action: Retry the request after ensuring that the CRS stack is running, the SCAN listener resource has been configured, and the user has update permission on the SCAN listener resource.
PRCS-01081: Failed to retrieve the invited subnets for service registration with Scan Listener {0}: Cause: An attempt to retrieve the invited subnets attribute of scan listener failed.; Action: Retry the request after ensuring that the CRS stack is running, the SCAN listener resource has been configured, and the user has update permission on the SCAN listener resource.
PRCS-01082: Invalid built-in server category name {0}: Cause: The specified category name was invalid.; Action: Provide a valid category name. It can be ora.hub.category or ora.leaf.category.
PRCS-01083: There is no server category {0} registered in CRS: Cause: The server category did not exist.; Action: Add the server category using the command 'crsctl add category <category_name>' or use the command 'crsctl status category' to get a list of server categories already registered in CRS.
PRCS-01084: Failed to find server categories using filter {0}: Cause: An attempt to look up server category entitites using the given filter failed.; Action: See the accompanying error messages for further details.
PRCS-01085: Server category {0} already exists: Cause: A server category that already exists was specified.; Action: Examine the accompanying error messages for details.
PRCS-01086: Failed to create category {0}: Cause: An attempt to create the specified server category failed.; Action: Examine the accompanying error messages for details.
PRCS-01087: SCAN name "{0}" does not resolve to an IPv4 or IPv6 address: Cause: The SCAN name did not resolve to an IP address (either IPv4 or IPv6).; Action: Ensure that the SCAN name resolves to an IP address.
PRCS-01088: SCAN name "{0}" resolves to a different number of IPv4 ({1}) and IPv6 ({2}) addresses: Cause: The number of IPv4 and IPv6 addresses that the SCAN name resolved to were not equal.; Action: Ensure that the SCAN name resolves to an equal number of IPv4 and IPv6 addresses.
PRCS-01089: Domain must be supplied because network "{0}" has type "{1}".: Cause: An attempt to add GNS on a non-static network was rejected because a domain was not supplied.; Action: Ensure that a domain is forwarded from DNS, and supply the domain using the command 'srvctl add gns -vip address -domain domain'.
PRCS-01090: Failed to retrieve the sub-domain configured for GNS: Cause: An attempt to retrieve the sub-domain attribute of the specified Grid Naming Service (GNS) failed.; Action: Retry the request after ensuring that the CRS stack is running, the GNS resource has been configured, and the user has read permission on the GNS resource.
PRCS-01091: The scan name "{0}" resolves to {1} addresses such as "{2}", while network {3} has only {4} subnet: Cause: The given scan name resolved to a type of addresses that the network did not have.; Action: Either modify the network via the command 'srvctl modify network -subnet' to include the missing type or make sure that the scan name resolves only to the addresses of the same type as the network.
PRCS-01092: Failed to get the value for the attribute {0} of server category {1}: Cause: An attempt to get the attribute value of the specified server category failed.; Action: Examine the accompanying error messages for details.
PRCS-01093: Server pool {0} does not have a server category defined: Cause: The server pool did not have the server category defined as required for policy-managed databases in a an Oracle Flex Cluster.; Action: Modify the server pool using the command 'srvctl modify srvpool -serverpool serverpool -category category -servers ""'.
PRCS-01094: Server category {0} of server pool {1} has the following non-hub active CSS role: {2}: Cause: The server category of the server pool did not have ACTIVE_CSS_ROLE=HUB as required for policy-managed databases in a Flex Cluster.; Action: Modify the server pool to use a server category that has the hub active CSS role or modify the server category to use ACTIVE_CSS_ROLE=HUB.
PRCS-01095: Conflicting specification of 'servers' and 'category' arguments for the serverpool {0}: Cause: Both 'servers' and 'category' arguments were specified on the command.; Action: Retry the request with either 'servers' or 'category' argument.
PRCS-01096: The serverpool {0} already contains the server names: Cause: The command 'srvctl modify srvpool' specified 'category' option, but the server pool already has a server names attribute.; Action: Remove the server names attribute by issuing the command 'srvctl modify srvpool -serverpool <pool_name> -servers ""'
PRCS-01097: The serverpool {0} already contains the server category: Cause: A 'srvctl modify srvpool' command specified 'servers' but the server pool already has a server category attribute.; Action: Remove the server category attribute by issuing the command 'srvctl modify srvpool -serverpool <pool_name> -category ""'
PRCS-01098: Active CSS role of the server category {0} of PQ server pool {1} is not set: Cause: The server category of the server pool did not specify ACTIVE_CSS_ROLE.; Action: Modify the PQ server pool to use a server category that has a valid active CSS role or modify the server category to set ACTIVE_CSS_ROLE.
PRCS-01099: Nodes {0} of the server pool {1} do not have HUB active CSS roles: Cause: The server pool did not have nodes with ACTIVE_CSS_ROLE=HUB as required for policy-managed databases in a Flex Cluster.; Action: Modify the server pool to use nodes that have HUB active CSS roles.
PRCS-01100: Nodes {0} of the PQ server pool {1} do not have LEAF active CSS roles: Cause: The server pool did not have nodes with ACTIVE_CSS_ROLE=LEAF as required for policy-managed databases in a Flex Cluster.; Action: Modify the server pool to use nodes that have LEAF active CSS roles.
PRCS-01101: Unable to create GNS resource because it already exists.: Cause: An attempt was made to add the GNS resource but the resource already exists.; Action: Either remove the GNS resource and then add it, or avoid adding an already existing resource.
PRCS-01102: Could not find any Single Client Access Name (SCAN) Virtual Internet Protocol (VIP) resources using filter {0} on network {1}: Cause: An attempt to retrieve the SCAN VIP resources on the indicated network failed.; Action: Ensure that the resource name supplied is correct. Examine the accompanying error messages for additional details.
PRCS-01103: Could not find any Single Client Access Name (SCAN) listener resources using filter {0} on network {1}: Cause: An attempt to retrieve the SCAN listener resources on the indicated network failed.; Action: Ensure that the resource name supplied is correct. Examine the accompanying error messages for additional details.
PRCS-01104: Could not find the Single Client Access Name (SCAN) listener with ordinal number {0} on network {1}: Cause: An attempt to find the SCAN listener for the specified ordinal number and network failed.; Action: Use the command 'srvctl config scan_listener -netnum' to check the available ordinal numbers on the given network.
PRCS-01105: Server category {0} of Parallel Query server pool {1} has the following non-leaf active CSS role: {2}: Cause: The server category of the server pool did not have ACTIVE_CSS_ROLE=LEAF as required for the parallel query helper service of the policy-managed databases in a Flex Cluster.; Action: Modify the Parallel Query server pool to use a server category that has the leaf active CSS role or modify the server category to use ACTIVE_CSS_ROLE=LEAF.
PRCS-01106: Nodes {0} of the Parallel Query server pool {1} do not have the leaf active CSS role: Cause: The server pool did not have nodes with ACTIVE_CSS_ROLE=LEAF as required for policy-managed databases in a Flex Cluster.; Action: Modify the server pool to use nodes that have the leaf active CSS role.
PRCS-01107: Cannot add resource on network {0}, which is configured as leaf.: Cause: An attempt to add a resource using a network configured as 'leaf' was made.; Action: Add the resource on a network not configured as 'leaf'.
PRCS-01108: Cannot modify resource to use network {0}, which is configured as leaf.: Cause: An attempt to modify a resource using a network configured as 'leaf' was made.; Action: Provide a network not configured as 'leaf'.
PRCS-01110: Single Client Access Name (SCAN) {0} does not resolve to {1} addresses although it should resolve to both IPv4 and IPv6 addresses: Cause: An attempt to modify the SCAN name while the network type was 'BOTH' was rejected because the specified SCAN name did not resolve to both IPv4 and IPv6 addresses required by the network.; Action: Make sure that the specified SCAN name resolves to both IPv4 and IPv6 addresses.
PRCS-01111: Could not modify GNS VIP because registered type and IP address type are different: Cause: The IP address type specified for the GNS VIP to be added differed from the registered network type.; Action: Specify an IP address of the type that is registered.
PRCS-01112: Server {0} is not assigned to any server pool.: Cause: The given server was not yet recognized by Oracle Clusterware and therefore was not active in any server pool.; Action: Check the state of the server using the command 'crsctl status server server -f'.
PRCS-01113: The Single Client Access Name (SCAN) VIP address "{0}" does not belong to network {1} which has only an {2} subnet.: Cause: The network modification failed because the type of the specified SCAN VIP address was incompatible with the subnet of the specified network.; Action: Either modify the network via the command 'srvctl modify network -subnet' to include the missing type or make sure that the SCAN VIP is an address of the same type as the network.
PRCS-01115: An attempt to retrieve the Rapid Home Provisioning Server host name and port number failed with the following error:\n{0}: Cause: While looking up Rapid Home Provisioning Server (RHPS) connection details in Grid Naming Service (GNS), an attempt to retrieve the host name and port number failed.; Action: Examine the accompanying error message. Make sure that both the GNS and the Rapid Home Provisioning Server are running on the RHPS cluster.
PRCS-01116: no SRV record for service {0} found in the Grid Naming Service (GNS): Cause: This is an internal error.; Action: Contact Oracle Support Services.
PRCS-01117: invalid format for SRV record {0} returned from the Grid Naming Service (GNS): Cause: This is an internal error.; Action: Contact Oracle Support Services.
PRCS-01118: The supplied GNS VIP name "{0}" resolves to multiple IP addresses "{1}".: Cause: Install prerequisite checking determined that the indicated GNS VIP name entered was resolved to the multiple IP addresses shown.; Action: Repeat the install interview supplying a GNS VIP name that resolves to exactly one address, or a numeric GNS VIP address. Alternatively, modify the name service address mapping to associate only one address with the name and rerun the prerequisite check.
PRCS-01119: illegal attempt to modify the Grid Naming Service instance role to client: Cause: An attempt to modify the Grid Naming Service (GNS) role to client was made.; Action: Valid GNS roles are PRIMARY and SECONDARY. Specify one of them and reissue the command.
PRCS-01120: The supplied GNS VIP name "{0}" resolves to multiple addresses "{1}" of types IPv4 or IPv6.: Cause: More than one IP address of either type IPv4 or type IPv6 were found when resolving the specified Grid Naming Service (GNS) VIP name.; Action: Supply a GNS VIP name that resolves to exactly two addresses, one of type IPv4 and one of type IPv6.
PRCS-01121: The supplied GNS VIP name "{0}" resolves to multiple addresses "{1}" of type IPv4.: Cause: More than one IP address of type IPv4 was found when resolving the specified Grid Naming Service (GNS) VIP name.; Action: Supply a GNS VIP name that resolves to exactly one IPv4 address, or supply a numeric GNS VIP address.
PRCS-01122: The supplied GNS VIP name "{0}" resolves to multiple addresses "{1}" of type IPv6.: Cause: More than one IP address of type IPv6 was found when resolving the specified Grid Naming Service (GNS) VIP name.; Action: Supply a GNS VIP name that resolves to exactly one IPv6 address, or supply a numeric GNS VIP address.
PRCS-01123: failed to get the extended cluster configuration information: Cause: An attempt to get the extended cluster configuration information failed.; Action: Examine the accompanying error messages for details and retry the command, making sure that the CRS stack is running.
PRCS-01124: failed to get Oracle Clusterware sites: Cause: An attempt to get Oracle Clusterware sites failed.; Action: Examine the accompanying error messages for details and retry the command, making sure that the CRS stack is running.
PRCS-01125: failed to get Oracle Clusterware site for node {0}: Cause: An attempt to retrieve Oracle Clusterware site for specified node failed.; Action: Examine the accompanying error messages for details and retry the command, making sure that the CRS stack is running.
PRCS-01126: SCAN {0} has no static IPv4 addresses configured for Single Client Access Name (SCAN) Virtual IPs (VIP).: Cause: An attempt to modify the network type of the indicated SCAN to 'static' was rejected because the SCAN did not have SCAN VIPs configured with static IPv4 addresses.; Action: Use the command 'srvctl modify scan' to configure the indicated SCAN with SCAN VIPs whose addresses resolve to static IPv4 addresses.
PRCS-01127: SCAN {0} has no static IPv6 addresses configured for Single Client Access Name (SCAN) Virtual IPs (VIP).: Cause: An attempt to modify the network type of the indicated SCAN to 'static' was rejected because the SCAN did not have SCAN VIPs configured with static IPv6 addresses.; Action: Use the command 'srvctl modify scan' to configure the indicated SCAN with SCAN VIPs whose addresses resolve to static IPv6 addresses.
PRCS-01128: SCAN {0} does not have static IP addresses of both types IPv4 and IPv6 configured for Single Client Access Name (SCAN) Virtual IPs (VIP).: Cause: An attempt to modify the network type of the indicated SCAN to 'static' was rejected because the SCAN did not have SCAN VIPs configured with static addresses of each of the types IPv4 and IPv6.; Action: Use the command 'srvctl modify scan' to configure the indicated SCAN with SCAN VIPs whose addresses resolve to static IPv4 and IPv6 addresses.
PRCS-01129: nodes {0} of the reader farm server pool {1} do not have LEAF active CSS roles: Cause: An attempt to add or modify a service was rejected because the specified server pool did not have nodes with ACTIVE_CSS_ROLE=LEAF as required for the policy-managed databases using reader farm services.; Action: Modify the server pool to use nodes that have LEAF active Oracle Cluster Synchronization Services (CSS) roles using 'srvctl modify serverpool -category' and retry the operation.
PRCS-01130: failed to add reader farm service because network {0} is not extended to work on Leaf Nodes: Cause: An attempt to add a reader farm service was rejected because the provided network was not extended to Leaf Nodes.; Action: Specify a network that is extended to work on Leaf Nodes, or run 'srvctl modify network -extendtoleaf' and repeat the operation.
PRCS-01131: unable to convert a reader farm service to another service type: Cause: An attempt to modify a reader farm service configuration was rejected because service type conversion is not supported.; Action: Create a new service of the required service type.
PRCS-01132: Database {0} is configured to use parallel query services.: Cause: An attempt to add a reader farm service configuration was rejected because the specified database was already configured to use parallel query services.; Action: Specify a different database or remove the parallel query services using the command 'srvctl remove service' and add the reader farm service using the command 'srvctl add service'.
PRCS-01133: Database {0} is configured to use reader farm services.: Cause: An attempt to add a parallel query service configuration was rejected because the specified database was already configured to use reader farm services.; Action: Specify a different database or remove the reader farm services using the command 'srvctl remove service' and add the parallel query service using the command 'srvctl add service'.
PRCS-01134: Server category {0} of server pool {1} has the following non-LEAF CSS role: {2}: Cause: An attempt to add or modify a reader farm service was rejected because the server category of the specified server pool did not have ACTIVE_CSS_ROLE=LEAF as required for reader farm services.; Action: Modify the server pool to use a server category that has the LEAF active CSS role or modify the server category to use ACTIVE_CSS_ROLE=LEAF and retry the operation.
PRCS-01135: unable to convert non-reader farm service {0} to reader farm service type: Cause: An attempt to modify a non-reader farm service configuration was rejected because service type conversion is not supported.; Action: Create a new reader farm service using the command 'srvctl add service -rfpool'.
PRCS-01136: unable to set the candidate server list for a server pool to a list of servers with mixed CSS roles.: Cause: An attempt to set the candidate server list for a server pool was rejected because the specified servers were not all Hub Nodes or all Leaf Nodes.; Action: Retry the operation specifying a list of servers that all have ACTIVE_CSS_ROLE set to 'hub' or that all have ACTIVE_CSS_ROLE set to 'leaf'.
PRCS-01137: The release specified must be 12.1.0.2 or later.: Cause: An attempt to export the Grid Naming Service (GNS) credentials with the -version option failed because the specified release was earlier than 12.1.0.2; Action: Reissue the command, specifying release 12.1.0.2 or later.
PRCS-01138: invalid VIP addresses "{0}" because the specified IP addresses are reachable: Cause: The specified command was rejected because the Virtual Internet Protocol (VIP) address was reachable.; Action: Configure VIPs to use IP addresses that are not active on any host system and cannot be reached using 'ping'.
PRCS-01139: failed to add reader farm service: Cause: An attempt to add a reader farm service was rejected because the hub service was either not provided or was invalid.; Action: Specify a hub service that exists and services the pluggable database to which the reader farm service can connect.
PRCS-01140: invalid GNS VIP address {0} because the specified IP address is not in the subnet {1} of the network resource {2}: Cause: The subnet of the Grid Naming Service Virtual Internet Protocol (GNS VIP) did not match the subnet of the network resource.; Action: Retry SRVCTL command with a combination of GNS VIP address and network whose subnet matches.
PRCS-01141: invalid GNS VIP address {0} because the specified IP address is not of type {1} of the network resource {2}: Cause: The IP address type specified for the GNS VIP to be added differed from the registered network type.; Action: Specify an IP address of the type that is registered.
PRCS-01142: Unable to create CDP resource because it already exists.: Cause: An attempt to add the Cross-cluster Dependency Proxies (CDP) resource was rejected because the resource already existed.; Action: None
PRCS-01143: failure to configure Cross-cluster Dependency Proxies resource: Cause: An attempt to add a cluster configuration for a Cross-cluster Dependency Proxies (CDP) resource failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying error messages that provide the details of which resources failed to be created. Check the Cause and Action for the individual resource creation failures.
PRCS-01144: Error executing the config script for CDP. Details: {0}: Cause: An error occurred while executing the configuration script for the Cross-cluster Dependency Proxies (CDP) resource. Specific failure data is displayed following the message.; Action: Examine the accompanying messages, resolve the identified problems, and then retry the operation.
PRCS-01145: Single Client Access Name (SCAN) listener resources not found for client cluster {0}.: Cause: An attempt to retrieve the SCAN listener resources for the indicated client failed. The accompanying error messages provide detailed failure information.; Action: Examine the accompanying error messages, resolve the indicated issues,and then retry the operation, ensuring that the supplied cluster name is correct.
PRCS-01146: Single Client Access Name (SCAN) listener resources already exist for client cluster {0}.: Cause: An attempt to create Single Client Access Name (SCAN) listeners was rejected because resources were already created for the specified client cluster.; Action: Retry the operation, specifying a different client cluster name.
PRCS-01147: unable to find any Oracle Notification Service (ONS) resources for client cluster {0}: Cause: An attempt to retrieve the ONS resources for the indicated client failed. The accompanying error messages provide detailed failure information.; Action: Examine the accompanying error messages, resolve the indicated issues, and then retry the operation, ensuring that the supplied resource name is correct.
PRCS-01148: An ONS resource already exists for client cluster {0}.: Cause: An attempt to create an Oracle Notification Service (ONS) resource was rejected because a resource already existed for the indicated client cluster.; Action: Retry the operation, specifying a different cluster name.
PRCS-01149: unable to find resource for ONS {0}: Cause: An attempt to query resources failed because the indicated Oracle Notification Service (ONS) resource did not exist.; Action: Retry the operation, specifying a valid ONS name.
PRCS-01150: The ONS resource already exists.: Cause: An attempt to create a resource was rejected because the Oracle Notification Service (ONS) resource already existed.; Action: None
PRCS-01151: The specified ONS resource is not configured for a client cluster.: Cause: An attempt to export client data for an Oracle Notification Service (ONS) resource was rejected because the specified ONS resource was not configured to serve a client cluster.; Action: Retry the operation, specifying an ONS resource that is configured to serve a client cluster.
PRCS-01152: The invited nodes cannot be modified for a SCAN listener on a client cluster.: Cause: An attempt to modify the invited nodes for a SCAN listener was rejected because the resource was configured for a client cluster.; Action: Retry the operation, specifying a SCAN listener on a server cluster.
PRCS-01153: The invited subnet cannot be modified for a SCAN listener on a client cluster.: Cause: An attempt to modify the invited subnet for a SCAN listener was rejected because the resource was configured for a client cluster.; Action: Retry the operation, specifying a SCAN listener on a server cluster.
PRCS-01154: The specified SCAN listener resource is not configured for a client cluster.: Cause: An attempt to export client data for a SCAN listener resource was rejected because the specified SCAN listener resource was not configured to serve a client cluster.; Action: Retry the operation, specifying a SCAN listener resource that serves a client cluster.
PRCS-01155: missing properties {0}: Cause: An attempt to get XML properties from the indicated data file failed because the required XML property attributes did not exist.; Action: Retry the operation, supplying a valid client data file.
PRCS-01156: Service {0} is already configured in server pool {1}.: Cause: An attempt to modify the reader farm service pool for the specified server pool failed because the service is already part of the server pool.; Action: No action is needed.
PRCS-01157: The CDP resource does not exist.: Cause: An attempt to retrieve the Cross-cluster Dependency Proxies (CDP) resource failed because the resource could not be found.; Action: Create the CDP resource using the command 'srvctl add cdp', then retry the operation.
PRCS-01158: The TFA resource does not exist.: Cause: An attempt to retrieve the Trace File Analyzer (TFA) failed because the resource could not be found.; Action: Create the TFA resource using the command 'srvctl add tfa', then retry the operation.
PRCS-01159: Unable to create the TFA resource because it already exists.: Cause: An attempt to add the Trace File Analyzer (TFA) resource was rejected because the resource already existed.; Action: None
PRCS-01160: The CDP proxy resource does not exist.: Cause: An attempt was made to retrieve the Cross-cluster Dependency Proxies (CDP) proxy resource but the CDP proxy resource was not found.; Action: Create the CDP proxy resource using the command 'srvctl add cdpproxy', then retry the operation.
PRCS-01161: Unable to create CDP proxy resource because it already exists.: Cause: An attempt was made to add the Cross-cluster Dependency Proxies (CDP) proxy resource but the resource already existed.; Action: None
PRCS-01162: Cannot create CDP proxy using unsupported type "{0}".: Cause: An attempt was made to add the Cross-cluster Dependency Proxies (CDP) proxy resource using an unknown, or unsupported, proxy type.; Action: Retry the operation, supplying a valid supported proxy type.
PRCS-01163: failed to remove the CDP resource {0}: Cause: An attempt to remove the Cross-cluster Dependency Proxies (CDP) resource failed because the resource was running or other resources depended on it.; Action: Check status for the identified CDP resource and stop the CDP resource before removing it. The force flag could be used to remove the CDP resource if CDP proxies depend on it.
PRCS-01164: could not modify CDP resources because the following CDP resources were running: {0}: Cause: An attempt to modify one or more Cross-cluster Dependency Proxies (CDP) resources was rejected because the indicated resources were running.; Action: Ensure that the indicated CDP resources are stopped and then retry the operation.
PRCS-01165: cluster {0} not registered with GNS: Cause: An attempt to retrieve information about the indicated cluster from the Grid Naming Service (GNS) found that the cluster was not registered.; Action: Ensure that the indicated cluster name is registered with GNS, and then retry the operation.
PRCS-01166: cluster GUID {0} not registered with GNS: Cause: An attempt to retrieve information about the indicated cluster from the Grid Naming Service (GNS) found that the cluster was not registered.; Action: Ensure that the indicated cluster GUID is registered with GNS, and then retry the operation.
PRCS-01167: no clusters registered with GNS: Cause: An attempt to retrieve the list of registered clusters from the Grid Naming Service (GNS) detected that no clusters were registered.; Action: Ensure that there is at least one cluster registered with GNS, and then retry the operation.
PRCS-01168: The cluster name "{0}" stored in the client data file is not the same as the configured cluster name "{1}".: Cause: An attempt to configure a Single Client Access Name (SCAN) resource on a client cluster was rejected because the client data file contained information for a different cluster name.; Action: Ensure that the client data file was exported for this cluster name and retry the operation.
PRCS-01169: invalid invited subnets value {0}: Cause: An attempt to change the invited subnets value was rejected because the invited subnets value was specified using incorrect syntax.; Action: Ensure that the invited subnets value is using either Classless Inter-Domain Routing (CIDR) syntax (e.g. 192.196.16.0/24) or wild cards (e.g. 192.196.16.*).
PRCS-01170: invalid node names value {0}: Cause: An attempt to add a Single Client Access Name (SCAN) was rejected because the node names value contained invalid active nodes.; Action: Ensure that the node names are active and unique, then retry the operation.
PRCS-01171: failed to delete category {0}: Cause: An attempt to delete the specified server category failed.; Action: Examine the accompanying messages, resolve the identified problems, and then retry the operation.
PRCS-01172: failed to update category {0}: Cause: An attempt to update the specified server category failed.; Action: Examine the accompanying messages, resolve the identified problems, and then retry the operation.