SQL> ! mv /u06/oradata/xport.dbf /u05/oradata/xport.dbf
SQL> alter tablespace xport rename datafile
2 '/u06/oradata/xport.dbf' to '/u05/oradata/xport.dbf';
Tablespace altered.
SQL> alter tablespace xport online;
Tablespace altered.
Note how this method is much more straightforward and much less disruptive than the alter
database method. The only downtime for the XPORT tablespace is the amount of time it takes to
move the datafile from one disk volume to another.
Moving Datafiles with EM Database Control
In release 1 of Oracle Database 11g, EM Database Control does not have an explicit function for
moving a datafile, short of performing a tablespace reorganization, as demonstrated earlier in the
chapter. For moving a datafile to another volume, this is overkill.
Moving Online Redo Log Files
Although it is possible to indirectly move online redo log files by dropping entire redo log groups
and re-adding the groups in a different location, this solution will not work if there are only two
redo log file groups because a database will not open with only one redo log file group. Temporarily
adding a third group and dropping the first or second group is an option if the database must be
kept open; alternatively, the method shown here will move the redo log file(s) while the database
is shut down.
In the following example, we have three redo log file groups with two members each. One
member of each group is on the same volume as the Oracle software and should be moved to
a different volume to eliminate any contention between log file filling and accessing Oracle
software components.
Pages:
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191