Which two Operating System users and groups must be created on each node before installing Oracle Grid Infrastructure 12c?
A.
an O/S user to own the Clusterware installation and a different O/S user to own the Automatic Storage Management (ASM) installation
B.
an O/S group to own the software inventory
C.
an O/S user to own the Oracle Database installation
D.
an O/S group called dba
E.
a group to own the ASMLIB-provisioned storage
F.
a group to own Automatic-Storage Management (ASM) Filter Driver-provisioned storage
Explanation:
B: Creating the Oracle Inventory Group If an Oracle Inventory Does Not Exist
If the oraInst.loc file does not exist, then create the Oracle Inventory group by entering a command similar to the following:
# /usr/sbin/groupadd -g 54321 oinstall
The preceding command creates the oraInventory group oinstall, with the group ID number 54321. Members of the oraInventory group are granted privileges to
write to the Oracle central inventory (oraInventory), and other system privileges for Oracle installation owner users.
D: Oracle recommends that you create one software owner to own each Oracle software product (typically, oracle, for the database software owner user, and grid
for Oracle Grid Infrastructure).
Incorrect Answers:
A: During an Oracle Grid Infrastructure installation, both Oracle Clusterware and Oracle Automatic Storage Management (Oracle ASM) are installed. You no longer
can have separate Oracle Clusterware installation owners and Oracle ASM installation owners.
https://docs.oracle.com/database/121/CWLIN/usrgrps.htm#CWLIN179
Create an Oracle Software inventory group on each node.
An operating system group needs to be created that will be associated with Oracle Central Inventory (oraInventory). oraInventory contains a registry of the Oracle home
directories from all Oracle products installed on the server. It is designed to be shared among many products. It also contains installation log files and trace files from the installation programs. The suggested name for the operating system group is oinstall. In a cluster installation, it is very important that the group ID be the same on all nodes of the cluster.
An operating system user needs to be created to own the Oracle Clusterware installation.Traditionally, all Oracle products installed on the same machine such as clusterware,databases, disk management, and enterprise management tools are owned by the same user called oracle. It is possible for each product to be created under a different operating system account. This may be desired if different job responsibilities are used to manage different components. It is very important that the user ID be the same on all nodes of the cluster.
It is required that the Oracle Clusterware software owner and the Oracle Database software owner have the same primary group as the Oracle Inventory group.
I think B,C CORRECT
Wrong: “A”, “D”
“E” and “F” ???
The question “C” is not so precise or true, the question is about the GI, not about DB
C is wrong because we are doing the installation of Grid. We dont need a db installation owner.
A is wrong because it is the same OS user for both
D is also wrong. The group is OSASM. This can be dba if for example a user oracle owned both grid and db installations or asmdba for user grid though i think the name realy doesnt matter
F doesnt really require a special group.
E I would say is correct. You create the Disks as root but after installation of Grid one of the OS user groups such as asmadmin becomes the group to administer the disks
I would say the answer therefore is B and E
ASMLIB is not mandatory to install GI.
A group diferent from OINSTALL should be created to own the storage.
I will go with B and F
Nelz, i think that you are right!
Now that you said… it make sense to me!
Not necessarily the group created to manage the disks will be used by the administrative accounts of the DB, and when you install ASMLib (if necessary to do so), you specify which group will be the owner of the disks, like in the next command, where you put the “grid owner” and the “group”, like “grid” and “asmadmin”:
[root@ca-test1 /]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets (‘[]’). Hitting without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface []: grid
Default group to own the driver interface []: asmadmin
Start Oracle ASM library driver on boot (y/n) [n]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration [ OK ]
Creating /dev/oracleasm mount point [ OK ]
Loading module “oracleasm” [ OK ]
Mounting ASMlib driver filesystem [ OK ]
Scanning system for ASM disks [ OK ]