5 Administering a Database on Windows

Managing Oracle Database Services

This section tells you how to manage the services that Oracle Database installs on your computer.

This section provides information on the following:

• Oracle Database Service Naming Conventions for Multiple Oracle Homes

• Starting Oracle Database Services

• Stopping Oracle Database Services

• Auto-starting Oracle Database Services

C:\> NET START service

C:\> net STOP service

Auto-starting Oracle Database Services

Oracle Database services can be set to start automatically whenever the Windows computer is restarted. You can turn auto-start on or off from two different locations:

• Control Panel

• Oracle Administration Assistant for Windows

Control Panel

To use the Control Panel to configure when and how Oracle Database is started:

1. Access your Windows Services dialog.

   See Also:

   Your operating system documentation for instructions

2. Select service OracleServiceSID and click Startup.

3. Choose Automatic from the Startup Type field.

4. Click OK.

5. Click Close to exit the Services dialog.

Oracle Administration Assistant for Windows

To automatically start Oracle Database services from Oracle Administration Assistant for Windows:

1. From the Start menu, select Programs, then select Oracle - HOME_NAME, then select Configuration and Migration Tools and then select Administration Assistant for Windows.

2. Right-click the SID.

   where SID is a specific instance name, such as orcl.

3. Choose Startup/Shutdown Options.

4. Choose the Oracle Service tab.

5. Choose Automatic in Oracle Service Startup Type.

6. Click Apply.

7. Click OK.

Description of the illustration ss_cnfg1.gif

Starting and Shutting Down a Database with SQL*Plus

These instructions assume that a database instance has been created.

To start or shut down Oracle Database:

1. Go to your Oracle Database server.

2. Start SQL*Plus at the command prompt:

   C:\> sqlplus /NOLOG
   

3. Connect to Oracle Database with username SYSDBA:

   SQL> CONNECT / AS SYSDBA 
   

4. To start a database, enter:

   SQL> STARTUP [PFILE=path\filename]
   

   This command uses the initialization parameter file specified in path\filename. To start a database using a file named init2.ora located in

   C:\app\oracle\product\11.2.0\admin\orcl\pfile
   

   you would enter:

   SQL> STARTUP PFILE=C:\app\oracle\product\11.2.0\admin\orcl\pfile\init2.ora
   

   If no PFILE is specified, then the command looks for an SPFILE in ORACLE_HOME\database. If the command finds one, then the command uses it to start the database. If it does not find an SPFILE, then it uses the default initialization parameter file located in ORACLE_BASE\ADMIN\db_name\pfile.

5. To stop a database, enter:

   SQL> SHUTDOWN [mode]
   

   where mode is normal, immediate, or abort.

   In a normal shutdown, Oracle Database waits for all currently-connected users to disconnect and disallows any new connections before shutting down. This is the default mode.

   In an immediate shutdown, Oracle Database terminates and rolls back active transactions, disconnects clients, and shuts down.

   In an abort shutdown, Oracle Database terminates active transactions and disconnects users; it does not roll back transactions. The database performs automatic recovery and rollback the next time it is started. Use this mode only in emergencies.

   See Also:

   Chapter 2, "Database Tools on Windows" for a list of other tools that can start Oracle Database and this guide for information on options you can specify when starting your database.

Starting and Shutting Down a Database Using Services

You can start or shut down Oracle Database by starting or stopping service OracleServiceSID in the Control Panel. Starting OracleServiceSID is equivalent to using the STARTUP command or manually entering:

C:\> oradim -STARTUP -SID SID [-STARTTYPE srvc | inst | srvc,inst] [-PFILE 
filename | -SPFILE]

Stopping OracleServiceSID is equivalent to using the SHUTDOWN command or manually entering:

C:\> oradim -SHUTDOWN -SID SID [-SHUTTYPE srvc | inst | srvc,inst] [-SHUTMODE 
normal | immediate | abort]

You can enable starting and stopping Oracle Database through OracleServiceSID two different ways:

• Oracle Administration Assistant for Windows

• Setting Registry Parameters

Oracle Administration Assistant for Windows

To start or stop a database using Oracle Database services from Oracle Administration Assistant for Windows:

1. From the Start menu, select Programs, then select Oracle - HOME_NAME, then select Configuration and Migration Tools and then select Administration Assistant for Windows.

2. Right-click the SID.

   where SID is a specific instance name, such as ORCL.

3. Choose Startup/Shutdown Options.

4. Choose the Oracle Instance tab.

5. Select Start up instance when service is started, Shut down instance when service is stopped, or both.

Setting Registry Parameters

To start or stop Oracle Database through Oracle Database Services, set the following registry parameters to the indicated values:

• ORA_SID_AUTOSTART

  When set to true, the default value, this parameter causes Oracle Database to start when OracleServiceSID is started.

• ORA_SID_PFILE

  This parameter sets the full path to the initialization parameter file. If this entry is not present, then oradim will try to start the database with an SPFILE or PFILE from ORACLE_HOME\database.

• ORA_SHUTDOWN

  When set to true, this parameter enables the selected instance of Oracle Database to be shut down when OracleServiceSID is stopped. This includes any database in the current Oracle home. Default value is false.

• ORA_SID_SHUTDOWN

  When set to true, the default value, this parameter causes the instance of Oracle Database identified by the SID value to shut down when OracleServiceSID is stopped manually‘Äîusing either the Control Panel or Net stop command.

  Caution:

  If ORA_SHUTDOWN or ORA_SID_SHUTDOWN is set to false, then manually shutting down OracleServiceSID will still shut down Oracle Database. But it will be an abnormal shutdown, and Oracle does not recommend it.

The following two registry parameters are optional:

• ORA_SID_SHUTDOWNTYPE

  This parameter controls database shutdown mode. Set it to a (abort), i (immediate), or n (normal). Default mode is i (immediate) if you do not set this parameter.

• ORA_SID_SHUTDOWN_TIMEOUT

  This parameter sets maximum time to wait before the service for a particular SID stops.

The registry location of these required and optional parameters is determined by the number of Oracle home directories on your computer. If you have only one Oracle home directory, then these parameters belong in:

HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0

If you have multiple Oracle home directories, then these parameters belong in:

HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID 

where ID is incremented for each additional Oracle home directory on your computer.

Starting or Stopping OracleServiceSID from the Control Panel

1. To start the database, start OracleServiceSID.

   This automatically starts ORADIM and issues the -STARTUP command using the initialization parameter file identified by ORA_SID_PFILE.

2. To stop the database, stop OracleServiceSID.

   This automatically starts ORADIM, which issues the -SHUTDOWN command in the mode indicated by ORA_SID_SHUTDOWNTYPE, and shuts down Oracle Database.

   See Also:

   Your operating system documentation for instructions on starting and stopping services.

Starting Multiple Instances

1. Start the service for each instance using ORADIM or the Services dialog of the Control Panel.

2. At the command prompt set the ORACLE_SID configuration parameter to the SID for the first instance to run:

   C:\> SET ORACLE_SID=SID
   

   where SID is the name of the Oracle Database instance.

3. Start SQL*Plus:

   C:\> sqlplus /NOLOG
   

4. Connect AS SYSDBA:

   SQL> CONNECT / AS SYSDBA
   

5. Start up the first instance:

   SQL> STARTUP PFILE=ORACLE_BASE\admin\db_name\pfile\init.ora
   

   where ORACLE_BASE is c:\app\oracle\product\11.2.0 (unless you changed it during installation) and db_name is the name of the instance.

6. Repeat Steps 2-5 for the other instances to run.

Creating and Populating Password Files

Use Password Utility to create password files. Password Utility is automatically installed with Oracle Database utilities. Password files are located in directory ORACLE_HOME\database and are named PWDsid.ora, where SID identifies the Oracle Database instance. Password files can be used for local or remote connections to Oracle Database.

To create and populate a password file:

1. Create a password file with the Password Utility:

   C:\> orapwd FILE=PWDsid.ora ENTRIES=max_users
   

   where

   • FILE specifies the password file name.

   • SID identifies the database instance.

   • ENTRIES sets maximum number of entries in password file. This corresponds to maximum number of distinct users allowed to connect to the database simultaneously with either the SYSDBA or the SYSOPER DBA privilege.

2. Set initialization parameter file parameter REMOTE_LOGIN_PASSWORDFILE to exclusive, shared, or none.

   The value exclusive specifies that only one instance can use the password file and that the password file contains names other than SYS. In search of the password file, Oracle Database looks in the registry for the value of parameter ORA_SID_PWFILE. If no value is specified, then it looks in the registry for the value of parameter ORA_PWFILE, which points to a file containing usernames, passwords, and privileges. If that is not set, then it uses the default:

   ORACLE_HOME\DATABASE\PWDsid.ORA.
   

   The default value is shared. It specifies that multiple instances (for example, an Oracle RAC environment) can use the password file. However, the only user recognized by the password file is SYS. Other users cannot log in with SYSOPER or SYSDBA privileges even if those privileges are granted in the password file. The shared value of this parameter affords backward compatibility with earlier Oracle releases. Oracle Database looks for the same files as it does when the value is exclusive.

   The value none specifies that Oracle Database ignores the password file and that authentication of privileged users is handled by the Windows operating system.

3. Start SQL*Plus:

   C:\> sqlplus /NOLOG
   

4. Connect AS SYSDBA:

   SQL> CONNECT / AS SYSDBA
   

   For an ASM instance, connect AS SYSASM:

   SQL> CONNECT / AS SYSASM
   

5. Start Oracle Database:

   SQL> STARTUP
   

6. Grant appropriate privileges to each user. Users who must perform database administration, for example, would be granted privilege SYSDBA:

   SQL> GRANT SYSDBA TO db_administrator;
   

   For an ASM instance:

   SQL> GRANT SYSASM TO SYS;
   

   If the grant is successful, then the following message displays:

   Statement Processed.
   

   This adds scott to the password file and enables scott to connect to the database with SYSDBA privileges. Use SQL*Plus to add or delete usernames, user passwords, and user privileges in password files.

   Caution:

   Copying or manually moving password files may result in ORADIM being unable to find a password to start an instance.

Connecting Remotely to the Database as SYS

When connecting to the starter database from a remote computer as SYS, you must use a different password from the one described in Oracle Database Installation Guide for Microsoft Windows when logging on with SYSDBA privileges. This is because the password file enables database access in this situation and it requires the password oracle for this purpose.

Automatically Encrypted Database Passwords

With Oracle Database, the password used to verify a remote database connection is automatically encrypted. Whenever a user attempts a remote login, Oracle Database encrypts the password before sending it to the remote database. If the connection fails, then the failure is noted in the operating system audit log.

Archiving Redo Log Files

If you installed Oracle Database through the Typical installation, then it is created in NOARCHIVELOG mode. If you created your database through the Custom option of Database Configuration Assistant, then you had the choice of either ARCHIVELOG or NOARCHIVELOG.

In NOARCHIVELOG mode, redo logs are not archived. Setting your archive mode to ARCHIVELOG and enabling automatic archiving causes redo log files to be archived. This protects Oracle Database from both instance and disk failure.