- 最后登录
- 2014-3-28
- 在线时间
- 118 小时
- 威望
- 5
- 金钱
- 394
- 注册时间
- 2011-10-12
- 阅读权限
- 100
- 帖子
- 110
- 精华
- 0
- 积分
- 5
- UID
- 10
|
2#
发表于 2012-8-21 16:20:45
参考下sql reference中的parallel_clause部分:
Notes on the parallel_clause The following notes apply to the parallel_clause:
■ Parallelism is disabled for DML operations on tables on which you have defined a
trigger or referential integrity constraint.
■ When you specify the parallel_clause during creation of a table, if the table
contains any columns of LOB or user-defined object type, then subsequent
INSERT, UPDATE, DELETE or MERGE operations that modify the LOB or object
type column are executed serially without notification. Subsequent queries,
however, will be executed in parallel.
■ A parallel hint overrides the effect of the parallel_clause.
■ DML statements and CREATE TABLE ... AS SELECT statements that reference
remote objects can run in parallel. However, the remote object must really be on a
remote database. The reference cannot loop back to an object on the local database,
for example, by way of a synonym on the remote database pointing back to an
object on the local database.
■ DML operations on tables with LOB columns can be parallelized. However,
intrapartition parallelism is not supported.
Note: The syntax of the parallel_clause supersedes syntax
appearing in earlier releases of Oracle. Superseded syntax is still
supported for backward compatibility but may result in slightly
different behavior from that documented.
See Also: Oracle Database Performance Tuning Guide, Oracle Database
Concepts, and Oracle Database Data Warehousing Guide for more
information on parallelized operations, and "PARALLEL Example" on
page 16-51 |
|