RE: Oracle Configuration Manager installation problems
- From: "Stephens, Chris" <Chris.Stephens@xxxxxxx>
- To: Wayne Smith <wts@xxxxxxxxx>
- Date: Fri, 12 Aug 2011 08:12:27 -0500
Thanks for the summarized list of steps.
I finally got around to attempting this again and it appears that Oracle has
resolved the issue on their end. The setupCCR script completed without error.
On to the database specific piece!
Thanks again.
Chris
From: Wayne Smith [mailto:wts@xxxxxxxxx]
Sent: Wednesday, August 10, 2011 3:24 PM
To: Stephens, Chris
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Oracle Configuration Manager installation problems
OCM is most useful to me because it enables "plans" and "health checks" on MOS.
I use it on all production and most test/dev databases that will exist long
enough to have their home updated (such as with a patchset or PSU or version
upgrade).
If all you've done is run setupCCR, then OCM isn't using your database
("collectconfig" is the thing that puts OCM stuff in your database). So I'm
guessing the reference is to a database back at
ccr.oracle.com<http://ccr.oracle.com> central. Maybe time for an SR? (I
haven't seen this error).
The rest of this post is just my cookbook for OCM install ... sorry I can't be
more helpful with this particular error :-(
Make sure you are using (at least) version 10.3.5 of OCM. If your database and
home have never had OCM installed, then I
1. remove the $ORACLE_HOME/ccr directory, if it exists (other steps must be
done before this if OCM has already been installed in one of your databases or
this is a clone of a database that had OCM installed)
2. download latest version of OCM zip file to the $ORACLE_HOME directory and
explode.
3. $ORACLE_HOME/ccr/bin/setupCCR -s [CSI MOSemail US]
* CSI is your CSI number; MOSemail is the email address you use on My
Oracle Support; "US" is my country code
* If your server does not have access to
ccr.oracle.com<http://ccr.oracle.com>, enter NONE or read abount DISCONNECTED
mode.
* If you have a proxy server that can give OCM access to
ccr.oracle.com<http://ccr.oracle.com>, enter its name and port when prompted.
1. For each database, use ". oraenv" to setup environment variables, then
setup the database for OCM with
* $ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectconfig;
1. Do an initial collection of data for MOS with
* $ORACLE_HOME/ccr/bin/emCCR collect
2. Set a daily collection time, if "now" is not good enough, with
* $ORACLE_HOME/ccr/bin/emCCR set collection_interval='FREQ=DAILY;
BYHOUR=04; BYMINUTE=15'
3. Occasionally view OCM status to ensure OCM hasn't updated itself into a
bad state
* $ORACLE_HOME/ccr/bin/emCCR status
(and let us know what the problem was, please!)
Cheers, Wayne
There is no job so simple that it cannot be done wrong. (Perrussel's Law)
On Fri, Aug 5, 2011 at 2:25 PM, Stephens, Chris
<Chris.Stephens@xxxxxxx<mailto:Chris.Stephens@xxxxxxx>> wrote:
I was going to see what OCM has to offer and install it on one of our
development servers. The install appears to be very easy. However, after
entering the information prompted after executing $ORACLE_HOME/ccr/bin/
setupCCR, I get the following:
Registration Server encountered a SQL Exception
SQL Exception: ORA-01552: cannot use system rollback segment for non-system
tablespace 'MGMT_TABLESPACE'
ORA-06512: at "SYSMAN.CCR_AUTH", line 2193
ORA-06512: at line 1
Since there is no tablespace with that name on the server I am attempt to
configure OCM on, I can only assume this is being generated from Oracle
support's repository? If so: way to be Oracle!
Anyone else have this problem? ...or has no one else installed OCM?
CONFIDENTIALITY NOTICE:
This message is intended for the use of the individual or entity to which it is
addressed and may contain information that is privileged, confidential and
exempt from disclosure under applicable law. If the reader of this message is
not the intended recipient or the employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please notify us
immediately by email reply.
Other related posts:
