EM 12c: RepManager Dropall Command Fails to Drop all the Enterprise Manager 12c Cloud Control Repository Objects

(Doc ID 1365820.1)

Last updated on JANUARY 06, 2017

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.1.0 and later
Information in this document applies to any platform.

Symptoms

Dropping the Enterprise Manager (EM) 12c Cloud Control Repository using "RepManager dropall" command does not drop all repository objects:

cd <OMS_HOME>/sysman/admin/emdrep/bin
RepManager repomachine.domain 1521 orcl -action dropall -dbUser sys -dbPassword oracle123 -dbRole sysdba -mwHome /home/oracle/Middleware
-mwOraHome /home/oracle/Middleware -oracleHome /home/oracle/Middleware/oms

Terminal output shows:
==================
............
processing arguments
.
action logger filename finally: emschema.log
filename: /home/oracle/Middleware/oms/sysman/log/schemamanager/emschema.log
newly created: /home/oracle/Middleware/oms/sysman/log/schemamanager/emschema.log
Driver: oracle.jdbc.driver.OracleDriver
jdbcUrl = jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(Host=repomachine.domain)(Port=1521)))(CONNECT_DATA=(SID=orcl)))
action to perform is: drop
action is non-transx - RCU based action
logger null: check if repos user exists..
logger null: found connection for DB user
logger null: query DB for repos user existence check
logger null: REPOS_CONN is null in check repos user... creating new one
jdbcUrl = jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(Host=repomachine.domain)(Port=1521)))(CONNECT_DATA=(SID=orcl)))
jdbcUrl = jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(Host=repomachine.domain)(Port=1521)))(CONNECT_DATA=(SID=orcl)))
logger null: connection is found null
Error found: Validation Failure for Action: [DROP]. The reason for failure was: [null repos-connection found]

Dropping MDS schema...
.
RCU Logfile : /home/oracle/Middleware/oms/emmds.log
Component schemas dropped:
Component Status Logfile
Metadata Services Success /home/oracle/Middleware/oms/mds.log
Repository Creation Utility - Drop : Operation Completed

Dropping OPSS schema...
.
RCU Logfile : /home/oracle/Middleware/oms/cfgtoollogs/cfgfw/emsecrepmgr.log
Component schemas dropped:
Component Status Logfile
Oracle Platform Security Services Success /home/oracle/Middleware/oms/cfgtoollogs/cfgfw/opss.log
Repository Creation Utility - Drop : Operation Completed
Successfully dropped schema

Dropping APM schema...
.
RCU Logfile : /home/oracle/Middleware/oms/cfgtoollogs/cfgfw/emsecrepmgr.log
Component schemas dropped:
Component Status Logfile
Authorization Policy Manager Success /home/oracle/Middleware/oms/cfgtoollogs/cfgfw/apm.log
Repository Creation Utility - Drop : Operation Completed
Successfully dropped schema

Dropping BIP schema...
.
Repository Creation Utility - Checking Prerequisites
Checking Global Prerequisites
RCU-6013:Specified prefix does not exist. Existing prefixes are: None
RCU-6091:Component name/schema prefix validation failed.

===========
- In the database, following repository users still exist:
SQL> select username,account_status from dba_users
where username like '%SYSMAN%';

USERNAME           ACCOUNT_STATUS
---------------    -----------------
SYSMAN             OPEN
SYSMAN_RO          EXPIRED & LOCKED

 

-  There are no errors reported on the terminal or in any of the log files generated by the RepManager:

<OMS_HOME>/emmds.log
<OMS_HOME>/cfgtoollogs/cfgfw/opss.log
<OMS_HOME>/cfgtoollogs/cfgfw/emsecrepmgr.log
<OMS_HOME>/cfgtoollogs/cfgfw/apm.log


All the log files show that the drop operation has been completed successfully.

-  The BIP schema log <OMS_HOME>/embiplatform.log reports the following error:

ERROR rcu: oracle.sysman.assistants.rcu.backend.RCUCommandLineParser::setComponentSelections: RCU-6013:Specified prefix does not exist. Existing prefixes are: None

This error can be ignored as it occurs if the BIP user (for Oracle BI Publisher) has not been configured in the Cloud Console. As the user does not exist, attempting to drop it fails with "RCU-6013:Specified prefix does not exist"

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms