Overview
I had an old installation of OEM in the REPOS database. Instead of trying to find out a way to fit the new installation of OMS into this OMR, I decided to drop the OMR, and continue with a fresh installation.
References
Procedure
Drop Old OMR
First, the schemas associated with the OMR were dropped from REPOS on GRIDCTRL :
drop user sysman cascade; drop user SYSMAN_BIPLATFORM cascade; drop user SYSMAN_MDS cascade; drop user SYSMAN_OPSS cascade; drop user SYSMAN_APM cascade; drop user SYSMAN_RO cascade;
Tablespaces were then dropped
drop tablespace MGMT_ECM_DEPOT_TS including contents; drop tablespace MGMT_TABLESPACE including contents; drop tablespace MGMT_AD4J_TS including contents;
Start Installation of New OMR
Connected to CRONULLA with an XTerm session, and started the OUI to configure the OMS:
ssh -Y oracle@cronulla /opt/app/oracle/middleware/oms/sysman/install/ConfigureGC.sh
Step 1: Installation Types
The following screen appeared:
Clicked Next .
Step 2: Select Plug-ins
The following screen appeared:
Clicked Next .
Step 3: WebLogic Server Configuration
The following screen appeared, and filled in the appropriate passwords:
Clicked Next .
Step 4: Database Connection Details
The following screen appeared, and filled in the appropriate details:
Clicked Next .
The following error message appeared:
Clicked OK to dismiss the screen.
Examine Logs
The log at /opt/app/oracle/oraInventory/logs/emdbprereqs/LATEST/emprereqkit.log has these two (2) snippets:
Executing Output Action
-----------------------------
Sep 3, 2015 6:14:33 PM oracle.sysman.emdrep.emprereqkit.logger.EMPrereqKitLogger logDebug
FINE: executing Action: select SYNONYM_NAME,table_owner from dba_synonyms where table_owner in ('SYSMAN','SYSMAN_MDS','MGMT_VIEW','SYSMAN_BIP','SYSMAN_APM','SYSMAN_OPSS','SYSMAN_RO')
Sep 3, 2015 6:14:33 PM oracle.sysman.emdrep.emprereqkit.logger.EMPrereqKitLogger log
INFO: Using an existing DB connection...
Sep 3, 2015 6:14:34 PM oracle.sysman.emdrep.emprereqkit.logger.EMPrereqKitLogger logDebug
FINE: Result=
And:
Executing Output Action
-----------------------------
Sep 3, 2015 6:14:34 PM oracle.sysman.emdrep.emprereqkit.logger.EMPrereqKitLogger logDebug
FINE: executing Action: select comp_name,owner from SCHEMA_VERSION_REGISTRY where (comp_name,owner) in (('Authorization Policy Manager','SYSMAN_APM'),('Metadata Services','SYSMAN_MDS'),('OraclePlatform Security Services','SYSMAN_OPSS'))
Sep 3, 2015 6:14:34 PM oracle.sysman.emdrep.emprereqkit.logger.EMPrereqKitLogger log
INFO: Using an existing DB connection...
Sep 3, 2015 6:14:34 PM oracle.sysman.emdrep.emprereqkit.logger.EMPrereqKitLogger logDebug
FINE: Result=
Authorization Policy Manager SYSMAN_APM
Metadata Services SYSMAN_MDS
Oracle Platform Security Services SYSMAN_OPSS
Clean up Synonyms
Ran the following code on REPOS to determine the user names involved with the errant synonyms:
select distinct owner
from dba_synonyms
where table_owner in ('SYSMAN','SYSMAN_MDS','MGMT_VIEW','SYSMAN_BIP','SYSMAN_APM','SYSMAN_OPSS','SYSMAN_RO')
/
The result was:
OWNER ------------------------------ PUBLIC MGMT_VIEW DBSNMP
Used the following command on REPOS to clean up MGMT_VIEW user:
drop user mgmt_view cascade;
For the other synonyms, I used the following anonymous PL/SQL block on REPOS :
DECLARE
CURSOR csr_syn IS
SELECT
owner,
synonym_name
FROM
dba_synonyms
WHERE
table_owner IN ('SYSMAN','SYSMAN_MDS','MGMT_VIEW','SYSMAN_BIP','SYSMAN_APM','SYSMAN_OPSS','SYSMAN_RO');
BEGIN
FOR l_syn IN csr_syn LOOP
IF l_syn.owner = 'PUBLIC' THEN
EXECUTE IMMEDIATE 'DROP PUBLIC SYNONYM ' || l_syn.synonym_name;
ELSE
EXECUTE IMMEDIATE 'DROP SYNONYM ' || l_syn.owner || '.' || l_syn.synonym_name;
END IF;
END LOOP;
END;
/
Clean Up SCHEMA_VERSION_REGISTRY
Ran the following command on REPOS to clean up SCHEMA_VERSION_REGISTRY :
DELETE
FROM
SCHEMA_VERSION_REGISTRY
WHERE
(comp_name,owner) IN (
('Authorization Policy Manager','SYSMAN_APM'),
('Metadata Services','SYSMAN_MDS'),
('Oracle Platform Security Services','SYSMAN_OPSS')
);
COMMIT;
Repeat Step 4
Clicked Next .
A new error message appeared:
Clicked Yes .
And a warning message appeared:
Clicked OK .
Step 5: Database Connection Details
The following screen appeared, and filled in the appropriate details:
Clicked Next .
Step 6: Port Configuration Details
The following screen appeared:
Clicked Next to accept the defaults.
Step 7: Review
The following screen appeared:
Clicked Configure .
Step 8: Installation
No image was captured of the installation. When completed, the installer immediately jumped to the next step.
Step 9: Finish
After a while, the following screen appeared:
Clicked Close .
Other Actions
Firewall Settings
Instead of following the procedure in 08 Configure Firewall Rules , I just turned off the firewall as follows:
service iptables stop chkconfig iptables off
Clean up Agent on GRIDCTRL
I removed the old installation of the OEM agent on GRIDCTRL as follows:
rm -fR /opt/oracle/app/agent
The installation of the OEM agent presented no problems.