Impossible to drop the undo tablespace

Similar Questions

• The UNDO tablespace and its data file cannot be removed

  I would like to delete an UNDO tablespace after you have created a new, but can't. I could follow a large number of instructions TOM and others, but tablepspace is still listed in the State to RECOVER. Please see what I've done below. Your help will be appreciated.
  

  SQL > drop tablespace UNDOTBS2;
  Drop tablespace UNDOTBS2
  *
  ERROR on line 1:
  ORA-01548: active rollback segment "_SYSSMU29_1272378969$" found, terminate
  drop the tablespace

  SQL > drop rollback segment "_SYSSMU29_1272378969$";
  Drop rollback segment "_SYSSMU29_1272378969$".
  *
  ERROR on line 1:
  ORA-30025: DROP segment ' _SYSSMU29_1272378969$ ' (in the undo tablespace) not
  permit

  Have you tried that
  http://arjudba.blogspot.com/2008/08/ora-01548-active-rollback-segment.html

• undo_segments in the undo tablespace

  (1) at least how undo_segments in undo tablespace?

  Is optimal?
  If I increase the size of the undo tablespace, undo_segments counts also have increased!

  Version of DB is 10g

  Hello

   

  The two time oracle maintains exactly 10 segments. (you can see nom_segment begins by _SYSSMU11)

  I'm not clear on what exactly 10 segments. I have undo tablespace of ~ 250 GB with 6676 stored in dba_rollback_segs.

  3) why undo tablespace with the only spaceMo 46,8125 '?

  
  

  (4) I mean why he is stiil 450Mo undo_retention even through time or same validation has occurred?

  Just Oracle - Doc

  Once a transaction is committed, the undo data are more necessary for purposes of recovery rollback or transaction. However, for consistent read purposes, long-running queries may require old undo information to produce older images of data blocks. In addition, the success of several Oracle Flashback features can also depend on the availability of the old cancellation information. For these reasons, it is desirable to keep the old information of cancellation for as long as possible.

  Introduction to the management of the automatic cancellation

  With undo tablespace, you would see extended with the status ACTIVE, EXPIRED, extents still to RUN.

  Active cancellation extended are used by transactions and will be always active, because they are needed for the restoration.

  Extensions has expired are not used by transactions, the data contained in these extended is committed and the time UNDO_RETENTION is passed, so it is not necessary for the coherence of reading and can be reused.

  Not expired extensions are extended no assets but honor UNDO_RETENTION. Transactions belonging to these bodies of cancellation are determined, but the retention time has failed, and it may be necessary for the coherence of reading!

  Paste the query result - below

  ! undo_extent_stat.SQL more

  status of collar for a30

  Select the State,

  round (sum_bytes / (1024 * 1024), 0) like MB,.

  Tour ((sum_bytes / undo_size) * 100, 0) as PERC

  Of

  (

  Select the State, sum (bytes) sum_bytes

  of dba_undo_extents

  Status group

  ),

  (

  Select sum (a.bytes) undo_size

  from dba_tablespaces c

  Join v$ tablespace b on b.name = c.tablespace_name

  Join v$ datafile on a.ts # b.ts = #.

  where c.contents = 'UNDO '.

  and c.status = 'ONLINE '.

  );

  Anand

• Changing data in the undo tablespace or db Oracle buffer cache

  Hello
  
  I have serious doubt in the feature of oracle architecture, when a user issues an update statement, the data blocks are transported to the db buffer cache and where the data changes are made? Made a copy data block is stored in the cache db pads and the changes are made to the block in the buffer cache? or the copy of the data block is stored in the undo tablespace and changes are made to the blocks in the undo tablespace?
  
  In singles, the changes to the data blocks are make to the db or undo tablespace buffer cache?
  
  
  Thanks in advance
  
  Kind regards
  007

  Did you have a look to the Internet for the answer?

  In short, if a trial Oracle wants to update a record in the table, it does:

  -Read the record to be changed in the buffercache
  -Audits (the record already locked, is the update allowed)
  -Put the folder (called image before) in a rollback in the UNDO tablespace segment
  -Writing redo information about this change in the UNDO tablespace
  -Lock the record
  -Write the change in registration in the buffer cache
  -Put the change also in the redo buffer
  S ' sit and wait... (for a commit or a rollback)

  When are committed:
  -Release the lock
  -Empty folder of restoration since the UNDO tablespace
  -Write a record of this change forward in the UNDO tablespace

  When rollback:
  -Release the lock
  -Rinse the record changed the buffercache
  -Read the original value
  -Empty folder of restoration since the UNDO tablespace
  -Write a record of this change forward in the UNDO tablespace

  It of here, some more specific complexity when a checkpoint occurs between the change and the commit / rollback or redo buffer has been emptied for redo files

  Please any other s/n, correct me if I'm wrong...

  See you soon
  FJFranken

• How to reduce the UNDO Tablespace

  Hello
  We had an UNDO Tablespace to 22 GB but it's using just 2GB. How to shrink the undo tablespace. We use the database in production cluster 3 node 10.2.0.4
  Is there is way we can worry about UNDO Tablespace or should I create an UNDO tablespace and assign the undo tablespace to DB and let fall the old CANCEL?
  How to ensure that the transactions are done and free to abandon the old CANCEL?
  That's what we must restart all three nodes each node has its own UNDO Tablespace.
  
  Need help on this issue.
  
  would appreciate your quick response.
  
  
  Thank you

  No you have not.

  concerning
  Mohamed

• Cannot drop the USERS tablespace.

  Hi all
  
  I am trying to drop tablespace USERS and in the face of error below.
  
  PLATFORM:
  OS: Linux Ubuntu 9.04, LTS
  SQL > select * from v version $;
  
  BANNER
  ----------------------------------------------------------------
  Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
  PL/SQL Release 10.2.0.1.0 - Production
  CORE 10.2.0.1.0 Production
  AMT for Linux: Version 10.2.0.1.0 - Production
  NLSRTL Version 10.2.0.1.0 - Production
  
  PROBLEM:
  SQL > drop tablespace users, including content and files of data cascade constraints;
  Drop tablespace users including data files and content cascade constraints
  *
  ERROR on line 1:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-24005: must use DBMS_AQADM. DROP_QUEUE_TABLE to drop queue tables
  
  
  When I see, dba_queue_tables...
  SQL > select the owner, queue_table from dba_queue_tables object_type.
  
  OWNER OBJECT_TYPE QUEUE_TABLE
  ------------------------------ ------------------------------ -------------------------------------------------------------
  SYS ALERT_QT SYS. ALERT_TYPE
  SYS AQ$ _MEM_MC
  SYS AQ_EVENT_TABLE SYS. AQ$ _EVENT_MESSAGE
  SYS AQ_SRVNTFN_TABLE SYS. AQ$ _SRVNTFN_MESSAGE
  SYS KUPC$ DATAPUMP_QUETAB SYS. KUPC$ _MESSAGE
  SCHEDULER SYS $_EVENT_QTAB SYS. PLANNER$ _EVENT_INFO
  SCHEDULER SYS $_JOBQTAB SYS. ANYDATA
  SYS SYS$ SERVICE_METRICS_TAB SYS. SYS$ RLBTYP
  SYSMAN MGMT_NOTIFY_QTABLE SYSMAN. MGMT_NOTIFY_NOTIFICATION
  SYSTEM DEF$ _AQCALL
  DEF SYSTEM $ _AQERROR
  
  11 selected lines.
  
  Also, there no tables in the tablespace USERS now, as I moved to another tablespace.
  SQL > select count (*) from dba_tables where nom_tablespace = 'USERS ';
  
  COUNT (*)
  ----------
  0
  
  Tablespace USERS is not permanent tablespace, as I changed to another, always the problem.
  SQL > select property_name, name from database_properties where PROPERTY_NAME = 'DEFAULT_PERMANENT_TABLESPACE. '
  
  PROPERTY-NAME NAME
  ------------------------------ ------------------------------
  DEV DEFAULT_PERMANENT_TABLESPACE
  
  
  Can you please help me drop the USERS tablespace.

  Hi boss,

  Please find the solution for the same problem, but by dropping the user. Try the same for the Tablespace too.

  SQL > drop user cascade COLOMBO_LIVE;
  drop the waterfall COLOMBO_LIVE user
  *
  ERROR on line 1:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-24005: must use DBMS_AQADM. DROP_QUEUE_TABLE to drop queue tables

  SQL > select object_name from user_OBJECTS;

  OBJECT_NAME
  -------------------------------------------------------------------------

  MYQ
  SYS_LOB0001130873C00025$ $
  SYS_C001810004

  SQL > drop table myq;
  drop table myq
  *
  ERROR on line 1:
  ORA-24005: must use DBMS_AQADM. DROP_QUEUE_TABLE to drop queue tables

  SQL > exec sys. DBMS_AQADM. DROP_QUEUE_TABLE (queue_table-online 'MYQ', force-online TRUE);

  PL/SQL procedure successfully completed.

• Block in the Undo tablespace corruption

  Dear all,
  
  
  I'm using oracle 10.1.0.2.0. Today because of the abnormal termination block corrouption in undo tablespace found and database will not open.
  In the alert log file
  
  Errors in the e:\oracle\product\10.1.0\admin\orc1\udump\orc1_ora_3188.trc file:
  ORA-01578: block ORACLE (corrupted file # 37, block # 25) data
  ORA-01110: data file 37: ' E:\ORACLE\PRODUCT\10.1.0\ORADATA\ORC1\UNDOTBS0. DBF'
  
  Sea Jul 07 10:18:42 2010
  1578 error happened during db open, close the database
  USER: termination litigation because of the 1578 error
  Sea Jul 07 10:18:43 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_arc3_3900.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:43 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_arc3_3900.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:43 2010
  Arc0: Assessment of the archive log 2 sequence of thread 1 479
  Sea Jul 07 10:18:43 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_dbw0_3692.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:43 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_ckpt_1552.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:43 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_mman_3912.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:44 2010
  Newspapers archived by another process
  Sea Jul 07 10:18:44 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_pmon_3744.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:44 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_arc1_3668.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:44 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_arc1_3668.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:45 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_reco_1076.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:45 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_smon_2660.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Sea Jul 07 10:18:45 2010
  Errors in the e:\oracle\product\10.1.0\admin\orc1\bdump\orc1_lgwr_1796.trc file:
  ORA-01578: ORACLE data block corrupted (file #, block #)
  
  Instance of stopped by USER, pid = 3188
  ORA-1092 marked during: ALTER DATABASE OPEN...
  
  Concerning

  Errors in the e:\oracle\product\10.1.0\admin\orc1\udump\orc1_ora_3188.trc file:
  ORA-01578: block ORACLE (corrupted file # 37, block # 25) data
  ORA-01110: data file 37: ' E:\ORACLE\PRODUCT\10.1.0\ORADATA\ORC1\UNDOTBS0. DBF'

  You have rman or backup to hot/cold? If so try like:
  * 1.*

  sqlplus "/as sysdba"
  shutdown immediate;
  startup mount;
  /*restore undo datafile then*/
  recover datafile 37;
  alter database open;
  

  * 2 If you have backup rman, then try

  rman terget /
  blockrecover datafile 37 block 25;
  

  * 3.* If you don't have a backup, you can start your database without this undo tablespace.

  1. backup current database;

  2. change pfile (parameter file) change undo_tablespace and undo_management as:

  undo_management=manual
  undo_tablespace=UNDOTBS2
  

  If you do not use pfile create pfile from spfile as:

  sqlplus "/as sysdba"
  create pfile='pfilelocation' from spfile='spfilelocation';
  

  3. then start database as:

  Connected to:
  Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
  With the Partitioning, OLAP and Data Mining options
  
  SQL> shutdown immediate;
  Database closed.
  Database dismounted.
  ORACLE instance shut down.
  SQL> startup mount pfile D:\oracle\product\10.2.0\admin\TEST\pfile\init.ora.5162
  010113556
  SP2-0714: invalid combination of STARTUP options
  SQL> startup mount pfile= D:\oracle\product\10.2.0\admin\TEST\pfile\init.ora.516
  2010113556
  ORACLE instance started.
  
  Total System Global Area  138412032 bytes
  Fixed Size                  1288172 bytes
  Variable Size              62916628 bytes
  Database Buffers           67108864 bytes
  Redo Buffers                7098368 bytes
  Database mounted.
  SQL> alter database open;
  alter database open
  *
  ERROR at line 1:
  ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
  ORA-01110: data file 2: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\UNDOTBS01.DBF'
  
  SQL> select name from v$datafile;
  
  NAME
  --------------------------------------------------------------------------------
  
  D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\SYSTEM01.DBF
  D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\UNDOTBS01.DBF
  D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\SYSAUX01.DBF
  D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\USERS01.DBF
  
  SQL> alter database datafile
  'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\UNDOTBS01.DBF' offline drop;
  
  Database altered.
  
  SQL> alter database open;
  
  Database altered.
  
  SQL> create undo tablespace UNDOTBS2
  datafile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\UNDOTBS2' size 200M;
  
  Tablespace created.
  
  SQL> create spfile from pfile;
  
  File created.
  
  SQL>
  

• It will frequently commit resolve ora-30036 (cannot extend the undo tablespace)

  I use 11.2.0.3 database. I confused on the use of validation to resolve ora-30036.

  I have the script in migration once that has many updates and I'm getting ORA-30036 (unable to extend segment by 4 in the "UNDOTBS" undo tablespace) .

  Our undo tablespace in NO mode autoextend and like this is just a one time event, we will not increase it.   He is currently 6 GB.

  We would commit determination ORA-30036 in my case? If not why? Is there a better solution to solve it.

  
  

  When I say commit frequent, I won't commit after each line, I just want to commit after may be million lines, so that my active cancellation extend turn into cancellation remaining will extend and Oracle will be able to use it in case of pressure of space.

  
  

  Note:

  UNDO_MANAGEMENT: AUTO

  UNDO_RETENTION: 2700

  Undo tablespace retention is NOGAURANTEE.

  I have the script in migration once that has many updates and I'm getting ORA-30036 (unable to extend segment by 4 in the "UNDOTBS" undo tablespace).

  Our undo tablespace in NO mode autoextend and like this is just a one time event, we will not increase it.   He is currently 6 GB.

  Why don't you increase it?

  You must use the correct size of UNDO necessary for the work that will be done.

  A lot of shops to create a for big lots new UNDO tablespace and then switch to it for batch processing. Once the task is completed, they switch back to the normal UNDO. That prevents the normal RETURN of autoextending far where it is normally necessary:

  ALTER SYSTEM SET UNDO_TABLESPACE

• Application of segment SS Enqueue and fate on 8.1.7.4 after attempting to drop the temp tablespace

  We have a case opened with the support of the Oracle, but I thought I'd throw it out there if it's ok.

  We have a 8.1.7.4 database running on HP - UX 11.11 PA-Risc and it looks like any session that wants to use a temp space is hung a SS enqueue or in some cases is waiting on a waiting "sort request of the segment.

  Saturday, we tried to move all users to a new temporary tablespace and drop the old one but the drop suspended and we control-C out of it.  We put the users to the original temp.  Note that both the old and the new temporary tablespaces are managed locally.

  Before trying to leave falling the old tablespace temp that we killed the existing sessions, including one who had worked for two weeks and has been hooked on SMON.

  Query v$ fast_start_transactions and x$ ktuxe indicate that SMON is back any large transaction.

  In addition, SMON seems to run this query always:

  SELECT file #, block #, LENGTH

  The UET $

  WHERE the ts # =: 1 AND segfile # =: 2 AND segblock # =: 3 AND ext # =: 4

  Here are the locks held by SMON for what it's worth:

  ADDR KADDR SID TY ID1 ID2 LMODE CTIME BLOCK REQUEST
  ---------------- ---------------- ---------- -- ---------- ---------- ---------- ---------- ---------- ----------
  C000000028C43CD8 C000000028C43CF8 74 16 4 0 59610 TT 8 0
  C000000028C43C68 C000000028C43C88 TS 74-666633304 8 6 0 0 59650
  C000000028C1CB38 C000000028C1CB58 8 ST 0 0 6 0 13 0

  ST, space management Transaction
  TS, temporary Segment (also TableSpace)
  TT, temporary Table

  Same database has a recovery scenario about a month or to go back due to some deleted data files.  Also, during the holidays, we had to rebuild a global index huge and increased our tablespace temp to get it, which is why we strive to reduce now create a smaller.  In addition, creating index was still holding in the tablespace existing managed dictionary so we ended up move the index to a managed locally.  Also, UET$ has about 33,000,000 lines and most of the data is in the dictionary managed tablespaces.  Dba_free_space queries typically take 30 minutes to return - that is, we know it is messed up and has been so for a long time.

  Pleasure for us.  If anyone has an idea that would be great.

  -Bobby

  Tablespace name I really used corresponded to ts #= 74 in v$ tablespace.

  We plan to rebuild the other indexes in this space in a new locally managed tablespace and then drop the tablespace existing managed dictionary.  My only question is whether corruption will drop the tablespace to fail.

  Hi Bobby,.

  I'm not sure of your current situation hope now, that's better.

  I couldn't find the time to reply back yesterday. Looking at the huge amounts of temporary segments in your tablespace (74), just made me think if you or Support of Oracle were you made aware of an event DROP_SEGMENTS which is an event of users can invoke to clear temporary segments. It deletes the temporary segments such as the SMON in the background. This event has the advantage of not having the CPU consumed by SMON.

  47400.1 Note : EVENT: DROP_SEGMENTS - forcing cleanup of TEMPORARY segments

  There is also a method to the dictionary (changes) patch (not recommended if not). You can enlist the help of Oracle Support

  The method is to identify the segment (which you already have) and update the segment_type from temporary to 999.

  388619.1 Note: last resort when SMON takes 100% of CPU

  Kind regards

  Suntrupth

• ORA-01555 - Tuning for the UNDO tablespace.

  Dear DBA Kings/Queens,
  
  I often "ORA-01555 snapshot too old error" due to the special delete statement. Which removes the lines about 50 000 all day as a batch. Eventhough, I reduced to 50 000 to 10 000 and 1000. No luck.
  Can someone tell me how to set UNDO tablespace.
  -----------------------------------------------------------------------------
  Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64 bit Production
  PL/SQL Release 9.2.0.7.0 - Production
  CORE 9.2.0.7.0; Production
  AMT for Solaris: release 9.2.0.7.0 - Production
  NLSRTL Version 9.2.0.7.0 - Production
  -----------------------------------------------------------------------------
  SQL > show Cancel parameter
  
  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  UNDO_MANAGEMENT string AUTO
  UNDO_RETENTION integer 10800
  undo_suppress_errors Boolean TRUE
  undo_tablespace string UNDOTBS1
  -----------------------------------------------------------------------------
  
  Size in GB:
  
  TOTAL USED FREE USED_PCNT NOM_TABLESPACE
  ------------------------------ ---------- ---------- ---------- ----------
  UNDOTBS1 13.5; 1.34; 12.17; 9.89

  Which removes the lines about 50 000 all day as a batch

  Has often committed?
  -do not commit frequently.

  -Increase the setting "undo_retention.

  -reduce the duration of operation (plan use of execution to check your query)... perhaps may create index. Or to commit all the 5000 rows

  -For collecting statistics on the table

  Edited by: Surachart Opun (HunterX) July 23, 2009 12:04 AM

• Impossible to drop the user after abruptly stop (Ctrl + C) impdp oracle 12.1.0.1.0.

  Hello Experts-

  Help me please drop the user.

  SQL > select sid from session $ v where username = "POLICY";

  no selected line

  SQL > drop user cascade of POLICY;

  drop the cascade of user POLICY

  *

  ERROR on line 1:

  ORA-00604: an error has occurred at the SQL level 1 recursive

  ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired

  Read the error message; the error is not about removing a user, it's dropping of the user OBJECTS, which were used at the time of the fall of attempt.  Import (so an insertion) was interrupted while Oracle has roll back the transaction, which takes time and locks the object.  Once the restore is complete, the locks have been released and the user, as well as all the objects for this user, could be deleted.

  David Fitzjarrell

• Impossible to drop the user in TimesTen

  Hi all
  
  I created a data store: "tt_demo."
  Created a user: 'test' and he granted "Admin, connect, create table, select on SYS. $OBJ ".
  Created a simple table: emp and inserted two records.
  
  Now, I need to drop this user, so I plugged to the data as a store below:
  
  [*oracle*@exalytics bin] $. / ttisql
  Command > Connect "dsn = tt_demo";
  Successful login: DSN = tt_demo; UID = oracle;...
  
  But when I try to drop the user I get following errors:
  
  Order > drop user test.
  15168: cannot remove a user who has database objects (TABLE TEST. EMP)
  The command failed.
  Order > drop user test cascade;
  805: DROP USER... CASCADE has not been implemented
  The command failed.
  
  CASCADE is not supported by the TTT?
  Can someone let me know the solution for this?
  
  FYI, Version TT: 11.2.2.4.1
  
  Thank you
  Srikanth

  According to the error message we have yet not DROP USER... CASCADE.

  So to remove a user, you must first delete all the objects belonged to this user.

  Chris

• Impossible to drop the disc?

  env: 11.2.0.2.3
  
  I have a redundancy normal diskgroup (asm/RDBMS compatibility set to 11.2.0.0) containing two discs, it's everyone in own failgroup.
  I've tested the disk_repair_time attribute and took one of the disks in the group offline and waited until the expiration of the timer - to see if the disc - Oracle and test how I can recover from this situation if the drive was missing.
  
  Then I took the LOG2 drive off line and waited...
  
  ASM alerts log, I see:

  Fri Sep 09 09:59:21 2011
  WARNING: Disk (LOG2) will be dropped in: (168) secs on ASM inst: (1)
  Fri Sep 09 10:00:55 2011
  WARNING: Disk (LOG2) will be dropped in: (74) secs on ASM inst: (1)
  Fri Sep 09 10:02:27 2011
  WARNING: PST-initiated drop of 1 disk(s) in group 3(.467124207))
  SQL> alter diskgroup LOG drop disk LOG2 force /* ASM SERVER */
  NOTE: GroupBlock outside rolling migration privileged region
  NOTE: requesting all-instance membership refresh for group=3
  Fri Sep 09 10:02:29 2011
  GMON updating for reconfiguration, group 3 at 30 for pid 33, osid 13932
  NOTE: group LOG: updated PST location: disk 0000 (PST copy 0)
  NOTE: group 3 PST updated.
  Fri Sep 09 10:02:29 2011
  NOTE: membership refresh pending for group 3/0x1bd7bfef (LOG)
  GMON querying group 3 at 31 for pid 18, osid 10302
  SUCCESS: refreshed membership for 3/0x1bd7bfef (LOG)
  SUCCESS: alter diskgroup LOG drop disk LOG2 force /* ASM SERVER */
  SUCCESS: PST-initiated drop disk in group 3(467124207))
  NOTE: Attempting voting file refresh on diskgroup LOG
  NOTE: starting rebalance of group 3/0x1bd7bfef (LOG) at power 1
  Starting background process ARB0
  Fri Sep 09 10:02:34 2011
  ARB0 started with pid=37, OS id=14883
  NOTE: assigning ARB0 to group 3/0x1bd7bfef (LOG) with 1 parallel I/O
  Fri Sep 09 10:02:40 2011
  NOTE: GroupBlock outside rolling migration privileged region
  NOTE: requesting all-instance membership refresh for group=3
  Fri Sep 09 10:02:40 2011
  NOTE: stopping process ARB0
  SUCCESS: rebalance completed for group 3/0x1bd7bfef (LOG)
  Fri Sep 09 10:02:43 2011
  GMON updating for reconfiguration, group 3 at 32 for pid 38, osid 14888
  NOTE: group LOG: updated PST location: disk 0000 (PST copy 0)
  NOTE: group 3 PST updated.
  WARNING: offline disk number 1 has references (904 AUs)
  NOTE: membership refresh pending for group 3/0x1bd7bfef (LOG)
  GMON querying group 3 at 33 for pid 18, osid 10302
  SUCCESS: refreshed membership for 3/0x1bd7bfef (LOG)
  NOTE: Attempting voting file refresh on diskgroup LOG

  And from RDBMS alerts journal:
  

  Fri Sep 09 10:02:32 2011
  SUCCESS: disk LOG2 (1.2526490858) renamed to _DROPPED_0001_LOG in diskgroup LOG

  OK, check in asm v$ asm_disk:
  

  SYS@+ASM1 SQL>r
    1  select a.name "GroupName", a.state "GroupState",b.name,b.mount_status,b.header_status,b.mode_status,b.state "DiskState",b.repair_timer
    2  from v$asm_diskgroup a,v$asm_disk b
    3  where a.group_number = b.group_number
    4* order by a.name,b.name
  
  GroupName                      GroupState  NAME                           MOUNT_S HEADER_STATU MODE_ST DiskStat REPAIR_TIMER
  ------------------------------ ----------- ------------------------------ ------- ------------ ------- -------- ------------
  DATA                           MOUNTED     DATA1                          CACHED  MEMBER       ONLINE  NORMAL              0
  DATA                           MOUNTED     DATA2                          CACHED  MEMBER       ONLINE  NORMAL              0
  GRID                           MOUNTED     GRID3                          CACHED  MEMBER       ONLINE  NORMAL              0
  GRID                           MOUNTED     GRID4                          CACHED  MEMBER       ONLINE  NORMAL              0
  GRID                           MOUNTED     GRID_0001                      CACHED  MEMBER       ONLINE  NORMAL              0
  LOG                            MOUNTED     LOG1                           CACHED  MEMBER       ONLINE  NORMAL              0
  LOG                            MOUNTED     _DROPPED_0001_LOG              MISSING UNKNOWN      OFFLINE FORCING             0
  
  7 rows selected.
  
  
  SYS@+ASM1 SQL>select * from v$asm_operation;
  
  no rows selected

  So, why the disc always showing to v$ asm_disk if it fell? Or is it? I thought that Oracle should drop the disc at the expiration of the timer of the repair, but then why I always see it? I want to add the failed drive to return once again... How can I realize that, if the drive is still a member of the diskgroup of the NEWSPAPER?
  
  Thank you..
  
  Published by: AJ on 09.sep.2011 01:17

  Hello

  the reason behind this, is that a DISC will get status COWARD, if all valid content could be moved to another drive.
  However, in your case your LOG diskgroup consisted only of 2 discs (and 2 failgroups). So when access to a failgroup had disappeared, the whole failgroup was set to offline.
  Now when the repair timer expires the disks to be abandoned. However, it cannot be moved, because the data on the disk can not be moved to other disks.
  So what happens, is that your discs will be defined in the sense of "FORCING", as soon as the data can be rebalanced to another drive (maybe when you add a new drive), the drive really will be abandoned.

  Concerning
  Sebastian

• Impossible to drop the user

  I get the following error while dropping the user...
  
  SQL > drop user cascade ONAIR.
  drop the ONAIR user cascade
  *
  ERROR on line 1:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-24005: must use DBMS_AQADM. DROP_QUEUE_TABLE to drop queue tables
  
  
  I asked dba_queue_tables but her shows that r thr tables without current queue...
  
  
  Select queue_table from the dba_queue_tables where owner = "FLIGHT."
  
  no selected line
  
  DB version is 10.2.0.4.0 aix Server

  RUN THE SYS. DBMS_AQADM. DROP_QUEUE_TABLE (queue_table-online 'JOB_QUEUE_DATA', force-online TRUE);

• Impossible to drop the schema

  Hi all
  
  I'm trying to drop the schema but below error is coming
  
  (1) bdr_local > drop user cascade HILLS_ISSUE_TRACKER;
  drop the waterfall HILLS_ISSUE_TRACKER user
  *
  ERROR on line 1:
  ORA-00604: an error has occurred at the SQL level 1 recursive
  ORA-00069: could not acquire lock - tables turned off for B_ISSUE_COMMENTS locks
  
  bdr_local 2) > alter table HILLS_ISSUE_TRACKER. B_ISSUE_COMMENTS activate the table lock;
  ALTER table HILLS_ISSUE_TRACKER. B_ISSUE_COMMENTS activate the table lock
  *
  ERROR on line 1:
  ORA-00054: resource busy and acquire with NOWAIT specified
  
  bdr_local 3) > SELECT * FROM v lock $
  WHERE id1 = (SELECT FROM object owner object_id WHERE = 'HILLS_ISSUE_TRACKER' AND object_name = "B_ISSUE_COMMENTS"); 2
  
  no selected line
  
  I took the rebound of db to release the lock, if any. Please help if some body the same question.
  
  Thank you
  Jamsher.

  Something new to learn, thanks for sharing this.