Starting oracle database 10g express edition instance

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.

To shut down 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 the command is successful, it displays the following output: Database closed. Database dismounted. All rights reserved. Book List. Master Index.

The database or one of its applications is functioning irregularly and none of the other types of shutdown works. You need to shut down the database instantaneously for example, if you know a power shutdown is going to occur in one minute. The database implicitly disconnects all connected users. The next startup of the database will require instance recovery procedures.

Shutdown modes that wait for users to disconnect or for transactions to complete have a limit on the amount of time that they wait. If all events blocking the shutdown do not occur within one hour, the shutdown command cancels with the following message: ORA user requested cancel of current operation. The quiesced state lets administrators perform actions that cannot safely be done otherwise.

These actions include:. Actions that fail if concurrent user transactions access the same object--for example, changing the schema of a database table or adding a column to an existing table where a no-wait lock is required. Actions whose undesirable intermediate effect can be seen by concurrent user transactions--for example, a multistep procedure for reorganizing a table when the table is first exported, then dropped, and finally imported.

A concurrent user who attempts to access the table after it was dropped, but before import, would not have an accurate view of the situation. Without the ability to quiesce the database, you would need to shut down the database and reopen it in restricted mode. This is a serious restriction, especially for systems requiring 24 x 7 availability.

Quiescing a database is much a smaller restriction, because it eliminates the disruption to users and the downtime associated with shutting down and restarting the database. When the database is in the quiesced state, it is through the facilities of the Database Resource Manager that non-DBA sessions are prevented from becoming active. Therefore, while this statement is in effect, any attempt to change the current resource plan will be queued until after the system is unquiesced.

Non-DBA active sessions will continue until they become inactive. No inactive sessions are allowed to become active. For example, If a user issues a SQL query in an attempt to force an inactive session to become active, the query will appear to be hung.

When the database is later unquiesced, the session is resumed, and the blocked action is processed. In an Oracle Real Application Clusters environment, this statement affects all instances, not just the one that issues the statement. See Oracle Database Reference for details on these view. If you interrupt the request to quiesce the database, or if your session terminates abnormally before all active sessions are quiesced, then Oracle Database automatically reverses any partial effects of the statement.

It only waits for the current fetch to finish. For both dedicated and shared server connections, all non-DBA logins after this statement is issued are queued by the Database Resource Manager, and are not allowed to proceed.

To the user, it appears as if the login is hung. The login will resume when the database is unquiesced. The database remains in the quiesced state even if the session that issued the statement exits.

A DBA must log in to the database to issue the statement that specifically unquiesces the database. All non-DBA activity is allowed to proceed. In an Oracle Real Application Clusters environment, this statement is not required to be issued from the same session, or even the same instance, as that which quiesced the database.

The column values has one of these values:. The suspend command is not specific to an instance. In an Oracle Real Application Clusters environment, when you issue the suspend command on one system, internal locking mechanisms propagate the halt request across instances, thereby quiescing all active instances in a given cluster. However, if someone starts a new instance another instance is being suspended, the new instance will not be suspended. Star ting Up a Database When you start up a database, you create an instance of that database and you determine the state of the database.

Understanding Initia lization Parameter Files 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.

Note: The spfile. There is no instance-specific location for storing a server parameter file. Note: You cannot use the IFILE initialization parameter within a text initialization parameter file to point to a server parameter file. See Also: Chapter 2, "Creating an Oracle Database" , for more information about initialization parameters, initialization parameter files, and server parameter files. You can start an instance in various modes: Start the instance without mounting a database.

Note: You cannot start a database instance if you are connected to the database through a shared server process. Note: It is possible to encounter problems starting up an instance if control files, database files, or redo log files are not available. If one or more of the datafiles or redo log files is not available or cannot be opened when attempting to open a database, the database returns a warning message and does not open the database.

Starting an Instance, and Mounting and Opening a Database Normal database operation means that an instance is started and the database is mounted and open. Starting an Instance Without Mounting a Database You can start an instance without mounting a database. Starting an Instance and Mounting a Database You can start an instance and mount a database without opening it, allowing you to perform specific maintenance operations.

For example, the database must be mounted but not open during the following tasks: Enabling and disabling redo log archiving options. It contains the following topics:. Oracle Database Express Edition Oracle Database XE starts up automatically immediately after installation and after each system restart.

Thus, there is no need to start up the database unless you previously shut it down. Each of these methods is described in the following sections:. This section explains how to start up the database from the desktop in Windows and in the following two Linux windowing managers: KDE and Gnome. This is typically the user oracle. See "Operating System Authentication" for more information. At the operating system prompt, enter the following command to start the SQL Command Line and connect to the database:.

If the command is successful, it displays output similar to the following. System global area sizes will vary depending on the amount of physical memory in your Oracle Database XE host computer.