Which Windows user is MANDATORY (or suggested) to use when installing Oracle patches? [message #483547] |
Mon, 22 November 2010 14:30 |
mkounalis
Messages: 147 Registered: October 2009 Location: Dallas, TX
|
Senior Member |
|
|
We have almost 400 production two-node RAC clusters in the environment I help manage - all these sites have databases where the database name is exactly the same, so using Grid Control right now isn't in the cards (and yes - I am working on assigning them all a unique name ). We want to use IBM's BIGFIX to deploy patch 32 on top of 10.2.0.3 for Windows Itanium. BigFix runs as a user different from that used to install the Oracle software originally. There is nothing in the patch notes to suggest that you must use a certain Windows user to install the patch - so the question is, does it matter what Windows User I use as long as they are an 'Administrator' equivalent?
Another question to ask you fine folks is how do you perform mass updates/patches in your Windows server environments? I am looking for examples outside of Grid Control - which I know would work if only my predecessor didn't name these databases the same .
Thanks all for you replies!
[Updated on: Mon, 22 November 2010 14:31] Report message to a moderator
|
|
|
Re: Which Windows user is MANDATORY (or suggested) to use when installing Oracle patches? [message #483550 is a reply to message #483547] |
Mon, 22 November 2010 15:39 |
John Watson
Messages: 8963 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
Hi - I can't make any suggestions on how to roll out patches in a large Windows environment without Grid Control, but I can say that Grid control has no problem with many databases having the same name. The target names within Grid Control will be different, but the target name does not have to be the same as the database name - so, no problem. You can even register the same database twice, which is a bit silly.
|
|
|
Re: Which Windows user is MANDATORY (or suggested) to use when installing Oracle patches? [message #483553 is a reply to message #483550] |
Mon, 22 November 2010 17:33 |
mkounalis
Messages: 147 Registered: October 2009 Location: Dallas, TX
|
Senior Member |
|
|
John - I tried your approach with Oracle's PM helping me, and what you describe does not seem to be the case. One thing I didn't mention above is that the DBID is the same for all systems because of how the systems were deployed - and that might be the cause of it. We tried for over a month to find a workaround, only to be told that the only way to solve our issue was to uniquely name the database instances. The target names discovered by the agents were all the same coming in to the Grid Control database, so I am not sure how the target could be changed - but I am not a Grid Control expert. If you have a document you can refer me to, I will take another look. Thanks for the reply!
[Updated on: Mon, 22 November 2010 17:33] Report message to a moderator
|
|
|
Re: Which Windows user is MANDATORY (or suggested) to use when installing Oracle patches? [message #483568 is a reply to message #483553] |
Tue, 23 November 2010 01:50 |
John Watson
Messages: 8963 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
I've just done it, as a test. Perhaps the problem is the automatic discovery? If you do it manually, you have to choose the target name. DBID is definitely not a problem, or it couldn't handle physical standbys. Doing it manually for 400 DBs would be silly, but you can script it with emcli. Have you got thet setup? Here's the relevant help:
Examples:
emcli add_target
-name="database"
-type="oracle_database"
-host="myhost.us.oracle.com"
-credentials="UserName:dbsnmp;password:dbsnmp;Role:Normal"
-properties="SID:semcli;Port:15091;OracleHome:/oracle;MachineName:smpamp-sun1.us.oracle.com"
-groups="Group1:group;Group2:group"
Add an oracle_database target with name "database". Take notice
of the way the credentials are specified. The "name"s in those
name-value pairs come from the oracle_database metadata file.
They must appear exactly as they are named in that file (the same
goes for the property "name"s). This example uses the base minimum
of required credentials and properties for the database target.
|
|
|
|
|
|