-db db_unique_name |
Unique name for the database
|
-eval |
Use this parameter to hypothetically evaluate the impact of the command on the system.
|
-startoption start_options |
Options for startup command (for example: OPEN , MOUNT , or NOMOUNT )
Notes:
-
This command parameter supports all database startup options.
-
For multi-word startup options, such as read only and read write , separate the words with a space and enclose in double quotation marks ("" ). For example, "read only" .
See Also: SQL*Plus User's Guide and Reference for more information about startup options
|
[-startconcurrency number_of_instances] |
Specify a number of database instances to start simultaneously, or specify 0 for an empty start concurrency value.
|
-node node_name |
The name of the node on which you want to start the database
Notes:
-
This command only applies to Oracle RAC One Node databases.
-
The node you specify must be in the candidate list for an administrator-managed Oracle RAC One Node database or in the server pool for a policy-managed Oracle RAC One Node database.
-
If the database is already running on a node than the one you specify, then the command returns an error.
-
If you do not specify a node, then Oracle Clusterware chooses which node on which to start the Oracle RAC One Node database according to its policies, such as dispersion, number of resources, and order of candidate nodes.
-
If there is an active online database relocation for the Oracle RAC One Node database you are attempting to start, then both instances will already be running and the command returns an error message saying so (remember that only during an online database relocation are two instances of an Oracle RAC One Node database in existence).
If the online database relocation failed for the Oracle RAC One Node database and you do not specify a node, then the command attempts to start both database instances.
If the online database relocation failed for the Oracle RAC One Node database and you specify a node, then the command attempts to abort the failed relocation and start the instance on that node.
|