ITPub博客

首页 > 数据库 > Oracle > Enterprise manager failed due to the following

Enterprise manager failed due to the following

原创 Oracle 作者:spectre2 时间:2011-07-18 13:45:53 0 删除 编辑

今天继续装rac,升级到10.2.0.5,dbca建库,到最后,报Enterprise manager failed due to the following error- error starting database control。。。错误,google,发现是ORACLE的bug,如下:

Bug 问题表现

       2011年安装Oracle 10.2.0.4 10.2.0.5 版本时,在配置OEM的时候会报错。 忽略这个错误后,DB 可以成功创建或者升级。

 

       MOS 上关于这个bug的说明,参考:[ID 1222603.1]

      

       bug 的表现为DBCADBUA 配置失败:

 

       Database Configuration Assistant (DBCA) and Database Upgrade Assistant (DBUA) will report the following error in the console:

Could not complete the Enterprise Manager configuration.
Enterprise manager configuration failed due to the following error –
Error starting Database Control

 

      

Oracle 对这个bug原因的说明:

 

       In Enterprise Manager Database Control with Oracle Database 10.2.0.4 and 10.2.0.5, the root certificate used to secure communications via the Secure Socket Layer (SSL) protocol will expire on 31-Dec-2010 00:00:00. The certificate expiration will cause errors if you attempt to configure Database Control on or after 31-Dec-2010. Existing Database Control configurations are not impacted by this issue.

       If you plan to configure Database Control with either of these Oracle Database releases, Oracle strongly recommends that you apply Patch 8350262 to your Oracle Home installations before you configure Database Control. Configuration of Database Control is typically done when you create or upgrade Oracle Database, or if you run Enterprise Manager Configuration Assistant (EMCA) in standalone mode.


Note the following:

 

       1The issue impacts configuration of Database Control with Oracle Database 10.2.0.4 and 10.2.0.5 only. It does not impact database creation or upgrade.

       2The issue does not impact existing Database Control configurations.

       3Application of Patch 8350262 does not require any database downtime

 

 

这个Patch 不受平台限制。

 

解决该问题步骤

       如果是在创建实例之前就把该patch给打上了,那么在创建OEM的时候不会受影响。

      

       如果是已经报错了,解决步骤如下:

 

For Single Instance

1. 使用Opatch 安装Patch 8350262

2. force stop the Database Control (dbconsole) process using the killDBConsole script. bundled with the patch. Note that the dbconsole process cannot be stopped using the emctl stop dbconsole command, as EMCTL is unable to connect to the process.

       1Set the ORACLE_HOME and ORACLE_SID environment variables.

       2Execute /killDBConsole.

       --windows 平台省略这一步

3.  Re-secure Database Control with the following command:
       /bin/emctl secure dbconsole -reset

4.  Re-start Database Control with the following command:
       /bin/emctl start dbconsole

 

 

For RAC Instance

1. 使用Opatch 安装Patch 8350262, 在一个节点安装就ok了。

2.  force stop the Database Control (dbconsole) process by executing the killDBConsole script. bundled with the patch on each node in the cluster

       在所有节点执行

       1Set the ORACLE_HOME and ORACLE_SID environment variables.

       2Execute /killDBConsole.

       --windows 平台省略这一步

3. Re-secure Database Control on the first cluster node with the following command:
       /bin/emctl secure dbconsole -reset

4. Re-secure Database Control on the remaining cluster nodes with the following command. Note that the -reset switch is not included with this command:
       /bin/emctl secure dbconsole

5.  Re-start Database Control by executing the following command on each node in the cluster:
       /bin/emctl start dbconsole

参考:http://blog.csdn.net/tianlesoftware/article/details/6568690

 

 

p8350262_10204_Generic.zip去掉.jpg

p8350262_10205_Generic.zip去掉.jpg

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/14184018/viewspace-702464/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论

注册时间:2011-02-27

  • 博文量
    196
  • 访问量
    1871866