Migrating an Oracle RAC database from Automatic Storage

Migrating an Oracle RACdatabase from AutomaticStorage Management toVeritas Cluster File System

Migrating an Oracle RAC database from AutomaticStorage Management to Veritas Cluster File System

The software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Legal NoticeCopyright © 2010 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo are trademarks or registered trademarks of SymantecCorporation or its affiliates in theU.S. and other countries. Other namesmaybe trademarksof their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The LicenseAgreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see theThird Party LegalNoticeAppendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. TheTechnical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, theTechnical Support groupworkswithProductEngineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s support offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and/or Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers software upgrades

■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

■ Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our Web siteat the following URL:

www.symantec.com/business/support/index.jsp

All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:

www.symantec.com/business/support/contact_techsupp_static.jsp

Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer onwhich theproblemoccurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

http://www.symantec.com/business/support/index.jsp

http://www.symantec.com/business/support/contact_techsupp_static.jsp

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf yourSymantecproduct requires registrationor a licensekey, access our technicalsupport Web page at the following URL:

www.symantec.com/business/support/

Customer serviceCustomer service information is available at the following URL:

www.symantec.com/business/support/

Customer Service is available to assist with non-technical questions, such as thefollowing types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and support contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals

http://www.symantec.com/business/support/

http://www.symantec.com/business/support/

Documentation feedbackYour feedback on product documentation is important to us. Send suggestionsfor improvements and reports on errors or omissions. Include the title anddocument version (located on the second page), and chapter and section titles ofthe text on which you are reporting. Send feedback to:

[email protected]

Support agreement resourcesIf youwant to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

mailto:[email protected]




Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Migrating an Oracle RAC database from ASM toCFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Migration overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Benefits of CFS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Setup overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Before you migrate ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installing and configuring the Veritas products ... . . . . . . . . . . . . . . . . . . . . . . . . 12Adding shared storage for CFS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Preparing the ASM database for migration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Migration from ASM to CFS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Migrating the ASM database to CFS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Completing the post-migration steps ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Verifying the database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Removing the ASM database files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Removing the ASM cluster instances from the SF Oracle RAC

nodes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Removing the ASM storage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Appendix A Sample migration procedure for multiple sharedvolumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Sample migration procedure for multiple shared volumes .... . . . . . . . . . . . . . . . 27Preparing to migrate ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Migrating from ASM to CFS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Appendix B Renaming the database files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Renaming the database files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Appendix C Deleting ASM data file copies using the RMANutility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Deleting ASM datafile copies using the RMAN utility ... . . . . . . . . . . . . . . . . . . . . . . . 35

Contents

Contents8

Migrating an Oracle RACdatabase from ASM to CFS

This chapter includes the following topics:

■ Migration overview

■ Setup overview

■ Before you migrate

■ Migration from ASM to CFS

Migration overviewThis guide provides instructions for migrating the Oracle RAC database fromOracleAutomatic StorageManagement(ASM) toVeritas Cluster File System(CFS).

ASM is a vertically integrated file system and volume manager, purpose-built forOracle database files. It is consistent across all server and storage platforms.

CFS enables you tomount the same file system onmultiple nodes simultaneouslyand is an extension of the industry-standard Veritas File System. CFS is a trueSANfile system.All thedata traffic takesplace over the storage areanetwork(SAN),and only the metadata traverses the cluster interconnects.

Figure 1-1 illustrates the migration from ASM to CFS

1Chapter

Figure 1-1 Migration from ASM to CFS

Benefits of CFS■ CFS facilitates easy creation and expansion of files. In ASM you must provide

Oracle with fixed size partitions. CFS however, allows dynamic storageallocation to meet future requirements.

■ CFS allows you to choose your backup strategy. In Oracle ASM you are limitedto a RAC-specific backup strategy. You can back up the database using theRecovery Manager(RMAN) utility only.

■ CFS eliminates the need for ASM instances, which require additional memoryand background processes to provide data to the Oracle database instances.

■ Akey element of Veritas Storage Foundation isDynamicMulti-pathing (DMP),which provides multiple parallel IO paths between servers and storage, toimprove storageavailability andscalability.ASMhasno inherentmulti-pathing.

■ Veritas ODM has the following performance benefits:

■ Locking feature for data integrity

■ IntegrationwithOracle database to leverage concurrency control and datacaching.

■ Fewer system calls and context switches

■ Increased I/O parallelism

■ Efficient file creation and disk allocation

Migrating an Oracle RAC database from ASM to CFSMigration overview

10

Setup overviewTo migrate from ASM to CFS, make sure that your Oracle configuration isanalogous to the following:

galaxy,nebulaMachine name

racdb1,racdb2Oracle SID

racdbDatabase name

+asm1, +asm2ASM instance name

+DATADGAvailable ASM disk groups

/oradataFile system available for database files

HP-UX, Solaris, AIX, LinuxOperating systems

SF Oracle RAC, SFCFS RAC (Linux only)Veritas products

For SF Oracle RAC: Oracle RAC 10g Release2, Oracle RAC11gRelease 1, Oracle RAC11gRelease 2

For SFCFS RAC: Oracle RAC 10g Release 2,Oracle RAC 11g Release 1

Oracle RAC versions

Before you migrateComplete the following tasks before you migrate the ASM database to CFS.

■ Install and configure the Veritas products.See “Installing and configuring the Veritas products” on page 12.

■ Add shared storage for CFS.See “Adding shared storage for CFS” on page 12.

Note: This step provides instructions for creating a single shared volume forall the Oracle files. For instructions on creating multiple shared volumes, seethe appendix Sample migration procedure for multiple shared volumes in thisdocument

■ Prepare the ASM database for migration.See “Preparing the ASM database for migration” on page 13.

11Migrating an Oracle RAC database from ASM to CFSSetup overview

Installing and configuring the Veritas productsTo install and configure SF Oracle RAC see, Veritas Storage Foundation™ forOracle® RAC Installation and Configuration Guide.

To install and configure SFCFS RAC on Linux see Veritas Storage Foundation™Cluster File System for Oracle® RAC Installation and Configuration Guide.

Adding shared storage for CFSPerform the following steps to add shared storage for CFS.

To add shared storage for CFS

1 Log in as a superuser on one of the nodes.

2 On the master node, create a shared disk group (for example, oradatadg).

# vxdg -s init oradatadg c4t1d2

3 Create a single shared volume (for example, oradatavol) that is large enoughto contain a file system for all Oracle files. For example, assuming 15 GB isrequired for database storage run the following command:

# vxassist -g oradatadg make oradatavol 15G

4 For HP-UX platform only:

Set the activation mode (sw) for HP-UX platform to allow shared access tothe disk group:

# vxdg -g oradatadg set activation=sw

5 Start the disk group volume:

# vxvol -g oradatadg startall

6 Create a VxFS file system in this volume:

# mkfs -F vxfs -o largefiles /dev/vx/rdsk/oradatadg/oradatavol

Note: The volume directory structure may vary according to the operatingsystem.

7 Create a mount point for the shared file system:

# mkdir /oradata

Migrating an Oracle RAC database from ASM to CFSBefore you migrate

12

8 Mount CFS:

# mount -F vxfs -o cluster /dev/vx/dsk/oradatadg/oradatavol /oradata

9 Change the owner to "Oracle" and set the permissions:

# chown oracle:oinstall /oradata

# chmod 755 /oradata

Preparing the ASM database for migrationLogin as the Oracle user and complete the following steps.

To prepare the ASM database for migration

1 Create a database directory on the CFS mount point:

$ mkdir –p /oradata/racdb

2 Connect as a user with "sysdba" privileges:

$ sqlplus “/as sysdba”

3 Check if block change tracking is disabled. Block change tracking is in adisabled state by default.

SQL> select status from v$block_change_tracking;

STATUS

----------

DISABLED

If block change tracking is enabled, disable it:

SQL> alter database disable block change tracking;

Note:Block change tracking records the blocksmodified since the last backupin a block change tracking file. When RMAN backs up the system it uses theblock change tracking file to identify the specific blocks that need to be backedup.This improves the RMAN's performance as it does not have to scan wholedatafiles to detect the changed blocks. Youmust disable block change trackingbefore you migrate from ASM to CFS because the block change tracking filecannot be migrated.

13Migrating an Oracle RAC database from ASM to CFSBefore you migrate

4 Check if flashback database is disabled:

SQL> select flashback_on from v$database;

FLASHBACK_ON

------------

YES

If flashback database is enabled, disable it:

SQL> alter database flashback off;

Note: You must disable Oracle Flashback database as flashback logs cannotbe migrated.

5 Exit sqlplus:

SQL> exit

6 Shutdown the database on all nodes:

$ srvctl stop database –d racdb

Migrating an Oracle RAC database from ASM to CFSBefore you migrate

14

7 Start one of the database instances in nomount state, and set the control filein the spfile to point to CFS:


SQL> startup nomount

ORACLE instance started.

Total System Global Area 1169149952 bytes

Fixed Size 2122464 bytes

Variable Size 754978080 bytes

Database Buffers 402653184 bytes

Redo Buffers 9396224 bytes

SQL> alter system set control_files='/oradata/racdb/control01.ctl'

\scope=spfile sid='*';

8 Shutdown the instance:

SQL> shutdown immediate;

Exit sqlplus:

SQL> exit

Migration from ASM to CFSComplete the following tasks to migrate the Oracle RAC database from ASM toCFS.

■ Migrate the ASM database to CFS.See “Migrating the ASM database to CFS” on page 16.

■ Complete the post-migration steps.See “Completing the post-migration steps” on page 18.

■ Verify the database.See “Verifying the database” on page 22.

■ Remove the ASM database files.See “Removing the ASM database files” on page 24.

■ Remove the ASM cluster instances from the SF Oracle RAC nodes.See “Removing the ASM cluster instances from the SF Oracle RAC nodes”on page 25.

15Migrating an Oracle RAC database from ASM to CFSMigration from ASM to CFS

■ Remove the ASM storage.See “Removing the ASM storage” on page 25.

Migrating the ASM database to CFSComplete the following steps to migrate the ASM database to CFS

To migrate the ASM database to CFS

1 Invoke the RMAN utility and start the database in nomount state:

$ $ORACLE_HOME/bin/rman

Recovery Manager: Release 11.1.0.6.0 -

Production on Thu Aug 20 15:06:03 2009

Copyright (c) 1982, 2007, Oracle. All rights reserved.

RMAN>

RMAN> connect target

RMAN> startup nomount;

2 Migrate the control file from the ASM location to CFS:

RMAN> RESTORE CONTROLFILE FROM '+DATADG/racdb/control01.ctl';

Starting restore at 19-AUG-09

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=140 instance=racdb1 device type=DISK

channel ORA_DISK_1: copied control file copy

output file name=/oradata/racdb/control01.ctl

Finished restore at 19-AUG-09

RMAN>

3 Mount the database:

RMAN> alter database mount;

Migrating an Oracle RAC database from ASM to CFSMigration from ASM to CFS

16

4 Copy the existing ASM database files to CFS.

Note: The datafile name depends on the format string you provide in RMAN.For example, "%U". For RMAN substitution variables that can be used informat strings, seehttp://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcmsubcl010.htm

RMAN> BACKUP AS COPY DATABASE format '/oradata/racdb/%U';

Starting backup at 19-AUG-09

using channel ORA_DISK_1

channel ORA_DISK_1: starting datafile copy

input datafile file number=00001 name=+DATADG/racdb/system01.dbf

output file name=/oradata/racdb/data_D-RACDB_I-439523838_TS-SYSTEM_FNO-1_04kn3str\

tag=TAG20090819T201659 RECID=1 STAMP=695333834

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:16


input datafile file number=00002 name=+DATADG/racdb/sysaux01.dbf

output file name=/oradata/racdb/data_D-RACDB_I-439523838_TS-SYSAUX_FNO-2_05kn3sub\




input datafile file number=00003 name=+DATADG/racdb/undotbs01.dbf

output file name=/oradata/racdb/data_D-RACDB_I-439523838_TS-UNDOTBS1_FNO-3_06kn3suq\




input datafile file number=00005 name=+DATADG/racdb/undotbs02.dbf

output file name=/oradata/racdb/data_D-RACDB_I-439523838_TS-UNDOTBS2_FNO-5_07kn3suu\




copying current control file

output file name=/oradata/racdb/cf_D-RACDB_id-439523838_08kn3suv\




input datafile file number=00004 name=+DATADG/racdb/users01.dbf

output file name=/oradata/racdb/data_D-RACDB_I-439523838_TS-USERS_FNO-4_09kn3sv0\




http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcmsubcl010.htm

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current SPFILE in backup set

channel ORA_DISK_1: starting piece 1 at 19-AUG-09

channel ORA_DISK_1: finished piece 1 at 19-AUG-09

piece handle=/oradata/racdb/0akn3sv1_1_1 tag=TAG20090819T201659 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 19-AUG-09

RMAN>

5 Switch the database files to CFS:

RMAN> SWITCH DATABASE TO COPY;

datafile 1 switched to datafile copy\

"/oradata/racdb/data_D-RACDB_I-439523838_TS-SYSTEM_FNO-1_04kn3str"


"/oradata/racdb/data_D-RACDB_I-439523838_TS-SYSAUX_FNO-2_05kn3sub"


"/oradata/racdb/data_D-RACDB_I-439523838_TS-UNDOTBS1_FNO-3_06kn3suq"


"/oradata/racdb/data_D-RACDB_I-439523838_TS-USERS_FNO-4_09kn3sv0"


"/oradata/racdb/data_D-RACDB_I-439523838_TS-UNDOTBS2_FNO-5_07kn3suu"

RMAN>

Note: Once you have migrated all the datafiles to CFS, the original datafilesstored on theASMdisk groups aremarked as copies. Youmayuse these copiesas backup or to migrate back to the ASM storage system.

6 Rename the Oracle datafiles.

For an example, seeAppendixB,Renaming thedatabase files in this document.

Completing the post-migration stepsOnce you have migrated the ASM database to CFS, the temporary tablespace andthe redo log files must be relocated and created on CFS.

■ To create a temporary tablespace on CFSSee “Creating the temporary tablespace on CFS” on page 19.


18

■ To create the online redo log filesSee “Creating the online redo log files on CFS” on page 19.

Creating the temporary tablespace on CFSComplete the following steps to create a temporary tablespace on CFS.

To create a temporary tablespace on CFS

1 Exit RMAN and open the database on one of the nodes:

RMAN> exit


SQL> alter database open;

2 Create the temporary tablespace in CFS:

SQL> create temporary tablespace temp_nonasm \

tempfile '/oradata/racdb/temp_nonasm.dbf' size 100M;

3 Set the new temporary tablespace as default and the drop the old temporarytablespace:

SQL> alter database default temporary tablespace temp_nonasm;

SQL> drop tablespace temp;

Creating the online redo log files on CFSComplete the following steps to create the online redo log files on CFS.


To create the online redo log files

1 Archive the online redo log files. Stop the archiving process after the onlineredo log files have been archived.

SQL> alter system archive log all;

SQL> alter system archive log stop;

2 Get the number, size, thread, and group information for the existing log files:

SQL> col member format a25

SQL> select lf.member, l.bytes, l.group#, l.thread# from\

v$logfile lf, v$log l where lf.group# = l.group# and\

lf.type = 'ONLINE' order by l.thread#,l.sequence#;

MEMBER BYTES GROUP# THREAD#

------------------------- ---------- ---------- ----------

+DATADG/racdb/redo01.log 52428800 1 1




3 Create the redo log files for thread 1 and thread 2 onCFS. Thread 1 and thread2 reside on the nodes galaxy and nebula respectively.

Note: Start the redo log file group creation with group 5 on CFS because ASMuses groups 1-4.

To create redo log files for thread 1:

■ Add a new log file for thread 1:

SQL> alter database add logfile thread 1

group 5 ('/oradata/racdb/log11.log') size 50M ,

group 6 ('/oradata/racdb/log12.log') size 50M;

■ Perform a log file switch twice to make the newly created log file groups5 and 6 active and current, respectively. Drop the old redo log file groups1 and 2 once they are inactive.

SQL> alter system switch logfile;


SQL> select group#, status from v$log;

GROUP# STATUS


20

-------- ------------

1 INACTIVE

2 INACTIVE

3 INACTIVE

4 CURRENT

5 ACTIVE

6 CURRENT

SQL> alter database drop logfile group 1;


To create redo log files for thread 2:

■ Add a new file for thread 2:

SQL> alter database add logfile thread 2

group 7 ('/oradata/racdb/log21.log') size 50M ,

group 8 ('/oradata/racdb/log22.log') size 50M;

■ Start the other database instance and switch the log files for the secondinstance. This makes the existing log file groups inactive.



SQL> select group#, status from v$log;

GROUP# STATUS

-------- ------------

4 INACTIVE

5 INACTIVE

6 CURRENT

7 ACTIVE

8 CURRENT




4 Set the destination directory of the archive log files to the CFS location:

ALTER SYSTEM SET log_archive_dest_1=\

'LOCATION=your new destination directory';

5 Migrate the spfile(server parameter file) from the ASM disk group to CFS :

SQL> create pfile='/tmp/tempinit1.ora' from spfile;

SQL> create spfile ='/oradata/racdb/spfileracdb.ora'

\from pfile='/tmp/tempinit1.ora';

Edit the init<SID>.ora file for each instance to point to the new location ofthe spfile:

SPFILE='/oradata/racdb/spfileracdb.ora'

Verifying the databaseAfter you have completed the post-migration steps verify the migrated database.


22

To verify the migrated database

1 Make sure that all the redo log and database files have been migrated to theCFS:

SQL> select member from v$logfile;

MEMBER

------------------------

/oradata/racdb/log11.log




SQL> select name from v$datafile;

NAME

----------------------------------------------------------------

/oradata/racdb/data_D-RACDB_I-439523838_TS-SYSTEM_FNO-1_04kn3str

/oradata/racdb/data_D-RACDB_I-439523838_TS-SYSAUX_FNO-2_05kn3sub

/oradata/racdb/data_D-RACDB_I-439523838_TS-UNDOTBS1_FNO-3_06kn3suq

/oradata/racdb/data_D-RACDB_I-439523838_TS-USERS_FNO-4_09kn3sv0

/oradata/racdb/data_D-RACDB_I-439523838_TS-UNDOTBS2_FNO-5_07kn3suu

SQL> select name from v$controlfile;

NAME

----------------------------

/oradata/racdb/control01.ctl

SQL> select name from v$tempfile;

NAME

-----------------------------------

/oradata/racdb/temp_nonasm.dbf

Note: The output of v$datafile output will be different after you rename theOracle datafiles.

2 Exit sqlplus:

SQL> EXIT


3 Check Oracle CRS after migration:

$ crs_stat -t

Name Type Target State Host

------------------------------------------------------------

ora....b1.inst application ONLINE ONLINE galaxy

ora....b2.inst application ONLINE ONLINE nebula

ora.racdb.db application ONLINE ONLINE nebula

ora....05.lsnr application ONLINE ONLINE galaxy

ora....l05.gsd application ONLINE ONLINE galaxy

ora....l05.ons application ONLINE ONLINE galaxy

ora....l05.vip application ONLINE ONLINE galaxy

ora....06.lsnr application ONLINE ONLINE nebula

ora....l06.gsd application ONLINE ONLINE nebula

ora....l06.ons application ONLINE ONLINE nebula

ora....l06.vip application ONLINE ONLINE nebula

(oracle@nebula)[~/db11g/lib]

4 Stop and start up the database:

$ srvctl stop database -d racdb

$ srvctl start database -d racdb

5 Check the status of the database:

$ srvctl status database -d racdb

Instance racdb1 is running on node galaxy

Instance racdb2 is running on node nebula

6 After you verify the database, back up the database.

Removing the ASM database filesDelete the ASM datafile copies using the RMAN utility:

RMAN> DELETE NOPROMPT FORCE COPY;

RMAN> exit

Note: RMAN stores a copy of the ASM datafiles in the database control filerepository. After you have migrated from ASM to CFS, you must delete thesedatafile copies. For an example on deleting copies using RMAN, see Appendix C,Deleting ASM datafile copies using the RMAN utility in this document.


24

Removing the ASM cluster instances from the SF Oracle RAC nodesAfter you have deleted the datafile copies, you must remove the ASM clusterinstances from all the SF Oracle RAC nodes.

To remove the ASM cluster instances

1 Remove the dependency of the database instances with the ASM instances:

Syntax:

$srvctl modify instance -d db_unique_name -i\

inst_name {-n node_name | -s <asm_instance_name> | -r}

Example:

$ srvctl modify instance -d racdb -i racdb1 -r

$ srvctl modify instance -d racdb -i racdb2 -r

Note:Each database instance is bound to oneASM instance only. Hence, eachinstance picks up the associated ASM instance automatically. The -r optionremoves the ASM instance dependency.

2 Stop the ASM instances on all the nodes:

$ srvctl stop asm -n galaxy

$ srvctl stop asm -n nebula

3 Remove the ASM instances from all the nodes:

$ srvctl remove asm -n galaxy

$ srvctl remove asm -n nebula

Removing the ASM storageTo complete the migration process, remove the ASM disk group volumes to freethe space occupied by the disk group volumes. If the disk groups reside onVeritasVolumeManager(VxVM) log on to the CVMmaster node and stop all the volumes:

# vxvol –g stopall VxVMdiskgroup

From the CVM master remove the VxVM diskgroup:

#vxdg destroy VxVMdiskgroup


Note: If the ASM disk groups use raw devices, then RMAN frees the space whileremoving the ASM database files. To make the raw devices reusable, restore thedefault owner/group.


26

Sample migrationprocedure for multipleshared volumes

This appendix includes the following topics:

■ Sample migration procedure for multiple shared volumes

Sample migration procedure for multiple sharedvolumes

This example illustrates the migration procedure from an ASM database to CFSfor multiple shared volumes.

Preparing to migrateComplete the following steps before you migrate from ASM to CFS

AAppendix

To prepare for migration

1 View the existing database files using SQL plus:

SQL> SELECT FILE#,NAME FROM V$DATAFILE;

1 +ORADATA/racdb/system01.dbf

2 +ORADATA/racdb/sysaux01.dbf

3 +ORADATA/racdb/undotbs01.dbf

4 +ORADATA/racdb/users01.dbf




2 Add shared storage for CFS and create a mount point:

# vxdg -s init oradata1 c7t0d3

# vxdg -g oradata1 set activation=sw

# vxassist -g oradata1 make datavol1 10g

# mkfs -F vxfs /dev/vx/rdsk/oradata1/datavol1

# mkdir /oradata1

# mount -F vxfs -o cluster /dev/vx/dsk/oradata2/datavol1 /oradata1/

# chown -R oracle:oinstall /oradata1/

3 Login as Oracle user on one of the nodes in the cluster and create a directoryfor placing the datafile on this mount(oradata 1):

$ mkdir -p /oradata1/racdb

4 Add shared storage and create a second mount point:

# vxdg -s init oradata2 c7t0d4

# vxdg -g oradata2 set activation=sw

# vxassist -g oradata2 make datavol2 10g

# mkfs -F vxfs /dev/vx/rdsk/oradata2/datavol2

# mkdir /oradata2

# mount -F vxfs -o cluster /dev/vx/dsk/oradata2/datavol2 /oradata2/

# chown -R oracle:oinstall /oradata2/

Migrating from ASM to CFSMigrate the datafiles fromASMtoCFSusing theRMANutility. The datafile namesare as mentioned in the 'Preparing to migrate' section.

Sample migration procedure for multiple shared volumesSample migration procedure for multiple shared volumes

28

To migrate from ASM to CFS using RMAN

1 Back up the datafiles 1,2 and 4 to /oradata1

RMAN> BACKUP AS COPY datafile 1 format '/oradata1/racdb/%U';

Starting backup at 28-JAN-10




input datafile file number=00001 name=+ORADATA/racdb/system01.dbf

output file name=/oradata1/racdb/data_D-RACDB_I-707107606_TS- SYSTEM_FNO-1_01l4k4u4\




copying current control file

output file name=/oradata1/racdb/cf_D-RACDB_id-707107606_02l4k4uj\



channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current SPFILE in backup set

channel ORA_DISK_1: starting piece 1 at 28-JAN-10

channel ORA_DISK_1: finished piece 1 at 28-JAN-10

piece handle=/oradata1/racdb/03l4k4uk_1_1 tag=TAG20100128T184315 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 28-JAN-10





input datafile file number=00002 name=+ORADATA/racdb/sysaux01.dbf

output file name=/oradata1/racdb/data_D-RACDB_I-707107606_TS- SYSAUX_FNO-2_04l4k4vh\








input datafile file number=00004 name=+ORADATA/racdb/users01.dbf

output file name=/oradata1/racdb/data_D-RACDB_I-707107606_TS- USERS_FNO-4_05l4k511\

29Sample migration procedure for multiple shared volumesSample migration procedure for multiple shared volumes




RMAN>

RMAN> switch datafile 1 to copy;


"/oradata1/racdb/data_D-RACDB_I- 707107606_TS-SYSTEM_FNO-1_01l4k4u4"



"/oradata1/racdb/data_D-RACDB_I- 707107606_TS-SYSAUX_FNO-2_04l4k4vh"



"/oradata1/racdb/data_D-RACDB_I- 707107606_TS-USERS_FNO-4_05l4k511"

RMAN>

2 Back up the datafiles 3,5,6 and 7 to /oradata2

run

{

BACKUP AS COPY datafile 3 format '/oradata2/racdb/%U';

switch datafile 3 to copy;







}

RMAN> run

2> {

3> BACKUP AS COPY datafile 3 format '/oradata2/racdb/%U';


4> BACKUP AS COPY datafile 5 format '/oradata2/racdb/%U';





30



}

RMAN>




input datafile file number=00003 name=+ORADATA/racdb/undotbs01.dbf

output file name=/oradata2/racdb/data_D-RACDB_I-707107606_TS- UNDOTBS1_FNO-3_09l4k6bq\






"/oradata2/racdb/data_D-RACDB_I- 707107606_TS-UNDOTBS1_FNO-3_09l4k6bq"

RMAN>





output file name=/oradata2/racdb/data_D-RACDB_I-707107606_TS- UNDOTBS2_FNO-5_06l4k5v7\




RMAN>


"/oradata2/racdb/data_D-RACDB_I- 707107606_TS-UNDOTBS2_FNO-5_06l4k5v7"

RMAN>





output file name=/oradata2/racdb/data_D-RACDB_I-707107606_TS- UNDOTBS3_FNO-6_07l4k5v9\




31Sample migration procedure for multiple shared volumesSample migration procedure for multiple shared volumes

RMAN>


"/oradata2/racdb/data_D-RACDB_I- 707107606_TS-UNDOTBS3_FNO-6_07l4k5v9"

RMAN>





output file name=/oradata2/racdb/data_D-RACDB_I-707107606_TS- UNDOTBS4_FNO-7_08l4k5vb\




3 Verify the datafiles after migration:

SQL> SELECT FILE#,NAME FROM V$DATAFILE;

FILE# NAME

---------- -------------------------------------------------------------------------------------------------

1 /oradata1/racdb/data_D-RACDB_I-707107606_TS-SYSTEM_FNO-1_01l4k4u4

2 /oradata1/racdb/data_D-RACDB_I-707107606_TS-SYSAUX_FNO-2_04l4k4vh

3 /oradata2/racdb/data_D-RACDB_I-707107606_TS-UNDOTBS1_FNO-3_09l4k6bq

4 /oradata1/racdb/data_D-RACDB_I-707107606_TS-USERS_FNO-4_05l4k511

5 /oradata2/racdb/data_D-RACDB_I-707107606_TS-UNDOTBS2_FNO-5_06l4k5v7

6 /oradata2/racdb/data_D-RACDB_I-707107606_TS-UNDOTBS3_FNO-6_07l4k5v9

7 /oradata2/racdb/data_D-RACDB_I-707107606_TS-UNDOTBS4_FNO-7_08l4k5vb

7 rows selected.


32

Renaming the databasefiles


■ Renaming the database files

Renaming the database filesThe Oracle database files must be renamed in the following manner.

To rename the Oracle database files

1 Shut down the database:

SQL> shutdown immediate

2 Move the datafile to the destination location:

$ mv source destination

For example:

$ cd /oradata/racdb

$ mv data_D-RACDB_I-439523838_TS-SYSTEM_FNO-1_04kn3str\

/oradata/racdb/mydatafile.dbf

3 Mount the database:

SQL> startup mount

BAppendix

4 Rename the datafiles.

Note: Each datafile must be renamed separately.

SQL> alter database rename filesource to destination

For example:

SQL> alter database rename file

'/oradata/racdb/data_D-RACDB_I-439523838_TS-SYSTEM_FNO-1_04kn3str\

/oradata/racdb/mydatafile.dbf'

to '/oradata/racdb/mydatafile.dbf'

5 Verify the renamed datafiles:

SQL> alter database open;

SQL> SELECT tablespace_name, file_name FROM dba_data_files;

Renaming the database filesRenaming the database files

34

Deleting ASM data filecopies using the RMANutility


■ Deleting ASM datafile copies using the RMAN utility

Deleting ASM datafile copies using the RMAN utilityThis section illustrates the removal of the ASM datafiles using the delete copy

command in RMAN.

RMAN> DELETE NOPROMPT FORCE COPY;

using target database control file instead of recovery catalog



List of Datafile Copies

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

Key File S Completion Time Ckp SCN Ckp Time

------- ---- - --------------- ---------- ---------------

5 1 A 28-JAN-10 908378 28-JAN-10

Name: +ORADATA/racdb/system01.dbf

6 2 A 28-JAN-10 908378 28-JAN-10

Name: +ORADATA/racdb/sysaux01.dbf

CAppendix

15 3 A 28-JAN-10 908378 28-JAN-10

Name: +ORADATA/racdb/undotbs01.dbf

7 4 A 28-JAN-10 908378 28-JAN-10

Name: +ORADATA/racdb/users01.dbf

9 5 A 28-JAN-10 908378 28-JAN-10


11 6 A 28-JAN-10 908378 28-JAN-10


13 7 A 28-JAN-10 908378 28-JAN-10


List of Control File Copies

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

Key S Completion Time Ckp SCN Ckp Time

------- - --------------- ---------- ---------------

2 A 28-JAN-10 908378 28-JAN-10

Name: /oradata1/racdb/cf_D-RACDB_id-707107606_02l4k4uj

Tag: TAG20100128T184315

List of Archived Log Copies for database with db_unique_name RACDB

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

Key Thrd Seq S Low Time

------- ---- ------- - ---------

1 1 3 A 28-JAN-10

Name: +FLASHBACK/racdb/archivelog/2010_01_28/thread_1_seq_3.266.709490981

6 1 4 A 28-JAN-10


10 1 5 A 28-JAN-10


14 1 6 A 28-JAN-10


2 2 1 A 28-JAN-10

Deleting ASM data file copies using the RMAN utilityDeleting ASM datafile copies using the RMAN utility

36


5 2 2 A 28-JAN-10


7 2 3 A 28-JAN-10


8 2 4 A 28-JAN-10


4 3 1 A 28-JAN-10


11 3 2 A 28-JAN-10


12 3 3 A 28-JAN-10


13 3 4 A 28-JAN-10


3 4 1 A 28-JAN-10


9 4 2 A 28-JAN-10


deleted datafile copy

datafile copy file name=+ORADATA/racdb/system01.dbf RECID=5 STAMP=709498005


datafile copy file name=+ORADATA/racdb/sysaux01.dbf RECID=6 STAMP=709498022


datafile copy file name=+ORADATA/racdb/undotbs01.dbf RECID=15 STAMP=709499312


datafile copy file name=+ORADATA/racdb/users01.dbf RECID=7 STAMP=709498032






37Deleting ASM data file copies using the RMAN utilityDeleting ASM datafile copies using the RMAN utility


deleted control file copy

control file copy file name=/oradata1/racdb/cf_D-RACDB_id-707107606_02l4k4uj\

RECID=2 STAMP=709497811

deleted archived log

archived log file name=\

+FLASHBACK/racdb/archivelog/2010_01_28/thread_1_seq_3.266.709490981\








+FLASHBACK/racdb/archivelog/2010_01_28/thread_1_seq_5.275.709496261\ RECID=10 STAMP=709496261





























38


















Deleted 22 objects

RMAN>

39Deleting ASM data file copies using the RMAN utilityDeleting ASM datafile copies using the RMAN utility


40

Documents

Migrating an Oracle RAC database from Automatic Storage