If you are using automatic file management, you only need to
create the new tablespace in the primary database for it to be propagated to the standby
databases.
To drop a tablespace, simply drop it in the primary database and force a log switch via the
alter system switch logfile command. You can then drop the file at the operating system level in
the primary and standby environments.
Changes to the names of datafiles are not propagated, even if you are using automatic file
management. To rename a datafile in a Data Guard configuration, take the tablespace offline and
rename the datafile at the operating system level on the primary server. Use the alter tablespace
rename datafile command on the primary database to point to the new location of the datafile.
Bring the tablespace back online with the alter tablespace tablespace_name online command.
On the standby database, query the V$ARCHIVED_LOG view to verify all logs have been applied
and then shut down the redo apply services:
alter database recover managed standby database cancel;
Shut down the standby database and rename the file on the standby server. Next, use the
startup mount command to mount the standby database. With the database mounted but not
opened, use the alter database rename file command to point to the new file location on the
standby server. Finally, restart the redo apply process:
alter database recover managed standby database
disconnect from session;
Performing DDL on a Logical Standby Database
As illustrated earlier in this chapter, you can temporarily disable Data Guard within a logical
standby database.
Pages:
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749