Steps To Migrate/Move a Database From Non-ASM to ASM And Vice-Versa

on
Migrating Databases from non-ASM to ASM and Vice-Versa

Overview
Automatic Storage Management (ASM) was introduced in Oracle10g Release 1 and is used to alleviate the DBA from having to manage individual files and drives. ASM is built into the Oracle kernel and provides the DBA with a way to manage thousands of disk drives 24x7 for both single and clustered instances of Oracle. Essentially, ASM is a file system / volume manager for all Oracle physical database files (datafiles, online redo logs, controlfiles, archived redo logs, RMAN backupsets, and SPFILEs). All of the database files (and directories) to be used for Oracle will be contained in a disk group. ASM automatically performs load balancing in parallel across all available disk drives to prevent hot spots and maximize performance, even with rapidly changing data usage patterns.Configuring an ASM environment (an ASM instance) is a straightforward process and can be done through the Database Configuration Assistant (DBCA) or manually (see Manually Creating an ASM Instance). Once the ASM instance is configured on a node and an ASM Disk Group is created, any database that resides on that node can start taking advantage of it. For example, consider an ASM instance named +ASM with an ASM disk group named TESTDB_DATA1. Creating a tablespace where the datafile will reside in ASM is as easy as:
SQL> CREATE TABLESPACE users2 DATAFILE '+TESTDB_DATA1' SIZE 100M;

Tablespace created.

SQL> SELECT tablespace_name, file_name FROM dba_data_files WHERE tablespace_name = 'USERS2';

TABLESPACE_NAME FILE_NAME
--------------- --------------------------------------------------
USERS2          +TESTDB_DATA1/testdb/datafile/users2.268.598475429
Given the SQL statement above, a new datafile will be created using Oracle Managed Files (OMF) in an ASM disk group named TESTDB_DATA1.
But, what if you already have an existing Oracle database which stores its database files using the local file system on the node you just configured ASM on and now want to relocate the entire database to be stored in ASM? Well, as with most file management tasks that involve ASM, it's RMAN to the rescue!
In this article, I will explain the steps necessary to migrate an existing Oracle database stored on the local file system to ASM. This will include all datafiles, tempfiles, online redo logfiles, controlfiles, and all flash recovery area files. I will then, within a follow-up section, explain how the process works in reverse - migrating a database stored in ASM to a local file system.

Current Configuration
The testing environment that I will be using for this article is best described in the following illustration and table of values:

Oracle ASM Configuration
Machine Name:linux3.idevelopment.info
Oracle SID:TESTDB
Database Name:TESTDB
Available
ASM Disk Groups:		+TESTDB_DATA1
+TESTDB_DATA2
+FLASH_RECOVERY_AREA
Available File System for DB Files:/u02/oradata
Available File System for Flash Recovery Area:/u02/flash_recovery_area
Operating System:Red Hat Linux 3 - (CentOS 3.4)
Oracle Release:Oracle10g Release 2 - (10.2.0.2.0)
 Please note that although I have two Oracle ASM disk groups defined for database files (+TESTDB_DATA1 and +TESTDB_DATA2), I will only be using+TESTDB_DATA1.

 This article assumes the database is open and in ARCHIVELOG mode:
SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     34
Next log sequence to archive   36
Current log sequence           36

Migrating Oracle Database from Local File System to ASM
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:
  1. 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 configuredb_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.
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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"
  7. 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.
  8. 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.

  9. 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.
  10. 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
  11. 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.
  12. 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

Migrating Oracle Database from ASM to Local File System

The following query lists database files as they exist in ASM for the TESTDB database. All of the files listed in this query will be relocated from ASM to the local file system:
$ ORACLE_SID=TESTDB; export ORACLE_SID
$ 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.
Also note that the target database uses an SPFILE which is stored in ASM. The target database starts using a text-based init.ora ($ORACLE_HOME/dbs/initTESTDB.ora) which defines the location of the SPFILE in ASM:
    SPFILE='+TESTDB_DATA1/TESTDB/spfileTESTDB.ora'
Use the following steps to fully migrate an existing Oracle database from ASM to a local file system:
  1. With the target database open, edit the initialization parameter control_files and db_create_file_dest to point to locations on the local file system (/u02/oradata). Also configuredb_recovery_file_dest to point to the Flash Recovery Area on the local file system (/u02/flash_recovery_area):
    SQL> ALTER SYSTEM SET control_files='/u02/oradata/TESTDB/control01.ctl' SCOPE=spfile;

System altered.

SQL> ALTER SYSTEM SET db_create_file_dest='/u02/oradata' SCOPE=spfile;

System altered.

SQL> ALTER SYSTEM SET db_recovery_file_dest='/u02/flash_recovery_area' SCOPE=spfile;

System altered.
  2. Backup the current SPFILE (in ASM) to a text-based init.ora file on the local file system. Then convert the text-based init.ora file to a binary SPFILE on the local file system:
    SQL> HOST mv $ORACLE_HOME/dbs/initTESTDB.ora $ORACLE_HOME/dbs/BACKUP_ASM.initTESTDB.ora

SQL> CREATE PFILE='$ORACLE_HOME/dbs/initTESTDB.ora' FROM SPFILE='+TESTDB_DATA1/TESTDB/spfileTESTDB.ora';

File created.

SQL> CREATE SPFILE='$ORACLE_HOME/dbs/spfileTESTDB.ora' FROM PFILE='$ORACLE_HOME/dbs/initTESTDB.ora';

File created.
  3. 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             150996092 bytes
Database Buffers          130023424 bytes
Redo Buffers                2932736 bytes
  4. From an RMAN session, copy one of your controlfiles from ASM to its new location on the local file system. The new controlfile will be copied to the value specified in the initialization parameter control_files:
    RMAN> RESTORE CONTROLFILE FROM '+TESTDB_DATA1/TESTDB/CONTROLFILE/backup.268.598481391';

Starting restore at 15-AUG-06
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK

channel ORA_DISK_1: copied control file copy
output filename=/u02/oradata/TESTDB/control01.ctl
Finished restore at 15-AUG-06
  5. From an RMAN or SQL*Plus session, mount the database. This will mount the database using the controlfile stored on the local file system:
    RMAN> ALTER DATABASE MOUNT;

using target database control file instead of recovery catalog
database mounted
  6. From an RMAN session, copy the database files from ASM to the local file system:
    RMAN> BACKUP AS COPY DATABASE FORMAT '/u02/oradata/TESTDB/%U';

Starting backup at 15-AUG-06
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: starting datafile copy
input datafile fno=00005 name=+TESTDB_DATA1/testdb/datafile/users.270.598481673
output filename=/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-USERS_FNO-5_0vhqpltd tag=TAG20060815T101925 recid=51 stamp=598530181
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:03:36
channel ORA_DISK_1: starting datafile copy
input datafile fno=00001 name=+TESTDB_DATA1/testdb/datafile/system.269.598482099
output filename=/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-SYSTEM_FNO-1_10hqpm45 tag=TAG20060815T101925 recid=52 stamp=598530235
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:55
channel ORA_DISK_1: starting datafile copy
input datafile fno=00003 name=+TESTDB_DATA1/testdb/datafile/sysaux.267.598482213
output filename=/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-SYSAUX_FNO-3_11hqpm5s tag=TAG20060815T101925 recid=53 stamp=598530274
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:46
channel ORA_DISK_1: starting datafile copy
input datafile fno=00002 name=+TESTDB_DATA1/testdb/datafile/undotbs1.256.598482299
output filename=/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-UNDOTBS1_FNO-2_12hqpm7a tag=TAG20060815T101925 recid=54 stamp=598530304
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting datafile copy
input datafile fno=00004 name=+TESTDB_DATA1/testdb/datafile/example.264.598482345
output filename=/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-EXAMPLE_FNO-4_13hqpm83 tag=TAG20060815T101925 recid=55 stamp=598530323
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting datafile copy
input datafile fno=00006 name=+TESTDB_DATA1/testdb/datafile/apex22.263.598482381
output filename=/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-APEX22_FNO-6_14hqpm8s tag=TAG20060815T101925 recid=56 stamp=598530343
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:16
channel ORA_DISK_1: starting datafile copy
input datafile fno=00007 name=+TESTDB_DATA1/testdb/datafile/flow_1.262.598482405
output filename=/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-FLOW_1_FNO-7_15hqpm9c tag=TAG20060815T101925 recid=57 stamp=598530353
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting datafile copy
copying current control file
output filename=/u02/oradata/TESTDB/cf_D-TESTDB_id-2370649665_16hqpm9j tag=TAG20060815T101925 recid=58 stamp=598530356
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:01
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 15-AUG-06
channel ORA_DISK_1: finished piece 1 at 15-AUG-06
piece handle=/u02/oradata/TESTDB/17hqpm9k_1_1 tag=TAG20060815T101925 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 15-AUG-06
  7. From an RMAN session, update the control file / data dictionary so that all database files point to the RMAN copy made on the local file system:
    RMAN> SWITCH DATABASE TO COPY;

datafile 1 switched to datafile copy "/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-SYSTEM_FNO-1_10hqpm45"
datafile 2 switched to datafile copy "/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-UNDOTBS1_FNO-2_12hqpm7a"
datafile 3 switched to datafile copy "/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-SYSAUX_FNO-3_11hqpm5s"
datafile 4 switched to datafile copy "/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-EXAMPLE_FNO-4_13hqpm83"
datafile 5 switched to datafile copy "/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-USERS_FNO-5_0vhqpltd"
datafile 6 switched to datafile copy "/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-APEX22_FNO-6_14hqpm8s"
datafile 7 switched to datafile copy "/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-FLOW_1_FNO-7_15hqpm9c"
  8. 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 7970332 generated at 08/15/2006 10:12:34 needed for thread 1
ORA-00289: suggestion :
/u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_5_%u_.arc
ORA-00280: change 7970332 for thread 1 is in sequence #5


Specify log: {=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.

SQL> ALTER DATABASE OPEN RESETLOGS;

Database altered.
  9. From a SQL*Plus session, re-create any tempfiles that are still currently using ASM to the local file system. This is done by simply dropping the tempfiles from ASM and re-creating them in the local file system. This example relies on the initialization parameter db_create_file_dest=/u02/oradata:
    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

SQL> alter database tempfile
  2  '+TESTDB_DATA1/testdb/tempfile/temp.261.598485663'
  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            /u02/oradata/TESTDB/datafile/o1_mf_temp_2g3spvq5_.tmp 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  '+TESTDB_DATA1/testdb/tempfile/temp.261.598485663'
  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: '+TESTDB_DATA1/testdb/tempfile/temp.261.598485663'
ORA-00372: file 601 cannot be modified at this time
ORA-01110: data file 601: '+TESTDB_DATA1/testdb/tempfile/temp.261.598485663'
    If this happens, you should attempt to drop the tempfile again so the operation is successful:
    SQL> alter database tempfile 
  2  '+TESTDB_DATA1/testdb/tempfile/temp.261.598485663'
  3  drop including datafiles;

Database altered.

  10. From a SQL*Plus session, re-create any online redo logfiles that are still currently using ASM to the local file system. This is done by simply dropping the logfiles from ASM and re-creating them on the local file system. This example relies on the initialization parameters db_create_file_dest=/u02/oradata and db_recovery_file_dest=/u02/flash_recovery_area:
    • Determine the current online redo logfiles to move to the local file system 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 +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.
    • 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 the local file system (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 the local file system.
    • Verify all online redo logfiles have been created in the local file system:
      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_2g3tc008_.log                    262144000
     2 /u02/oradata/TESTDB/onlinelog/o1_mf_2_2g3tkbwn_.log                    262144000
     3 /u02/oradata/TESTDB/onlinelog/o1_mf_3_2g3tmwno_.log                    262144000
     1 /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_1_2g3tc763_.log        262144000
     2 /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_2_2g3tkmr6_.log        262144000
     3 /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_3_2g3tn2g5_.log        262144000

6 rows selected.
  11. Verify that all database files have been created in the local file system:
    $ sqlplus "/ as sysdba"

SQL> @dba_files_all

Tablespace Name /
File Class           Filename                                                                        File Size Auto        Next             Max
-------------------- ------------------------------------------------------------------------- --------------- ---- ----------- ---------------
APEX22               /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-APEX22_FNO-6_14hqpm8s       104,857,600 NO             0               0
EXAMPLE              /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-EXAMPLE_FNO-4_13hqpm83      157,286,400 YES      655,360  34,359,721,984
FLOW_1               /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-FLOW_1_FNO-7_15hqpm9c        52,494,336 NO             0               0
SYSAUX               /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-SYSAUX_FNO-3_11hqpm5s       419,430,400 YES   10,485,760  34,359,721,984
SYSTEM               /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-SYSTEM_FNO-1_10hqpm45       608,174,080 YES   10,485,760  34,359,721,984
TEMP                 /u02/oradata/TESTDB/datafile/o1_mf_temp_2g3spvq5_.tmp                         536,870,912 YES  262,144,000  34,359,721,984
UNDOTBS1             /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-UNDOTBS1_FNO-2_12hqpm7a     209,715,200 YES    5,242,880  34,359,721,984
USERS                /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-USERS_FNO-5_0vhqpltd      2,382,888,960 YES    1,310,720  34,359,721,984
[ CONTROL FILE    ]  /u02/oradata/TESTDB/control01.ctl
[ ONLINE REDO LOG ]  /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_1_2g3tc763_.log               262,144,000
[ ONLINE REDO LOG ]  /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_2_2g3tkmr6_.log               262,144,000
[ ONLINE REDO LOG ]  /u02/flash_recovery_area/TESTDB/onlinelog/o1_mf_3_2g3tn2g5_.log               262,144,000
[ ONLINE REDO LOG ]  /u02/oradata/TESTDB/onlinelog/o1_mf_1_2g3tc008_.log                           262,144,000
[ ONLINE REDO LOG ]  /u02/oradata/TESTDB/onlinelog/o1_mf_2_2g3tkbwn_.log                           262,144,000
[ ONLINE REDO LOG ]  /u02/oradata/TESTDB/onlinelog/o1_mf_3_2g3tmwno_.log                           262,144,000
                                                                                               ---------------
sum                                                                                              6,044,581,888

15 rows selected.
  12. At this point, the target database is open with all of its datafiles, controlfiles, online redo logfiles, tempfiles, and SPFILE stored in the local file system. If we wanted to remove the database files that were stored using ASM (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) and SPFILE that were stored using ASM using a SQL*Plus session logged in to the ASM instance:
     If this is a production database, it would be best practice to first backup the database files on the local disk before removing the copies stored using ASM!

    RMAN> DELETE NOPROMPT FORCE COPY;

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

List of Datafile Copies
Key     File S Completion Time Ckp SCN    Ckp Time        Name
------- ---- - --------------- ---------- --------------- ----
59      1    A 15-AUG-06       7970332    15-AUG-06       +TESTDB_DATA1/testdb/datafile/system.269.598482099
60      2    A 15-AUG-06       7970332    15-AUG-06       +TESTDB_DATA1/testdb/datafile/undotbs1.256.598482299
61      3    A 15-AUG-06       7970332    15-AUG-06       +TESTDB_DATA1/testdb/datafile/sysaux.267.598482213
62      4    A 15-AUG-06       7970332    15-AUG-06       +TESTDB_DATA1/testdb/datafile/example.264.598482345
63      5    A 15-AUG-06       7970332    15-AUG-06       +TESTDB_DATA1/testdb/datafile/users.270.598481673
64      6    A 15-AUG-06       7970332    15-AUG-06       +TESTDB_DATA1/testdb/datafile/apex22.263.598482381
65      7    A 15-AUG-06       7970332    15-AUG-06       +TESTDB_DATA1/testdb/datafile/flow_1.262.598482405

List of Control File Copies
Key     S Completion Time Ckp SCN    Ckp Time        Name
------- - --------------- ---------- --------------- ----
58      A 15-AUG-06       7970332    15-AUG-06       /u02/oradata/TESTDB/cf_D-TESTDB_id-2370649665_16hqpm9j

List of Archived Log Copies
Key     Thrd Seq     S Low Time  Name
------- ---- ------- - --------- ----
54      1    4       A 14-AUG-06 /u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_4_2g3qxnxt_.arc
55      1    5       A 14-AUG-06 /u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_5_2g3qxo2c_.arc
56      1    1       A 15-AUG-06 /u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_1_2g3t3v8b_.arc
57      1    2       A 15-AUG-06 /u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_2_2g3t4q1g_.arc
58      1    3       A 15-AUG-06 /u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_3_2g3tdm2s_.arc
59      1    4       A 15-AUG-06 /u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_4_2g3tlkfk_.arc
60      1    5       A 15-AUG-06 /u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_5_2g3tqb1h_.arc
deleted datafile copy
datafile copy filename=+TESTDB_DATA1/testdb/datafile/system.269.598482099 recid=59 stamp=598531780
deleted datafile copy
datafile copy filename=+TESTDB_DATA1/testdb/datafile/undotbs1.256.598482299 recid=60 stamp=598531780
deleted datafile copy
datafile copy filename=+TESTDB_DATA1/testdb/datafile/sysaux.267.598482213 recid=61 stamp=598531780
deleted datafile copy
datafile copy filename=+TESTDB_DATA1/testdb/datafile/example.264.598482345 recid=62 stamp=598531780
deleted datafile copy
datafile copy filename=+TESTDB_DATA1/testdb/datafile/users.270.598481673 recid=63 stamp=598531780
deleted datafile copy
datafile copy filename=+TESTDB_DATA1/testdb/datafile/apex22.263.598482381 recid=64 stamp=598531780
deleted datafile copy
datafile copy filename=+TESTDB_DATA1/testdb/datafile/flow_1.262.598482405 recid=65 stamp=598531780
deleted control file copy
control file copy filename=/u02/oradata/TESTDB/cf_D-TESTDB_id-2370649665_16hqpm9j recid=58 stamp=598530356
deleted archive log
archive log filename=/u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_4_2g3qxnxt_.arc recid=54 stamp=598531956
deleted archive log
archive log filename=/u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_5_2g3qxo2c_.arc recid=55 stamp=598531962
deleted archive log
archive log filename=/u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_1_2g3t3v8b_.arc recid=56 stamp=598534203
deleted archive log
archive log filename=/u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_2_2g3t4q1g_.arc recid=57 stamp=598534231
deleted archive log
archive log filename=/u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_3_2g3tdm2s_.arc recid=58 stamp=598534483
deleted archive log
archive log filename=/u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_4_2g3tlkfk_.arc recid=59 stamp=598534673
deleted archive log
archive log filename=/u02/flash_recovery_area/TESTDB/archivelog/2006_08_15/o1_mf_1_5_2g3tqb1h_.arc recid=60 stamp=598534826
Deleted 15 objects

RMAN> exit

$ ORACLE_SID=+ASM; export ORACLE_SID
$ sqlplus "/ as sysdba"

SQL> ALTER DISKGROUP TESTDB_DATA1 DROP FILE '+TESTDB_DATA1/TESTDB/CONTROLFILE/backup.268.598481391';

Diskgroup altered.

SQL> ALTER DISKGROUP TESTDB_DATA1 DROP FILE '+TESTDB_DATA1/TESTDB/spfileTESTDB.ora';

Diskgroup altered.
  13. One final note. Throughout this article, you will have noticed that I relied on using Oracle Managed Files (OMF) whenever possible. However, you can see that after relocating the database files from ASM to the local file system that our datafiles and controlfile(s) are not OMF. In this final task, I will convert the current datafiles and controlfile(s) to OMF:
    • First, determine the non-OMF controlfiles (to be renamed) currently in use:
      SQL> select name from v$controlfile;

NAME
---------------------------------
/u02/oradata/TESTDB/control01.ctl
    • Next, determine the non-OMF datafiles (to be renamed) by examining the view DBA_DATA_FILES:
      SQL> SELECT tablespace_name, file_name
  2  FROM dba_data_files;

TABLESPACE_NAME FILE_NAME
--------------- -------------------------------------------------------------------------
SYSTEM          /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-SYSTEM_FNO-1_10hqpm45
UNDOTBS1        /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-UNDOTBS1_FNO-2_12hqpm7a
SYSAUX          /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-SYSAUX_FNO-3_11hqpm5s
EXAMPLE         /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-EXAMPLE_FNO-4_13hqpm83
USERS           /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-USERS_FNO-5_0vhqpltd
APEX22          /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-APEX22_FNO-6_14hqpm8s
FLOW_1          /u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-FLOW_1_FNO-7_15hqpm9c

7 rows selected.
    • Shutdown the database:
      SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
    • Rename the non-OMF controlfile(s) in the file system to the newest OMF file name format:
      $ cd /u02/oradata/TESTDB
$ mkdir -p controlfile
$ cp control01.ctl controlfile/o1_mf_8du3s3er_.ctl
$ cp control01.ctl controlfile/o1_mf_y2is93je_.ctl
$ rm control01.ctl
    • Modify the control_files initialization parameter in your init.ora or SPFILE to reference the new name(s):
      SQL> startup nomount
ORACLE instance started.

Total System Global Area  285212672 bytes
Fixed Size                  1260420 bytes
Variable Size             150996092 bytes
Database Buffers          130023424 bytes
Redo Buffers                2932736 bytes

SQL> alter system set
  2  control_files='/u02/oradata/TESTDB/controlfile/o1_mf_8du3s3er_.ctl',
  3                '/u02/oradata/TESTDB/controlfile/o1_mf_y2is93je_.ctl'
  4  scope=spfile;

System altered.

SQL> shutdown immediate
ORA-01507: database not mounted


ORACLE instance shut down.
    • Rename the non-OMF datafiles in the file system to the newest OMF file name format:
      $ cd /u02/oradata/TESTDB
$ mkdir -p datafile
$ mv data_D-TESTDB_I-2370649665_TS-SYSTEM_FNO-1_10hqpm45    datafile/o1_mf_system_2fb4b8s2_.dbf
$ mv data_D-TESTDB_I-2370649665_TS-UNDOTBS1_FNO-2_12hqpm7a  datafile/o1_mf_undotbs1_2fb4c2wf_.dbf
$ mv data_D-TESTDB_I-2370649665_TS-SYSAUX_FNO-3_11hqpm5s    datafile/o1_mf_sysaux_2fb4cb7z_.dbf
$ mv data_D-TESTDB_I-2370649665_TS-EXAMPLE_FNO-4_13hqpm83   datafile/o1_mf_example_2fb4ccw2_.dbf
$ mv data_D-TESTDB_I-2370649665_TS-USERS_FNO-5_0vhqpltd     datafile/o1_mf_users_2fb4cqf4_.dbf
$ mv data_D-TESTDB_I-2370649665_TS-APEX22_FNO-6_14hqpm8s    datafile/o1_mf_apex22_2ft4eswu_.dbf
$ mv data_D-TESTDB_I-2370649665_TS-FLOW_1_FNO-7_15hqpm9c    datafile/o1_mf_flow_1_2fb4cegw_.dbf
    • Rename the files in the controlfile:
      SQL> startup mount
ORACLE instance started.

Total System Global Area  285212672 bytes
Fixed Size                  1260420 bytes
Variable Size             150996092 bytes
Database Buffers          130023424 bytes
Redo Buffers                2932736 bytes
Database mounted.

SQL> alter database rename file
  2  '/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-SYSTEM_FNO-1_10hqpm45'
  3  to '/u02/oradata/TESTDB/datafile/o1_mf_system_2fb4b8s2_.dbf';

Database altered.

SQL> alter database rename file
  2  '/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-UNDOTBS1_FNO-2_12hqpm7a'
  3  to '/u02/oradata/TESTDB/datafile/o1_mf_undotbs1_2fb4c2wf_.dbf';

Database altered.

SQL> alter database rename file
  2  '/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-SYSAUX_FNO-3_11hqpm5s'
  3  to '/u02/oradata/TESTDB/datafile/o1_mf_sysaux_2fb4cb7z_.dbf';

Database altered.

SQL> alter database rename file
  2  '/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-EXAMPLE_FNO-4_13hqpm83'
  3  to '/u02/oradata/TESTDB/datafile/o1_mf_example_2fb4ccw2_.dbf';

Database altered.

SQL> alter database rename file
  2  '/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-USERS_FNO-5_0vhqpltd'
  3  to '/u02/oradata/TESTDB/datafile/o1_mf_users_2fb4cqf4_.dbf';

Database altered.

SQL> alter database rename file
  2  '/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-APEX22_FNO-6_14hqpm8s'
  3  to '/u02/oradata/TESTDB/datafile/o1_mf_apex22_2ft4eswu_.dbf';

Database altered.

SQL> alter database rename file
  2  '/u02/oradata/TESTDB/data_D-TESTDB_I-2370649665_TS-FLOW_1_FNO-7_15hqpm9c'
  3  to '/u02/oradata/TESTDB/datafile/o1_mf_flow_1_2fb4cegw_.dbf';

Database altered.
    • Open database and verify the new OMF files:
      SQL> alter database open;

Database altered.

SQL> SELECT tablespace_name, file_name
  2  FROM dba_data_files;

TABLESPACE_NAME FILE_NAME
--------------- ---------------------------------------------------------
SYSTEM          /u02/oradata/TESTDB/datafile/o1_mf_system_2fb4b8s2_.dbf
UNDOTBS1        /u02/oradata/TESTDB/datafile/o1_mf_undotbs1_2fb4c2wf_.dbf
SYSAUX          /u02/oradata/TESTDB/datafile/o1_mf_sysaux_2fb4cb7z_.dbf
EXAMPLE         /u02/oradata/TESTDB/datafile/o1_mf_example_2fb4ccw2_.dbf
USERS           /u02/oradata/TESTDB/datafile/o1_mf_users_2fb4cqf4_.dbf
APEX22          /u02/oradata/TESTDB/datafile/o1_mf_apex22_2ft4eswu_.dbf
FLOW_1          /u02/oradata/TESTDB/datafile/o1_mf_flow_1_2fb4cegw_.dbf

7 rows selected.
====================================================

 Steps To Migrate/Move a Database From Non-ASM to ASM And Vice-Versa (Doc ID 252219.1)

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 12.1.0.2 [Release 10.1 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 20-May-2015*** 

PURPOSE

This article describes the steps to migrate a database from Non-ASM to ASM and vice-versa.

To setup ASM, please follow
Note 452924.1 - How to Prepare Storage for ASM
Note 265633.1 - ASM Technical Best Practices
Note 249992.1 - New Feature on ASM (Automatic Storage Manager).

SCOPE

A scheduled downtime is needed.

DETAILS

Step 1: Edit the pfile/spfile of DB to point the new control_file location on ASM
E.g. : if your disk group name is '+DATA'
control_files='+DATA//control01.ctl'
 The setting here is actually an alias for the controlfile.
For 10gR1 or you don't want to use an alias for controlfile, please set control_files='+DATA' and use the following note to update the parameter again in the pfile/spfile after the controlfile is created at step #3.
Note 468458.1  How To Move Controlfile To ASM
If you later want to duplicate an extra copy of control file, please see
Note 345180.1  How to duplicate a controlfile when ASM is involved
Step 2: Startup the database in nomount state
SQL> Startup nomount
Step 3: From RMAN session, copy the control file from old location to new location
RMAN> CONNECT TARGET

RMAN> RESTORE CONTROLFILE FROM '/u01/TST/control01.ctl';
Here /u01/TST/control01.ctl is the old location of control file.

Step 4: From SQL session, mount the database
SQL> ALTER DATABASE MOUNT;
 Step 5: Using RMAN, copy the datafile from NON-ASM to ASM
RMAN>BACKUP AS COPY DATABASE FORMAT '+DATA';
 Step 6: Using RMAN, rename the datafile , using the following command
RMAN> SWITCH DATABASE TO COPY;
 Step 7: Switch tempfile and open database.
RMAN> run {
set newname for tempfile 1 to '+DATA';
set newname for tempfile 2 to '+DATA';
...
switch tempfile all;
}

RMAN> ALTER DATABASE OPEN;
 Step 8: Do the following maintenance
SQL> SELECT a.group#, b.member, a.status FROM v$log a, v$logfile b WHERE a.group#=b.group#;
SQL> ALTER DATABASE ADD LOGFILE MEMBER '+ASM_Disk_group' TO GROUP 1;
SQL> ALTER DATABASE ADD LOGFILE MEMBER '+ASM_Disk_group' TO GROUP 2;
SQL> ALTER DATABASE DROP LOGFILE MEMBER '';
SQL> ALTER SYSTEM SWITCH LOGFILE;
SQL> ALTER DATABASE DROP LOGFILE MEMBER '';
SQL> ALTER SYSTEM SWITCH LOGFILE;
... repeat for *all* online redo log members.
A redo log member can only be dropped after being archived and being in INACTIVE mode. If needed, switch logfile multiple times until the logfile is ready for dropping. 
STEP of MIGRATION from ASM to NON-ASM
1. Start your database with ASM.
2. Create pfile from spfile.
3. Edit pfile/spfile to reflect controlfile name in file system location.
4. Startup nomount the DB.
SQL> Startup nomount
5. Use RMAN to copy the control file from ASM to NON-ASM. 
RMAN> RESTORE CONTROLFILE FROM '';
6. Mount the DB.
SQL> alter database mount;
7. Use RMAN to copy the database from ASM to NON-ASM.
RMAN> BACKUP AS COPY DATABASE format '/u01/oradata/nonasmdb/datafile/%U';
8. From RMAN.
RMAN> SWITCH DATABASE TO COPY;
9. Recreate the tempfile and redo logs as before. See step 7 and 8 above.
NOTE:  FYI, there is a new feature to asmcmd:
Note 1610615.1 How to Move a Datafile from Filesystem to ASM Using ASMCMD CP Command. 
Reference

Additional Resources

Community Discussions: Storage Management
Still have questions? Use the above community to search for similar discussions or start a new discussion on this subject.

REFERENCES

NOTE:345180.1 - How to duplicate a controlfile when ASM is involved
NOTE:468458.1 - How To Move Controlfile To ASM
NOTE:249992.1 - New Feature on ASM (Automatic Storage Manager).
NOTE:265633.1 - ASM Technical Best Practices For 10g and 11gR1 Release
NOTE:1610615.1 - How to Move a Datafile from Filesystem to ASM Using ASMCMD CP Command.
NOTE:452924.1 - How to Prepare Storage for ASM

 ===================================================================

 Note---> This informationmation taken from oracle metalink. all copy rights oracle only.

Comments

Post a Comment

Oracle DBA Information