Global Sequences are Oracle sequences that generate unique values across multiple instances in an Oracle RAC or a Data Guard configuration. Regarding their behavior and performance when connected to a physical standby database with Real-Time Query enabled:
A: The usage of Global Sequences can indeed have a performance impact on the primary database due to the need to generate unique values that are consistent across both primary and standby databases.
D: The performance impact on the physical standby database may occur if theCACHEsize is too small. This is because the standby database will frequently have to access the primary database to replenish the cache, which can increase the load and potentially lead to performance degradation.
E: Global Sequences should have theNOORDERandCACHEoptions set. TheNOORDERoption ensures that sequence numbers are provided without guaranteeing sequence order, thus improving scalability and performance. TheCACHEoption is used to specify how many sequence values will be held in memory for faster access.
Option B is incorrect as theLOG_ARCHIVE_DEST_nparameter's definition for standbys pointing back to the primary does not directly pertain to the creation of sequences.
Option C is incorrect because there is no requirement that the size of the cache for a sequence must be at least 100. TheCACHEsize can be set to a different number based on specific use cases or performance considerations.
[References:Oracle's documentation on sequences and their behavior in a Data Guard environment provides insights into the performance considerations and best practices for using sequences, particularly in a Real-Time Query context., ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit