10. Click Yes.
The Startup page appears, indicating that the database is being started up. When startup is complete, the Login page appears.
11. Log in to the database (and to Database Control).
The Database Home page appears indicating that the database instance status is Up.
Shutting Down and Starting Up Using the Windows Services Program
On Microsoft Windows, you can also start and shut down your Oracle database using the Services program in Control Panel. You must start or stop the following services:
■ OracleServiceSID, which is your Oracle instance.
■ OracleORACLE_HOMETNSListener, which is your listener. The listener is required for clients to connect to your database.
■ OracleDBConsoleSID, which enables clients to connect to Database Control. In the preceding service names, SID refers to the system identifier for the instance and
ORACLE_HOME refers to the Oracle home name.
To start or stop Oracle Database services: 1. Do one of the following:
■ On Windows XP and Windows Server 2003, click Start, and then select
Control Panel.
■ On Windows 2000 Server, click Start, select Settings, and then select Control
Panel.
The Control Panel window opens.
2. Double-click the Administrative Tools icon, and then double-click the Services
icon.
The Services window opens, displaying all Windows services that are available on your system.
3. Locate the Oracle Database services listed at the beginning of this section. For example, if your SID is orcl, then locate the following services:
■ OracleServiceORCL
■ OracleOraDb11g_home1TNSListener
■ OracleDBConsoleorcl
4. Start or stop all three services, using the following steps for each service:
a. Select the service name.
b. In the Action menu, click Start or Stop.
Viewing and Modifying Initialization Parameters
This section provides instructions about viewing the initialization parameter settings for your database and modifying these parameters. You can modify the initialization parameters for the database in one of three ways:
Viewing and Modifying Initialization Parameters
■ Until the instance is shut down: The new values for the initialization parameters
are applied to the currently running instance, but, when the database is restarted, the initialization parameter values revert to their previous settings.
■ From now until the initialization parameter is changed again: The changes are
applied to the currently running instance and are also stored in the server
parameter file. The changes made to the initialization parameters persist when the database is restarted.
■ When the database is restarted: The new values for the initialization parameters
are recorded in server parameter file, but are not applied to the currently running instance. The changes take effect only when the database is restarted.
To view or modify initialization parameters:
1. At the top of the Database Home page, click Server to view the Server subpage.
2. Under Database Configuration, click Initialization Parameters.
Oracle Enterprise Manager Database Control (Database Control) displays the Initialization Parameters page.
The Initialization Parameters page has two subpages:
■ Current—This subpage (the default) displays all initialization parameter
values that are currently active (in memory) for the Oracle instance.
■ SPFile—This subpage displays initialization parameter settings in the server
parameter file. This subpage is present only when the current instance started up with a server parameter file. The file location is displayed at the top of the subpage.
See the online Help for the Initialization Parameters page for field descriptions.
Note: These three scenarios correspond to using the SCOPE=MEMORY,
SCOPE=BOTH, and SCOPE=SPFILE clauses of the ALTERSYSTEM SQL statement, respectively, when you use the ALTERSYSTEM statement to change initialization parameters.
Viewing and Modifying Initialization Parameters
3. (Optional) On either subpage, reduce the number of initialization parameters displayed by doing one or both of the following, and then clicking Go:
■ In the Name field, enter text.
■ Select from one or more of the lists next to the Name field.
For example, to view only initialization parameters that have the text DEST
anywhere in the parameter name, enter dest in the Name field, and then click
Go.
4. To modify one or more initialization parameters for the currently running instance only, with the modifications being lost when the instance is restarted, complete the following steps:
a. On the Current subpage, in the Value column, enter new values for the initialization parameters.
b. Ensure that Apply changes in current running instance(s) mode to SPFile is not selected.
c. (Optional) In the Comments column, enter text explaining the reasons for the changes.
d. Click Apply.
A confirmation message appears.
5. To modify initialization parameters for the currently running instance, and also record the modifications in the server parameter file that will persist when the database is restarted, complete the following steps:
a. On the Current subpage, in the Value column, enter new values for the initialization parameters.
b. Select Apply changes in current running instance(s) mode to SPFile.
c. (Optional) In the Comments column, enter text explaining the reasons for the changes.
d. Click Apply.
A confirmation message appears.
6. To modify initialization parameters in the server parameter file only, such that the current instance is not affected and changes take effect only when the database is next restarted, complete the following steps:
a. Click SPFile to view the SPFile subpage.
b. (Optional) Reduce the number of entries in the initialization parameter list as described in Step 3.
c. In the Value column, enter new values for the initialization parameters.
d. (Optional) In the Comments column, enter text explaining the reasons for the changes.
e. Click Apply.
Note: If the Value column cannot be written to for a particular initialization parameter, then it means that this parameter is not dynamic—that is, it cannot be changed for the current instance.