| Tablespace for LogMiner Objects on the Primary
Database
The metadata for a logical Oracle instance
is
maintained in SYS and SYSTEM schema, which, by default, is kept in
the system tablespace. These metadata are mostly related to LogMiner
activity on the logical standby site. It is good practice to create
a dedicated tablespace on the primary database for these objects and
to move these objects from the system tablespace to the new
tablespace before a backup is made to be used to create a logical
standby database.
As a result, this tablespace will exist in both
the primary and the standby database. Although this is an optional
step in creating a logical standby database, it might save
considerable time later when a switchover between the primary and
the logical Oracle instance
is performed.
Oracle provides the
dbms_logmnr_d.set_tablespace procedure to move all these log miner
related objects to a new tablespace. The syntax is:
EXECUTE DBMS_LOGMNR_D.SET_TABLESPACE ('<New
Tablespace Name>');
Once these preparatory tasks have been
completed, the process to start the creation of the logical standby
database can begin. The next section will present the step-by-step
process of creating a logical standby database. For this text, it is
assumed that there is no other Oracle instance
associated with this
primary database.
|
