Which is true concerning Database Replay in an Oracle Real Application Cluster (RAC)
database?
A.
Workload capture is per instance.
B.
You only need to restart one instance to begin workload capture.
C.
Specifically in RAC, you shut down all instances, restart them individually, and begin
workload capture with the last instance started.
D.
RAC does not support workload capture, but it does support workload replay.
E.
None of the above.
Yes D is correct
Workload capture is per database.
In RAC you have to restart all instances before capturing.
Specifically in RAC, you shut down all instances, restart one of them and begin
workload capture, then start the other instances.
RAC does support workload capture.
See
http://oracle.su/docs/11g/server.112/e12254/dbr_capture.htm#CACCGCFB
E is actually correct for 11gR2.
https://docs.oracle.com/cd/E11882_01/server.112/e41481/dbr_capture.htm#RATUG109
For Oracle RAC, consider using a shared file system. Alternatively, you can set up one capture directory path that resolves to separate physical directories on each instance, but you will need to consolidate the files created in each of these directories into a single directory. The entire content of the local capture directories on each instance (not only the capture files) must be copied to the shared directory before it can be used for preprocessing or data masking. For example, assume that you are:
Running a Oracle RAC environment in Linux with two database instances named host1 and host2
Using a capture directory object named CAPDIR that resolves to /$ORACLE_HOME/rdbms/capture on both instances
Using a shared directory that resides in /nfs/rac_capture
You will need to login into each host and run the following command:
cp -r /$ORACLE_HOME/rdbms/capture/* /nfs/rac_capture
After this is done for both instances, the /nfs/rac_capture shared directory is ready to be preprocessed or masked.