OCP-1Z0-053-V12.02-257题

257.Which client requests to the database can be captured as a part of the workload capture? (Choose all that apply.)
A. flashback query
B. distributed transactions
C. logging in and logging out of sessions
D. all DDL statements having bind variables
E. direct path load of data from external files
Answer: CD

答案解析：

参考：http://docs.oracle.com/cd/E11882_01/server.112/e41481/dbr_capture.htm#RATUG115

排除法，选CD

同675题：/article/1348094.html

The following types of user sessions and client requests are not supported by Database Replay:

Direct path load of data from external files using utilities such as SQL*Loader

Non-PL/SQL based Advanced Queuing (AQ)

Flashback queries

Oracle Call Interface (OCI) based object navigations

Non SQL-based object access

Distributed transactions

Any distributed transactions that are captured will be replayed as local transactions.

XA transactions

XA transactions are not captured or replayed. All local transactions are captured.

J***A_XA

transactions

If the workload uses the

J***A_XA

package,

J***A_XA

function and procedure calls are captured as normal PL/SQL workload. To avoid problems during workload replay, consider dropping the

J***A_XA

package on the replay system
to enable the replay to complete successfully.

Database Resident Connection Pooling (DRCP)

Workloads using OUT binds

Multi-threaded Server (MTS) and shared server sessions with synchronization mode set to

OBJECT_ID

Migrated sessions

The workload is captured for migrated sessions. However, user logins or session migration operations are not captured. Without a valid user login or session migration, the replay may cause errors because the workload may be replayed by a wrong user.

Typically, Database Replay refrains from capturing these types of non-supported user sessions and client requests. Even when they are captured, Database Replay will not replay them. Therefore, it is usually not necessary to manually
filter out non-supported user sessions and client requests. In cases where they are captured and found to cause errors during replay, consider using workload capture filters to exclude them from the workload.