The following query lists database files as they exist on the local file system for the TESTDB database.
All of the files listed in this query will be relocated from the local file system to ASM:
$ ORACLE_SID=TESTDB; export ORACLE_SID
$ sqlplus "/ as sysdba"
SQL> @dba_files_all
Tablespace Name /
File Class Filename File Size Auto Next Max
--------------------- --------------------------------------------------------------- --------------- ---- ----------- --------------
APEX22 /u02/oradata/TESTDB/datafile/o1_mf_apex22_2ft4eswu_.dbf 104,857,600 NO 0 0
EXAMPLE /u02/oradata/TESTDB/datafile/o1_mf_example_2fb4ccw2_.dbf 157,286,400 YES 655,360 34,359,721,984
FLOW_1 /u02/oradata/TESTDB/datafile/o1_mf_flow_1_2fb4cegw_.dbf 52,494,336 NO 0 0
SYSAUX /u02/oradata/TESTDB/datafile/o1_mf_sysaux_2fb4cb7z_.dbf 419,430,400 YES 10,485,760 34,359,721,984
SYSTEM /u02/oradata/TESTDB/datafile/o1_mf_system_2fb4b8s2_.dbf 608,174,080 YES 10,485,760 34,359,721,984
TEMP /u02/oradata/TESTDB/datafile/o1_mf_temp_2g17lvcq_.tmp 536,870,912 YES 262,144,000 34,359,721,984
UNDOTBS1 /u02/oradata/TESTDB/datafile/o1_mf_undotbs1_2fb4c2wf_.dbf 209,715,200 YES 5,242,880 34,359,721,984
USERS /u02/oradata/TESTDB/datafile/o1_mf_users_2fb4cqf4_.dbf 2,382,888,960 YES 1,310,720 34,359,721,984
[ CONTROL FILE ] /u02/oradata/TESTDB/controlfile/o1_mf_8du3s3er_.ctl
[ CONTROL FILE ] /u02/oradata/TESTDB/controlfile/o1_mf_y2is93je_.ctl
[ ONLINE REDO LOG ] /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_1_2g1g6bq0_.log 262,144,000
[ ONLINE REDO LOG ] /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_2_2g1gdgn1_.log 262,144,000
[ ONLINE REDO LOG ] /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_3_2g1ghz8z_.log 262,144,000
[ ONLINE REDO LOG ] /u02/oradata/TESTDB/onlinelog/o1_mf_1_2g1g61bm_.log 262,144,000
[ ONLINE REDO LOG ] /u02/oradata/TESTDB/onlinelog/o1_mf_2_2g1gd4pr_.log 262,144,000
[ ONLINE REDO LOG ] /u02/oradata/TESTDB/onlinelog/o1_mf_3_2g1ghs0t_.log 262,144,000
---------------
sum 6,044,581,888
16 rows selected.
Also note that the target database uses an SPFILE on the local file system:
$ORACLE_HOME/dbs/spfileTESTDB.ora
Use the following steps to fully migrate an existing Oracle database from a local file system to ASM:
- With the target database open, edit the initialization
parameter control_files and db_create_file_dest to point to the ASM
disk group +TESTDB_DATA1. Also configure
db_recovery_file_dest to point to the ASM disk group
+FLASH_RECOVERY_AREA:
SQL> ALTER SYSTEM SET control_files='+TESTDB_DATA1' SCOPE=spfile;
System altered.
SQL> ALTER SYSTEM SET db_create_file_dest='+TESTDB_DATA1' SCOPE=spfile;
System altered.
SQL> ALTER SYSTEM SET db_recovery_file_dest='+FLASH_RECOVERY_AREA' SCOPE=spfile;
System altered.
- Startup the target database in NOMOUNT mode:
SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP NOMOUNT
ORACLE instance started.
Total System Global Area 285212672 bytes
Fixed Size 1260420 bytes
Variable Size 171967612 bytes
Database Buffers 109051904 bytes
Redo Buffers 2932736 bytes
- From an RMAN session, copy one of your controlfiles from
the local file system to its new location in ASM. The new
controlfile will be copied to the value specified in the
initialization parameter control_files:
RMAN> RESTORE CONTROLFILE FROM '/u02/oradata/TESTDB/controlfile/o1_mf_8du3s3er_.ctl';
Starting restore at 14-AUG-06
using channel ORA_DISK_1
channel ORA_DISK_1: copied control file copy
output filename=+TESTDB_DATA1/testdb/controlfile/backup.268.598481391
Finished restore at 14-AUG-06
- From an RMAN or SQL*Plus session, mount the database. This will mount
the database using the controlfile stored in ASM:
RMAN> ALTER DATABASE MOUNT;
database mounted
released channel: ORA_DISK_1
- From an RMAN session, copy the database files from the local file system
to ASM:
RMAN> BACKUP AS COPY DATABASE FORMAT '+TESTDB_DATA1';
Starting backup at 14-AUG-06
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=158 devtype=DISK
channel ORA_DISK_1: starting datafile copy
input datafile fno=00005 name=/u02/oradata/TESTDB/datafile/o1_mf_users_2fb4cqf4_.dbf
output filename=+TESTDB_DATA1/testdb/datafile/users.270.598481673 tag=TAG20060814T205432 recid=36 stamp=598482095
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:07:06
channel ORA_DISK_1: starting datafile copy
input datafile fno=00001 name=/u02/oradata/TESTDB/datafile/o1_mf_system_2fb4b8s2_.dbf
output filename=+TESTDB_DATA1/testdb/datafile/system.269.598482099 tag=TAG20060814T205432 recid=37 stamp=598482206
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:55
channel ORA_DISK_1: starting datafile copy
input datafile fno=00003 name=/u02/oradata/TESTDB/datafile/o1_mf_sysaux_2fb4cb7z_.dbf
output filename=+TESTDB_DATA1/testdb/datafile/sysaux.267.598482213 tag=TAG20060814T205432 recid=38 stamp=598482292
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:25
channel ORA_DISK_1: starting datafile copy
input datafile fno=00002 name=/u02/oradata/TESTDB/datafile/o1_mf_undotbs1_2fb4c2wf_.dbf
output filename=+TESTDB_DATA1/testdb/datafile/undotbs1.256.598482299 tag=TAG20060814T205432 recid=39 stamp=598482340
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:45
channel ORA_DISK_1: starting datafile copy
input datafile fno=00004 name=/u02/oradata/TESTDB/datafile/o1_mf_example_2fb4ccw2_.dbf
output filename=+TESTDB_DATA1/testdb/datafile/example.264.598482345 tag=TAG20060814T205432 recid=40 stamp=598482374
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting datafile copy
input datafile fno=00006 name=/u02/oradata/TESTDB/datafile/o1_mf_apex22_2ft4eswu_.dbf
output filename=+TESTDB_DATA1/testdb/datafile/apex22.263.598482381 tag=TAG20060814T205432 recid=41 stamp=598482399
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting datafile copy
input datafile fno=00007 name=/u02/oradata/TESTDB/datafile/o1_mf_flow_1_2fb4cegw_.dbf
output filename=+TESTDB_DATA1/testdb/datafile/flow_1.262.598482405 tag=TAG20060814T205432 recid=42 stamp=598482415
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting datafile copy
copying current control file
output filename=+TESTDB_DATA1/testdb/controlfile/backup.261.598482421 tag=TAG20060814T205432 recid=43 stamp=598482423
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 14-AUG-06
channel ORA_DISK_1: finished piece 1 at 14-AUG-06
piece handle=+TESTDB_DATA1/testdb/backupset/2006_08_14/nnsnf0_tag20060814t205432_0.260.598482425 tag=TAG20060814T205432 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 14-AUG-06
- From an RMAN session, update the control file / data dictionary so that all database files point
to the RMAN copy made in ASM:
RMAN> SWITCH DATABASE TO COPY;
datafile 1 switched to datafile copy "+TESTDB_DATA1/testdb/datafile/system.269.598482099"
datafile 2 switched to datafile copy "+TESTDB_DATA1/testdb/datafile/undotbs1.256.598482299"
datafile 3 switched to datafile copy "+TESTDB_DATA1/testdb/datafile/sysaux.267.598482213"
datafile 4 switched to datafile copy "+TESTDB_DATA1/testdb/datafile/example.264.598482345"
datafile 5 switched to datafile copy "+TESTDB_DATA1/testdb/datafile/users.270.598481673"
datafile 6 switched to datafile copy "+TESTDB_DATA1/testdb/datafile/apex22.263.598482381"
datafile 7 switched to datafile copy "+TESTDB_DATA1/testdb/datafile/flow_1.262.598482405"
- From a SQL*Plus session, perform incomplete recovery and open the database
using the RESETLOGS option:
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
ORA-00279: change 7937583 generated at 08/14/2006 20:33:55 needed for thread 1
ORA-00289: suggestion : +FLASH_RECOVERY_AREA
ORA-00280: change 7937583 for thread 1 is in sequence #36
Specify log: {=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> ALTER DATABASE OPEN RESETLOGS;
Database altered.
- From a SQL*Plus session, re-create any tempfiles that are still currently on the local
file system to ASM. This is done by simply dropping the tempfiles from the local file system
and re-creating them in ASM. This example relies on the initialization
parameter db_create_file_dest=+TESTDB_DATA1:
SQL> select tablespace_name, file_name, bytes from dba_temp_files;
TABLESPACE_NAME FILE_NAME BYTES
--------------- ----------------------------------------------------- ---------
TEMP /u02/oradata/TESTDB/datafile/o1_mf_temp_2g17lvcq_.tmp 536870912
SQL> alter database tempfile
2 '/u02/oradata/TESTDB/datafile/o1_mf_temp_2g17lvcq_.tmp'
3 drop including datafiles;
Database altered.
SQL> alter tablespace temp add tempfile size 512m
2 autoextend on next 250m maxsize unlimited;
Tablespace altered.
SQL> select tablespace_name, file_name, bytes from dba_temp_files;
TABLESPACE_NAME FILE_NAME BYTES
--------------- ------------------------------------------------ ---------
TEMP +TESTDB_DATA1/testdb/tempfile/temp.261.598485663 536870912
 |
If users are currently accessing the tempfile(s) you are attempting
to drop, you may receive the following error:
SQL> alter database tempfile
2 '/u02/oradata/TESTDB/datafile/o1_mf_temp_2g17lvcq_.tmp'
3 drop including datafiles;
ERROR at line 1:
ORA-25152: TEMPFILE cannot be dropped at this time
As for the poor users who were using the tempfile, their transaction will
end and will be greeted with the following error message:
SQL> @testTemp.sql
join dba_extents c on (b.segment_name = c.segment_name)
*
ERROR at line 4:
ORA-00372: file 601 cannot be modified at this time
ORA-01110: data file 601: '/u02/oradata/TESTDB/datafile/o1_mf_temp_2g17lvcq_.tmp'
ORA-00372: file 601 cannot be modified at this time
ORA-01110: data file 601: '/u02/oradata/TESTDB/datafile/o1_mf_temp_2g17lvcq_.tmp'
If this happens, you should attempt to drop the tempfile again so the operation
is successful:
SQL> alter database tempfile
2 '/u02/oradata/TESTDB/datafile/o1_mf_temp_2g17lvcq_.tmp'
3 drop including datafiles;
Database altered.
|
|
- From a SQL*Plus session, re-create any online redo logfiles that are still currently on the local
file system to ASM. This is done by simply dropping the logfiles from the local file system
and re-creating them in ASM. This example relies on the initialization
parameters db_create_file_dest=+TESTDB_DATA1 and
db_recovery_file_dest=+FLASH_RECOVERY_AREA:
- Determine the current online redo logfiles to move to ASM
by examining the file names (and sizes) from V$LOGFILE:
SQL> select a.group#, a.member, b.bytes
2 from v$logfile a, v$log b where a.group# = b.group#;
GROUP# MEMBER BYTES
------ --------------------------------------------------------------- ---------
1 /u02/oradata/TESTDB/onlinelog/o1_mf_1_2g1g61bm_.log 262144000
2 /u02/oradata/TESTDB/onlinelog/o1_mf_2_2g1gd4pr_.log 262144000
3 /u02/oradata/TESTDB/onlinelog/o1_mf_3_2g1ghs0t_.log 262144000
1 /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_1_2g1g6bq0_.log 262144000
2 /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_2_2g1gdgn1_.log 262144000
3 /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_3_2g1ghz8z_.log 262144000
6 rows selected.
- Force a log switch until the last redo log is marked
"CURRENT" by issuing the following command:
SQL> select group#, status from v$log;
GROUP# STATUS
---------- ----------------
1 CURRENT
2 INACTIVE
3 INACTIVE
SQL> alter system switch logfile;
SQL> alter system switch logfile;
SQL> select group#, status from v$log;
GROUP# STATUS
---------- ----------------
1 INACTIVE
2 INACTIVE
3 CURRENT
- After making the last online redo log file the CURRENT one,
drop the first online redo log:
SQL> alter database drop logfile group 1;
Database altered.
 |
As a DBA, you should already be aware that if you
are going to drop a logfile group, it cannot be the
current logfile group. I have run into instances; however,
where attempting to drop the logfile group resulted in
the following error as a result of the logfile group
having an active status:
SQL> ALTER DATABASE DROP LOGFILE GROUP 1;
ALTER DATABASE DROP LOGFILE GROUP 1
*
ERROR at line 1:
ORA-01624: log 1 needed for crash recovery of instance TESTDB (thread 1)
ORA-00312: online log 1 thread 1: ''
Easy problem to resolve. Simply perform a checkpoint on the database:
SQL> ALTER SYSTEM CHECKPOINT GLOBAL;
System altered.
SQL> ALTER DATABASE DROP LOGFILE GROUP 1;
Database altered.
|
|
- Re-create the dropped redo log group in ASM (and a different size if desired):
SQL> alter database add logfile group 1 size 250m;
Database altered.
- After re-creating the online redo log group, force a log switch.
The online redo log group just created should become the CURRENT one:
SQL> select group#, status from v$log;
GROUP# STATUS
---------- ----------------
1 UNUSED
2 INACTIVE
3 CURRENT
SQL> alter system switch logfile;
SQL> select group#, status from v$log;
GROUP# STATUS
---------- ----------------
1 CURRENT
2 INACTIVE
3 ACTIVE
- After re-creating the first online redo log group, loop back to drop / re-create the next
online redo logfile until all logs are rebuilt in ASM.
- Verify all online redo logfiles have been created in ASM:
SQL> select a.group#, a.member, b.bytes
2 from v$logfile a, v$log b where a.group# = b.group#;
GROUP# MEMBER BYTES
------ ----------------------------------------------------------- ---------
1 +TESTDB_DATA1/testdb/onlinelog/group_1.259.598486831 262144000
2 +TESTDB_DATA1/testdb/onlinelog/group_2.260.598487179 262144000
3 +TESTDB_DATA1/testdb/onlinelog/group_3.258.598487365 262144000
1 +FLASH_RECOVERY_AREA/testdb/onlinelog/group_1.259.598486879 262144000
2 +FLASH_RECOVERY_AREA/testdb/onlinelog/group_2.257.598487225 262144000
3 +FLASH_RECOVERY_AREA/testdb/onlinelog/group_3.260.598487411 262144000
6 rows selected.
- Perform the following steps to relocate the SPFILE from the local
file system to an ASM disk group.
- Create a text-based initialization parameter file from
the current binary SPFILE located on the local file system:
SQL> CREATE PFILE='$ORACLE_HOME/dbs/initTESTDB.ora'
2 FROM SPFILE='$ORACLE_HOME/dbs/spfileTESTDB.ora';
File created.
- Create new SPFILE in an ASM disk group:
SQL> CREATE SPFILE='+TESTDB_DATA1/TESTDB/spfileTESTDB.ora'
2 FROM PFILE='$ORACLE_HOME/dbs/initTESTDB.ora';
File created.
- Shutdown the Oracle database:
SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
- Update the text-based init.ora file with the
new location of the SPFILE in ASM:
$ echo "SPFILE='+TESTDB_DATA1/TESTDB/spfileTESTDB.ora'" > $ORACLE_HOME/dbs/initTESTDB.ora
- Remove (actually rename) the old SPFILE on the local file system so that the new text-based
init.ora will be used:
$ mv $ORACLE_HOME/dbs/spfileTESTDB.ora $ORACLE_HOME/dbs/BACKUP_ASM.spfileTESTDB.ora
- Open the Oracle database using the new SPFILE:
SQL> STARTUP
- Verify that all database files have been created in ASM:
$ sqlplus "/ as sysdba"
SQL> @dba_files_all
Tablespace Name /
File Class Filename File Size Auto Next Max
--------------------- ----------------------------------------------------------- --------------- ---- ----------- ---------------
APEX22 +TESTDB_DATA1/testdb/datafile/apex22.263.598482381 104,857,600 NO 0 0
EXAMPLE +TESTDB_DATA1/testdb/datafile/example.264.598482345 157,286,400 YES 655,360 34,359,721,984
FLOW_1 +TESTDB_DATA1/testdb/datafile/flow_1.262.598482405 52,494,336 NO 0 0
SYSAUX +TESTDB_DATA1/testdb/datafile/sysaux.267.598482213 419,430,400 YES 10,485,760 34,359,721,984
SYSTEM +TESTDB_DATA1/testdb/datafile/system.269.598482099 608,174,080 YES 10,485,760 34,359,721,984
TEMP +TESTDB_DATA1/testdb/tempfile/temp.261.598485663 536,870,912 YES 262,144,000 34,359,721,984
UNDOTBS1 +TESTDB_DATA1/testdb/datafile/undotbs1.256.598482299 209,715,200 YES 5,242,880 34,359,721,984
USERS +TESTDB_DATA1/testdb/datafile/users.270.598481673 2,382,888,960 YES 1,310,720 34,359,721,984
[ CONTROL FILE ] +TESTDB_DATA1/testdb/controlfile/backup.268.598481391
[ ONLINE REDO LOG ] +FLASH_RECOVERY_AREA/testdb/onlinelog/group_1.259.598486879 262,144,000
[ ONLINE REDO LOG ] +FLASH_RECOVERY_AREA/testdb/onlinelog/group_2.257.598487225 262,144,000
[ ONLINE REDO LOG ] +FLASH_RECOVERY_AREA/testdb/onlinelog/group_3.260.598487411 262,144,000
[ ONLINE REDO LOG ] +TESTDB_DATA1/testdb/onlinelog/group_1.259.598486831 262,144,000
[ ONLINE REDO LOG ] +TESTDB_DATA1/testdb/onlinelog/group_2.260.598487179 262,144,000
[ ONLINE REDO LOG ] +TESTDB_DATA1/testdb/onlinelog/group_3.258.598487365 262,144,000
---------------
sum 6,044,581,888
15 rows selected.
- At this point, the target database is open
with all of its datafiles, controlfiles, online redo logfiles, tempfiles, and SPFILE
stored in ASM. If we wanted to remove
the database files that were stored on the local file system (which are actually now RMAN copies),
this could be done from an RMAN session. You could also then remove
the old version of the controfile(s) that were stored on the local
file system:
 |
If this is a production database,
it would be best practice to first backup the database files on
the local disk before removing them!
|
|
RMAN> DELETE NOPROMPT FORCE COPY;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=139 devtype=DISK
List of Datafile Copies
Key File S Completion Time Ckp SCN Ckp Time Name
------- ---- - --------------- ---------- --------------- ----
44 1 A 14-AUG-06 7937583 14-AUG-06 /u02/oradata/TESTDB/datafile/o1_mf_system_2fb4b8s2_.dbf
45 2 A 14-AUG-06 7937583 14-AUG-06 /u02/oradata/TESTDB/datafile/o1_mf_undotbs1_2fb4c2wf_.dbf
46 3 A 14-AUG-06 7937583 14-AUG-06 /u02/oradata/TESTDB/datafile/o1_mf_sysaux_2fb4cb7z_.dbf
47 4 A 14-AUG-06 7937583 14-AUG-06 /u02/oradata/TESTDB/datafile/o1_mf_example_2fb4ccw2_.dbf
48 5 A 14-AUG-06 7937583 14-AUG-06 /u02/oradata/TESTDB/datafile/o1_mf_users_2fb4cqf4_.dbf
49 6 A 14-AUG-06 7937583 14-AUG-06 /u02/oradata/TESTDB/datafile/o1_mf_apex22_2ft4eswu_.dbf
50 7 A 14-AUG-06 7937583 14-AUG-06 /u02/oradata/TESTDB/datafile/o1_mf_flow_1_2fb4cegw_.dbf
List of Control File Copies
Key S Completion Time Ckp SCN Ckp Time Name
------- - --------------- ---------- --------------- ----
43 A 14-AUG-06 7937583 14-AUG-06 +TESTDB_DATA1/testdb/controlfile/backup.261.598482421
List of Archived Log Copies
Key Thrd Seq S Low Time Name
------- ---- ------- - --------- ----
48 1 34 A 14-AUG-06 +FLASH_RECOVERY_AREA/testdb/archivelog/2006_08_14/thread_1_seq_34.259.598482825
49 1 35 A 14-AUG-06 +FLASH_RECOVERY_AREA/testdb/archivelog/2006_08_14/thread_1_seq_35.258.598482825
47 1 36 A 14-AUG-06 +FLASH_RECOVERY_AREA/testdb/archivelog/2006_08_14/thread_1_seq_36.260.598482821
deleted datafile copy
datafile copy filename=/u02/oradata/TESTDB/datafile/o1_mf_system_2fb4b8s2_.dbf recid=44 stamp=598482495
deleted datafile copy
datafile copy filename=/u02/oradata/TESTDB/datafile/o1_mf_undotbs1_2fb4c2wf_.dbf recid=45 stamp=598482495
deleted datafile copy
datafile copy filename=/u02/oradata/TESTDB/datafile/o1_mf_sysaux_2fb4cb7z_.dbf recid=46 stamp=598482496
deleted datafile copy
datafile copy filename=/u02/oradata/TESTDB/datafile/o1_mf_example_2fb4ccw2_.dbf recid=47 stamp=598482496
deleted datafile copy
datafile copy filename=/u02/oradata/TESTDB/datafile/o1_mf_users_2fb4cqf4_.dbf recid=48 stamp=598482496
deleted datafile copy
datafile copy filename=/u02/oradata/TESTDB/datafile/o1_mf_apex22_2ft4eswu_.dbf recid=49 stamp=598482496
deleted datafile copy
datafile copy filename=/u02/oradata/TESTDB/datafile/o1_mf_flow_1_2fb4cegw_.dbf recid=50 stamp=598482496
deleted control file copy
control file copy filename=+TESTDB_DATA1/testdb/controlfile/backup.261.598482421 recid=43 stamp=598482423
deleted archive log
archive log filename=+FLASH_RECOVERY_AREA/testdb/archivelog/2006_08_14/thread_1_seq_34.259.598482825 recid=48 stamp=598482824
deleted archive log
archive log filename=+FLASH_RECOVERY_AREA/testdb/archivelog/2006_08_14/thread_1_seq_35.258.598482825 recid=49 stamp=598482824
deleted archive log
archive log filename=+FLASH_RECOVERY_AREA/testdb/archivelog/2006_08_14/thread_1_seq_36.260.598482821 recid=47 stamp=598482824
Deleted 11 objects
RMAN> exit
$ rm /u02/oradata/TESTDB/controlfile/o1_mf_8du3s3er_.ctl
$ rm /u02/oradata/TESTDB/controlfile/o1_mf_y2is93je_.ctl
No comments:
Post a Comment