Oracle home user windows

During Oracle Database installation, you can specify an optional Oracle home user associated with the Oracle home.

For example, assume that you use an Administrator user named OraSys to install the software (Oracle Installation user), then you can specify the ORADOMAIN\OraDb domain user as the Oracle home user for this installation. The specified Oracle home domain user must exist before you install the Oracle Database software.

Oracle home user can be a Windows Built-in Account (LocalSystem for Server and LocalService for Client), Virtual Account, or a regular (not an administrator) Windows account. If you specify an existing user as the Oracle home user, then the Windows User Account you specify can either be a Windows Domain User or a Windows Local User.

A Windows User Account need not be created by the Administrator if a Virtual Account or a Windows Built-in Account is used during installation.

If you specify a non-existing user as the Oracle home user, then the Windows User Account you specify must be a Windows Local User. The installer creates this account automatically to run the Windows services for the Oracle home. Do not log in using this account to perform administrative tasks.

The Group Managed Services Account (gMSA) and Virtual Accounts enables you to install Oracle Database, create, and manage Database services without passwords. The gMSA is a domain level account that can be used by multiple servers in a domain to run the services using this account. Windows User Account can be a Windows Local User, Windows Domain User, Managed Services Account (MSA), or Group Managed Services Account (gMSA).

If you want to create a new user during installation, then it can only be a Windows Local User. It cannot be a Windows Domain User, an MSA, or a gMSA. The new user that is created is denied interactive logon privileges to the Windows computer. However, a Windows administrator can manage this account like any other Windows account. Oracle recommends that you use Virtual Account or a standard Windows User Account (instead of Windows Built-in Account) as the Oracle Home User for enhanced security.

You cannot change the Oracle Home User after the installation is complete. If you must change the Oracle Home User, then you must reinstall the Oracle Database software.

When you specify an Oracle Home user, the installer configures that user as the Oracle Service user for all software services that run from the Oracle home. The Oracle Service user is the operating system user that the Oracle software services run as, or the user from which the services inherit privileges.

Silent installation is enhanced to support password prompt for the Oracle home user. So, customers and independent software vendors (ISV) can use response files without hard coding the password into the source code.

Oracle recommends using Virtual Account or a standard Windows User Account (not an Administrator account) as the Oracle Home User for typical installation, software-only installation, and cloning.

If an existing Windows User Account is used as the Oracle home user for software-only installation, then a password is not required. Thus, you can perform a silent, software-only installation using Windows User Account.

If you use a Windows User Account as the Oracle home user for cloning individual Oracle Database installations, then a password is not required.

Virtual Account is the Oracle home user for Oracle Database Single Instance database installation. The account enables you to install Oracle Database, create, and manage Database services without passwords. The gMSA is a domain level account that can be used by multiple servers in a domain to run the services using this account. The gMSA is a low privilege user account.

Oracle home user windows

During Oracle Database Client installation, you can specify an optional Oracle Home User associated with the Oracle home.

For example, assume that you use an Administrator user named OraSys to install the software (Oracle Installation user), then you can specify the ORADOMAIN\OraDb domain user as the Oracle Home User for this installation. The specified Oracle home domain user must exist before you install the Oracle Database Client software.

The Oracle Home User can be either the Windows Built-in Account (LocalService) or a Windows User Account. This account is used for running the Windows services for the Oracle home. Do not log in using this account to perform administrative tasks.

Windows User Account can be a Windows Local User, Windows Domain User, Managed Services Account (MSA), or Group Managed Services Account (gMSA). Starting with Oracle Database 12 c Release 2 (12.2), Group Managed Services Account (gMSA) is introduced as an additional option.

Using Windows built-in account, MSA, or gMSA enables you to install Oracle Database Client, and create and manage Database services without passwords.

If you specify an existing user as the Oracle Home User, then the Windows User Account you specify can either be a Windows Domain User or a Windows Local User. If you specify a non-existing user as the Oracle Home User, then the Windows User Account you specify must be a Windows Local User. The new user is then created during installation and the created user is denied interactive logon privileges to the Windows computer. However, a Windows administrator can manage this account like any other Windows account.

For enhanced security, Oracle recommends that you use the standard Windows User Account or Windows Built-in Account (LocalService), which is not an administrator account, to install Oracle Database Client.

You cannot change the Oracle Home User after the installation is complete. If you must change the Oracle Home User, then you must reinstall the Oracle Database Client software.

When you specify an Oracle Home User, the installer configures that user as the Oracle Service user for all software services that run from the Oracle home. The Oracle Service user is the operating system user that the Oracle software services run as, or the user from which the services inherit privileges.

Silent installation is enhanced to support password prompt for the Oracle Home User. So, customers and independent software vendors (ISV) can use response files without hard coding the password into the source code.

Oracle home user windows

Starting with Oracle Database 12 c Release 1 (12.1), Oracle Database supports the use of Oracle Home User, specified at the time of Oracle Database installation. Oracle Home User is used to run the Windows services for the Oracle home.

Oracle Home User can be a Windows Built-in Account or Virtual Account or a standard Windows User Account (not an Administrator account). Oracle Home User cannot be changed post installation.

If a Windows Built-in Account is used, then no user name or password is required during installation and administration. However, if a Windows User Account is used as Oracle Home User, then you must provide the user name and password during installation and some of the administration tasks.

Virtual Accounts allow you to install an Oracle Database and, create and manage Database services without passwords. A Virtual Account can be used as the Oracle Home User for Oracle Database Single Instance installations and does not require a user name or password during installation and administration.

Oracle Home User is different from Oracle Installation User. Oracle Installation User is the user who requires administrative privileges to install Oracle products. Oracle Home User is used to run the Windows services. You must not log into the Oracle Home User to perform administrative tasks.

Note that the Windows administrator privilege is still required to perform Oracle administrative functions such as installation, upgrade, patching, and other functions.

A Windows User Account used as Oracle Home User cannot have the administrator privileges as it causes the Oracle Universal Installer to display an error message.

• Managing Oracle Home User
  If you use a Windows User Account as the Oracle Home User, then you must ensure that this user account is present in the Windows system and its password is managed securely to ensure the proper operation and security of the database.
• Using Oracle Home User for an Oracle Database and Oracle Database Client
  For a single-instance Oracle Database and Oracle Database Client installations, you can use Built-in Account or a Windows User Account as the Oracle Home User. Single-instance Oracle Database installations may also use a Virtual Account.
• Using Oracle Home User for Multiple Oracle Homes
  Different Oracle homes on a system can use the same Oracle Home User or use different Oracle Home User names. Note that the earlier releases (11.2 and earlier) of Oracle Database are treated equivalent to using the Windows Built-in Account as the Oracle Home User.
• Using Oracle Home User During Oracle Database Upgrade
  You can use Oracle Database Upgrade Assistant to upgrade or move databases across Oracle homes if both the Oracle homes use the same Windows User Account as Oracle Home User, or at least one of the Oracle homes is configured to use Windows built-in account as the Oracle Home User.
• Converting from Single-Instance Oracle Database to Oracle Real Application Clusters
  You can convert from Oracle Database 12 c Release 2 (12.2) single-instance databases to Oracle RAC using Oracle Database Configuration Assistant, rconfig , or Oracle Enterprise Manager.

Microsoft documentation for more information on different types of Windows user accounts

Oracle home user windows

Oracle Database supports the use of Oracle Home User, specified at the time of Oracle Database installation. Oracle Home User is used to run the Windows services for the Oracle home.

Oracle Home User can be a Windows Built-in Account or a Virtual Account or a standard Windows User Account (not an Administrator account). Oracle Home User cannot be changed post installation.

If a Windows Built-in Account is used, then no user name or password is required during installation and administration. However, if a Windows User Account is used as Oracle Home User, then you must provide the user name and password during installation and some of the administration tasks.

Virtual Accounts allow you to install an Oracle Database and, create and manage Database services without passwords. A Virtual Account can be used as the Oracle Home User for Oracle Database Single Instance installations and does not require a user name or password during installation and administration.

Oracle Home User is different from Oracle Installation User. Oracle Installation User is the user, who installs a given Oracle Home and hence requires administrative privileges. Oracle Home User is used to run the Windows services. You must not log into the Windows system as Oracle Home User to perform administrative tasks.

Note that the Windows administrator privilege is still required to perform Oracle administrative functions such as installation, upgrade, patching, and other functions.

A Windows User Account used as Oracle Home User cannot have the administrator privileges as it causes the Oracle Universal Installer to display an error message.

• Managing Oracle Home User
  If you use a Windows User Account as the Oracle Home User, then you must ensure that this user account is present in the Windows system and its password is managed securely to ensure the proper operation and security of the database.
• Using Oracle Home User for an Oracle Database and Oracle Database Client
  For a single-instance Oracle Database and Oracle Database Client installations, you can use Built-in Account or a Windows User Account as the Oracle Home User. Single-instance Oracle Database installations may also use a Virtual Account.
• Using Oracle Home User for Multiple Oracle Homes
  Different Oracle homes on a system can use the same Oracle Home User or use different Oracle Home User names. Note that the earlier releases (11.2 and earlier) of Oracle Database are treated equivalent to using the Windows Built-in Account as the Oracle Home User.
• Using Oracle Home User During Oracle Database Upgrade
  You can use Oracle Database Upgrade Assistant to upgrade or move databases across Oracle homes if both the Oracle homes use the same Windows User Account as Oracle Home User, or at least one of the Oracle homes is configured to use Windows built-in account as the Oracle Home User.
• Converting from Single-Instance Oracle Database to Oracle Real Application Clusters
  You can convert from Oracle Database 19c single-instance databases to Oracle RAC using Oracle Database Configuration Assistant, rconfig , or Oracle Enterprise Manager.

Microsoft documentation for more information on different types of Windows user accounts

4 Configuring Users, Groups and Environments for Oracle Database

This chapter describes the users, groups, and environment settings to complete before you install Oracle Database and Grid Infrastructure for a standalone server.

This chapter contains the following topics:

4.1 Creating Required Operating System Groups and Users

Depending on if this is the first time you are installing Oracle software on your system and on the products that you are installing, you may have to create several operating system groups and users.

You can choose to create one administrative user and use one group for operating system authentication for all system privileges on the storage and database tiers. For example, you can designate the oracle user to be the Oracle Installation user for all Oracle software and use only the ORA_DBA group for authentication. You can also create custom configuration groups and users based on job role separation that divide access privileges.

Log in as an Administrator user, and use the following instructions to create the Oracle Installation user for Oracle Database.

4.1.1 About the Oracle Installation User

To install Oracle Grid Infrastructure for a standalone server or Oracle Database software, you must use either a local or domain user that is also a member of the Administrators group. This user is the Oracle Installation User. The Oracle Installation User can be either a local user or a domain user.

4.1.2 Creating Oracle Home User

During Oracle Database installation, you can specify an optional Oracle Home User associated with the Oracle home. For example, assume that you use an Administrator user named OraSys to install the software (Oracle Installation user), then you can specify the ORADOMAIN\OraDb domain user as the Oracle Home user for this installation. The specified Oracle Home domain user must exist before you install the Oracle Database software.

The Oracle Home User can be either the Windows built-in account (LocalSystem) or an existing user. If you specify an existing user as the Oracle Home User, then the Windows User Account you specify can either be a Windows Domain User or a Windows Local User.

If you specify a non-existing user as the Oracle Home User, then the Windows User Account you specify must be a Windows Local User. This account is used for running the Windows services for the Oracle home. Do not log in using this account to perform administrative tasks. Windows User Account can be a Windows Local User, Windows Domain User or Managed Services Account (MSA).

If you want to create a new user during installation, then it can only be a Windows Local User. It cannot be a Windows Domain User or an MSA. The new user that is created is denied interactive logon privileges to the Windows computer. However, a Windows administrator can manage this account like any other Windows account. Oracle recommends that you use the standard Windows User Account (instead of Windows Built-in Account) as the Oracle Home User for enhanced security.

You cannot change the Oracle Home User after the installation is complete. If you must change the Oracle Home User, then you must reinstall the Oracle Database software.

When you specify an Oracle Home user, the installer configures that user as the Oracle Service user for all software services that run from the Oracle home. The Oracle Service user is the operating system user that the Oracle software services run as, or the user from which the services inherit privileges.

Silent installation is enhanced to support password prompt for the Oracle Home User. So, customers and independent software vendors (ISV) can use response files without hard coding the password into the source code.

Oracle recommends using the standard Windows User Account (not an Administrator account) as the Oracle Home User for typical installation, software-only installation, and cloning.

If an existing Windows User Account is used as the Oracle Home User for software-only installation, then a password is not required. Thus, you can perform a silent, software-only installation using Windows User Account.

If using a Windows User Account as the Oracle Home User for cloning individual Oracle Database installations, then a password is not required.

4.1.3 Understanding the Oracle Inventory Directory and the Oracle Inventory Group

The Oracle Inventory directory is the central inventory location for all Oracle software installed on a server. By default, the location of the Oracle Inventory directory is C:\Program Files\Oracle\Inventory .

When you install Oracle software on the system for the first time, OUI creates the directories for the Oracle central inventory and the Oracle Inventory group, ORA_INSTALL . The ORA_INSTALL group contains all the Oracle Home Users for all Oracle homes on the server.

Whether you are performing the first installation of Oracle software on this server, or are performing an installation of additional Oracle software on the server, you do not need to create the Oracle central inventory or the ORA_INSTALL group; the Oracle Universal Installer creates them automatically. You cannot change the name of the Oracle Inventory group — it is always ORA_INSTALL .

4.1.4 Operating System Groups Created During Oracle Database Installation

During installation, the user groups listed in Table 4-1 are created, if they do not already exist. In the following table, the HOMENAME variable refers to the generated HOMENAME for a software installation, which is of the form Ora product majorVersion Home number . For example, OraDB12cHome1 .

Table 4-1 User Groups Created During Oracle Database Installation

SYSDBA system privileges for all Oracle Database installations on the server

A special OSDBA group for the Windows operating system.

Members of this group are granted SYSDBA system privileges for all Oracle Databases installed on the server.

SYSOPER system privileges for all Oracle databases installed on the server

A special OSOPER group for the Windows operating system.

Members of this group are granted SYSOPER system privileges all Oracle Databases installed on the server. This group does not have any members after installation, but you can manually add users to this group after the installation completes.

SYSASM system privileges for Oracle ASM administration

The OSASM group for the Oracle ASM instance.

Using this group and the SYSASM system privileges enables the separation of SYSDBA database administration privileges from Oracle ASM storage administration privileges. Members of the OSASM group are authorized to connect using the SYSASM privilege and have full access to Oracle ASM, including administrative access to all disk groups that the Oracle ASM instance manages.

SYSDBA system privileges on the Oracle ASM instance

The OSDBA group for the Oracle ASM instance.

This group grants access for the database to connect to Oracle ASM. During installation, the Oracle Installation Users are configured as members of this group. After you create an Oracle Database, this groups contains the contains Oracle Home Users of those database homes.

SYSOPER for ASM system privileges

The OSOPER group for the Oracle ASM instance.

Members of this group are granted SYSOPER system privileges on the Oracle ASM instance, which permits a user to perform operations such as startup, shutdown, mount, dismount, and check disk group. This group has a subset of the privileges of the OSASM group. Similar to the ORA_ HOMENAME _OPER group, this group does not have any members after installation, but you can manually add users to this group after the installation completes.

ORA _ HOMENAME _ DBA

SYSDBA system privileges for all instances that run from the Oracle home with the name HOMENAME

An OSDBA group for a specific Oracle home with a name of HOMENAME .

Members of this group can use operating system authentication to gain SYSDBA system privileges for any database that runs from the specific Oracle home. If you specified an Oracle Home User during installation, the user is added to this group during installation.

ORA_ HOMENAME _OPER

SYSOPER system privileges for all instances that run from the Oracle home with a name HOMENAME

An OSDBA group for the Oracle home with a name of HOMENAME .

Members of this group can use operating system authentication to gain SYSOPER system privileges for any database that runs from the specific Oracle home. This group does not have any members after installation, but you can manually add users to this group after the installation completes.

ORA_ HOMENAME _SYSBACKUP

SYSBACKUP system privileges for all instances that run from the Oracle home with a name of HOMENAME

OSBACKUPDBA group for a specific Oracle home with a name of HOMENAME .

Members of this group have privileges necessary for performing database backup and recovery tasks on all database instances that run from the specified Oracle home directory.

ORA_ HOMENAME _SYSDG

SYSDG system privileges for all instances that run from the Oracle home with a name of HOMENAME

OSDGDBA group for a specific Oracle home with a name of HOMENAME .

Members of this group have privileges necessary for performing Data Guard administrative tasks on all database instances that run from the specified Oracle home directory.

ORA_ HOMENAME _SYSKM

SYSKM system privileges for all instances that run from the Oracle home with a name of HOMENAME .

OSKMDBA group for a specific Oracle home with a name of HOMENAME .

Members of this group have privileges necessary for performing encryption key management tasks on all database instances that run from the specified Oracle home directory.

During the installation of Oracle Database, all groups mentioned in the table are populated for proper operation of Oracle products. You must not remove any group member populated by Oracle. However, if you want to assign specific database privileges to new Windows operating system users, then you can manually add users to these groups after the installation completes.

Oracle creates other groups, such as, ORA_INSTALL , ORA_CLIENT_LISTENERS , ORA_GRID_LISTENERS , ORA_ HOMENAME _SVCSIDS during installation and you should not change these groups, memberships, and ACLs associated with various Oracle created groups.

4.1.5 Operating System Groups and Users for Job Role Separation

A job role separation configuration of Oracle Database and Oracle ASM is a configuration with groups and users to provide separate groups for operating system authentication.

This section contains the following topics:

4.1.5.1 About Job Role Separation Operating System Privileges Groups and Users

During the Oracle Database installation, the OSDBA, OSOPER, OSBACKUPDBA, OSDGDBA and OSKMDBA groups are created and users assigned to these groups. Members of these groups are granted operating system authentication for the set of database system privileges each group authorizes. Oracle recommends that you use different operating system groups for each set of system privileges.

4.1.5.2 Oracle Software Owner For Each Oracle Software Product

You can create a single user (for example, oracle ) to own both Oracle Database, and Oracle Grid Infrastructure for a standalone server installations. However, Oracle recommends that you create one software owner to own each Oracle software installation typically, oracle , for the database software and grid for the Oracle Restart owner user.

You must create at least one software owner the first time you install Oracle software on the system.

In Oracle documentation, a user created to own only Oracle Grid Infrastructure software installations is called the grid user. A user created to own either all Oracle installations, or only Oracle database installations, is called the oracle user.

4.1.5.3 Standard Oracle Database Groups for Job Role Separation for Oracle Database

The following is a list of standard Oracle Database groups. These groups provide operating system authentication for database administration system privileges:

All these groups are automatically created as a part of Oracle Database installation on Windows.

The OSDBA group ( ORA_DBA )

Use this group the first time you install Oracle Database software on the system. This group identifies operating system user accounts that have database administrative privileges the SYSDBA privilege for all database instances running on the server.

Members of the ORA_DBA group do not have SYSASM privileges on Oracle ASM instances, which are needed for mounting and dismounting disk groups.

The OSOPER group for Oracle Database ( ORA_OPER )

Use this group if you want a separate group of operating system users to have a limited set of database administrative privileges for starting up and shutting down the database (the SYSOPER privilege).

The OSDBA group for a particular Oracle home ( ORA_ HOMENAME _DBA )

This group is created the first time you install Oracle Database software into a new Oracle home. This group identifies operating system user accounts that have database administrative privileges (the SYSDBA privilege) for the database instances that run from that Oracle home.

The OSOPER group for a particular Oracle home ( ORA_ HOMENAME _OPER )

Use this group if you want a separate group of operating system users to have a limited set of database administrative privileges for starting up and shutting down the database instances that run from a particular Oracle home (the SYSOPER privilege).

4.1.5.4 Extended Oracle Database Groups for Job Role Separation

In addition to the SYSOPER privilege to start up and shut down the database, you can create new administrative privileges that are more task-specific and less privileged than the ORA_DBA /SYSDBA system privileges to support specific administrative privileges tasks required for everyday database operation. Users granted these system privileges are also authenticated through operating system group membership.

During installation, you are prompted to provide operating system groups whose members are granted access to these system privileges. You can assign the same group to provide authentication for these privileges for example, ORA_DBA , but Oracle recommends that you provide a unique group to designate each privilege.

The OSDBA subset job role separation privileges and groups consist of the following:

The OSBACKUPDBA group for Oracle Database ( ORA_ HOMENAME _SYSBACKUP )

Use this group if you want a separate group of operating system users to have a limited set of database backup and recovery related administrative privileges, the SYSBACKUP privilege.

The OSDGDBA group for Oracle Data Guard ( ORA_ HOMENAME _SYSDG )

Use this group if you want a separate group of operating system users to have a limited set of privileges to administer and monitor Oracle Data Guard, the SYSDG privilege.

The OSKMDBA group for encryption key management ( ORA_ HOMENAME _SYSKM )

Use this group if you want a separate group of operating system users to have a limited set of privileges for encryption key management such as Oracle Wallet Manager management, the SYSKM privilege.

All these groups, ORA_ HOMENAME _SYSBACKUP , ORA_ HOMENAME _SYSDG , and ORA_ HOMENAME _SYSKM , are applicable only to the database instances running from that particular Oracle home.

4.1.5.5 Oracle Automatic Storage Management Groups for Job Role Separation

Create the following operating system groups if you are installing Oracle Grid Infrastructure:

The OSDBA group for Oracle ASM ( ORA_ASMDBA)

This group grants access for the database to connect to Oracle ASM. During installation, the Oracle Installation Users are configured as members of this group. After you create an Oracle Database, this group contains the Oracle Home Users of those database homes. Any client of Oracle ASM that needs to access storage managed by Oracle ASM needs to be in this group.

The OSASM group for Oracle ASM Administration ( ORA_ASMADMIN )

Use this separate group to have separate administration privilege groups for Oracle ASM and Oracle Database administrators. Members of this group are granted the SYSASM system privilege to administer Oracle ASM. In Oracle documentation, the operating system group whose members are granted privileges is called the OSASM group. During installation, the Oracle Installation User for Oracle Grid Infrastructure and Oracle Database Service IDs are configured as members of this group. Membership in this group also grants database access to the Oracle ASM disks.

Members of the OSASM group can use SQL to connect to an Oracle ASM instance as SYSASM using operating system authentication. The SYSASM privilege permits mounting and dismounting disk groups, and other storage administration tasks. SYSASM system privileges do not grant access privileges on an Oracle Database instance.

The OSOPER group for Oracle ASM ( ORA_ASMOPER )

This is an optional group. Create this group if you want a separate group of operating system users to have a limited set of Oracle ASM instance administrative privileges, the SYSOPER for ASM privilege, including starting up and stopping the Oracle ASM instance. By default, members of the OSASM group also have all privileges granted by the SYSOPER for ASM privilege.

To use the Oracle ASM Operator group to create an Oracle ASM administrator with fewer privileges than those granted by the SYSASM system privilege, you must assign the user to this group after installation.

Oracle Database Administrator’s Guide

Oracle Database Security Guide

4.2 Stopping Existing Oracle Services

If you are installing additional Oracle Database 12 c products in an existing Oracle home, then stop all processes, including the listener and database, running in the Oracle home. You cannot install into an existing Oracle home other than 12 c . You must complete this task to enable Oracle Universal Installer to relink certain executables and libraries.

Consider the following before you install Oracle Grid Infrastructure for a standalone server or Oracle Database:

If you plan to use Oracle Restart, then you must install the Oracle Grid Infrastructure for a standalone server before you install and create the database. When you perform a database installation, the database must use the same listener created during the Oracle Grid Infrastructure for a standalone server installation, thereafter you do not have to perform the steps listed in this section.

The default listener and any additional listeners must run from the Oracle Grid Infrastructure home.

If you have an existing Oracle Database 12 c running on Oracle ASM, then stop any existing Oracle ASM instances. After you finish installing Oracle Grid Infrastructure for a standalone server, start the Oracle ASM instance again.

If you choose to create a database during the installation, then most installation types configure and start a default Oracle Net listener using TCP/IP port 1521 and the IPC key value EXTPROC . However, if an existing Oracle Net listener process is using the same port or key value, Oracle Universal Installer looks for the next available port (for example, 1522 ) and configures and starts the new listener on this available port.

4.3 Configuring User Accounts

During installation, you can specify an Oracle Home User. Before starting the installation, there are a few checks you must perform for the Oracle Installation users, to ensure the installation succeeds.

This section contains the following topics:

4.3.1 Configuring Environment Variables for the Software Installation Owner

Before starting the Oracle Database installation, ensure that the TEMP environment variable is set correctly. See «Hard Disk Space Requirements» for more information.

4.3.2 Managing User Accounts with User Account Control

To ensure that only trusted applications run on your computer, the Windows operating systems supported for Oracle Database provide User Account Control. If you have enabled this security feature, then, depending on how you have configured it, Oracle Universal Installer prompts you for either your consent or your credentials when installing Oracle Database. Provide either the consent or your Windows Administrator credentials as appropriate.

You must have Administrator privileges to run some Oracle tools, such as Database Configuration Assistant, Net Configuration Assistant, and OPatch, or to run any tool or application that writes to any directory within the Oracle home. If User Account Control is enabled, and you are logged in as the local Administrator, then you can successfully run each of these commands in the usual way. However, if you are logged in as «a member of the Administrator group,» then you must explicitly start these tasks with Windows Administrator privileges. All the Oracle shortcuts that require Administrator privileges start as «Administrator» automatically when you click the shortcuts. However, if you run the above tools from a Windows command prompt, you must run them from an Administrator command prompt. OPatch does not have a shortcut and has to be run from an Administrator command prompt.

To start a command prompt window with Windows Administrator privileges:

On your desktop, create a shortcut for the command prompt window. An icon for that shortcut appears on the desktop.

Right-click the icon for the newly created shortcut, and specify Run as administrator .

When you open this window, the title bar reads Administrator: Command Prompt. Commands run from within this window are run with Administrator privileges.

Operating System Group Name	Related System Privilege	Description