Database Reference
In-Depth Information
9.
rename the current
RAPTEST
tablespace (give it a new name).
SQL> ALTER TABLESPACE RAPTEST RENAME TO RAPTEST_COPY;
10.
Verify rename of tablespace.
11.
import the transportable tablespace. set the host from the sQl prompt to complete the
operation.
SQL> host bash-3.2$ impdp system dumpfile=expdat.dmp directory=data_pump_dir
transport_datafiles ='+OBITST_DATA/obitst/datafile/raptest01.dbf' remap_
schema=raptest:raptest1 logfile=tts_import.log
12.
Change tablespace back to read write.
SQL> ALTER TABLESPACE RAPTEST_COPY READ WRITE;
13.
Change new tablespace to read write.
SQL> ALTER TABLESPACE RAPTEST READ WRITE;
14.
assign the new tablespace as the default tablespace to owner schema.
SQL> ALTER USER RAPTEST1 DEFAULT TABLESPACE RAPTEST;
■
another option to restore the database to an earlier state is to use flashback mode in the database and flash
the database back to a point in time.
Note
SQL Performance Analyzer
Similar to the Database Replay functionality, the SQL Performance Analyzer is focused on predicting and preventing
performance problems for any environment changes that may affect SQL execution times. This functionality provides
assessment of environment change on an SQL execution plan and statistics by running the SQL statements serially
before change and after change on the different environments. Based on the reports generated from the Database
Replay functionality when migrating from single instance to a RAC configuration, this functionality can help tune SQL
statements to scale across multiple instances: for example, optimizing SQL statements to use parallelism on a single
instance and then scaling the query across multiple instances. Apart from testing a single query or multiple queries for
scalability, SQL Performance Analyzer (SPA) can also be used to test the effect of parameter changes or SQL structure
changes or changes to Oracle database optimizer versions. Figure
5-22
illustrates the various options provided by SPA.
Search WWH ::
Custom Search