Oracle® Database Recovery Manager Reference 10g Release 1 (10.1) Part Number B10770-02 |
|
|
View PDF |
startup::=
To start the target database from within the RMAN environment. This command is equivalent to using the SQL*Plus STARTUP
command. You can:
Additionally, the RMAN STARTUP
command can start an instance in NOMOUNT
mode even if no server parameter file or initialization parameter file exists. This feature is useful when you need to restore a lost server parameter file.
See Also:
Oracle Database Administrator's Guide to learn how to start up and shut down a database, and SQL*Plus User's Guide and Reference for SQL*Plus |
STARTUP
command to open the recovery catalog database: execute a STARTUP
statement in a SQL*Plus session instead.If you do not specify any options, then RMAN mounts and opens the database with the default server parameter file.
Syntax Element | Description |
---|---|
|
If you specify only |
Restricts access to users with the |
|
If the database is open, then |
|
Starts the instance, then mounts the database without opening it |
|
Starts the instance without mounting the database. If no parameter file exists, then RMAN starts the instance with a "dummy" parameter file. You can then run |
|
Specifies the filename of the |
This example starts and opens the database:
STARTUP;
This example forces a SHUTDOWN
ABORT
and then mounts the database with restricted access, specifying a nondefault parameter file location:
STARTUP FORCE MOUNT DBA PFILE=/tmp/initTRGT.ora;
The following example starts an instance without using a parameter file, then runs RESTORE
SPFILE
:
SET DBID 1447326980; STARTUP FORCE NOMOUNT; # RMAN starts instance with dummy parameter file RESTORE SPFILE FROM AUTOBACKUP; # restore a server parameter file STARTUP FORCE; # restart instance with restored server parameter file