One Important note from the 10.2.0.5 patch Release notes:
As part of the upgrade of a Grid Control installation from 10.2.x.x to 10.2.0.3 or higher, you must download and install Clone Support Files from My Oracle Support and install the files onto each OMS as part of a post-patch configuration task to enable clone support for Oracle Tech stack components.
This step can often be overlooked and will result in issues for the cloning and provisioning subsystems.
Sir Grid Guy.
ReplyDeleteI came to your site after googling around . I hope I have come at the right spot.
My introduction jokingly The most Unhappy OEM GRID control guy.
If hope you can make me happy.
I am doing a fresh install of Oracle Enterprise manager on
Linux 32 bit using OLE5.3
using
How to Install Grid Control 10.2.0.5.0 on Enterprise Linux 5 Using
the
Existing Database (11g) Option
Doc ID: 784963.1
As per the Metalink note I have 11.1.0.7 DB installed and doing OEM install using existing Database .I am doing software only install of 10.2.0.1 oem
and then 10.2.0.5 oem with no config.
Then I manually run the following last step
ConfigureGC.pl script: where I get this error
.../oms10g/perl/bin/perl .../oms10g/sysman/install/ConfigureGC.pl
/u01/app/gc
Any ideas/suggestions to solve this ? This is not related to sys/
sysman password I think
Oc4jDeploy tool completed, but with errors.
'
INFO: oracle.sysman.top.oms:PerformSecureCommand:runCmd:Command
Output
stderr:
'java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at oracle.j2ee.tools.deploy.Oc4jDeploy.doDeploy(Unknown
Source)
at oracle.j2ee.tools.deploy.Oc4jDeploy.execute(Unknown
Source)
at oracle.j2ee.tools.deploy.Oc4jDeploy.deploy(Unknown Source)
at oracle.j2ee.tools.deploy.Oc4jDeploy.main(Unknown Source)
Caused by: java.lang.NoClassDefFoundError
at
com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_
SERVER
(RMIConnection.java:1634)
at com.evermind.server.rmi.RMIConnection.invokeMethod
(RMIConnection.java:1585)
at com.evermind.server.rmi.RemoteInvocationHandler.invoke
(RemoteInvocationHandler.java:55)
at
com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke
(RecoverableRemoteInvocationHandler.java:23)
at __Proxy0.bindWebApp(Unknown Source)
at com.evermind.client.orion.BindWebAppCommand.execute
(BindWebAppCommand.java:28)
at com.evermind.client.orion.Oc4jAdminConsole.executeCommand
(Oc4jAdminConsole.java:139)
... 8 more
Died at /u01/app/oracle/product/10.2.0/oms10g/sysman/install/
emdeploy.pl line 154.
'
INFO: oracle.sysman.top.oms:OmsPlugIn:Requested Configuration Step 1
have been completed with status=false
INFO: oracle.sysman.top.oms:EmcpPlug:invoke:Completed EmcpPlug invoke
method on an aggregate=oracle.sysman.top.oms for Action=configuration
in step=2:microstep=0
INFO: oracle.sysman.top.oms:The plug-in OMS Configuration has failed
its perform method
INFO: Cfm.save() was called
INFO: Cfm.save(): 15 aggregate instances saved
Simon, I can only give you suggestions and pointers as
ReplyDeleteto your particular issue.
Note: It is always harder to install onto an existing database then it is to create a new repository database. So be prepared for errors like this,
especially since a lot of steps
are manual as per the note.
The note mentions Oracle Enterprise Linux 5 should be installed with the preparation described in Note 815157.1 (Operating System Package Prerequisites). Did you follow this?
11.1.0.7 is supported as per the certify matrix, so recreate the database (provided it is not production and there is nothing else in it) and try the install again.
Otherwise open an SR - the Metalink guys are pretty ok at solving installation issues.
It may be a bug since the document also mentions a few errors.
If you are doing this just to test out Grid Control, I simply suggest you create a new repository database, that is the simplest and most workable option. Often the simplest things work best.
Thanks for your inputs.I am doing this to play around with GRID so that I can do a successful install in Production. The case study is itself a nightmare.
ReplyDeleteHmmm.
I did the install with 11.1.0.7 as existing Blnak Database.
I see what you are saying "Often the simplest things work best."
I was only trying to follow the"ORACLE RECOMMEDED APPROACH"
http://www.oracle.com/technology/software/products/oem/htdocs/gridR5_10205_readme.html
BTW the above is the most ever confusing README ever written by Oracle. A Simple flowchart would have been sufficient.
"If you do not have Grid control installed in your environment, then fast and recommended method is to perform a software-only installation of 10.2.0.5.
Refer to "Installing Software-Only and Configuring Later" described in Enterprise Manager Grid Control Installation and Basic Configuration Guide available at the following URL. This URL takes you to the Enterprise Manager documentation library page, and from the table, click View Library. On the following page, click the Documentation tab, and then click the name of the document you want to access.
http://www.oracle.com/technology/documentation/oem.html
This method does not require any DST patches because we will be upgrading the Grid Control 10.2.0.1.0 to 10.2.0.5.0 directly using the software-only installation method .
"
It seems what Oracle recommends rarely works for GRID.
I have been following message boards at OTN and elsewhere and I see similar issues thoughout.
I really cant understand why Installation of GRID or any Installation should be such a difficult task. To me design/development needs creativity But Installation should be simply follow instructions ( which should work).
Once we have work arounds or fixes during Installation means Product is not stable. I may be wrong.
But thanks for your inputs.
I hope someone in ORACLE reads this and fixes GRID installation.
Coming to doing a Fresh Install. I first read the Readme file ( which should be actually dont_readme file).
It seems even the base install in new DB has lots of patches and upgrades to finally come to 10.2.0.5 , I am a lazy DBA wanted the shortest path which obviously is a rough terrain.
"Often the simplest things work best."
Simon,
ReplyDeleteHow did you come to the 11.1.0.7 database for the repository? If you perform a first time install of Grid Control then it will install its own new database of 10g which I suggest you do, that will cut out a lot of the errors. Then upgrade the Grid Control to 10.2.0.5. That is truly the simplest approach.