Skip to main content

DROP RESTORE POINT AND DELETING ALL THE ARCHIVE LOGS USING RMAN IN ORACLE


DROP RESTORE POINT AND DELETING ALL THE ARCHIVE LOGS USING RMAN IN ORACLE AND TURN OFF FLASHBACK AND ARCHIVE LOG MODE

SQL> select name from v$database;

NAME
---------
PMITCKU

SQL> column NAME format a40;
SQL> SELECT NAME, SCN, TIME, DATABASE_INCARNATION#,
              GUARANTEE_FLASHBACK_DATABASE, STORAGE_SIZE
              FROM V$RESTORE_POINT
              WHERE GUARANTEE_FLASHBACK_DATABASE='YES'
  ORDER BY TIME;  2    3    4    5

NAME                                            SCN
---------------------------------------- ----------
TIME
---------------------------------------------------------------------------
DATABASE_INCARNATION# GUA STORAGE_SIZE
--------------------- --- ------------
FEB09_2011                               2.2071E+10
09-FEB-11 02.08.02.000000000 PM
                    1 YES    382599168


SQL> SELECT NAME FROM V$RESTORE_POINT WHERE GUARANTEE_FLASHBACK_DATABASE='YES'  ORDER BY TIME;

NAME
----------------------------------------
FEB09_2011

SQL> DROP RESTORE POINT FEB09_2011;

Restore point dropped.

irutdbapvn1.back.tickets.com@/home/oracle: $ORACLE_HOME/bin/rman

RMAN> connect target /

connected to target database: PMITCKU (DBID=2999848811)

RMAN> delete noprompt archivelog all;

using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=132 devtype=DISK

List of Archived Log Copies
Key     Thrd Seq     S Low Time  Name
------- ---- ------- - --------- ----
1       1    722     A 09-FEB-11 +FLASHBACK/pmitcku/archivelog/2011_02_09/thread_1_seq_722.12683.742659745
2       1    723     A 09-FEB-11 +FLASHBACK/pmitcku/archivelog/2011_02_09/thread
3       1    724     A 09-FEB-11 +FLASHBACK/pmitcku/archivelog/2011_02_09/thread
4       1    725     A 09-FEB-11 +FLASHBACK/pmitcku/archivelog/2011_02_09/thread
5       1    726     A 09-FEB-11 +FLASHBACK/pmitcku/archivelog/2011_02_10/thread
6       1    727     A 10-FEB-11 +FLASHBACK/pmitcku/archivelog/2011_02_10/thread
7       1    728     A 10-FEB-11 +FLASHBACK/pmitcku/archivelog/2011_02_10/thread
deleted archive log
archive log filename=+FLASHBACK/pmitcku/archivelog/2011_02_09/thread_1_seq_722.1
deleted archive log
archive log filename=+FLASHBACK/pmitcku/archivelog/2011_02_09/thread_1_seq_723.1
deleted archive log
archive log filename=+FLASHBACK/pmitcku/archivelog/2011_02_09/thread_1_seq_724.5
deleted archive log
archive log filename=+FLASHBACK/pmitcku/archivelog/2011_02_09/thread_1_seq_725.4
deleted archive log
archive log filename=+FLASHBACK/pmitcku/archivelog/2011_02_10/thread_1_seq_726.6
deleted archive log
archive log filename=+FLASHBACK/pmitcku/archivelog/2011_02_10/thread_1_seq_727.2
deleted archive log
archive log filename=+FLASHBACK/pmitcku/archivelog/2011_02_10/thread_1_seq_728.9
Deleted 7 objects


RMAN> exit


Recovery Manager complete.

SQL> select name from v$database;

NAME
---------
PMITCKU

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP MOUNT
ORACLE instance started.

Total System Global Area 1577058304 bytes
Fixed Size                  1273900 bytes
Variable Size             251662292 bytes
Database Buffers         1308622848 bytes
Redo Buffers               15499264 bytes
Database mounted.
SQL> alter database flashback off;

Database altered.

SQL> alter database noarchivelog;

Database altered.

SQL> ALTER DATABASE OPEN;

Database altered.

SQL> select name from v$database;

NAME
---------
PMITCKU

SQL>

Labels:

Comments

Post a Comment

Popular posts from this blog

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG...
Post a Comment
Read more

ORA-01143: cannot disable media recovery - file 1 needs media recovery

I got a request from the client - To flashback the database to the existing restore point & disable flashback and archive log mode for database UATB. Here I came a cross error - ORA-01143. I followed the below steps. 1. SQL> select name from v$database; NAME ------------ UATB 2. SQL> SELECT NAME FROM V$RESTORE_POINT WHERE GUARANTEE_FLASHBACK_DATABASE='YES' ORDER BY TIME; NAME --------- UATB_COPY Here I'm going to restore the database to the above restore point. NOTE: The flashback database restore has to be done in MOUNT stage of the database. SQL> select name from v$database; NAME --------- UATB SQL> shut immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> startup mount ORACLE instance started. Total System Global Area  612368384 bytes Fixed Size                  1250428 bytes Variable Size             167775108 bytes ...
2 comments
Read more