Doc ID: Note:434858.1 Type: HOWTO
Last Revision Date: 04-JUN-2007 Status: MODERATED
In this Document
Goal
Solution
Option 1: Configuration Assistant
Option 2: Full Clean up of Failed Installation
--------------------------------------------------------------------------------
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.
Applies to:
Enterprise Manager Grid Control - Version: 10.2.0.0
Information in this document applies to any platform.
Goal
The following provides 2 different options on how to progress with a failed installation for Grid Control.
IMPORTANT NOTE: Please make sure that any issues identified has been corrected before re-attempting to complete installation
Solution
Option 1: Configuration Assistant
If partial installation has failed, it is possible to manually run the following Configuration Assistants rather than performing a re-installation.
NOTE: In some circumstances a full reinstallation process may be required. Please see Option 2, for procedure on full cleanup and re-installation.
OMS:
runConfig.sh ORACLE_HOME=
Please see Note 362217.1 for further details on using runConfig.sh
Agent:
Option 2: Full Clean up of Failed Installation
1. Abort the runInstaller wizard.
2. Manually kill off any rogue/residue processes still running from failed installation:
Windows:
Kill any opmn, agent processes owned by oracle via Task Manager and then perform reboot.
Unix:
ps -ef|grep opmn ps -ef|grep agent |grep oracle kill
3. Cleanup Repository as per
4. Execute runInstaller go to:
Installed Products > Select items "oms" and "agent" > Click Remove
NOTE: If the option chosen for initial installation was for "New Database" (default), verify that database is running ok and alert
6) Remove subdirectories for oms10g and agent10g
rm -rf oms10g/ agent10g/
7) Remove Oracle installation subdirectories under /tmp
Unix only:
rm -rf /tmp/em rm -rf /tmp/OraInstall*
8) Then perform a re-installation:
runInstaller
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Subject: How To Drop, Create And Recreate DB Control In A 10g Database
Doc ID: Note:278100.1 Type: BULLETIN
Last Revision Date: 05-JUN-2007 Status: PUBLISHED
In this Document
Purpose
Scope and Application
How To Drop, Create And Recreate DB Control In A 10g Database
DB Control options:
A. Delete DB Control Objects:
B. Create DB Control Objects
C. Recreate/ReConfig DB Control
--------------------------------------------------------------------------------
Applies to:
Enterprise Manager Grid Control - Version: 10.1 to 10.2
Information in this document applies to any platform.
DBConsole
Purpose
This article provides detailed instructions on how to 1) create, 2) drop and 3)recreate the repository and configuration files for the DB Control application used to manage a single 10g Database.
Scope and Application
The steps in this article are written for a DBA or System Administrator who needs to create, drop or reconfigure the DB Control Application.
The format of the document will include steps for both 10.1 and 10.2 EMCA because the commands changed between the two releases.
How To Drop, Create And Recreate DB Control In A 10g Database
DB Control options:
A. Delete DB Control Objects:
Option 1. Delete DB Control Configuration Files using EMCA scripts
Option 2. Delete DB Control Configuration Files Manually:
Option 3. Delete DB Control Repository Objects using RepManager
Option 4. Delete DB Control Repository Objects Manually
Option 5. Delete DB Control Configuration Files and Repository Objects using EMCA
Option 1. Delete DB Control Configuration Files using EMCA scripts:
For DB Control 10.1.x, run the command:
Option 2. Delete DB Control Configuration Files Manually:
Remove the following directories from your filesystem:
NOTE:
On Windows you also need to delete the DB Console service:
- run regedit
- navigate to HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services
- locate the OracleDBConsole
Alternatively on Windows XP and Windows Server 2003 you can run the following from the command line:
'sc delete
- where
Also available from Microsoft is the delsrv.exe command. (Free download from Microsoft)
Option 3. Delete DB Control Repository using RepManager:
This option is not as complete as the other options. You may find that dropping the repository using the commandline options is a better solution. Also note, RepManager is not used to create a DB Control Repository.
In both 10g R1 and R2 run:
Option 4. Delete DB Control Repository Objects Manually
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> DECLARECURSOR c1 ISSELECT owner, synonym_name nameFROM dba_synonymsWHERE table_owner
= 'SYSMAN';BEGINFOR r1 IN c1 LOOPIF r1.owner = 'PUBLIC' THENEXECUTE IMMEDIATE 'DROP PUBLIC SYNONYM '||r1.name;ELSEEXECUTE
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;
Note: The above will completely delete the DB Control repository from the database; under certain circumstances (e.g. you want to recreate the repository later on) the following statements may be sufficient to remove the repository:
Logon SQLPLUS as user SYS or SYSTEM, and drop the sysman account and management objects:SQL> drop user
sysman cascade;SQL> drop role MGMT_USER;SQL> drop user MGMT_VIEW cascade;SQL> drop public synonym MGMT_TARGET_BLACKOUTS;SQL> drop public synonym SETEMVIEWUSERCONTEXT;
Option 5. Delete DB Control Configuration Files and Repository Objects using EMCA
For DB Control 10.1.x, dropping both the configuration files and the repository objects is a two step process. Run the following two commands:
For DB Control 10.2.x, both configuration files and repository objects can be deleted with a single command. Run the command:
B. Create DB Control Objects
Option 1. Create the DB Control Configuration Files
Option 2. Create the DB Control Repository Objects and Configuration Files
Option 1. Create the DB Control Configuration Files
To create only the DB Control configuration files, skipping the repository creation (this would be done for instance if you dropped only the files and left the repository in place):
For DB Control 10.1.x, run the command:
Option 2. Create the DB Control Repository Objects and Configuration Files
For DB Control 10.1.x, run the command:
C. Recreate/ReConfig DB Control
Option 1. Recreate the DB Control Configuration Files only (leave Repository intact)
Option 2. Recreate the DB Control Configuration Files and Repository
In 10.2, the EMCA commands can be used to reconfigure the existing installs without removing them first.
Option 1. Recreate the DB Control Configuration Files only (leave Repository intact):
For DB Control 10.2.x, run the command:
Option 2. Recreate the DB Control Configuration Files and Repository
For DB Control 10.2.x, run the command:
For additional information on EMCA commandline options, please see the Oracle Enterprise Manager 10g Advanced Configuration Guide or see Note 330130.1 Overview Of The EMCA Commands Available for DB Control 10.2
Keywords
'EMCA' 'REPMANAGER' 'DB~CONTROL' 'DBCONSOLE'
No comments:
Post a Comment