molecular operating environment installation directory

Molecular Operating Environment Ation Directory Software Owners Require

The SYSASM privileges permit mounting and dismounting of disk groups, and other storage administration tasks.

To simplify using the defaults for Oracle tools the group name should be oinstall.

However, if you use one group to provide operating system authentication for all system privileges, then this group must be the primary group for all users to whom you want to grant administrative system privileges.

Members of this group have write privileges to the Oracle central inventory ( oraInventory ) directory, and are also granted permissions for various Oracle Restart resources and directories in the Oracle Restart home to which DBAs need write access, and other necessary privileges.

In Oracle documentation, this group is represented as oinstall in code examples.

See Creating the Oracle Inventory Group If an Oracle Inventory Does Not Exist.

Molecular Operating Environment Ation Directory Software Owners Require

Oracle software owners require membership to the OSDBA group of the Oracle Grid infrastructure home so that database instances can log on to Oracle ASM.

Oracle recommends that you do not have more than one central inventory for Oracle installations.

If an Oracle software owner has a different central inventory group, then you may corrupt the central inventory.

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).

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.

This group identifies operating system user accounts that have database administrative privileges (the SYSDBA privilege).

Create 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).

This group cannot directly connect as SYSOPER, unless explicitly granted.

However, they have the privileges granted by the SYSOPER privilege.

By default, members of the OSDBA group have all privileges granted by the SYSOPER privilege.

Users granted these system privileges are also authenticated through operating system group membership.

You can assign the same group to provide authentication for these privileges, but Oracle recommends that you provide a unique group to designate each privilege.

Membership in the OSDBA group enables access to the files managed by Oracle ASM.

If you have a separate OSDBA group for Oracle ASM, then the Oracle Restart software owner must be a member of the OSDBA group for each database and the OSDBA group for Oracle ASM.

Members of this group are granted the SYSASM system privileges to administer Oracle ASM.

In Oracle documentation, the operating system group whose members are granted SYSASM privileges is called the OSASM group, and in command lines, is referred to as asmadmin.

If you have multiple databases on your system, and use multiple OSDBA groups so that you can provide separate SYSDBA privileges for each database, then you should create a group whose members are granted the OSASMSYSASM administrative privileges, and create a grid infrastructure user ( grid ) that does not own a database installation, so that you separate Oracle Grid Infrastructure SYSASM administrative privileges from a database administrative privileges group.

Molecular Operating Environment Installation Directory