OCP 5 Database Replay

  1. When performing workload capture, what happens if you run out of space in the directory to which you are capturing workload data?
    The capture stops, but any workload captured to that point can be used for replay.
  2. Which four steps are required with Database Replay?
    Workload capture, preprocessing, replay, and analysis
  3. Which feature would you use to see how a system change, such as an operating system or database upgrade, might impact the system before actually implementing the change?
    Database Replay
  4. Before performing workload capture, must you restart the database?
    No, but for a clean capture, you should restart the database in RESTRICTED mode.
  5. When performing workload capture, are distributed transactions captured?
  6. When replaying workload, what does the THINK_TIME_SCALE parameter specify?
    The time between successive user calls in a session, or effectively, the replay speed
  7. After capturing database workload, what must be done to the workload before it can be replayed?
    It must be pre-processed.
  8. When performing workload capture, are user logins and logouts captured?
  9. When replaying workload, a TRUE value for which parameter will indicate that the replay will have its original commit order preserved?
    The SYNCHRONIZATION parameter
  10. When performing workload capture, are flashback queries captured?
  11. What does a THINK_TIME_SCALE parameter value of 0 indicate?
    The replay should be performed as quickly as possible.
  12. What does a CONNECT_TIME_SCALE parameter value of 0 indicate?
    The replay should attempt to connect all sessions immediately.
  13. Which replay parameter could you use to adjust session connect time during replay?
    The CONNECT_TIME_SCALE parameter
  14. Which replay parameter could you use to explicitly adjust the time between session requests during database replay?
    The THINK_TIME_SCALE parameter
Card Set
OCP 5 Database Replay
OCP 5 Database Replay