FAQ
Folks

CASE 1

Qs 1 If "oinstall" is the primary group of the Oracle Owner i.e. all the
10gR2 Oracle software binaries are owned by "oinstall" group, then what
is the use of the "dba" group in RAC?

Qs 2 Is "dba" a reserved word and does any Unix user belonging to this
group automatically have "DBA" role grants/privileges in 10gR2 / Solaris
10?

Qs 3 Is it advisable to use "oinstall" as the primary group of the
ORACLE Owner in place of "dba" as advised in the Oracle Manuals for 10g
RAC setup?

From the Oracle Manual:-

To create the oracle user, enter a command similar to the following:

# /usr/sbin/useradd -u 200 -g oinstall -G dba[,oper] oracle

In the preceding command:

The -u option specifies the user ID. Using this command flag
is optional, as you can allow the system to provide you with an
automatically generated user ID number. However, you must make note of
the oracle user ID number, as you require it later during
pre-installation.

The -g option specifies the primary group, which must be the
Oracle Inventory group--for example, oinstall

The -G option specifies the secondary groups, which must
include the OSDBA group, and, if required, the OSOPER group. For
example: dba, or dba,oper

CASE 2

Qs 1 - If Oracle 10gR2 Binaries (NON-RAC type installation) already
exists on the Machine, in Order to do a NEW RAC setup using the Same
machine as 1 of the nodes, is it advisable to again install respective
RAC type Oracle 10gR2 Binaries into another ORACLE_HOME path?

If YES, should any changes me made to the /var/opt/oracle/oraInst.loc
file to prevent the NEW Oracle RAC Binaries installation from knowing
about the previous NON-RAC Oracle installation?

/var/opt/oracle/oraInst.loc Contents:-

inventory_loc=/oracle/ora10gr2/oraInventory

inst_group=dba

Thanks indeed

CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

Search Discussions

  • VIVEK_SHARMA at Nov 21, 2006 at 12:00 pm
    Folks

    CASE 1

    Qs 1 If "oinstall" is the primary group of the Oracle Owner i.e. all the
    10gR2 Oracle software binaries are owned by "oinstall" group, then what
    is the use of the "dba" group in RAC?

    Qs 2 Is "dba" a reserved word and does any Unix user belonging to this
    group automatically have "DBA" role grants/privileges in 10gR2 / Solaris
    10?

    Qs 3 Is it advisable to use "oinstall" as the primary group of the
    ORACLE Owner in place of "dba" as advised in the Oracle Manuals for 10g
    RAC setup?

    From the Oracle Manual:-

    To create the oracle user, enter a command similar to the following:

    # /usr/sbin/useradd -u 200 -g oinstall -G dba[,oper] oracle

    NOTE-

    The -u option specifies the user ID.

    The -g option specifies the primary group, which
    must be the Oracle Inventory group--for example, oinstall

    The -G option specifies the secondary groups,
    which must include the OSDBA group, and, if required, the OSOPER group.
    For example: dba, or dba,oper

    CASE 2

    Qs 1 - If Oracle 10gR2 Binaries (NON-RAC type installation) already
    exists on the Machine, in Order to do a NEW RAC setup using the Same
    machine as 1 of the nodes, is it advisable to again install respective
    RAC type Oracle 10gR2 Binaries into another ORACLE_HOME path?

    If YES, should any changes me made to the /var/opt/oracle/oraInst.loc
    file to prevent the NEW Oracle RAC Binaries installation from knowing
    about the previous existing NON-RAC Oracle installation?

    /var/opt/oracle/oraInst.loc Contents:-

    inventory_loc=/oracle/ora10gr2/oraInventory

    inst_group=dba

    Thanks indeed

    CAUTION - Disclaimer *****************
    This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
    ***INFOSYS******** End of Disclaimer ********INFOSYS***

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouporacle-l @
categoriesoracle
postedNov 21, '06 at 11:55a
activeNov 21, '06 at 12:00p
posts2
users1
websiteoracle.com

1 user in discussion

VIVEK_SHARMA: 2 posts

People

Translate

site design / logo © 2022 Grokbase