PRKZ-01029 to PRKZ-01233

137 PRKZ-01029 to PRKZ-01233

PRKZ-01029: HAVIP {0} is already disabled: Cause: The 'disable havip' command failed because HAVIP was already disabled.; Action: If this is the expected state then this is not an error. If it is not then HAVIP can be enabled by 'srvctl enable havip' command.
PRKZ-01030: export file system {0} is already disabled: Cause: The 'disable exportfs' command failed because it was already disabled.; Action: If this is the expected state then this is not an error. If it is not then it can be enabled by 'srvctl enable exportfs' command.
PRKZ-01031: HAVIP {0} is already enabled: Cause: The 'enable havip' failed because HAVIP was already enabled.; Action: If this is the expected state then this is not an error. If it is not then HAVIP can be disabled by 'srvctl disable havip' command.
PRKZ-01032: export file system {0} is already enabled: Cause: The 'enable exportfs' command failed because it was already enabled.; Action: If this is the expected state then this is not an error. If it is not then it can be disabled by 'srvctl disable exportfs' command.
PRKZ-01058: HAVIP exists for address {0}: Cause: An attempt to add a HAVIP found that it already exists; Action: Check the input and if HAVIP needs to be modified use the command 'srvctl modify havip'.
PRKZ-01059: HAVIP with ID {0} does not exist: Cause: The 'add exportfs' failed because the HAVIP with the specified ID does not exist.; Action: Specify the ID of an HAVIP that exists, or create the HAVIP for the specified ID using the command 'srvctl add havip -id id -address vip'.
PRKZ-01060: Export file system {0} does not exist: Cause: The export file system resource with the specified name does not exist.; Action: Check the name and retry with the export file system name that is already configured.
PRKZ-01062: Cannot determine which subnet to modify to network type "{0}". The network resource has two subnets configured with network type "{1}".: Cause: The command 'srvctl modify network -nettype' failed because the network had both IPv4 and IPv6 subnets, thus the subnet to modify could not be determined.; Action: Specify the '-subnet' option with the command 'srvctl modify network -nettype' to indicate whether to change type for IPv4 or IPv6 subnet.
PRKZ-01065: Invalid combination of options specified: Cause: The '-name' and '-id' options cannot be combined together.; Action: Issue the command with either '-name' or '-id' option.
PRKZ-01066: Invalid subnet string: "{0}": Cause: The given subnet string was not a valid IPv4 or IPv6 subnet number in dotted-decimal format.; Action: Make sure that the subnet string is a valid IPv4 or IPv6 subnet number in dotted-decimal format.
PRKZ-01067: Invalid subnet mask string: "{0}": Cause: The given subnet mask string was not a valid IPv4 subnet mask in dotted-decimal format or IPv6 prefix length.; Action: Make sure that the subnet mask string is a valid IPv4 subnet mask in dotted-decimal format or IPv6 prefix length.
PRKZ-01068: {0} object is not supported on Windows Operating System: Cause: The object specified on the command line was not a valid object on Windows Operating System.; Action: Objects rhpserver|rhpclient|havip|exportfs are not valid on Windows Operating System. Use a valid object.
PRKZ-01069: "srvctl modify network -iptype both" cannot include the {0} option: Cause: The command 'srvctl modify network -iptype both' request included conflicting options.; Action: Issue the command 'srvctl modify network -iptype both' separate from other network changes.
PRKZ-01070: Changing network type from {0} to {1} requires new VIP addresses: Cause: The command 'srvctl modify nodeapps -nettype mixed' was issued without specifying the VIP address when the IPv4 or IPv6 network type was dynamic.; Action: Issue the command 'srvctl modify nodeapps -nettype mixed -address' to specify the new VIP address.
PRKZ-01071: '-netnum' option cannot be supplied without '-address' option: Cause: The commande 'srvctl modify havip -netnum' was issued without specifying a VIP address that matches the new network Subnet.; Action: Retry the command 'srvctl modify havip' using '-address' option along with '-netnum' option to specify a new address for the HAVIP resource.
PRKZ-01072: SCAN name "{0}" is already registered on network {1}: Cause: The command 'srvctl add scan -scanname' was issued for a Single Client Access Name (SCAN) name that was already registered on the specified network.; Action: Use a distinct SCAN name.
PRKZ-01073: Cannot modify network type to 'mixed' because GNS is not configured.: Cause: An attempt to modify the network type to 'mixed' failed because Grid Naming Service (GNS) was not configured.; Action: Configure Grid Naming Service (GNS) and retry 'srvctl modify network' command.
PRKZ-01074: Failed to modify network type because the specified subnet "{0}" does not match any configured subnet.: Cause: The specified subnet did not match any configured subnet in the network resource.; Action: Specify a configured subnet to modify its network type.
PRKZ-01075: '-iptype' option cannot be given along with '-subnet': Cause: A command attempted to modify both the network IP type and its subnet.; Action: Use 'srvctl modify network' with '-subnet' or '-iptype', not both.
PRKZ-01076: Cannot modify network with network type 'mixed': Cause: An attempt to modify the subnet or IP type of a network resource with network type 'mixed' was issued.; Action: Use 'srvctl modify network -nettype' to modify the network type to STATIC, DHCP or AUTOCONFIG, before making any other change.
PRKZ-01078: Object {0} is not supported on an ASM client cluster.: Cause: The object specified on the command line was not a valid object for an ASM client cluster.; Action: Objects ASM, DISKGROUP, and VOLUME are not supported on an ASM client cluster. Use a valid object.
PRKZ-01079: Invalid subnet value {0} for '-invitedsubnets' option: Cause: The command was rejected because the invited subnets value was specified using incorrect syntax.; Action: Reissue the command specifying the invited subnets using either Classless Inter-Domain Routing (CIDR) syntax (e.g. 192.196.16.0/24) or wild cards.
PRKZ-01080: '-netnum' and '-vip' options conflict.: Cause: The 'srvctl start|stop vip' command was rejected because the '-netnum' option was specified along with the '-vip' option.; Action: Use the command 'srvctl start|stop vip' with either '-netnum' or '-vip', not both.
PRKZ-01082: The VIP name "{0}" cannot be resolved.: Cause: An unresolvable VIP name was specified.; Action: Make sure that the VIP name resolves to an IP address.
PRKZ-01083: The VIP name "{0}" resolves to "{1}" which cannot be found in any VIP.: Cause: An attempt to find a VIP with one of the specified addresses to which the VIP name resolved failed."; Action: Specify a VIP name that resolves to an address that is found in a VIP resource.
PRKZ-01084: The network type for the specified subnet ({0}) that is added cannot be set to 'mixed'.: Cause: An attempt was made to add an IPv4 or IPv6 subnet and set its network type directly to 'mixed'.; Action: Reissue the command and use a different value than 'mixed' for the -nettype option.
PRKZ-01085: Internal error: {0}: Cause: An internal error occurred. The included value is an internal identifier.; Action: Oracle internal error. Contact Oracle Support Services.
PRKZ-01119: nothing to modify: Cause: No options were specified to modify.; Action: Specify at least one option with the 'modify' command.
PRKZ-01125: Oracle Grid Infrastructure Management Repository (GIMR) client is not configured.: Cause: An attempt to retrieve GIMR client information failed because GIMR client did not exist.; Action: Add the GIMR client and try again.
PRKZ-01126: The network storage service is already disabled.: Cause: The network storage server resource could not be disabled because it was already disabled.; Action: None
PRKZ-01127: The network storage service is already enabled.: Cause: The network storage server resource could not be enabled because it was already enabled.; Action: None
PRKZ-01128: Host {0} is not reachable.: Cause: The command 'srvctl modify nodeapps -remoteservers hostname' specified a hostname that was not reachable.; Action: Ensure the host is up and reachable on the network and reissue the command.
PRKZ-01129: Host {0} is unknown.: Cause: The command 'srvctl modify nodeapps -remoteservers hostname' specified the indicated hostname, but that host was unknown.; Action: Reissue the command with a host name that is known to be correct.
PRKZ-01130: Port {0} is invalid.: Cause: The command 'srvctl modify nodeapps -remoteservers hostname:port' specified the indicated port, which was not a valid port .; Action: Reissue the command with a port that is known to be correct.
PRKZ-01131: {0} is only supported on an ASM client cluster.: Cause: An attempt to execute a command using the specified object was rejected because the specified object was not supported for a ASM client cluster.; Action: Use valid objects ASM, disk group or volume.
PRKZ-01133: invalid query of management repository status on member cluster: Cause: A request to query the management database from a member cluster was rejected because the management database status can only be queried on the domain services cluster.; Action: Check the documentation on commands related to the management database and execute commands from the appropriate cluster.
PRKZ-01143: cannot decommission database {0} because it is enabled: Cause: An attempt to mark the indicated database as 'Decommissioned' was rejected because the database was currently enabled.; Action: Disable the database using the command 'srvctl disable database' and retry the command.
PRKZ-01205: removing the GNS VIP resource with the force option results in the GNS VIP address {0} continuing to be reachable on node {1}: Cause: Status message; Action: Not an error
PRKZ-01214: Service cannot be enabled while patching is in progress because the service {0} has been identified as a Java service.: Cause: An attempt to enable a Java-based service was rejected because patching of the Oracle Java Virtual Machine (OJVM) was in progress, and Java services must remain disabled during OJVM patching.; Action: Complete the patching process on all database instances.
PRKZ-01217: ASM network resource does not exist.: Cause: The ASM network resource to be operated on did not exist.; Action: The ASM network resource can be created using the command 'srvctl add asmnetwork'.
PRKZ-01218: The ASM network resource is already started on nodes: {0}: Cause: The start asmnetwork command failed because ASM network resource is already started.; Action: None
PRKZ-01219: ASM network resource is already stopped on nodes: {0}: Cause: The stop asmnetwork command failed because ASM network resource is already stopped.; Action: None
PRKZ-01233: Database {0} is not administrator-managed and does not support the failback option.: Cause: An attempt to add or modify a service using '-failback' option was rejected because this option can be used with administrator-managed databases only.; Action: Reissue the command without the '-failback' option.