It is recommended that you enable the recovery process to take place immediately, after which you can shut down the database normally. Skip Headers. To start up the database using the desktop: Do one of the following: On Windows: Log in to the Oracle Database XE host computer as a Windows administrator—that is, as a user who is a member of the Administrator group. If not already opened, open a terminal session or command window. Linux platform only: Ensure that environment variables are set properly.
Database opened. If users or applications are still logged in when you begin a shutdown operation, the shutdown proceeds under the following conditions: No new connections are permitted, and no new transactions are allowed to be started.
Any uncommitted transactions are rolled back. All users and applications are immediately disconnected. You can start or stop the database using Windows Services : From the Start menu, enter services. Right-click the service name, and from the menu, select Start or Stop. To set its startup properties, right-click and select Properties , and in the dialog box, select either Automatic , Manual , or Disabled from the Startup type list. Section 2.
Before you start Oracle Database 11 g , ensure that both an instance and a database exist on the local system. COM file. In this command, you must specify the full directory path. For example:. You can choose to complete startup tasks separately when monitoring instance performance, for example. Alternatively, you can start an instance and then open a database after making some modifications.
When starting up Oracle Database 11 g , you start the current instance. If the file is not in the current default directory, then you must include the directory location of the file:.
In addition, you must run the COM file that makes the logical name assignments required to run Oracle Database 11 g. COM file to set the instance. The following sections explain how to alter the availability of a database:. When you perform specific administrative operations, the database must be started and mounted to an instance, but closed. You can achieve this scenario by starting the instance and mounting the database. You can make a mounted but closed database available for general use by opening the database.
Opening a database in read-only mode enables you to query an open database while eliminating any potential for online data content changes. While opening a database in read-only mode guarantees that data file and redo log files are not written to, it does not restrict database recovery or operations that change the state of the database without generating redo. For example, you can take data files offline or bring them online since these operations do not affect data content.
If a query against a database in read-only mode uses temporary tablespace, for example to do disk sorts, then the issuer of the query must have a locally managed tablespace assigned as the default temporary tablespace.
Otherwise, the query will fail. Limitations of a Read-only Database. An application must not write database objects while executing against a read-only database. For example, an application writes database objects when it inserts, deletes, updates, or merges rows in a database table, including a global temporary table.
An application writes database objects when it manipulates a database sequence. If your application calls any of these functions and procedures, or if it performs any of the preceding operations, your application writes database objects and hence is not read-only.
When executing on a read-only database, you must commit or roll back any in-progress transaction that involves one database link before you use another database link. This is true even if you execute a generic SELECT statement on the first database link and the transaction is currently read-only. You cannot invoke a remote procedure even a read-only remote procedure from a read-only database if the remote procedure has never been called on the database.
You can either put the remote procedure call in a stored procedure, or you can invoke the remote procedure in the database prior to it becoming read only. When you place a running instance in restricted mode, no user sessions are terminated or otherwise affected. Therefore, after placing an instance in restricted mode, consider killing terminating all current user sessions before performing administrative tasks.
If your database is being managed by Oracle Restart, the recommended way to shut down the database is with the srvctl stop database command. Control is not returned to the session that initiates a database shutdown until shutdown is complete. Users who attempt connections while a shutdown is in progress receive a message like the following:. There are several modes for shutting down a database: normal, immediate, transactional, and abort. Some shutdown modes wait for certain events to occur such as transactions completing or users disconnecting before actually bringing down the database.
There is a one-hour timeout period for these events. To shut down a database in normal situations, use one of these commands:. For SRVCTL, if the -o option is omitted, the shutdown operation proceeds according to the stop options stored in the Oracle Restart configuration for the database.
The default stop option is immediate. Before the database is shut down, the database waits for all currently connected users to disconnect from the database. When the database or one of its applications is functioning irregularly and you cannot contact users to ask them to log off or they are unable to log off. No new connections are allowed, nor are new transactions allowed to be started, after the statement is issued.
Any uncommitted transactions are rolled back. If long uncommitted transactions exist, this method of shutdown might not complete quickly, despite its name. Oracle Database does not wait for users currently connected to the database to disconnect. The database implicitly rolls back active transactions and disconnects all connected users.
When you want to perform a planned shutdown of an instance while allowing active transactions to complete first, use one of the following commands:. After all transactions have completed, any client still connected to the instance is disconnected. A transactional shutdown prevents clients from losing work, and at the same time, does not require all users to log off.
You can shut down a database instantaneously by aborting the database instance. If possible, perform this type of shutdown only in the following situations:.
The database or one of its applications is functioning irregularly and none of the other types of shutdown works. You must shut down the database instantaneously for example, if you know a power shutdown is going to occur in one minute.
0コメント