Skip to Main Content

Enterprise Manager

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

12c Cloud Control install: How to drop SYSMAN?

1165010Mar 19 2014 — edited Mar 20 2014

Hello,

This is my current error:

/apps/oracle/Middleware/oms/sysman/install/ConfigureGC.sh -silent -responseFile /home/oracle/new_install.rsp  Starting Oracle Universal Installer...                                                                                                 
Checking Temp space: must be greater than 400 MB.   Actual 12829 MBPassed
Checking swap space: must be greater than 150 MB.   Actual 2046 MBPassed

ERROR: ERROR:SQLException null Resultset

Unable to connect to the database and validate whether it is a supported database due to one of the following reasons:

(1) Incorrect credentials
(2) Listener may be down
(3) Database may be down

Check the credentials ,the status of the listener and the database and retry.

I'm fairly certain the issue is because the 'SYSMAN' user still exists in the target db:

Stuck at Configuration Details when installing Enterprise Manager 12c linux

So I'm trying to drop the SYSMAN user in several ways, but its failing each way:

Method 1:

/apps/oracle/Middleware/oms/sysman/admin/emdrep/bin/RepManager   ....

processing arguments

compiling arguments for validation

Enter password for: SYS                                                                                                                   done checking required user credentials...

done creating arguments...

creating logger..

Connection exception in  action logger path calculated: /apps/oracle/Middleware/oms/sysman/log/schemamanager/

action logger path calculated: /apps/oracle/Middleware/oms/sysman/log/schemamanager/

action logger path calculated finally: /apps/oracle/Middleware/oms/sysman/log/schemamanager/

no action logger file name from previous session

action logger filename after search: emschema.log

action logger filename finally: emschema.log

filename: /apps/oracle/Middleware/oms/sysman/log/schemamanager/emschema.log

newly created: /apps/oracle/Middleware/oms/sysman/log/schemamanager/emschema.log

Driver: oracle.jdbc.driver.OracleDriver

...

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: executing: SELECT HOST_NAME, STATUS FROM sysman.mgmt_oms_states where APPLICATION_TYPE='console'

logger null: found exception : ORA-00942: table or view does not exist

logger null: found exception in all OMS up check: ORA-00942: table or view does not exist

Error found: Validation Failure for Action: [DROP]. The reason for failure was: [ORA-00942: table or view does not exist

*  I did manually drop all the objects belonging to  SYSMAN which is probably why this error is thrown.

Method 2:

[oracle@orahc01a ~]$ emca -repos drop ...

The properties file /u01/app/oracle/product/11.2.0.3/dbhome_1/sysman/config/emcalog.properties needed to initialize the EMCA logger was not found.  Default settings will be used

STARTED EMCA at Mar 19, 2014 7:06:01 PM

EM Configuration Assistant, Version 11.2.0.3.0 Production

Copyright (c) 2003, 2011, Oracle.  All rights reserved.

Exception in thread "main" java.lang.NoClassDefFoundError: oracle/sysman/emSDK/util/jdk/Platform

        at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:570)

        at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:529)

* I don't care to fix this issue since I wont be using its local emca tool once Cloud Control is up:

Method 3 :

> startup restricted;

SQL> drop user SYSMAN cascade;

drop user SYSMAN cascade

*

ERROR at line 1:

ORA-01940: cannot drop a user that is currently connected

Elapsed: 00:00:00.00

* and verified no jobs/sessions currently running that belong to SYSMAN yet it manages to connect still. Even trying revoking all its privileges, to no avail.

Can you please  confirm dropping the SYSMAN user is the root of my /ConfigureGC error, and if so, how to get rid of SYSMAN?

Thanks!

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Apr 17 2014
Added on Mar 19 2014
9 comments
7,001 views