RE: DB12c in Production?
- From: "Ruel, Chris" <Chris.Ruel@xxxxxxx>
- To: "oracledbaquestions@xxxxxxxxx" <oracledbaquestions@xxxxxxxxx>, ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 16 Jun 2014 15:57:13 +0000
I don’t think that today there is a physical/technical reason to have separate
owners. In my experience, there are a few reasons I have seen this done.
Mostly commonly, it is for some sort of separation of duty. For example, you
could have storage admins whom manage your ASM or SysAdmins that manage the
clusterware (less common). However, if you do go down this path, you also have
to make sure that “oracle/RDBMS” and “grid/clusterware” are grouped accordingly
as well else both user can pretty much do the same things anyway. I have also
seen it as an organizational tactic for your software such as naming your RDBMS
software owners like “oracle10g” or “oracle11g” but that is another topic
altogether.
Even if you do separate your users (as we do), you can still add the
$GRID_HOME/bin to your oracle user $PATH...just might make sure that
$ORACLE_HOME/bin (rdbms) comes before $GRID_HOME/bin for the RDBMS account.
This would allow you to find and run certain clusterware related binaries that
might make managing from two accounts easier. There could some caveats to this
such as certain binaries may not work properly so use at your own discretion.
Chris..
Chris Ruel * Oracle Database Administrator
cruel@xxxxxxx<mailto:cruel@xxxxxxx> * Desk:317.759.2172 * Cell 317.523.8482
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Dba DBA
Sent: Monday, June 16, 2014 11:40 AM
To: ORACLE-L
Subject: Re: DB12c in Production?
Chris,
yeah separate users. I set it up with a grid/oracle users because oracle
recommends it. I find that its actually a little more work to swap between
users when I need to look at things. My hunch is that this is a direction
oracle is going in and it will be more necessary with future releases.
On Mon, Jun 16, 2014 at 11:31 AM, Ruel, Chris
<Chris.Ruel@xxxxxxx<mailto:Chris.Ruel@xxxxxxx>> wrote:
Are you talking about separate users? i.e grid for GI/clusterware and oracle
for RDBMS? The GI/clusterware has needed a separate home as far back as I can
remember.
Prior to 11gR2, you could share the same home for ASM/RDBMS but that stopped
with 11gR2 with the integration of ASM with the GI.
Chris..
Chris Ruel * Oracle Database Administrator
cruel@xxxxxxx<mailto:cruel@xxxxxxx> * Desk:317.759.2172<tel:317.759.2172> *
Cell 317.523.8482<tel:317.523.8482>
From: oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>
[mailto:oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>] On
Behalf Of Dba DBA
Sent: Monday, June 16, 2014 11:26 AM
To: ORACLE-L
Subject: Re: DB12c in Production?
Slightly off topic, but related question... In 11g Oracle started recommended
that we have a separate Grid and Oracle Home. In 11g, I didn't see a good
reason to do this. Seemed like extra cluster. Oracle often makes changes like
this as part of a phased in change in later releases.
I am wondering if people see more use for the grid home in 12c? Might work
better with the pluggable DB option.
I admitted have not spent a lot of time looking at 12c. I don't expect to use
it at all for atleast 1-2 years minimum.
On Fri, Jun 6, 2014 at 9:29 AM, Hans Forbrich
<fuzzy.graybeard@xxxxxxxxx<mailto:fuzzy.graybeard@xxxxxxxxx>> wrote:
On 06/06/2014 6:49 AM, Mark W. Farnham wrote:
A single PDB in a multi-tenant architecture does not invoke the multi-tenant
upcharge in any license documentation I have seen. IF it did, I think all of
Niall’s concerns would be valid.
I concur. (With this as well as the rest of your post. Except about Ed ... no
personal experience so I can not comment. ;-) )
They should rewrite it to say "Multi-tenant Architecture is part of Oracle
Database 12c. The option is for Multiple Pluggable User Databases (more than
one) in one Container."
(I keep insisting on the term User Databases or User PDB, because the
architecture requires a Root and a Seed PDB that you can not touch.)
/Hans
Notice of Confidentiality: **This E-mail and any of its attachments may contain
Lincoln National Corporation proprietary information, which is privileged,
confidential,
or subject to copyright belonging to the Lincoln National Corporation family of
companies. This E-mail is intended solely for the use of the individual or
entity to
which it is addressed. If you are not the intended recipient of this E-mail,
you are
hereby notified that any dissemination, distribution, copying, or action taken
in
relation to the contents of and attachments to this E-mail is strictly
prohibited
and may be unlawful. If you have received this E-mail in error, please notify
the
sender immediately and permanently delete the original and any copy of this
E-mail
and any printout. Thank You.**
Notice of Confidentiality: **This E-mail and any of its attachments may contain
Lincoln National Corporation proprietary information, which is privileged,
confidential,
or subject to copyright belonging to the Lincoln National Corporation family of
companies. This E-mail is intended solely for the use of the individual or
entity to
which it is addressed. If you are not the intended recipient of this E-mail,
you are
hereby notified that any dissemination, distribution, copying, or action taken
in
relation to the contents of and attachments to this E-mail is strictly
prohibited
and may be unlawful. If you have received this E-mail in error, please notify
the
sender immediately and permanently delete the original and any copy of this
E-mail
and any printout. Thank You.**
Other related posts:
