暂无图片

QUERY_REWRITE_INTEGRITY:QUERY_REWRITE_INTEGRITY determines the degree to which query rewriting must be enforced by the Oracle server. In the safest level, query rewrite transformations that rely on unenforced relationships are not used. With ENFORCE, consistency and integrity are enforced and guaranteed by Oracle. With NO_ENFORCE, rewrites are allowed using relationships that have been declared, but that are not enforced by Oracle. With USE_STALE, rewrites are allowed using unenforced relationships, and materialized views are eligible for rewrite even if they are known to be inconsistent with the underlying detail data. Parameter Type: String Syntax: QUERY_REWRITE_INTEGRITY = { enforced | trusted | stale_tolerated } Default value: ENFORCE Range of values: enforce, trusted, stale_tolerated Modifiable: ALTER SESSION, ALTER SYSTEM Real Application Clusters: Multiple instances can have different values. Version: 8.1.4

错误码

错误描述:QUERY_REWRITE_INTEGRITY determines the degree to which query rewriting must be enforced by the Oracle server. In the safest level, query rewrite transformations that rely on unenforced relationships are not used. With ENFORCE, consistency and integrity are enforced and guaranteed by Oracle. With NO_ENFORCE, rewrites are allowed using relationships that have been declared, but that are not enforced by Oracle. With USE_STALE, rewrites are allowed using unenforced relationships, and materialized views are eligible for rewrite even if they are known to be inconsistent with the underlying detail data. Parameter Type: String Syntax: QUERY_REWRITE_INTEGRITY = { enforced | trusted | stale_tolerated } Default value: ENFORCE Range of values: enforce, trusted, stale_tolerated Modifiable: ALTER SESSION, ALTER SYSTEM Real Application Clusters: Multiple instances can have different values. Version: 8.1.4

向认证技术专家提问

向技术专家提问

相关搜索
查看更多》