Re: dbca 11g and em 12c agent

From: Jeremy Schneider <jeremy.schneider_at_ardentperf.com>
Date: Fri, 1 Mar 2013 15:37:11 -0600
Message-ID: <20130301153711.00f30525_at_jeremy-nb>

Thanks again for the reply. Interesting - maybe it's fixed in bp14? BTW I think you misread my email; dbca runs fine. But dbca dynamically decides which pages from the wizard will be displayed and on QA it excludes the EM page entirely.

-J

-- 
Jeremy Schneider
Pythian Consulting Group
Chicago

+1 312-725-9249
http://www.pythian.com



On Fri, 1 Mar 2013 15:26:48 -0600
Q A I S E R <qrasheed_at_gmail.com> wrote:



> Jeremy,

> 

> That sounds more like xauth/X11 issue, since you are not able to run

> dbca.

> 

> We upgraded Exadata from 11.2.0.2 11.2.0.3 BP14.

> OMS is 12.1.0.2 with Exadata PLUG-IN 12.1.0.3

> 

> As for the URL, we are using the same URL for EM as before the

> upgrade. You don't even get an option to see the URL using this

> method, since you are only changing a property (ORACLE_HOME) in the

> configuration. Please note: DO *NOT* choose "Enterprise Manager

> Option" on the database components screen, as mentioned at point # 5

> below. Following is from Note 1373255.1.

> 

> *Re-configure the database for Enterprise Manager Cloud Control 12c

> using DBCA.*

> 

> 

> Perform these actions on the DBCA screens to update the properties of

> an already registered database in 12c OMS after the database upgrade.

> 

> 1. On the Welcome screen, select the database type you like to

> administer, for most deployments that will be 'RAC'.

> 2. On the 'Select the operation that you want to perform screen',

> select 'Configure Database Options', and then click Next.

> 3. On 'Select the database that you want to configure options for'

> screen, select the database you want to re-configure EM for, provide

> the details for SYSDBA and then click Next.

> 4. On the 'Enterprise Manager' screen, select 'Configure Enterprise

> Manager', verify the management service to register with for

> centralized management, click Next. When prompted specify ASMSNMP

> password specific for ASM.

> 5. On 'Database Components' screen, do not select the 'Enterprise

> Manager Repository' option, then click Next.

> 6. Specify administrative passwords, click Next

> 7. Do not change the mode in which the database needs to operate,

> click Finish. On 'Configure new settings for database', click 'OK'

> 8. On Progress screen, when 'Completing Database Configuration' is

> you will be prompted for another operation, click 'NO'.

> 

> Performing this step will also cause the properties for the Grid

> Infrastructure targets to be updated to their new values.

> Monitoring properties for standby databases need to be updated

> manually in the EM Console. Go to Target and right click. Select

> database and then target setup. Select monitoring configuration.

--
http://www.freelists.org/webpage/oracle-l

Received on Fri Mar 01 2013 - 22:37:11 CET