Moving the Replication Queue Tables (DEF$) Out of the System Tablespace
(Doc ID 1037317.6)
Last updated on SEPTEMBER 08, 2021
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 8.1.7.0 to 11.2.0.2 [Release 8.1.7 to 11.2]
Information in this document applies to any platform.
Purpose
The Oracle replication dictionary and deferred queue reside in the SYSTEM
tablespace. This may not be appropriate for systems that have large or high
throughput deferred queues, or where it may be necessary to reclaim fragmented
space.
This article describes the steps required to move the deferred queue out of the
SYSTEM tablespace. Due to the dependencies among the replication catalog tables
it is very important that these steps be carried out in order.
Scope
Before starting this procedure, perform the following:
1) Make sure all objects owned by SYS and SYSTEM are valid
2) Backup of the database
** Customers should be aware that while the procedures described in this
** document have been fully tested by Oracle Support Services, they have
** not been certified by** not been certified byOracle development.
** document have been fully tested by Oracle Support Services, they have
** not been certified by** not been certified byOracle development.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |