Re: relink OMS oracle home

  • From: Tony van Lingen <tony_vanlingen@xxxxxxxxxxxxxxxxxxxxx>
  • To: Joel.Patterson@xxxxxxxxxxx
  • Date: Fri, 22 Jan 2010 14:01:39 +1000

Joel,

None of my installations (DB or IAS) has an ins_emagent.mk file. The relink scripts all do "$MAKE -f $ORACLE_HOME/sysman/lib/ins_sysman.mk install". On the box where I looked $MAKE is /usr/bin/make and $ORACLE_HOME is taken from the environment. there is an agent target in ins_sysman.mk, which is included in the install target, together with some supporting libraries.

Cheers,
Tony
Around 21/01/2010 11:52 PM, Joel.Patterson@xxxxxxxxxxx said:

Thank you Tony. I do wonder if 'oemagent' isn't the same as my make command below? In other words isn't that the same as the 'AGENT' home? I have an AGENT ORACLE_HOME on every server, but I only have one OMS [IAS] ORACLE_HOME on one server.

This is for the sysadmin to do so I don't have to 'wake up' for this. J relink all leads to a lot of failure messages ... e.g. rdbms doesn't exist in agent home, Sqlplus doesn't exist etc.

It is recommended to relink even with solaris upgrade, but your probably right it might work without doing so... OEM is still working and I haven't relinked it yet.

I was suggesting "relink all" for every oracle home... but he would never know which errors are legit. For simplicity I could just leave it at that, but my DBA side wants to know the 'real way'.

Joel Patterson
Database Administrator
904 727-2546

* From: * Tony van Lingen [mailto:tony_vanlingen@xxxxxxxxxxxxxxxxxxxxx]
* Sent: * Wednesday, January 20, 2010 5:44 PM
* To: * Patterson, Joel
* Cc: * oracle-l@xxxxxxxxxxxxx
* Subject: * Re: relink OMS oracle home

Joel,

From the header comments in $ORACLE_HOME/bin/relink on a Solaris 10 box it appears that either 'relink all' or 'relink oemagent' should do it. This is from a 10gR2 home:

#    DESCRIPTION
#      performs manual relinking of Oracle product executables based
#      on what has been installed in the ORACLE_HOME.
#      script calls appropriate makefile targets for the following
#      accepted script parameters:
#        all -- everything which has been installed
#        oracle -- oracle database executable only
#        network -- net_client, net_server, cman, names
#        client -- net_client, plsql
#        client_sharedlib
#        interMedia -- ctx
#        ctx --Oracle Text Utilities
#        precomp -- all precompilers which have been installed
#        utilities -- utilities and sqlplus
#        oemagent -- oemagent
#        ldap -- ldap/oid executables
#

On our installations sysman is in the same OH as the database, but then we don't run grid..

As an aside, I didn't think you'd have to relink as Solaris should be upgradeable without breaking the ABI, at least between Solaris 8, 9 and 10?

Cheers,
Tony

Around 21/01/2010 5:48 AM, Joel.Patterson@xxxxxxxxxxx <mailto:Joel.Patterson@xxxxxxxxxxx> said:

I can use Relink all for Database Homes.

For agent homes, I can use, not sure about relink all:

   cd <$AGENT_ORACLE_HOME>/sysman/lib

   make -f ins_emagent.mk agent

for agent homes.

What do I use for OMS ORACLE_HOME or what do you use? I've googled and searched MOS, but don't wish to create an SR for this.

(Upgrading solaris OS to newer version on Sparc).

Other related posts: