How To Drop/Create EM dbconsole of Single Instance Database

Manually recreate dbconsole 10gR2 Single Instance : $ORACLE_HOME/bin/emca -config dbcontrol db -repos create RAC Database : $ORACLE_HOME/bin/emca -config dbcontrol db -repos create -cluster First remove repository and files How to drop DBConsole configuration files using EMCA (leave repository intact) ?   To remove DBConsole configuration files (leaving repository intact) run following EMCA command. <ORACLE_HOME>/bin/emca -deconfig dbcontrol db Enter the following information: Database SID: orcl Do you wish to continue? [yes(Y)/no(N)]: Note: This command will remove only the DBConsole configuration files which are under   <ORACLE_HOME>/<Hostname_SID> and  <ORACLE_HOME>/oc4j/j2ee/OC4J_DBConsole_<Hostname>_<SID> EXAMPLE D:>emca -deconfig dbcontrol db STARTED EMCA at Aug 2, 2011 12:38:43 PM EM Configuration Assistant, Version 10.2.0.1.0 Production Copyright (c) 2003, 2005, Oracle.  All rights reserved. Enter the following information: Database SID: orcl Do you wish to continue? [yes(Y)/no(N)]: Y Aug 2, 2011 12:38:54 PM oracle.sysman.emcp.EMConfig perform INFO: This operation is being logged at D:\oracle\product\10.2.0\db_1\cfgtoollog s\emca\emca_2011-08-02_12-38-43-PM.log. Aug 2, 2011 12:38:56 PM oracle.sysman.emcp.EMDBPreConfig invoke WARNING: Database instance unavailable. Aug 2, 2011 12:38:56 PM oracle.sysman.emcp.util.DBControlUtil stopOMS INFO: Stopping Database Control (this may take a while) ... Aug 2, 2011 12:39:01 PM oracle.sysman.emcp.target.TargetManager cleanupAgent WARNING: Error initializing SQL connection. SQL operations cannot be performed Enterprise Manager configuration completed successfully FINISHED EMCA at Aug 2, 2011 12:39:02 PM Drop DBConsole configuration files manually remove both directories <ORACLE_HOME>/<Hostname_SID> <ORACLE_HOME>/oc4j/j2ee/OC4J_DBConsole_<Hostname>_<SID> How to drop DBConsole repository objects manually ? DBConsole repository can be dropped manually by executing following SQL statements. Step 1: Drop AQ related objects in the SYSMAN schema Logon SQLPLUS as user SYS   SQL> exec DBMS_AQADM.DROP_QUEUE_TABLE(queue_table=>'SYSMAN.MGMT_NOTIFY_QTABLE',force=>TRUE); Step 2: Drop the DB Control Repository Objects Logon SQLPLUS as user SYS or SYSTEM, and drop the sysman account and management objects:   SQL> SHUTDOWN IMMEDIATE; SQL> STARTUP RESTRICT; SQL> EXEC sysman.emd_maintenance.remove_em_dbms_jobs; SQL> EXEC sysman.setEMUserContext('',5); SQL> REVOKE dba FROM sysman; SQL> DECLARE CURSOR c1 IS SELECT owner, synonym_name name FROM dba_synonyms WHERE table_owner = 'SYSMAN'; BEGIN FOR r1 IN c1 LOOP IF r1.owner = 'PUBLIC' THEN EXECUTE IMMEDIATE 'DROP PUBLIC SYNONYM '||r1.name; ELSE EXECUTE IMMEDIATE 'DROP SYNONYM '||r1.owner||'.'||r1.name; END IF; END LOOP; END; / SQL> DROP USER mgmt_view CASCADE; SQL> DROP ROLE mgmt_user; SQL> DROP USER sysman CASCADE; SQL> ALTER SYSTEM DISABLE RESTRICTED SESSION; On Windows you also need to delete the DB Console service: Using regedit - run regedit - navigate to HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services - locate the OracleDBConsole<sid> entry and delete it Or On Windows XP and Windows Server 2003 you can run the following from the command line: CMD> sc delete <service_name> - where <service_name> is the DB Control service name (typically: OracleDBConsole<sid>) Or CMD> nmesrvops delete <servicename> - where <service_name> is the DB Control service name (typically: OracleDBConsole<sid>).

EM Database Control -Recovering From Errors Due to CA Expiry on Oracle DB 10.2.0.4

Purpose      What is the Issue?   Scope and Application      Who is Affected?   Enterprise Manager Database Control Configuration - Recovering From Errors Due to CA Expiry on Oracle Database 10.2.0.4 or 10.2.0.5 [Video]      What Happens During Database Control Configuration Failure?      Recovering from Configuration Errors on a Single Instance Database      Recovering from Configuration Errors in an Oracle Real Application Clusters (RAC) Environment   References Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.4 to 10.2.0.5 - Release: 10.2 to 10.2 Oracle Database Configuration Assistant - Version: 10.2.0.4 to 10.2.0.5   [Release: 10.2 to 10.2] Information in this document applies to any platform. Enterprise Manager Database Control 10.2.0.4 and 10.2.0.5 Purpose What is the Issue? 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: The 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. The issue does not impact existing Database Control configurations. Application of Patch 8350262 does not require any database downtime Note: If you apply Patch 8350262 to your Oracle Home installations before you configure Database Control, you will not need to follow the recovery steps outlined in this document. Scope and Application Who is Affected? If you did not apply Patch 8350262 before configuring Database Control, you will encounter errors during the Database Control configuration process on or after 31-Dec-2010 under the following conditions: When configuring Database Control while installing Oracle Database 10.2.0.4 or 10.2.0.5 using Database Configuration Assistant (DBCA) When configuring Database Control while upgrading to Oracle Database 10.2.0.4 or 10.2.0.5 on a new or existing Oracle Home using Database Upgrade Assistant (DBUA) When configuring or re-configuring Database Control for Oracle Database 10.2.0.4 or 10.2.0.5 on an existing Oracle Home using Database Configuration Assistant (DBCA) or Enterprise Manager Configuration Assistant (EMCA) Enterprise Manager Database Control Configuration - Recovering From Errors Due to CA Expiry on  Oracle Database 10.2.0.4 or 10.2.0.5 [Video] PATCH:8350262 -  CREATE DBCONSOLE CERT WITH 10YEAR VALIDITY NOTE:1217493.1 -  ATTENTION - Enterprise Manager Database Control 10.2.0.4 Or 10.2.0.5 - Patch Required from 31-Dec-2010 onwards What Happens During Database Control Configuration Failure? Database Configuration Assistant (DBCA) and Database Upgrade Assistant (DBUA) Errors 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 Enterprise Manager Configuration Assistant (EMCA) Errors Enterprise Manager Configuration Assistant (EMCA) will write errors similar to those below to the emca.log file: CONFIG: Securing Database Control completed successfully . Jan 2, 2011 7:22:47 PM oracle.sysman.emcp.ParamsManager getParam CONFIG: No value was set for the parameter ORACLE_HOSTNAME. Jan 2, 2011 7:22:47 PM oracle.sysman.emcp.util.DBControlUtil startOMS INFO: Starting Database Control (this may take a while) ... Jan 2, 2011 7:22:47 PM oracle.sysman.emcp.util.PlatformInterface addEnvVarToList CONFIG: Value for env var 'ORACLE_HOSTNAME' is '', discarding the same CONFIG: Returning env array from cache Jan 2, 2011 7:22:47 PM oracle.sysman.emcp.util.PlatformInterface executeCommand CONFIG: Starting execution: /myhost/bin/emctl start dbconsole Jan 2, 2011 7:27:26 PM oracle.sysman.emcp.util.PlatformInterface executeCommand CONFIG: Exit value of 1 Jan 2, 2011 7:27:26 PM oracle.sysman.emcp.util.PlatformInterface executeCommand CONFIG: Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0 Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved. https://myhost:5501/em/console/aboutApplication Starting Oracle Enterprise Manager 10g Database Control ............................................................................................. failed. ------------------------------------------------------------------ Logs are generated in directory /myhost/sysman/log Jan 2, 2011 7:27:26 PM oracle.sysman.emcp.util.PlatformInterface executeCommand WARNING: Error executing /myhost/bin/emctl start dbconsole Jan 2, 2011 7:27:26 PM oracle.sysman.emcp.EMConfig perform SEVERE: Error starting Database Control Refer to the log file at /myhost/dbua/d4/upgrade/emConfig.log for more details. Jan 2, 2011 7:27:26 PM oracle.sysman.emcp.EMConfig perform CONFIG: Stack Trace: oracle.sysman.emcp.exception.EMConfigException: Error starting Database Control at oracle.sysman.emcp.EMDBPostConfig.performUpgrade(EMDBPostConfig.java:763) at oracle.sysman.emcp.EMDBPostConfig.invoke(EMDBPostConfig.java:232) at oracle.sysman.emcp.EMDBPostConfig.invoke(EMDBPostConfig.java:193) at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:184) at oracle.sysman.assistants.util.em.EMConfiguration.run(EMConfiguration.java:436) at oracle.sysman.assistants.util.em.EMConfigStep.executeImpl(EMConfigStep.java:140) at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210) at oracle.sysman.assistants.util.step.BasicStep.callStep(BasicStep.java:251) at oracle.sysman.assistants.dbma.backend.EMConfigStep.executeStepImpl(EMConfigStep.java:104) at oracle.sysman.assistants.dbma.backend.SummarizableStep.executeImpl(SummarizableStep.java:175) at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210) at oracle.sysman.assistants.util.step.Step.execute(Step.java:140) at oracle.sysman.assistants.util.step.StepContext$ModeRunner.run(StepContext.java:2488) at java.lang.Thread.run(Thread.java:534) The EMCA console will display output similar to the following: aime@myhost09 db_1]$ bin/emca -config dbcontrol db -repos recreate -cluster STARTED EMCA at Jan 11, 2011 4:11:01 PM EM Configuration Assistant, Version 10.2.0.1.0 Production Copyright (c) 2003, 2005, Oracle. All rights reserved. Enter the following information: Database unique name: catest Database Control is already configured for the database catest You have chosen to configure Database Control for managing the database catest This will remove the existing configuration and the default settings and perform a fresh configuration Do you wish to continue? [yes(Y)/no(N)]: Y Listener port number: 1521 Cluster name: mycluster Password for SYS user: Password for DBSNMP user: Password for SYSMAN user: Email address for notifications (optional): Outgoing Mail (SMTP) server for notifications (optional): ........ Jan 11, 2011 4:18:05 PM oracle.sysman.emcp.util.DBControlUtil secureDBConsole INFO: Securing Database Control (this may take a while) ... Jan 11, 2011 4:19:31 PM oracle.sysman.emcp.util.DBControlUtil startOMS INFO: Starting Database Control (this may take a while) ... Jan 11, 2011 4:28:38 PM oracle.sysman.emcp.EMConfig perform SEVERE: Error starting Database Control Refer to the log file at /myhost/oracle/product/10.2.0/db_1/cfgtoollogs/emca/catest/emca_2011-01-11_ 04-11-01-PM.log for more details. Could not complete the configuration. Refer to the log file at /myhost/oracle/product/10.2.0/db_ 1/cfgtoollogs/emca/catest/emca_2011-01-11_04-11-01-PM.log for more details. Checking the ORACLE_HOME\<hostname>_<SID>\sysman\log\emagent.trc, one can see also: 2011-01-09 09:36:56 Thread-51125136 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://myhost:1158/em/upload/: retStatus=-1 2011-01-09 09:36:56 Thread-51125136 ERROR ssl: Open wallet failed, ret = 28750 2011-01-09 09:36:56 Thread-51125136 ERROR ssl: nmehlenv_openWallet failed 2011-01-09 09:36:56 Thread-51125136 ERROR http: 15: Unable to initialize ssl connection with server, aborting connection attempt Also, the following errors has been reported in some cases: 2011-01-06 18:50:54 Thread-3393 ERROR ssl: nzos_Initialize failed, ret = 43061 2011-01-06 18:50:54 Thread-3393 ERROR http: 14: Unable to initialize ssl connection with server, aborting connection attempt 2011-01-06 18:50:54 Thread-3393 ERROR pingManager: nmepm_pingReposURL: Cannot connect tohttps://myhost:1158/em/upload/:retStatus=-1 At the end of the database installation on non-Windows platforms, both Database Control and the Management Agent will be up and running, even though the status of both components will be shown as not running, because EMCTL will be unable to connect to the dbconsole process. In addition, Database Control will fail to connect to the Agent. Note for Windows Platform Only: On Windows, the dbconsole process will be stopped after the failed configuration attempt. Note that the tool used to perform Database Control configuration (DBUA, DBCA or EMCA) will also wait for 15 minutes for Database Control to start, then time out. The output of the "emctl status dbconsole" command incorrectly returns the status of Database Control, as shown below (note that this command may take a while to complete, especially in a RAC environment) : $ ./emctl status dbconsole Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0 Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved. https://myhost:1158/em/console/aboutApplication Oracle Enterprise Manager 10g is not running. The output of the "emctl status agent" command incorrectly returns the status of the Agent, as shown below: $ ./emctl status agent Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0 Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved. --------------------------------------------------------------- Agent is Not Running 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. NOTE:   The database instance and the listener DO NOT have to be stopped for applying this patch, but ensure that all java processes sourced from the Oracle Home being patached are stopped in this case (i.e., all Oracle Home-related java.exe on Windows, for instance). opatch apply Invoking OPatch 10.2.0.4.2 Oracle Interim Patch Installer version 10.2.0.4.2 Copyright (c) 2007, Oracle Corporation. All rights reserved. Oracle Home : /myhost Central Inventory : /scratch/pchebrol/oraInventory from : /etc/oraInst.loc OPatch version : 10.2.0.4.2 OUI version : 10.2.0.4.0 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, 10.2.0.4.0a... Updating jar file "/myhost/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/fsc/FSWalletUtil.class" Updating jar file "/myhost/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/rep/RepWalletUtil.class" Updating jar file "/myhost/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/util/RootCert.class" Updating jar file "/myhost/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/util/SecConstants.class" Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_ java.jar/oracle/sysman/eml/sec/fsc/FSWalletUtil.class" Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_ java.jar/oracle/sysman/eml/sec/rep/RepWalletUtil.class" Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_ java.jar/oracle/sysman/eml/sec/util/RootCert.class" Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_ java.jar/oracle/sysman/eml/sec/util/SecConstants.class" 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 <PATCH_HOME>/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: $ <PATCH_HOME>/killDBConsole ORACLE_HOME=/myhost/db_1 ORACLE_SID=caem31 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: <ORACLE_HOME>/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 10.2.0.4.0 Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved. https://myhost:5501/em/console/aboutApplication 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) ? Y 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) ? Y Generating Enterprise Manager Root Key (this takes a minute)... Done.Fetching Root Certificate from the Repository... Done. Updating HTTPS port in emoms.properties 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/emd.properties Done. Configuring Key store.. Done. Securing dbconsole... Sucessful. 5. Re-start Database Control with the following command: <ORACLE_HOME>/bin/emctl start dbconsole Recovering from Configuration Errors in an Oracle Real Application Clusters (RAC) Environment 1. Ignore any errors and continue with the upgrade, so that the database is upgraded without errors. 2. Apply Patch 8350262 to your Oracle Home installation. Note that the OPatch utility will apply the patch to all nodes in the cluster, as shown below: ../OPatch/opatch apply Invoking OPatch 10.2.0.4.2 Oracle Interim Patch Installer version 10.2.0.4.2 Copyright (c) 2007, Oracle Corporation. All rights reserved. Oracle Home : /myhost/oracle/product/10.2.0/db_1 Central Inventory : /myhost/app/oraInventory from : /etc/oraInst.loc OPatch version : 10.2.0.4.2 OUI version : 10.2.0.4.0 OUI location : /myhost/oracle/product/10.2.0/db_1/oui Log file location : /myhost/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2011-01-01_ 21-30-27PM.log ApplySession applying interim patch '8350262' to OH '/myhost/oracle/product/10.2.0/db_1' Running prerequisite checks... OPatch detected the node list and the local node from the inventory. OPatch will patch the local system then propagate the patch to the remote nodes. 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, 10.2.0.4.0a... Updating jar file "/myhost/oracle/product/10.2.0/db_1/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/fsc/FSWalletUtil.class" Updating jar file "/myhost/oracle/product/10.2.0/db_1/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/rep/RepWalletUtil.class" Updating jar file "/myhost/oracle/product/10.2.0/db_1/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/util/RootCert.class" Updating jar file "/myhost/oracle/product/10.2.0/db_1/sysman/jlib/emCORE.jar" with "/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/util/SecConstants.class" Updating jar file "/myhost/oracle/product/10.2.0/db_1/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_java.jar/oracle/sysman/eml/sec/fsc/FSWalletUtil.class" Updating jar file "/myhost/oracle/product/10.2.0/db_1/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_java.jar/oracle/sysman/eml/sec/rep/RepWalletUtil.class" Updating jar file "/myhost/oracle/product/10.2.0/db_1/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_java.jar/oracle/sysman/eml/sec/util/RootCert.class" Updating jar file "/myhost/oracle/product/10.2.0/db_1/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_java.jar/oracle/sysman/eml/sec/util/SecConstants.class" 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. Patching in rolling mode. Updating nodes 'myhost' Apply-related files are: FP = :/myhost/oracle/product/10.2.0/db_1/.patch_storage/8350262_Sep_14_2010_04_59_44/rac/copy_ files.txt" DP = "/myhost/oracle/product/10.2.0/db_1/.patch_storage/8350262_Sep_14_2010_04_59_44/rac/copy_ dirs.txt" MP = "/myhost/oracle/product/10.2.0/db_1/.patch_storage/8350262_Sep_14_2010_04_59_44/rac/make_ cmds.txt" RC = "/myhost/oracle/product/10.2.0/db_1/.patch_storage/8350262_Sep_14_2010_04_59_44/rac/remote_ cmds.txt" Instantiating the file "/myhost/oracle/product/10.2.0/db_1/.patch_storage/8350262_Sep_14_2010_04_59_ 44/rac/copy_files.txt.instantiated" by replacing $ORACLE_HOME in "/myhost/oracle/product/10.2.0/db_ 1/.patch_storage/8350262_Sep_14_2010_04_59_44/rac/copy_files.txt" with actual path. Propagating files to remote nodes... Instantiating the file "/myhost/oracle/product/10.2.0/db_1/.patch_storage/8350262_Sep_14_2010_04_59_ 44/rac/copy_dirs.txt.instantiated" by replacing $ORACLE_HOME in "/myhost/oracle/product/10.2.0/db_ 1/.patch_storage/8350262_Sep_14_2010_04_59_44/rac/copy_dirs.txt" with actual path. Propagating directories to remote nodes... OPatch succeeded. 3. After applying the patch, force stop the Database Control (dbconsole) process by executing the killDBConsole script bundled with the patch on each node in the cluster. 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 <PATCH_HOME>/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: $ <PATCH_HOME>/killDBConsole ORACLE_HOME=/myhost/catest/db_1 ORACLE_SID=caem31 State directory = /myhost/catest/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 NOTE:   The following is a REQUIRED STEP! 4. Re-secure Database Control on the first cluster node with the following command: <ORACLE_HOME>/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 10.2.0.4.0 Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved. https://myhost:5501/em/console/aboutApplication 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) ? Y 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) ? Y Generating Enterprise Manager Root Key (this takes a minute)... Done.Fetching Root Certificate from the Repository... Done. Updating HTTPS port in emoms.properties 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/sysman/config/emd.properties Done. Configuring Key store.. Done. Securing dbconsole... Sucessful. 5. Re-secure Database Control on the remaining cluster nodes with the following command. Note that the -reset switch is not included with this command: <ORACLE_HOME>/bin/emctl secure dbconsole (Note:   the "Enter Enterprise Manager Root Password :" value is that for sysman) [myhost bin]$ ./emctl secure dbconsole Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0 Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved. https://myhost:1158/em/console/aboutApplication Enter Enterprise Manager Root password : Enter a Hostname for this OMS : myhost 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... Done. Fetching Root Certificate from the Repository... Done. Updating HTTPS port in emoms.properties 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/oracle/product/10.2.0/db_1/myhost/sysman/c onfig/emd.properties Done. Configuring Key store.. Done. Securing dbconsole... Sucessful. 6. Re-start Database Control by executing the following command on each node in the cluster: <ORACLE_HOME>/bin/emctl start dbconsol