Skip to Main Content

Oracle Database Discussions

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!

How to force DROP a user?

Beauty_and_dBestMay 20 2017 — edited May 20 2017

Hi ALL,

12c

I am dropping a db user, but it is stubborn to be dropped

SQL> drop user BOM cascade;

drop user BOM cascade

*

ERROR at line 1:

ORA-00600: internal error code, arguments: [16662], [kqldrsu], [4], [0],

[30357], [], [], [], [], [], [], []

Errors in file /home/orasales/SALES/12.1.0/admin/SALES_sales2/diag/rdbms/sales/SALES/trace/SALES_ora_1571.trcĀ  (incident=7477):

ORA-00600: internal error code, arguments: [16662], [kqldrsu], [4], [0], [30357], [], [], [], [], [], [], []

Incident details in: /home/orasales/SALES/12.1.0/admin/SALES_sales2/diag/rdbms/sales/SALES/incident/incdir_7477/SALES_ora_1571_i7477.trc

Non critical error ORA-48913 caught while writing to trace file "/home/orasales/SALES/12.1.0/admin/SALES_sales2/diag/rdbms/sales/SALES/incident/incdir_7477/SALES_ora_1571_i7477.trc"

Error message: ORA-48913: Writing into trace file failed, file size limit [10485760] reached

Writing to the above trace file is disabled for now on...

Use ADRCI or Support Workbench to package the incident.

See Note 411.1 at My Oracle Support for error and packaging details.

Sun May 21 01:59:40 2017

Dumping diagnostic data in directory=[cdmp_20170521015940], requested by (instance=1, osid=1571), summary=[incident=7477].

Sun May 21 01:59:41 2017

Sweep [inc][7477]: completed

Sweep [inc2][7477]: completed

Why is this error happening?

Please help...

Kind regards,

jc

This post has been answered by John Thorton on May 20 2017
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 17 2017
Added on May 20 2017
7 comments
1,754 views