Cloud Control combines a GUI console, agents, common services, and tools to provide an integrated and comprehensive systems management platform for managing Oracle products. You can use Cloud Control to administer your database, including starting it up and shutting it down. Starting Up a Database Using Cloud Control.You may prefer to do this if your are within the RMAN environment and do not want to invoke SQL*Plus. You can also use Recovery Manager (RMAN) to execute STARTUP and SHUTDOWN commands. Starting Up a Database Using Recovery Manager.Using SQL*Plus in this way is the only method described in detail in this book. You can start a SQL*Plus session, connect to Oracle Database with administrator privileges, and then issue the STARTUP command. You can start up an instance using SQL*Plus or Oracle Restart. You must perform some preliminary steps before attempting to start an instance of your database using SQL*Plus. When your database is managed by Oracle Restart, you can configure startup options for each individual database service (service). About Automatic Startup of Database Services.You can specify nondefault locations for these files, and the method for doing so depends on whether you start the database with SQL*Plus (when Oracle Restart is not in use) or with SRVCTL (when the database is being managed with Oracle Restart). The database looks for these files in a default location. To start an instance, the database must read instance configuration parameters (the initialization parameters) from either a server parameter file ( SPFILE) or a text initialization parameter file (PFILE). Specifying Initialization Parameters at Startup.If your database is being managed by Oracle Restart, the recommended way to start the database is with SRVCTL. When Oracle Restart is not in use, you can start up a database instance with SQL*Plus, Recovery Manager, or Oracle Enterprise Manager Cloud Control (Cloud Control). The INSTANCE_ABORT_DELAY_TIME initialization parameter specifies the amount of time, in seconds, to delay shutting down a database when an error causes the instance to abort. Use the ALTER SYSTEM RESUME statement to resume normal database operations.
When the database is suspended all preexisting I/O operations are allowed to complete and any new database accesses are placed in a queued state.
The suspended state lets you back up a database without I/O interference.
The ALTER SYSTEM SUSPEND statement halts all input and output (I/O) to data files (file header and file data) and control files. You can shut down a database with SQL*Plus or Oracle Restart.Ī quiesced database allows only DBA transactions, queries, fetches, or PL/SQL statements. You may want to do this in order to restrict access for maintenance reasons or to make the database read only. You can alter the availability of a database. Doing so makes the database available for any valid user to connect to and perform typical data access operations. Normally, you start up an instance by mounting and opening the database. When you start up a database, you create an instance of that database and you determine the state of the database.
0 kommentar(er)
