Questions Regarding Oracle Replication Objects

1. We are doing some volume testing in our replicated environment and have encountered maxextents errors on a variety of Oracle objects which support replication, including the deferred queue. These objects are all defined with initial and next extent sizes of 16K and a maxextents of 505. To get our test to run, we changed the maxextents to unlimited on each object that encountered the error. We started to play with the next extents sizes, but thought better of it and stopped.

 None of the Oracle documentation mentions configuring these objects, so is  what we're encountering typical? Has anyone else run into these limits  and modified them? Should we go through and set all DEF$ objects to  unlimited?  

 The specific objects that we had trouble with, owed by SYSTEM, were:  

• Deferred queue table DEF$_AQCALL and two indexes on it: PK index and DEF$_TRANORDER
• Table DEF$_CALLDEST and two indexes on it: DEF$_CALLDEST_PRIMARY and DEF$_CALLDEST_N2 2. Related to this is placement of the replication objects owned by SYSTEM. Should they be located in SYSTEM or built in a separate tablespace? In our installation, some objects are in SYSTEM (like the deferred queue) and some are in TOOLS (because we typically change SYSTEM's default tablespace to TOOLS and we ran catrep.sql after doing so).

 Should SYSTEMs default tablespace be left as SYSTEM?  Is it feasible to build the replication objects, especially the deferred  queue, in their own tablespace (and not SYSTEM)?  

 3. How does Oracle generated deferred_tran_ids? Can we ever run out of  numbers? Received on Mon Jul 10 2000 - 22:14:53 CDT