Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
General
cancel
Showing results for 
Search instead for 
Did you mean: 

Multiple Oracle Environments - Concurrent Manager

Chris Maehara
Occasional Advisor

Multiple Oracle Environments - Concurrent Manager

Am currently running several Oracle Environments on a single server with many Concurrent Manager processes all with the same Oracle uid. Is there any way to distinguish which Concurrent Managers belong to which Oracle Environment? This would help in setting up ServiceGuard to monitor the Concurrent Manager process, and eventually backups and MWA.

Thanks
8 REPLIES

Re: Multiple Oracle Environments - Concurrent Manager

Hi Chris,

Before supplying a script as an answer, I would like to know if the user-id of the concurrent managers is different for every database.

example: concurrent manager (conman)
oracle database (oraofi)


With regards,
Dieter Degrendele
Dieter@Work
Devbinder Singh Marway
Valued Contributor

Re: Multiple Oracle Environments - Concurrent Manager

You can try , creating a unix user same as your database name , and whent starting up concurrent manager , set up the oracle sid and other environment, and depending on what the SID is do an su

e.g. if dbase is DEV ( nb:- DEV is also a unix user created)
set sid up and other environment
if sid is DEV then su DEV -c startmgr ARGUMENTS e.g. ( ArGUMENTS depending on dbase
DEV i.e sysmgr="apps/fnd

so su DEV -c startmgr sysmgr="apps/fnd"

so when you do a ps -ef | grep DEV you can tell these processes are for the DEV databases

just a thought , HTP
just a thought
Seek and you shall find
Steve Slade
Frequent Advisor

Re: Multiple Oracle Environments - Concurrent Manager

Chris,

Based on the exposure I have had to oracle databases, (which is pretty low), Oracle appends the database identifier to the end of the database management processes.

Therefore if your database identifier was abc, something along the lines of :

ps -ef | grep ora_ | grep abc

will show all the database management processes for that database instance.

Did that answer the question - I have forgotten?
If at first you do not succeed. Destroy all evidence that you even attempted.
Rick Garland
Honored Contributor

Re: Multiple Oracle Environments - Concurrent Manager

The oracle instance will be appended to the process name. Example, if you do ps -fu oracle, you will see all processes owned by oracle and the processes will be specified by the database instance
Chris Maehara
Occasional Advisor

Re: Multiple Oracle Environments - Concurrent Manager

Thanks for all the responses. Unfortunately, all the Concurrent Managers are running under the same uid. In order for MWA to track the process, the first entry in the process has to be unique. Still need help.
Rick Garland
Honored Contributor

Re: Multiple Oracle Environments - Concurrent Manager

From what you are stating, all oracle instances were setup with the same user.
You will need to specify the UID in order to get some of the stats you are looking for.

To get unique UIDs for the managers, the oracle setup would have to be changed.
Steve Slade
Frequent Advisor

Re: Multiple Oracle Environments - Concurrent Manager

Chris,

It sounds like you need to have multiple dba unix userids, each with responsiblity
for starting/stopping its own database.

This is quite easy to do - any unix user in the unix group dba automatically is assumed to be a dba userid by oracle.

All you need to do ensure that for each userid, the environment variable ORACLE_SID reflects the required database identifier - all other parms can match your existing dba userid.
If at first you do not succeed. Destroy all evidence that you even attempted.
Sandro Schaer
Occasional Advisor

Re: Multiple Oracle Environments - Concurrent Manager

hi there

we just had similar problems. we are running 18 identical applications each with it's own oracle instance. so we created 18 unix users and defined the ORACLE_SID and the Oracle relevant PATH's in the users profile. to have the necessary rights to start/stop an instance all this users belong to the oracle dba group. if your're interested i wrote a daemon which is taking care of all instances and listeners on your system. even failover in combination with serviceguard is supported...

C U
unix and oracle administrator