博客
关于我
强烈建议你试试无所不能的chatGPT,快点击我
不被Database Replay支持的请求
阅读量:4556 次
发布时间:2019-06-08

本文共 2122 字,大约阅读时间需要 7 分钟。

ocp 053

675.Which two client requests are captured during database replay Capture? (Choose two)

A. Flashback queries

B. Shared server requests

C. Login and logoff activities of sessions

D. Direct path load of data from external files by using utilities such as SQL *loader

E. Data definition language (DDL) and data manipulation language (DML) operations

Answer: CE

答案解析:

参考:

排除法,选CE

 

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.

  • JAVA_XA transactions

    If the workload uses the JAVA_XA package, JAVA_XA function and procedure calls are captured as normal PL/SQL workload. To avoid problems during workload replay, consider dropping the JAVA_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.

转载于:https://www.cnblogs.com/gispf/p/3792803.html

你可能感兴趣的文章
$.each 和$(selector).each()的区别
查看>>
11-EasyNetQ之多态发布和订阅
查看>>
iOS App 的运行周期
查看>>
一、 kettle开发、上线常见问题以及防错规范步骤
查看>>
XSS Script
查看>>
qt中文乱码问题
查看>>
sed 删除最后几行 和删除指定行 awk使用
查看>>
LeetCode: Candy
查看>>
单词统计
查看>>
web基础,用html元素制作web页面
查看>>
[LeetCode] String to Integer (atoi)
查看>>
移动端设置-----rem
查看>>
JS数组和函数
查看>>
软件工程综合实践专题-第三次作业-了解原型设计的工具
查看>>
SpringMVC之ajax传递jason数据详解以及@RequestBody和@ResonseBody注解
查看>>
Oprofile:CPU性能分析工具指南
查看>>
python 调用apollo
查看>>
文件上传与下载
查看>>
Jmeter之压测探索和结果分析
查看>>
【CQOI2017】小Q的棋盘
查看>>