首页 > Linux操作系统 > Linux操作系统 > 折腾oracle的em1


原创 Linux操作系统 作者:tonglei2000 时间:2011-04-02 15:40:46 0 删除 编辑
Recovering from Configuration Errors on a Single Instance Database
1. Ignore any errors and continue with the installation or upgrade. The database will be created without errors.
2. Apply Patch 8350262 to your Oracle Home installation using OPatch.
opatch apply
Invoking OPatch
Oracle Interim Patch Installer version
Copyright (c) 2007, Oracle Corporation. All rights reserved.
Oracle Home : /myhost
Central Inventory : /scratch/pchebrol/oraInventory
from : /etc/oraInst.loc
OPatch version :
OUI version :
OUI location : /myhost/oui
Log file location : /myhost/cfgtoollogs/opatch/opatch2011-01-02_11-00-00AM.log
ApplySession applying interim patch '8350262' to OH '/myhost'
Running prerequisite checks...
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '8350262' for restore. This might take a while...
Backing up files affected by the patch '8350262' for rollback. This might take a while...
Patching component oracle.sysman.agent.core,
Updating jar file "/myhost/sysman/jlib/emCORE.jar" with
Updating jar file "/myhost/sysman/jlib/emCORE.jar" with
Updating jar file "/myhost/sysman/jlib/emCORE.jar" with
Updating jar file "/myhost/sysman/jlib/emCORE.jar" with
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_
ApplySession adding interim patch '8350262' to inventory
Verifying the update...
Inventory check OK: Patch ID 8350262 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 8350262 are present in Oracle Home.
OPatch succeeded.
3. After applying the patch, 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.
To execute the killDBConsole script.:
Set the ORACLE_HOME and ORACLE_SID environment variables.
Execute /killDBConsole.
Note for Windows Platform. Only:
It is not necessary to force stop the dbconsole process on the Windows platform, because the process will
already be in a stopped state at the end of the failed configuration attempt.
The killDBConsole script. output is shown below:
$ /killDBConsole
State directory = /myhost/db_1/staxd10_caem31
WatchDog PID = 802932
DBconsole PID = 577716
EMAgent PID = 512156
Killing WatchDog (pid=802932) ...
Successfully killed process 802932
Killing DBConsole (pid=577716) ...
Successfully killed process 577716
Killing EMAgent (pid=512156) ...
Successfully killed process 512156
4. Re-secure Database Control with the following command:
/bin/emctl secure dbconsole -reset
You will be prompted twice to confirm that the Root key must be overwritten. In both cases, enter upper-case "Y" as the response. Any other response (including lower-case "y") will cause the command to terminate without completing. If this happens, the command can be re-invoked.
$ ./emctl secure dbconsole -reset
Oracle Enterprise Manager 10g Database Control Release
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root Password :
DBCONSOLE already stopped... Done.
Agent is already stopped... Done.
Securing dbconsole... Started.
Checking Repository... Done.
Checking Em Key... Done.
Checking Repository for an existing Enterprise Manager Root Key...
WARNING! An Enterprise Manager Root Key already exists in
the Repository. This operation will replace your Enterprise
Manager Root Key.
All existing Agents that use HTTPS will need to be
reconfigured if you proceed. Do you wish to continue and
overwrite your Root Key
(Y/N) ?
Are you sure ? Reset of the Enterprise Manager Root Key
will mean that you will need to reconfigure each Agent
that is associated with this OMS before they will be
able to upload any data to it. Monitoring of Targets
associated with these Agents will be unavailable until
after they are reconfigured.
(Y/N) ?
Generating Enterprise Manager Root Key (this takes a minute)... Done.Fetching Root Certificate from
the Repository... Done.
Updating HTTPS port in file... Done.
Generating Java Keystore... Done.
Securing OMS ... Done.
Generating Oracle Wallet Password for Agent.... Done.
Generating wallet for Agent ... Done.
Copying the wallet for agent use... Done.
Storing agent key in repository... Done.
Storing agent key for agent ... Done.
Configuring Agent...
Configuring Agent for HTTPS in DBCONSOLE mode... Done.
EMD_URL set in /myhost/myhost/sysman/config/
Configuring Key store.. Done.
Securing dbconsole... Sucessful.
5. Re-start Database Control with the following command:
/bin/emctl start dbconsole

来自 “ ITPUB博客 ” ,链接:,如需转载,请注明出处,否则将追究法律责任。

上一篇: aix rac安装
下一篇: 折腾oracle的em2
请登录后发表评论 登录


  • 博文量
  • 访问量