Migrating files to ASM
Oracle 11g New Features Tips by Burleson
June 27, 2008
Moving files to ASM
The OEM page for Migrate Database to ASM
makes it easier to use Enterprise Manager to migrate non-ASM
Automatic Storage Management (ASM) was a new
feature in Oracle 10g that freed the Remote DBA from managing files and
disk drives, which eliminated the need for third-party volume
managers. Later, Oracle 10gR2 introduced the ability to
migrate an entire database to ASM. Finally, 11g now supports
the capability to migrate tablespaces to ASM with a Tablespace
Migration Wizard in OEM.
Initially, migrating a tablespace to ASM may be
a little tricky. The process is begun by first clicking the Server
tab, then Migrate to ASM. Next is a prompt to enter host
credentials, followed by a migration options screen. The next
screen presented is the Disk Group Options, as shown in Figure 4.11.
Figure 4.11 Using
the Customize button within the Disk Group Options page
Click the Customize button, as noted in Figure
4.11 above, and the next screen allows the selection of specific
tablespaces to migrate over to ASM, as shown in Figure 4.12.
Selecting tablespaces for migration to ASM
In 10g, using the Enterprise Manager 10g Java
Console to manage Advanced Replication and Workspace was required.
However, in 11g Remote DBAs can access the Workspace Manager within OEM.
To access the Workspace Manager interface, click the Schema tab,
then Workspaces. The Workspace Manager has been improved to
include support for:
Find Referential Integrity Constraints
Previously, Remote DBAs would call the
DBMS_WM.FindRICSet procedure to find tables that needed to be
version-enabled due to referential integrity constraints. 11g
provides an interface for this, as shown in Figure 4.13.
Version-enabling tables in the new 11g interface
Compress a Workspace
To compress a workspace within OEM, choose
Compress from the Actions dropdown as shown in Figure 4.14.
command line Aproach
Oracle ACE Aman
Sharma also offers these suggestions for migrating to ASM using
RMAN. The migration from normal filesystem to ASM is
actually not a very challenging task. All what you have to do is
1 - Take a
backup on the Flash Recovery Area (FRA) which should be lying on
the ASM diskgroup using RMAN's copy option.
2. Once this is
done, using the RMAN "switch to copy option", the database would
be shifted to ASM.
This is an
excerpt from the new book
Oracle 11g New Features: Expert Guide to the Important
New Features by John Garmany, Steve Karam, Lutz Hartmann, V. J.
Jain, Brian Carr.
You can buy it direct from the publisher
for 30% off.