Thursday, January 27, 2011

Enterprise Manager Creating Oracle Data Guard Standby for 11.2 Database with Grid user role separation

We recently had a LinkedIn discussion in which one of my friends had written:

We went down the role separation path with a grid user for storage/cluster admin that we were going to handover to our unix team and the oracle user for normal DB admin.....It turns out our Unix admins didn't want anything to do with managing ASM or GI so we'd have been better staying with it all under the oracle account. The role separation does cause it's fair share of issues. The listener being owned by the grid user is a particular problem as the oracle user can no longer reconfigure/restart the listener. This breaks a lot of the OEM provisioning functionality and causes problems when attempting to create standby databases...... a lot of manaul work arounds are needed to resolve.

My response to this was:

What he said about "Keep it simple" is right - that principle applies in any case. However just want to clarify on the issue mentioned. A little later after the comment was made, this issue was investigated further in his "My Oracle Support" SR and it was found it was a listener.ora file parsing issue - some spaces were missing in the sid_list_listener entry in the listener.ora file probably because the entry had been manually made. The person concerned himself found this out and fixed the issue. When the extra spaces were added in this line, the file parsed ok. So, there were no real issues with the EM11g Create Data Guard Standby database wizard which he was talking about (this is actually separate from EM11g Provisioning procedures). The EM Create Data Guard Standby database wizard works ok even with role separation with a grid user for the Grid Infrastructure home.

5 comments:

Anonymous said...

Just as I started installing 12c cloud control agents on my RAC clusters installed with role separation I encountered the question - install it as grid or oracle. Nothing in the docs nor many hits on google. Wondering what your thoughts are on it since you seem to have worked on the subject of role separation.

Porus Homi Havewala (પોરસ હોમી હવેવાલા) said...

Based on my personal preference, I would say install the 12c Cloud Control agent as oracle.

Sriram J said...

I appreciate your quick response.

So how does agent get access to OS resources like cluvfy command, database, asm and gi logs. It was straight forward without role separation. Now with role separation does the agent just use its setuid root to get to these resources as root - I hope oracle did not do that - sys admins & security folks will go "I told you we could not trust you with setuid root"? Or does it require OS credentials to be entered for database, ASM, and cluster monitoring?

Porus Homi Havewala (પોરસ હોમી હવેવાલા) said...
This comment has been removed by the author.
Porus Homi Havewala (પોરસ હોમી હવેવાલા) said...

I have checked back on this. The General recommendation is that the agent user is in the same GROUP as install user. Monitoring doesn't require root privileges. EM prompts for root privileges where required for admin operations.

Disclaimer

Opinions expressed in this blog are entirely the opinions of the writers of this blog, and do not reflect the position of Oracle corporation. No responsiblity will be taken for any resulting effects if any of the instructions or notes in the blog are followed. It is at the reader's own risk and liability.

Blog Archive