[oracle@rh2 admin]$ pwd /s01/oracle/product/11.2.0/dbhome_1/network/admin [oracle@rh2 admin]$ cat sqlnet.ora ENCRYPTION_WALLET_LOCATION= (SOURCE=(METHOD=FILE)(METHOD_DATA= (DIRECTORY=/s01/wallet))) SQL> ALTER SYSTEM SET ENCRYPTION KEY AUTHENTICATED BY "oracle"; System altered. SQL> conn maclean/maclean Connected. SQL> create table enctab (t1 int encrypt); Table created. SQL> select * from enctab; no rows selected Execution Plan ---------------------------------------------------------- Plan hash value: 3026244987 ---------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ---------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 1 | 47 | 2 (0)| 00:00:01 | | 1 | TABLE ACCESS FULL| ENCTAB | 1 | 47 | 2 (0)| 00:00:01 | ---------------------------------------------------------------------------- Note ----- - dynamic sampling used for this statement (level=2) Statistics ---------------------------------------------------------- 0 recursive calls 0 db block gets 0 consistent gets 0 physical reads 0 redo size 330 bytes sent via SQL*Net to client 512 bytes received via SQL*Net from client 1 SQL*Net roundtrips to/from client 0 sorts (memory) 0 sorts (disk) 0 rows processed SQL> select * from enctab where t1=10; no rows selected Execution Plan ---------------------------------------------------------- Plan hash value: 3026244987 ---------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ---------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 1 | 47 | 2 (0)| 00:00:01 | |* 1 | TABLE ACCESS FULL| ENCTAB | 1 | 47 | 2 (0)| 00:00:01 | ---------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 1 - filter(INTERNAL_FUNCTION("T1")=10) Note ----- - dynamic sampling used for this statement (level=2) Statistics ---------------------------------------------------------- 1 recursive calls 0 db block gets 0 consistent gets 0 physical reads 0 redo size 330 bytes sent via SQL*Net to client 512 bytes received via SQL*Net from client 1 SQL*Net roundtrips to/from client 0 sorts (memory) 0 sorts (disk) 0 rows processed SQL> desc enctab; Name Null? Type ----------------------------------------- -------- ---------------------------- T1 NUMBER(38) ENCRYPT SQL> col WRL_PARAMETER for a20 SQL> set linesize 140 SQL> select * from V$ENCRYPTION_WALLET; WRL_TYPE WRL_PARAMETER STATUS -------------------- -------------------- ------------------ file /s01/wallet OPEN
Internal_Function with Encryption in SQL PLAN
原创maclean_007 ©著作权
©著作权归作者所有:来自51CTO博客作者maclean_007的原创作品,请联系作者获取转载授权,否则将追究法律责任
Sometimes,the columns are decrypted as a result and decrypt functions (appears as INTERNAL_FUNCTION in the execution plan) are applied on them, which can lead to poor approximations of column selectivity, leading to improper plans. This happens mostly when the encrypted columns are using SALT to encrypt the data, but it can happen for other reasons as well, including bugs.
Bug:7147087 AFTER ENABLING TDE, EXECUTION PLAN CHANGES FOR THE WORSE
and it can be recognized from the following symptoms:
1. both tables participating in a join have encrypted columns.
2. there is at least a join condition with encrypted columns at both ends.
3. the second table has an index on the join column(s).
4. the INTERNAL_FUNCTION is applied to the encrypted columns in the join in the second table and the execution plan that used to be an INDEX UNIQUE SCAN on the unenecrypted columns turns into an INDEX RANGE SCAN or FULL TABLE SCAN.
Scenario 2: Pushed Predicates
The second known TDE performance bug is the one when the queries are using pushed predicates on encrypted columns inside explicit or implicit views and the encrypted column values are decrypted to filter out the values instead of encrypting the pushed predicates. This situation is met when:
1. external predicates are pushed into views
2. the execution plan presents predicate of the form INTERNAL_FUNCTION(column) = ;
On the other hand, INTERNAL_FUNCTION may consume more memory and cpu than normal
上一篇:诊断RAC数据库的启动
提问和评论都可以,用心的回复会被更多人看到
评论
发布评论
相关文章
-
使用Azure Automation自动调整App Services Plan大小
说到App Services Plan大家可能比较陌生,但是如果提到Azure App Services大家肯定都很熟悉,相信很多朋友都在其上托管了一些Web应用。其实我们所使用的App Services始终是在App Services Plan中运行的。App Services Plan的定价层确定了所提供的App Services功能和计划费用。这也就意味着,如果想要控制App Services所产生的费用,就需要从App Services Plan入手。
Azure 成本优化 App Services Plan Web应用