Skip Headers
Oracle® Database Error Messages
11g Release 2 (11.2)
Part Number E10880-02
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
 

74 PRKO-02000 to PRKO-09059

PRKO-02000: Invalid command line syntax for a single instance database
Cause: user specified invalid command line syntax.
Action: Look at the usage provided for this command and specify all mandatory options.
PRKO-02001: Invalid command line syntax
Cause: The syntax of the command is incorrect.
Action: Look at the usage provided for this command and use the correct syntax.
PRKO-02002: Invalid command line option:
Cause: Invalid command line option was specified.
Action: Check the value printed along with the exception and specify the correct value.
PRKO-02003: Invalid command line option value:
Cause: Invalid command line option was specified.
Action: Check the value printed along with the exception and specify the correct value.
PRKO-02004: Repetition of command line option:
Cause: The command line option printed along with the exception was repeated.
Action: Delete the repeated command line option and try the command again.
PRKO-02005: Failure in getting Cluster Database Configuration for:
Cause: The specified database does not exist.
Action: Check the specified database name and try again.
PRKO-02006: Invalid node name: {0}
Cause: Unable to get the hostname for the given node/machine name.
Action: Check the node name and try again.
PRKO-02007: Invalid instance name: {0}
Cause: Unable to obtain the node name on which the instance name specified was running.
Action: Check the instance name specified and try again.
PRKO-02008: Invalid connect string:
Cause: The connect string specified was not in the format username/password [as {SYSDBA|SYSOPER}]
Action: Check the connect string and try again.
PRKO-02009: Invalid name/value string: {0}
Cause: The name value string should be of the form name = value
Action: check the input name/value pair and try again.
PRKO-02010: Invalid command specified on command line: {0}
Cause: The <command> specified on the command line was not recognized.
Action: Valid commands are enable|disable|start|stop|relocate|status|add|remove|modify|getenv|setenv|unsetenv|config. Usage of srvctl is printed with this errori. Check the usage and specify a valid command.
PRKO-02011: Invalid object specified on command line: {0}
Cause: The <object> specified on the command line was not recognized.
Action: Valid objects are database|instance|service|nodeapps|vip|asm|diskgroup|listener|srvpool|scan|scan_listener|oc4j|home|filesystem|gns. Srvctl usage is printed along with this exception. Check the usage printed with this error and use a valid object.
PRKO-02012: {0} object is not supported in Oracle Restart
Cause: The <object> specified on the command line was not a valid object for the Oracle Restart mode.
Action: Valid objects for Oracle Restart mode are database|service|asm|diskgroup|listener|home|ons|eons. Srvctl usage is printed along with this exception. Check the usage printed with this error and use a valid object.
PRKO-02013: {0} object is not supported in Oracle Clusterware
Cause: The <object> specified on the command line was not a valid object for the Oracle Clusterware mode.
Action: Valid objects for Oracle Clusterware are database|instance|service|nodeapps|vip|asm|diskgroup|listener| srvpool|scan|scan_listener|oc4j|home|filesystem|gns. Srvctl usage is printed along with this exception. Check the usage printed with this error and use a valid object.
PRKO-02014: The -a option should be specified with -d <dbunique_name> for 'srvctl config database' command
Cause: -a option was specified without the required -d option specifying for which database to retrieve configuration.
Action: To retrieve the full configuration of the database, specify both -d and -a option with the 'srvctl config database' command.
PRKO-02017: Service {0} does not exist for database {1}.
Cause: The service being updated is not defined for the given database.
Action: If the service needs to be added don't use '-u' option in 'srvctl modify service' command. Option '-u' is for updating existing services.
PRKO-02049: Invalid name-value string: {0}
Cause: The name=value string specified is not in valid format.
Action: The format for the string should be name=value. Check input and correct the error.
PRKO-02050: Error in enabling ASM instance on node {0}. {1}
Cause: ASM could not be enabled.
Action: Make sure that the node name is correct and that ASM exists on the specified node and it is not already enabled on the node. The current state of the ASM can be found using 'srvctl status asm' command. To check if ASM is configured or not, use 'srvctl config asm' command.
PRKO-02053: Error in disabling ASM instance on node {0}. {1}
Cause: ASM could not be disabled.
Action: Make sure that the node name is correct and that ASM exists on the specified node and it is not already disabled on the node. The current state of the ASM can be found using 'srvctl status asm' command. To check if ASM is configured or not, use 'srvctl config asm' command.
PRKO-02054: Invalid command line syntax, mandatory options are either {0} or {1}, but not both.
Cause: The command requires exactly one set of mandatory command line options. But either some options in one set were missing or the options from both sets were specified.
Action: Check the command line options entered and make sure that all the mandatory options in one set are specified.
PRKO-02056: Error occured while checking dependent resources on network {0}. Network was not removed.
Cause: An attempt made to check if any resources are dependent on the given network failed.
Action: Make sure that the network is up. Make sure that the user has sufficient permission to remove network. If force flag was not specified in the remove command then specify force flag and try the command again.
PRKO-02058: Scan name {0} cannot be the same as a cluster node name: {1}
Cause: Scan name is same as a cluster node name.
Action: Choose a different scan name and issue the command.
PRKO-02065: Only one server pool should be provided for a single instance database on a cluster
Cause: An attempt to create a single instance database failed because more than one server pool was specified.
Action: Provide only one server pool while creating the single instance database.
PRKO-02067: The size of server pool should be one for single instance database
Cause: An attempt to create a single instance database failed because a server pool with more than one server was specified.
Action: Provide a server pool with only one server while creating a single instance database.
PRKO-02069: OC4J could not be created as it already exists
Cause: A new OC4J instance could not be created, as there is an existing instance of OC4J.
Action: Only one instance of OC4J can exists at any given time.
PRKO-02070: OC4J creation failed
Cause: A new OC4J instance could not be added because of OC4J exception.
Action: Resolve the OC4J exception and then try the OC4J addition again.
PRKO-02072: OC4J is not configured
Cause: OC4J is not configured on the cluster.
Action: Check the exception printed with this message. If OC4J is not configured then OC4J instance can be created using 'srvctl add oc4j'. If their are other errors shown with this error then check the cause/action messages of underlying exception.
PRKO-02074: OC4J is still running. It must be stopped before removing.
Cause: 'srvctl remove oc4j' was issued while OC4J instance was running.
Action: Stop the oc4j instance using 'srvctl stop oc4j' and then try removing.
PRKO-02075: OC4J could not be removed
Cause: OC4J instance could not be removed because it does not exist.
Action: The current OC4J configuration can be checked using 'srvctl config oc4j' command. Make sure that OC4J instance is running on that port. If their are other underlying messages printed then check the cause/action for the underlying errors shown with this.
PRKO-02077: OC4J RMI port could not be modified
Cause: OC4J RMI port could not be modified.
Action: Make sure that OC4J instance exists and port is not in use by using the command 'srvctl config oc4j' and try again.
PRKO-02079: OC4J could not be started
Cause: The start of OC4J instance failed.
Action: Make sure that OC4J instance exists and is not already started.
PRKO-02081: OC4J failed to stop
Cause: The OC4J instance could not be stopped.
Action: Make sure that OC4J instance exists and are not already stopped.
PRKO-02082: Missing mandatory option {0}
Cause: The specified mandatory command option is missing.
Action: Use srvctl with the -h option to display option details for the command and make sure that all the mandatory options are specified.
PRKO-02087: OC4J could not be enabled
Cause: OC4J instance could not be enabled.
Action: Make sure that node name is correct and that OC4J instance exists and is not already enabled. The current state of the OC4J instance can be found using 'srvctl status oc4j' command. To check if OC4J instance is configured or not use 'srvctl config oc4j' command.
PRKO-02090: OC4J could not be disabled
Cause: OC4J instance could not be disabled.
Action: Make sure that Node name is correct and that OC4J instance exists and is not already disabled. The current state of the OC4J instance can be found using the srvtl status oc4j command. To check if OC4J instance is configured or not use 'srvctl config oc4j' command.
PRKO-02093: OC4J could not be relocated
Cause: OC4J instance could not be relocated to given node.
Action: If the node name was passed in the command line make sure that the node name is valid. Also make sure that 0C4J instance exists on the cluster and is running.
PRKO-02100: Cannot update service {0} because {1} is not is not administrator-managed
Cause: An attempt to update the service using "-u" option failed because this option can be used with administrator-managed databases only.
Action: Make sure that you provide correct options for 'srvctl add service' command.
PRKO-02102: Failed to create server pool {0}: {1}
Cause: An attempt to create the specified server pool failed because of the reason provided by the accompanying error.
Action: Examine the accompanying error messages for details.
PRKO-02103: The '-a' and '-r' options cannot both be supplied with '-u'
Cause: Command 'srvctl add service' with '-u' option failed because both options '-a' and '-r' were provided.
Action: Correct options and issue command again.
PRKO-02104: Option '-a' or '-r' should be supplied with '-u
Cause: Command 'srvctl add service' with option '-u' failed because both it requires options '-a' or '-r' to be provided.
Action: Correct options and issue command again.
PRKO-02105: Option '-g' cannot be used with option '-r','-a' or '-P'
Cause: Incorrect usage of -g option.
Action: Correct options and issue command again.
PRKO-02106: There is no server pool associated with database {0}
Cause: Command 'srvctl add service' failed because the given database doesn't have an associated server pool.
Action: Oracle internal error. Contact customer support.
PRKO-02108: Command line options '-i' and '-n' cannot be used at the same time
Cause: Incorrect usage of -i and -n options.
Action: Correct options and issue command again.
PRKO-02110: Option '-c' cannot be used to create services with admin managed database {0}
Cause: Incorrect usage of -c option.
Action: Remove -c option and issue command again.
PRKO-02111: Invalid number {0} for command line option {1}
Cause: Invalid value was specified for the command line option that requires a number in a certain range.
Action: Check the value printed and specify a number within the required range.
PRKO-02115: OC4J is already disabled
Cause: OC4J instance could not be disabled because it is already disabled.
Action: If this is the expected state then this is not an error. If it is not then enable OC4J instance by using the 'srvctl enable oc4j' command.
PRKO-02116: OC4J is already enabled
Cause: OC4J instance could not be enabled because it is already enabled.
Action: If this is the expected state then this is not an error. If it is not then disable OC4J instance by using the 'srvctl disable oc4j' command.
PRKO-02165: VIP does not exist on node(s) : {0}
Cause: VIP was not configured on the nodes.
Action: Add VIP using 'srvctl add nodeapps' or 'srvctl add vip' and try this command again.
PRKO-02166: GSD does not exist on node(s): {0}
Cause: GSD was not configured on the nodes
Action: Add GSD using 'srvctl add nodeapps' and try this command again.
PRKO-02167: VIP {0} does not exist.
Cause: VIP with the specified name was not configured.
Action: Add VIP using 'srvctl add nodeapps' or 'srvctl add vip' and try this command again.
PRKO-02168: Node applications are still running on node:
Cause: Node applications are still running on node when a remove was attempted.
Action: Stop the node applications before removing them or use force flag when attempting removal.
PRKO-02172: Some or all node applications are not removed successfully on node:
Cause: Not all node applications were removed on the node.
Action: Make sure that all resources that depend on node applications are stopped before attempting to remove node applications. Also if force flag was not specified, reissue this command with the force flag specified.
PRKO-02173: Instance {0} is already a preferred instance for service {1}.
Cause: Given instance is already a preferred instance for the service.
Action: Specify an instance other than the preferred instances of this service.
PRKO-02174: Instance {0} is already an available instance for service {1}.
Cause: Given instance is already an available instance for the service.
Action: Specify an instance other than the available instances of this service.
PRKO-02176: ONS daemon does not exist on node(s): {0}
Cause: ONS was not configured on the nodes.
Action: Add ONS using 'srvctl add nodeapps' command and try this command again.
PRKO-02182: eONS daemon does not exist on node(s): {0}
Cause: eONS was not configured on the nodes.
Action: Add eONS using 'srvctl add nodeapps' command and try this command again.
PRKO-02183: Node applications run on default network only. The netmask given {0} doesn't match default networks netmask {1}
Cause: The netmask given in the modify command doesn't match with default network's netmask.
Action: Modify the default network first using 'srvctl modify nodeapps -S <options>' and then try modifying the VIP.
PRKO-02184: Node applications run on default network only. The interface given {0} doesn't match default networks interface {1}
Cause: The interface specified in the modify command doesn't match with default network's interface.
Action: Modify the default network's interface using 'srvctl modify nodeapps -S <options>' and then try modifying the VIP.
PRKO-02185: The new VIP address given is same as the current VIP address
Cause: The VIP address given for modification is same as the current VIP. So there is nothing to modify.
Action: Check the VIP address you want to modify and specify the correct value.
PRKO-02186: The command line parameter host port list should be in the form <host>[:<port>][,<host>:[<port>]...]
Cause: The command line parameter -t <host_port_list> was not in the format <host>[:<port>][,<host>:[<port>]...] with port being numeric.
Action: Check the input and correct any error and try the command again.
PRKO-02187: The network resource has been modified successfully. VIP and other resources that depend on it might not start up unless they are modified
Cause: When underlying network resource has been modified the VIP should be updated to the new network resource. This is not a error and is just a status message.
Action: Use 'srvctl modify nodeapps -A <options>' to update the VIP to the new network.
PRKO-02188: All the node applications already exist. They were not recreated.
Cause: 'srvctl add nodeapps' was attempted when all the node applications already existed.
Action: If you want to modify node applications you should use 'srvctl modify nodeapps' command.
PRKO-02190: VIP exists for node {0}, VIP name {1}
Cause: The VIP being added already exists.
Action: Check the input and if VIP needs to be modified use 'srvctl modify VIP' command.
PRKO-02199: Invalid address string:
Cause: VIP address being passed on the command line is not a valid address string.
Action: Address string should be of the format <name|ip>/<netmask>/[if1[|if2...]]. Check the usage and correct the address format.
PRKO-02200: Invalid interface specified on command line: {0}
Cause: VIP address specification '-A <name|ip>/<netmask>[/if1[|if2|...]]' or the network address specification '-S <subnet>/<netmask>[/if1[|if2|...]]' on the command line contained interfaces names, none of which exist on current node.
Action: Check the interfaces listed in the address string and make sure that they are enabled and are up. Use network interface names on the command line if there is more than one interfaces that connect to the same network.
PRKO-02207: -{0} option has been deprecated and will be ignored.
Cause: Deprecated option has been used in the command line. The option will be ignored.
Action: Check the documentation for the new syntax of the command.
PRKO-02208: {0} command has been deprecated and will be ignored.
Cause: The command being executed has been deprecated and will not do any action.
Action: Check the documentation for the commands supported by srvctl.
PRKO-02209: {0} command is not supported for configuration using server pool.
Cause: The given command failed because it isn't applicable to instances of policy managed-databases.
Action: Check the documentation on the commands that are applicable to policy-managed databases.
PRKO-02211: ASM listener was not found
Cause: Check the reported message, ASM listener may not exist.
Action: Use "srvctl modify asm -l <lsnr_name>" to set the listener that ASM should register with.
PRKO-02310: VIP does not exist on node {0}.
Cause: VIP was not configured on that node on which modification was attempted.
Action: VIP must be added using 'srvctl add nodeapps' command, before it can be modified.
PRKO-02313: VIP {0} does not exist.
Cause: An attempt was made to remove a VIP with the specified vipname. No such VIP was configured on the cluster.
Action: If this is the expected state then it is not an error. Check the status of VIPs using 'srvctl status vip' command. VIP must be added using 'srvctl add vip' command before it can be removed.
PRKO-02318: Target instance {0} already supports service {1}.
Cause: Given database instance already provides the given service.
Action: Specify an instance that is not a preferred or available instance for this service.
PRKO-02331: ONS daemon does not exist.
Cause: ONS daemon was not configured on this cluster.
Action: ONS daemon can be configured using the 'srvctl add nodeapps' command.
PRKO-02339: eONS daemon does not exist.
Cause: eONS daemon was not configured on this cluster.
Action: eONS daemon can be configured using the 'srvctl add nodeapps' command.
PRKO-02377: eONS already uses {0} as listening port. Nothing to modify.
Cause: The listening port specified in this command is already in use by eONS.
Action: Check the input and if the listening port needs to be changed then specify a different port.
PRKO-02380: VIP {0} is still running on node: {1}
Cause: VIP to be removed is still running on a node.
Action: Stop the VIP before attempting to remove it or retry the command with force flag.
PRKO-02381: VIP {0} is not removed successfully:
Cause: VIP remove action failed because VIP was running and force flag was not specified or an exception occurred during the removal.
Action: Make sure that any applications, like for example listener, that depend on VIP are down. Try using -f option to remove the VIP. If you use force option to remove VIP then any application that depends on this VIP will stop working. Look at the help message for the accompanying exception.
PRKO-02383: Network {0} is not removed successfully:
Cause: Since there were no VIPs hosted on the network an attempt was made to remove the network and network removal failed.
Action: Make sure that all other applications that depend on default network are stopped. If force flag was not specified then specify force flag and try the command again.
PRKO-02385: The specified hostname or address {0} cannot be resolved.
Cause: An invalid IP address or irresolvable hostname was specified.
Action: If IP address is specified then make sure that it is of legal length. If a host name is specified then make sure that the host name resolves to an IP address.
PRKO-02386: Netmask is missing in address string:
Cause: NETMASK is missing in the VIP address that was passed in the command string.
Action: VIP address is of form <ip_or_name>/<netmask>[/<interface1>[|<interface2>...]]. Specify the netmask.
PRKO-02387: -n <node_name> option has been deprecated.
Cause: -n <node_name> has been deprecated in this release.
Action: Try to remove the usage of -n <node_name> in the command.
PRKO-02388: Command line option {0} should be followed by a value.
Cause: The value needs to be specified by the command line option.
Action: Look at the usage and of the command and specify an appropriate value.
PRKO-02389: Invalid command line options. Neither -A nor -n can be specified with -S.
Cause: Invalid combination of options specified for add/modify node application command. -A is node-specific option and has to be used with -n option. -S option is a global option and it cannot be used with -A or -n option.
Action: Issue the command using either -A and -n together or -S without -A or -n.
PRKO-02390: -n <node_name> option has been deprecated and is ignored.
Cause: -n <node_name> option has been deprecated and is ignored from this release. It has no effect on the command.
Action: Remove the usage of -n <node_name> from the command line.
PRKO-02391: Network resource {0},{1} already exists. Nothing to modify
Cause: The subnet specified is already the default subnet.
Action: Check the input and if the subnet needs to be modified then specify a different subnet.
PRKO-02392: eONS already uses {0} as Multicast address. Nothing to modify.
Cause: The Multicast address specified in this command is already in use by eONS.
Action: Check the input and if the Multicast address needs to be changed then specify a different address.
PRKO-02393: eONS already uses {0} as Multicast port. Nothing to modify.
Cause: The Multicast port specified in this command is already in use by eONS.
Action: Check the input and if the Multicast port needs to be changed then specify a different port.
PRKO-02394: ONS already uses {0} as port for local connections. Nothing to modify.
Cause: The modify node applications command failed because the ONS port for local connections is already used by ONS for local connections.
Action: Check the input and if the port used by ONS for local connections need to be modified specify a different address.
PRKO-02395: ONS already uses {0} as port for remote connections. Nothing to modify.
Cause: The modify node applications command failed because the ONS port for remote connections is already used by ONS for remote connections.
Action: Check the input and if the port used by ONS for remote connections need to be modified specify a different address.
PRKO-02396: The list of remote host/port ONS pairs matches the current list : {0}. Nothing to modify.
Cause: The modify node applications command failed because the remote host/port ONS pairs matches the current list.
Action: Check the input and if the remote host/port pairs need to be modified and specify a different host/port list.
PRKO-02405: Network resource does not exist on the cluster nodes.
Cause: Network resource does not exist on the cluster nodes.
Action: Node applications can be added by using 'srvctl add nodeapps' command.
PRKO-02409: GSD is already disabled on node(s): {0}
Cause: The disable node applications command failed because GSD was already disabled.
Action: If this is the expected state then this is not an error. If it is not then GSD can be enabled by 'srvctl enable nodeapps' command.
PRKO-02410: VIP is already disabled on node(s): {0}
Cause: The disable node applications command failed because VIP was already disabled.
Action: If this is the expected state then this is not an error. If it is not then VIP can be enabled by 'srvctl enable nodeapps' command.
PRKO-02411: Network resource is already disabled.
Cause: The disable node applications command failed because Network resource was already disabled.
Action: If this is the expected state then this is not an error. If it is not then Network resource can be enabled by 'srvctl enable nodeapps' command.
PRKO-02412: ONS is already disabled on node(s): {0}
Cause: The disable node applications command failed because ONS was already disabled.
Action: If this is the expected state then this is not an error. If it is not then ONS can be enabled by 'srvctl enable nodeapps' command.
PRKO-02413: eONS is already disabled on node(s): {0}
Cause: The disable node applications command failed because eONS was already disabled.
Action: If this is the expected state then this is not an error. If it is not then eONS can be enabled by 'srvctl enable nodeapps' command.
PRKO-02414: GSD is already enabled on node(s): {0}
Cause: The enable node applications command failed because GSD is already enabled.
Action: If this is the expected state then this is not an error. If it is not then GSD can be disabled by 'srvctl disable nodeapps' command.
PRKO-02415: VIP is already enabled on node(s): {0}
Cause: The enable node applications command failed because VIP is already enabled.
Action: If this is the expected state then this is not an error. If it is not then VIP can be disabled by 'srvctl disable nodeapps' command.
PRKO-02416: Network resource is already enabled.
Cause: The enable node applications command failed because Network resource is already enabled.
Action: If this is the expected state then this is not an error. If it is not then Network resource can be disabled by 'srvctl disable nodeapps' command.
PRKO-02417: ONS is already enabled on node(s): {0}
Cause: The enable node applications command failed because ONS is already enabled.
Action: If this is the expected state then this is not an error. If it is not then ONS can be disabled by 'srvctl disable nodeapps' command.
PRKO-02418: eONS is already enabled on node(s): {0}
Cause: The enable node applications command failed because eONS is already enabled.
Action: If this is the expected state then this is not an error. If it is not then eONS can be disabled by 'srvctl disable nodeapps' command.
PRKO-02419: GSD is already started on node(s): {0}
Cause: The start node applications command failed because GSD is already started.
Action: If this is the expected state then this is not an error. If it is not then GSD can be stopped by 'srvctl stop nodeapps' command.
PRKO-02420: VIP is already started on node(s): {0}
Cause: The start node applications command failed because VIP is already started.
Action: If this is the expected state then this is not an error. If it is not then VIP can be stopped by 'srvctl stop nodeapps' command.
PRKO-02421: Network resource is already started on node(s): {0}
Cause: The start node applications command failed because Network resource is already started.
Action: If this is the expected state then this is not an error. If it is not then Network resource can be stopped by 'srvctl stop nodeapps' command. Note that once started network resource cannot be stopped.
PRKO-02422: ONS is already started on node(s): {0}
Cause: The start node applications command failed because ONS is already started.
Action: If this is the expected state then this is not an error. If it is not then ONS can be stopped by 'srvctl stop nodeapps' command.
PRKO-02423: eONS is already started on node(s): {0}
Cause: The start node applications command failed because eONS is already started.
Action: If this is the expected state then this is not an error. If it is not then eONS can be stopped by 'srvctl stop nodeapps' command.
PRKO-02424: GSD is already stopped on node(s): {0}
Cause: The stop node applications command failed because GSD is already stopped.
Action: If this is the expected state then this is not an error. If it is not then GSD can be started by 'srvctl start nodeapps' command.
PRKO-02425: VIP is already stopped on node(s): {0}
Cause: The stop node applications command failed because VIP is already stopped.
Action: If this is the expected state then this is not an error. If it is not then VIP can be started by 'srvctl start nodeapps' command.
PRKO-02426: ONS is already stopped on node(s): {0}
Cause: The stop node applications command failed because ONS is already stopped.
Action: If this is the expected state then this is not an error. If it is not then ONS can be started by 'srvctl start nodeapps' command.
PRKO-02427: eONS is already stopped on node(s): {0}
Cause: The stop node applications command failed because eONS is already stopped.
Action: If this is the expected state then this is not an error. If it is not then eONS can be started by 'srvctl start nodeapps' command.
PRKO-02428: VIP is running on the node {0} and cannot be modified.
Cause: Modify nodeapps command failed because VIP being modified is running on a node.
Action: Stop the node application by issuing 'srvctl stop nodeapps' and retry the modify again.
PRKO-02429: -n <node_name> should be specified with -A <name|ip>/netmask[/if1[|if2]] for modifying VIP.
Cause: If -n <node_name> option is specified then -A option should also be specified for modifying VIP.
Action: If you want to modify the VIP then use specifiy both the -n and -A options. Otherwise remove the -n <node_name> option and try command again.
PRKO-02430: -A <name|ip>/netmask[/if1[|if2] should be specified with -n <node_name> for modifying VIP.
Cause: -A <options> has been specified for the modify nodeapps command without specifying which node VIP needs to be modified.
Action: Specify the node whose VIP needs to be modified by using -n option.
PRKO-02431: Warning: the -n option is obsolescent; 'srvctl remove vip' is preferred for removing per-node VIP resource
Cause: A 'srvctl remove nodeapps' command was issued with the -n option specifying one or more nodes. Support for this option will be removed in a future release, at which time you must use the preferred command 'srvctl remove vip -i <vip_list>'.
Action: The command is processed normally and attempts to remove VIP resources for the specified node(s). This message is displayed only to alert you to a future change. Use 'srvctl remove nodeapps' to remove all node applications from the last node of the cluster.
PRKO-02438: Network resource does not exist.
Cause: Network resource to be started/stopped/modified/enabled/disabled does not exist.
Action: Network resource can be created using 'srvctl add nodeapps' command.
PRKO-02439: VIP does not exist.
Cause: VIP to be started/stopped/modified/enabled/disabled does not exist.
Action: VIP can be created using 'srvctl add nodeapps' command.
PRKO-02440: Network resource is already stopped.
Cause: The stop node applications command failed because network resource was already stopped.
Action: If this is the expected state then this is not an error. If it is not then network resource can be started by 'srvctl start nodeapps' command.
PRKO-02452: ONS already exists
Cause: A new instance of ONS daemon could not be created, as there is an existing instance of ONS.
Action: If this is the expected state then it is not an error. Use 'srvctl config ons' command to look at ONS daemon attributes and 'srvctl modify ons' command to modify ONS attributes.
PRKO-02453: eONS already exists
Cause: A new instance of eONS daemon could not be created, as there is an existing instance of eONS.
Action: If this is the expected state then it is not an error. Use 'srvctl config eons' command to see if eONS daemon is configured. Use 'srvctl modify eons' command to modify eONS attributes.
PRKO-02458: ONS does not exist
Cause: ONS daemon was not configured on this instance of Oracle Restart.
Action: Add ONS daemon using the 'srvctl add ons' command and try this command again.
PRKO-02463: eONS does not exist
Cause: eONS daemon was not configured on this instance of Oracle Restart.
Action: Add eONS daemon using the command 'srvctl add eons' command and try this command again.
PRKO-02465: ONS does not exist.
Cause: ONS daemon was not configured on this instance of Oracle Restart.
Action: ONS daemon can be configured using the 'srvctl add ons' command.
PRKO-02567: eONS daemon does not exist.
Cause: eONS daemon was not configured on this instance of Oracle Restart.
Action: eONS daemon can be configured using the 'srvctl add eons' command.
PRKO-02569: ONS is already started.
Cause: The 'srvctl start ons' command failed because the ONS daemon was already started.
Action: If this is the expected state then this is not an error. If it is not then ONS can be stopped by 'srvctl stop ons' command.
PRKO-02571: eONS is already started.
Cause: The 'srvctl start eons' command failed because the eONS daemon was already started.
Action: If this is the expected state then this is not an error. If it is not then eONS can be stopped by 'srvctl stop eons' command.
PRKO-02573: ONS daemon is already stopped.
Cause: The 'srvctl stop ons' command failed because the ONS daemon was already stopped.
Action: If this is the expected state then this is not an error. If it is not then ONS can be started by 'srvctl start ons' command.
PRKO-02575: eONS daemon is already stopped.
Cause: The 'srvctl stop eons' command failed because the eONS daemon was already stopped.
Action: If this is the expected state then this is not an error. If it is not then eONS can be started by 'srvctl start eons' command.
PRKO-02576: ONS is already enabled.
Cause: The 'srvctl enable ons' command failed because the ONS was already enabled.
Action: If this is the expected state then this is not an error. If it is not then ONS can be disabled by 'srvctl disable ons' command.
PRKO-02579: eONS is already enabled.
Cause: The 'srvctl enable eons' command failed because the eONS was already enabled.
Action: If this is the expected state then this is not an error. If it is not then eONS can be disabled by 'srvctl disable eons' command.
PRKO-02581: ONS is already disabled.
Cause: The 'srvctl disable ons' command failed because the ONS was already disabled.
Action: If this is the expected state then this is not an error. If it is not then ONS can be enabled by 'srvctl enable ons' command.
PRKO-02583: eONS is already disabled.
Cause: The 'srvctl disable eons' command failed because the eONS was already disabled.
Action: If this is the expected state then this is not an error. If it is not then eONS can be enabled by 'srvctl enable eons' command.
PRKO-02588: ONS daemon could not be removed because it is still running.
Cause: 'srvctl remove ons' command failed because ONS daemon was still running.
Action: Stop the ons daemon by using 'srvctl stop ons' command and then attempt to remove it. You can also use the force option to remove a running ons daemon.
PRKO-02589: eONS daemon could not be removed because it is still running.
Cause: 'srvctl remove eons' command failed because eONS daemon was still running.
Action: Stop the ons daemon by using 'srvctl stop eons' command and then attempt to remove it. You can also use the force option to remove a running eons daemon.
PRKO-02590: None of the ONS daemon parameters were modified.
Cause: The configuration of the ONS daemon has remained the same after the 'srvctl modify ons' command.
Action: Make sure that at least one of the optional modification parameters was specified on the command line. The current values of parameters of the ONS daemon can be found by using 'srvctl config ons' command. Specify at least one value different then current value while issuing the 'srvctl modify ons' command.
PRKO-02591: None of the eONS daemon parameters were modified.
Cause: The configuration of the eONS daemon has remained the same after the 'srvctl modify eons' command.
Action: Make sure that at least one of the optional modification parameters was specified on the command line. The current values of parameters of the eONS daemon can be found by using 'srvctl config eons' command. Specify at least one value different then current value while issuing the 'srvctl modify eons' command.
PRKO-02593: enable of GNS failed.
Cause: Enabling the GNS server failed.
Action: Examine the accompanying exception for details.
PRKO-02595: modify of GNS failed.
Cause: Modification the GNS server failed.
Action: Examine the accompanying exception for details.
PRKO-02597: disable of GNS failed.
Cause: Disabling the GNS server failed.
Action: Examine the accompanying exception for details.
PRKO-02599: relocation of GNS failed.
Cause: Relocation of the GNS server failed.
Action: Examine the accompanying exception for details.
PRKO-02601: removal of GNS failed.
Cause: Removal of the GNS server failed.
Action: Examine the accompanying exception for details.
PRKO-02603: addition of GNS failed.
Cause: The addition of the GNS server failed.
Action: Examine the accompanying exception for details.
PRKO-02604: GNS is already running
Cause: The GNS server is already running.
Action: Remove the GNS server first before trying to add it.
PRKO-02611: GNS VIP does not exist. Specify the {0} option to create one.
Cause: The attempt to add GNS failed because the VIP associated with it does not exist.
Action: Create the VIP.
PRKO-03026: Only one instance can be listed in -i <inst_name_list> when -n option is specified
Cause: More than one instance was specified for -i option when both -i and -n options were used.
Action: Supply one instance name for -i option when using both -i and -n option.
PRKO-03031: Server pool {0} already exists
Cause: Command 'srvctl add serverpool' failed because the given server pool already exists.
Action: Make sure that the name of server pool is correct and a server pool with the given name doesn't exist.
PRKO-03032: Invalid instance name(s): {0}
Cause: Some of the supplied instance names do not exist in the database configuration.
Action: Please supply valid instance names and retry.
PRKO-03077: Failed to remove database {0}:
Cause: Failed to remove the database.
Action: Examine the accompanying message(s) for details of the error, and respond accordingly.
PRKO-03081: No such environment variable setting: {0}
Cause: The environment variable(s) does not exist for the specified resource.
Action: Supply a valid environment variable.
PRKO-03085: Volume device: {0}
Cause: Volume device label
Action: None
PRKO-03086: Mountpoint path: {0}
Cause: Mountpoint path label
Action: None
PRKO-03087: User: {0}
Cause: User label
Action: None
PRKO-03113: Administrator-managed database {1} can not support policy-managed service {0}.
Cause: The specified database does not support policy-managed services.
Action: Provide a database which supports policy-managed services.
PRKO-03114: Policy-managed database {1} can not support administrator-managed service {0}.
Cause: The specified database does not support administrator-managed services.
Action: Provide a database which supports administrator-managed services.
PRKO-03115: -P option cannot be used with policy-managed service {0}.
Cause: -P option cannot be used with policy-managed services.
Action: Remove -P option from a command line.
PRKO-03116: '-g' or '-r' option should be provided
Cause: one of specified options should be provided.
Action: make sure that one of specified options is incuded into the command line.
PRKO-03117: Service {0} already exists in database {1}
Cause: The service being added already exists.
Action: If the service needs to be modified use 'srvctl modify service' command.
PRKO-03118: Failed to check if service {0} exists: {1}
Cause: Failed to get the servcie data.
Action: Make sure that Oracle Clusterware is active.
PRKO-03119: Database {0} cannot be started since it has no configured instances.
Cause: The specified database is an administrator-managed database and it cannot be started because no instances were configured.
Action: Use srvctl add instance command to configure the instance and then retry.
PRKO-03120: Database {0} cannot be stopped since it has no configured instances.
Cause: The specified database is an administrator-managed database and it could not be stopped because no instances were configured.
Action: Use srvctl add instance command to configure the instance and then retry.
PRKO-03121: -i option or -n option is required for starting an instance on the administrator-managed database {0}.
Cause: The specified database is an administrator-managed database and the srvctl start instance command requires the instance name or nodename to be specified.
Action: Use srvctl start instance command with either the -i or -n option to start the instance.
PRKO-03122: -i option or -n option is required for stopping an instance of database {0}
Cause: Neither the instance name nor the nodename was provided during 'srvctl stop instance' command invocation.
Action: Use 'srvctl stop instance' command with either the -i or -n option to specify which instance to stop.
PRKO-03125: Invalid value {0} for command line option {1}
Cause: Invalid value was specified for the command line option.
Action: Check the value printed and specify the correct value.
PRKO-03126: Invalid GNS logging level: "{0}"
Cause: The level of logging specified was not a positive integer.
Action: Specify a positive integer.
PRKO-03128: Unable to add database because the resource for diskgroup {0} could not be found. {1}
Cause: The resource for the specified disk group could not be found. Either the diskgroup name was misspelled or the diskgroup has not been mounted.
Action: Correct the diskgroup spelling or use sqlplus to create the diskgroup.
PRKO-03129: Unable to modify database because the resource for diskgroup {0} could not be found. {1}
Cause: The resource for the specified disk group could not be found. Either the diskgroup name was misspelled or the diskgroup has not been mounted.
Action: Correct the diskgroup spelling or use sqlplus to create the diskgroup.
PRKO-03130: Server pool {0} is internally managed as part of administrator-managed database configuration and therefore cannot be modified directly via srvpool object.
Cause: An attempt was made to alter configuration of an internally managed server pool that is hosting an administrator-managed configuration.
Action: Do not modify this server pool via srvpool object directly. Instead use srvctl add/remove instance or srvctl modify database/service to alter this server pool's configuration.
PRKO-03132: -i option or -n option is required for checking the status of an instance of database {0}
Cause: Neither the instance name nor the nodename was provided during 'srvctl status instance' command invocation.
Action: Use 'srvctl status instance' command with either the -i or -n option to check the status of the instance.
PRKO-03133: Database {0} has no instance on node {1}
Cause: Instance was not configured on the specified node.
Action: Both 'srvctl add instance' or 'srvctl modify instance' command can also be used to change inst-node mapping in administrator-managed db's. For policy-managed database, use either 'srvctl start instance' command with -n option to start the instance on the specified node or use 'srvctl modify instance' command to configure an instance for that node.
PRKO-03134: -n option cannot be specified in conjunction with -z option
Cause: -n and -z options were both provided during 'srvctl modify instance' command invocation.
Action: Use 'srvctl modify instance' command with either the -n or -z option to modify the node instance mapping of the database instance.
PRKO-03135: -z option cannot be used with admin managed database {0}
Cause: -z option cannot be used to remove node instance mapping of admin managed database.
Action: Use 'srvctl remove instance' command to remove node instance mapping of admin managed database.
PRKO-03136: Option '-c' cannot be used with admin managed service {0}
Cause: -c option cannot be used with admin managed services.
Action: Reissue the command without the -c option.
PRKO-03137: '-P PRECONNECT' option cannot be used with policy-managed service {0}.
Cause: '-P PRECONNECT' option cannot be used with policy-managed services.
Action: Remove -P option from a command line.
PRKO-03138: Node {0} does not belong to server pool {1} which defines nodes for service {2}
Cause: Node doesn't belong to the server pool which defines nodes which can be used to run the specified service.
Action: Supply a node which belongs to specified server pool.
PRKO-03139: Options '-i' and '-t' cannot be used with policy-managed service {0}
Cause: -i and -t options cannot be used to relocate a policy-managed service.
Action: Use options -c and -n to relocate a service.
PRKO-03140: Options '-c' and '-n' cannot be used with admin managed service {0}
Cause: -c and -n options cannot be used to relocate a admin managed service.
Action: Use options -i and -t to relocate a service.
PRKO-03141: Database {0} could not be removed because it was running
Cause: A 'srvctl remove database' command failed because the database was running.
Action: Stop the database by using 'srvctl stop database' command and then attempt to remove it. You can also use the force option to remove the running database.
PRKO-03142: Option '-i' cannot be used to enable/disable services for policy-managed database {0}
Cause: Policy-managed database services can only be enabled or disabled by node, not by instance.
Action: Use option -n <node> to specify nodes on which to enable or disable services for this policy-managed database.
PRKO-03143: Options '-i', '-t', '-r', '-n' and '-a' cannot be used to modify policy-managed service {0}
Cause: Options -i, -t, -r, -n and -a can be used to modify administrator-managed service only.
Action: Make sure that the service you are going to modify is an administrator-managed service.
PRKO-03144: Option '-a' requires options '-n' and '-i' to be provided
Cause: Option -a can not be used without options -n and -i.
Action: Make sure that options -n, -i and -a are provided according to 'srvctl modify service' syntax.
PRKO-03145: Option '-i' requires one of the options '-t', '-r' or '-n' to be set
Cause: Option -i can not be used without additional options.
Action: Make sure that required option is provided according to 'srvctl modify service' syntax.
PRKO-03146: Option '-i' is not provided
Cause: Options -t,-r, and -n requires option -i to be set.
Action: Make sure that required option is provided according to 'srvctl modify service' syntax.
PRKO-03147: Instance {0} cannot be removed because it is the only preferred instance for service(s) {1} for database {2}
Cause: An attempt was made to remove the instance which is the only preferred instance for specified services.
Action: Make sure that specified services have more than one preferred instance or modify services to not have the instance as a preferred instance.
PRKO-03148: Instance {0} does not support service {1}.
Cause: The given database instance is not defined as a preferred or available instance for the given service.
Action: Specify an instance that is defined as preferred or available instance for the given service.
PRKO-03149: The candidate server {0} of server pool {1} is different from the server {2} specified with the '-x' option
Cause: Specified server must be the candidate server of the specified server pool.
Action: Make sure that the server specified with '-x' option is the same as the candidate server of the given server pool.
PRKO-03150: The server pool(s) {0} specified with the '-g' cannot be used to add an administrator-managed database
Cause: A request to add an administrator-managed database specified the -g option.
Action: Use 'srvctl add database' without the '-g' option to add an administrator-managed database.
PRKO-03151: Option '-g' cannot have more than one specified server pool when converting an administrator-managed database to a policy-managed database
Cause: An attempt was made to convert an administrator-managed database to a policy-managed database by specifying more than one server pool.
Action: Make sure to specify only one server pool with the '-g' option when converting an administrator-managed database to a policy-managed database.
PRKO-03152: The server pool(s) {0} specified with the '-g' option are subpools of Generic and therefore cannot be used to modify the server pool value of a policy-managed database
Cause: The supplied server pools are meant for managing administrator-managed databases because they are subpools of Generic.
Action: Make sure that none of the supplied server pools are meant for managing administrator-managed database. Only supply server pools meant for managing policy-managed databases to the -g option of 'srvctl modify database' command. Use 'srvctl config srvpool' command to list the qualified server pools meant for managing policy managed databases.
PRKO-03153: -i option and/or -n option is required for starting an instance on the policy-managed database {0}.
Cause: The specified database is a policy-managed database and the 'srvctl start instance' command requires the instance name and/or nodename to be specified.
Action: Use 'srvctl start instance' command with either the -i or -n option or both -i and -n options to start the instance.
PRKO-03154: Both -i and -n options are specified for starting an instance on the administrator-managed database {0}.
Cause: The specified database is an administrator-managed database and the 'srvctl start instance' command requires either the instance name or nodename to be specified but not both.
Action: Use 'srvctl start instance' command with either the -i or -n option to start the instance.
PRKO-03155: Can not start the instance {0} on the specified node {1} because the node is assigned to another user configured instance {2}
Cause: The database specified on 'srvctl start instance' is policy managed and has another instance already configured on the nodename specified with the -n option.
Action: Either reformulate the 'srvctl start instance' command so that there is no conflict with configured instances' nodes, or use 'srvctl modify instance' to change configured instances' nodes.
PRKO-03160: Server pool {0} is internally managed as part of administrator-managed database configuration and therefore cannot be queried directly via srvpool object.
Cause: An attempt was made to query configuration of an internally managed server pool that is hosting an administrator-managed configuration.
Action: Do not query this server pool via srvpool object directly. Instead use srvctl config/status database/service command to query servers that are part of this pool's configuration.
PRKO-03161: Server pool {0} is internally managed as part of administrator-managed database configuration and therefore cannot be removed directly via srvpool object.
Cause: An attempt was made to remove configuration of an internally managed server pool that is hosting an administrator-managed configuration.
Action: Do not remove this server pool via srvpool object directly. Instead use srvctl remove service/database command to remove this server pool and any service/database hosted by the server pool.
PRKO-03162: The actions setenv, getenv, and unsetenv are not suppported for Single Client Access Name listener {0}
Cause: Failed to use srvctl setenv, getenv, and unsetenv listener command for specified Single Client Access Name Listener. The environment variables for Single Client Access Name Listener cannot be changed.
Action: Do not set, get, and unset environment variables for Single Client Access Name Listener.
PRKO-09059: Invalid command line options for listener. '-a' can not be specified with '-l'.
Cause: Invalid combination of options specified for listener command.
Action: Issue the command using either '-l <listener_name>' or '-a'.
Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us