SQLPerformanceAnalyzer實(shí)操

1、什么是SPA(SQL Performance Analyzer)？

SPA( SQL Performance Analyzer) 是Oracle的SQL性能優(yōu)化分析器。Oracle Database 11g 引入了 SQL 性能分析器；使用該工具可以準(zhǔn)確地評估數(shù)據(jù)庫變更對 SQL 語句的影響。SQL 性能分析器可幫助預(yù)測潛在的更改對 SQL 的性能影響。這種功能可向 DBA 提供有關(guān) SQL 語句性能的詳細(xì)信息，例如，執(zhí)行前后的統(tǒng)計(jì)信息，提高或降低性能的語句。

SPA其實(shí)也是Oracle Real Application Testing的一個(gè)組件，另外一個(gè)組件Database Replay。SPA的原理是通過變更前對收集的STS進(jìn)行執(zhí)行，獲取基線數(shù)據(jù)，變更后再次進(jìn)行執(zhí)行，然后進(jìn)行對比，從多個(gè)維度比如CPU時(shí)間，I/O，buffer get等生成詳細(xì)的變更對比報(bào)告。典型用法是捕捉STS，然后通過SPA生成對比報(bào)告，然后對變更后衰減的SQL調(diào)用STA進(jìn)行優(yōu)化。

創(chuàng)新互聯(lián)公司-專業(yè)網(wǎng)站定制、快速模板網(wǎng)站建設(shè)、高性價(jià)比兩當(dāng)網(wǎng)站開發(fā)、企業(yè)建站全套包干低至880元,成熟完善的模板庫,直接使用。一站式兩當(dāng)網(wǎng)站制作公司更省心,省錢,快速模板網(wǎng)站建設(shè)找我們，業(yè)務(wù)覆蓋兩當(dāng)?shù)貐^(qū)。費(fèi)用合理售后完善，10多年實(shí)體公司更值得信賴。

2、SPA作用

SQL 性能分析器可用于預(yù)測和防止會(huì)影響 SQL 執(zhí)行計(jì)劃結(jié)構(gòu)的任何數(shù)據(jù)庫環(huán)境更改所帶來的潛在性能問題。這些更改可以包括（但不限于）以下任何一種更改：

1）數(shù)據(jù)庫升級

2）實(shí)施優(yōu)化建議

3）更改方案

4）收集統(tǒng)計(jì)信息

5）更改數(shù)據(jù)庫參數(shù)

6）更改操作系統(tǒng)和硬件

3、SPA測試流程

為了盡可能的減小對正式生產(chǎn)庫的性能影響，SPA測試可以從AWR資料庫中的SQL數(shù)據(jù)轉(zhuǎn)化而來的SQL Tuning Set進(jìn)行整體的SQL性能測試。

本次測試主要分為以下幾個(gè)步驟：

在源端：

1.環(huán)境準(zhǔn)備：創(chuàng)建SPA測試專用用戶

2.采集數(shù)據(jù)：

a)在生產(chǎn)庫轉(zhuǎn)化AWR中SQL為SQL Tuning Set

b)在生產(chǎn)庫從現(xiàn)有SQL Tuning Set提取SQL

3.導(dǎo)出數(shù)據(jù)：打包(pack)轉(zhuǎn)化后的SQL Tuning Set，并導(dǎo)出傳輸?shù)綔y試服務(wù)器

在目標(biāo)庫端：

1.環(huán)境準(zhǔn)備：創(chuàng)建SPA測試專用用戶

2.測試準(zhǔn)備：導(dǎo)入SQL Tuning Set表，并解包(unpack)，創(chuàng)建SPA分析任務(wù)

3.前期性能：從SQL Tuning Set中轉(zhuǎn)化得出11g的性能Trail

4.后期性能：在19c測試數(shù)據(jù)庫中執(zhí)行SQL Tuning Set中SQL，生成19c性能Trail

5.對比分析：執(zhí)行對比分析任務(wù)，分別按執(zhí)行時(shí)間，CPU時(shí)間和邏輯讀三個(gè)維度進(jìn)行

6.匯總報(bào)告：取出對比報(bào)告，對每個(gè)維度分別取出All，Unsupport，Error 3類報(bào)告

總結(jié)報(bào)告：分析匯總報(bào)告，優(yōu)化其中的性能下降SQL，編寫SPA測試報(bào)告

4、SPA實(shí)操

4.1、初始化數(shù)據(jù)庫（源端和目標(biāo)端數(shù)據(jù)庫）

在進(jìn)行SPA操作前，需要為數(shù)據(jù)庫進(jìn)行檢測，目標(biāo)端的數(shù)據(jù)庫的表空間的大小和名字需要和源端的表空間的大小和名字一致（除去系統(tǒng)表空間）

a、檢測源端數(shù)據(jù)庫的表空間

SQL> select tablespace_name,bytes/1024/1024m from dba_data_files;
TABLESPACE_NAME                         M
------------------------------ ----------
SYSTEM                                700
SYSAUX                                600
UNDOTBS1                              200
USERS                                   5
TEST                                  100

b、查看目標(biāo)端表空間

SQL> select tablespace_name,bytes/1024/1024m from dba_data_files;
TABLESPACE_NAME                         M
------------------------------ ----------
SYSTEM                                900
SYSAUX                                600
USERS                                   5
UNDOTBS1                               55

通過對表空間的檢測可以看到，目標(biāo)端沒有test表空間，需要在目標(biāo)端創(chuàng)建一個(gè)名為TEST，大小為100 MB的表空間

c、目標(biāo)端進(jìn)行表空間創(chuàng)建

查看表空間的位置
SQL> col file_name for a80
SQL> select file_name,tablespace_name from dba_data_files;
FILE_NAME                                                                        TABLESPACE_NAME
-------------------------------------------------------------------------------- ------------------------------
C:\ORACLE\APP\LI\ORADATA\HAPPY\LUFFY\DATAFILE\O1_MF_SYSTEM_GJ3K66GF_.DBF         SYSTEM
C:\ORACLE\APP\LI\ORADATA\HAPPY\LUFFY\DATAFILE\O1_MF_SYSAUX_GJ3K79OK_.DBF         SYSAUX
C:\ORACLE\APP\LI\ORADATA\HAPPY\LUFFY\DATAFILE\O1_MF_USERS_GJ3K7T1V_.DBF          USERS
C:\ORACLE\APP\LI\ORADATA\HAPPY\LUFFY\DATAFILE\O1_MF_UNDOTBS1_GJ3K7RWQ_.DBF       UNDOTBS1
創(chuàng)建表空間
SQL> create tablespace test datafile 'C:\ORACLE\APP\LI\ORADATA\HAPPY\LUFFY\DATAFILE\TEST.DBF' size 100m;
表空間已創(chuàng)建。
SQL> select file_name,tablespace_name from dba_data_files;
FILE_NAME                                                                        TABLESPACE_NAME
-------------------------------------------------------------------------------- ------------------------------
C:\ORACLE\APP\LI\ORADATA\HAPPY\LUFFY\DATAFILE\O1_MF_SYSTEM_GJ3K66GF_.DBF         SYSTEM
C:\ORACLE\APP\LI\ORADATA\HAPPY\LUFFY\DATAFILE\O1_MF_SYSAUX_GJ3K79OK_.DBF         SYSAUX
C:\ORACLE\APP\LI\ORADATA\HAPPY\LUFFY\DATAFILE\TEST.DBF                           TEST
C:\ORACLE\APP\LI\ORADATA\HAPPY\LUFFY\DATAFILE\O1_MF_USERS_GJ3K7T1V_.DBF          USERS
C:\ORACLE\APP\LI\ORADATA\HAPPY\LUFFY\DATAFILE\O1_MF_UNDOTBS1_GJ3K7RWQ_.DBF       UNDOTBS1

4.2、導(dǎo)入導(dǎo)出數(shù)據(jù)

把源端的tns拷貝到目標(biāo)端（測試不需要，如果是生產(chǎn)庫則需要進(jìn)行tns的拷貝）

同時(shí)需要注意DB link

a、源端導(dǎo)出數(shù)據(jù)

查看directory
SQL> col DIRECTORY_PATH for a80
SQL> select * from dba_directories;
OWNER                          DIRECTORY_NAME                 DIRECTORY_PATH
------------------------------ ------------------------------ --------------------------------------------------------------------------------
SYS                            ORACLE_OCM_CONFIG_DIR          /oracle/app/oracle/product/11.2.0/dbhome_1/ccr/hosts/source/state
SYS                            DATA_PUMP_DIR                  /oracle/app/oracle/admin/source/dpdump/
SYS                            ORACLE_OCM_CONFIG_DIR2         /oracle/app/oracle/product/11.2.0/dbhome_1/ccr/state
創(chuàng)建directory
SQL> create directory dump_dir as '/oracle/app/dump';
Directory created.
SQL> select * from dba_directories;
OWNER                          DIRECTORY_NAME                 DIRECTORY_PATH
------------------------------ ------------------------------ --------------------------------------------------------------------------------
SYS                            DUMP_DIR                       /oracle/app/dump
SYS                            ORACLE_OCM_CONFIG_DIR          /oracle/app/oracle/product/11.2.0/dbhome_1/ccr/hosts/source/state
SYS                            DATA_PUMP_DIR                  /oracle/app/oracle/admin/source/dpdump/
SYS                            ORACLE_OCM_CONFIG_DIR2         /oracle/app/oracle/product/11.2.0/dbhome_1/ccr/state

源端導(dǎo)出數(shù)據(jù)

[oracle@source dump]$ cat /oracle/app/dump/full.sh 
PATH=$PATH:$HOME/bin
NLS_LANG=AMERICAN_AMERICA.ZHS16GBK; export NLS_LANG
export PATHORACLE_SID=source; export ORACLE_SID  
ORACLE_BASE=/oracle/app/oracle;     export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1;    export ORACLE_HOME
PATH=/usr/sbin:$PATH; export PATH
PATH=$ORACLE_HOME/bin:$PATH; export PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH
export LANG=C
export 022
/oracle/app/oracle/product/11.2.0/dbhome_1/bin/expdp system/oracle DIRECTORY=dump_dir parallel=1 dumpfile=source_full_` date +%y%m%d`_%U.dmp logfile=source_full_` date +%y%m%d`.log compression=all cluster=N full=y

目標(biāo)端導(dǎo)入數(shù)據(jù)

C:\Users\li>impdp ' / as sysdba' directory=dump parallel=1 dumpfile=source_full_190617_01.dmp logfile=impdp.source.full.log cluster=no full=y

Import: Release 19.0.0.0.0 - Production on 星期二 6月 18 14:40:49 2019

Version 19.3.0.0.0

口令:oracle

;;;

Import: Release 19.0.0.0.0 - Production on 星期二 6月 18 14:40:49 2019

Version 19.3.0.0.0

;;;

連接到: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

已成功加載/卸載了主表 "SYS"."SYS_IMPORT_FULL_01"

啟動(dòng) "SYS"."SYS_IMPORT_FULL_01": "/******** AS SYSDBA" directory=dump parallel=1 dumpfile=source_full_190617_01.dmp logfile=impdp.source.full.log cluster=no full=y

處理對象類型 DATABASE_EXPORT/TABLESPACE

導(dǎo)入報(bào)錯(cuò)內(nèi)容

（1）表空間、角色、用戶、序列等已存在，忽略

ORA-31684: 對象類型 TABLESPACE:"UNDOTBS1" 已存在

ORA-31684: 對象類型 TABLESPACE:"TEMP" 已存在

ORA-31684: 對象類型 TABLESPACE:"USERS" 已存在

ORA-31684: 對象類型 TABLESPACE:"TEST" 已存在

ORA-31685: 由于權(quán)限不足, 對象類型 USER:"SYS" 失敗。失敗的 sql 為:

ALTER USER "SYS" IDENTIFIED BY VALUES 'S:6BF11CCC7A4D3D308B5CF151AE6BE8E8981F1612723B5B95DDDD17182B38;8A8F025737A9097A' TEMPORARY TABLESPACE "TEMP"

ORA-31684: 對象類型 USER:"OUTLN" 已存在

ORA-31684: 對象類型 USER:"ORACLE" 已存在

ORA-31684: 對象類型 ROLE:"SELECT_CATALOG_ROLE" 已存在

ORA-31684: 對象類型 ROLE:"EXECUTE_CATALOG_ROLE" 已存在

ORA-31684: 對象類型 ROLE:"DBFS_ROLE" 已存在

ORA-31684: 對象類型 ROLE:"AQ_ADMINISTRATOR_ROLE" 已存在

ORA-31684: 對象類型 ROLE:"AQ_USER_ROLE" 已存在

ORA-31684: 對象類型 ROLE:"ADM_PARALLEL_EXECUTE_TASK" 已存在

ORA-31684: 對象類型 ROLE:"GATHER_SYSTEM_STATISTICS" 已存在

ORA-31684: 對象類型 ROLE:"RECOVERY_CATALOG_OWNER" 已存在

ORA-31684: 對象類型 ROLE:"SCHEDULER_ADMIN" 已存在

ORA-31684: 對象類型 ROLE:"HS_ADMIN_SELECT_ROLE" 已存在

ORA-31684: 對象類型 ROLE:"HS_ADMIN_EXECUTE_ROLE" 已存在

ORA-31684: 對象類型 ROLE:"HS_ADMIN_ROLE" 已存在

ORA-31684: 對象類型 ROLE:"GLOBAL_AQ_USER_ROLE" 已存在

ORA-31684: 對象類型 ROLE:"OEM_ADVISOR" 已存在

ORA-31684: 對象類型 ROLE:"OEM_MONITOR" 已存在

ORA-31684: 對象類型 ROLE:"WM_ADMIN_ROLE" 已存在

ORA-31684: 對象類型 DIRECTORY:"DATA_PUMP_DIR" 已存在

ORA-31684: 對象類型 CONTEXT:"GLOBAL_AQCLNTDB_CTX" 已存在

ORA-31684: 對象類型 CONTEXT:"DBFS_CONTEXT" 已存在

ORA-31684: 對象類型 CONTEXT:"REGISTRY$CTX" 已存在

ORA-31684: 對象類型 CONTEXT:"LT_CTX" 已存在

ORA-39083: 對象類型 PROCACT_SYSTEM 創(chuàng)建失敗, 出現(xiàn)錯(cuò)誤:

ORA-20000: Incompatible version of Workspace Manager Installed

失敗的 sql 為:

BEGIN

declare ver varchar2(100) ; cnt integer ; dummy integer; vdummy varchar2(30) ; compile_exception EXCEPTION; PRAGMA EXCEPTION_INIT(compile_exception, -06550); invalid_table EXCEPTION; PRAGMA EXCEPTION_INIT(invalid_table, -00942); procedure createErrorProc is begin execute immediate 'create or replace function system.wm$_check_install return boolean is begin return true ; end;' ; end ; begin select status into vdummy from dba_registry where comp_id = 'OWM' ; if (vdummy not in ('VALID', 'UPGRADED', 'LOADED')) then raise compile_exception ; end if ; select 1 into dummy from dual where exists (select 1 from all_users where username = 'WMSYS') ; execute immediate 'create or replace function wmsys.wm$_old_version return varchar2 is begin return ''11.2.0.4.0'' ; end;' ; select count(*) into cnt from dba_procedures where object_name='LT_EXPORT_PKG' and procedure_name='IMPORTEXPORTSUPPORT'; if (cnt=0) then raise_application_error(-20000, 'Incompatible version of Workspace Manager Installed'); end if ; execute immediate 'select value from wmsys.wm$env_vars where name=''OWM_VERSION''' into ver ; if (0>0 and ver != '11.2.0.4.0') then raise_application_error(-20000, 'Unable to import due to one or more versioned tables not having a ''VERSIONED'' status'); end if ; execute immediate 'declare cnt integer ; begin select count(*) into cnt from (select workspace from wmsys.wm$version_hierarchy_table where version!=0 union all select table_name from wmsys.wm$versioned_tables) ; if (cnt>0)

ORA-39083: 對象類型 PROCACT_SYSTEM 創(chuàng)建失敗, 出現(xiàn)錯(cuò)誤:

ORA-20000: Incompatible version of Workspace Manager Installed

失敗的 sql 為:

BEGIN

ORA-39126: 在 KUPW$WORKER.SEND_TRACE_MSG [KUPW: ORA-39083: 對象類型 PROCACT_SYSTEM 創(chuàng)建失敗, 出現(xiàn)錯(cuò)誤:

ORA-20000: Incompatible version of Workspace Manager Installed

失敗的 sql 為:

BEGIN

] 中 Worker 發(fā)生意外致命錯(cuò)誤

PROCACT_SYSTEM

ORA-06502: PL/SQL: 數(shù)字或值錯(cuò)誤 : 字符串緩沖區(qū)太小

ORA-06512: 在 "SYS.DBMS_SYS_ERROR", line 105

ORA-06512: 在 "SYS.KUPW$WORKER", line 12620

ORA-06512: 在 "SYS.DBMS_SYS_ERROR", line 105

ORA-06512: 在 "SYS.KUPW$WORKER", line 34278

----- PL/SQL Call Stack -----

object line object

handle number name

00007FF70BE8F840 33476 package body SYS.KUPW$WORKER.WRITE_ERROR_INFORMATION

00007FF70BE8F840 12641 package body SYS.KUPW$WORKER.DETERMINE_FATAL_ERROR

00007FF70BE8F840 34341 package body SYS.KUPW$WORKER.SEND_TRACE_MSG

00007FF70BE8F840 28767 package body SYS.KUPW$WORKER.SEND_MSG

00007FF70BE8F840 5418 package body SYS.KUPW$WORKER.LOAD_METADATA

00007FF70BE8F840 13781 package body SYS.KUPW$WORKER.DISPATCH_WORK_ITEMS

00007FF70BE8F840 2429 package body SYS.KUPW$WORKER.MAIN

00007FF70BD34800 2 anonymous block

DBMS_LOB.TRIM

DBMS_LOB.FREETEMPORARY

KUPW: In procedure UPDATE_TYPE_COMPLETION_ROW

KUPW: Old Seqno: 108 New Path: PO Num: -6 New Seqno: 0 error count: 1

KUPW: Primary row is: FALSE

KUPW: Working on old seqno with count of: 4

KUPW: In procedure SEND_MSG. Fatal=0

KUPW: Error count: 1

KUPW: In procedure DETERMINE_FATAL_ERROR with ORA-06502: PL/SQL: 數(shù)字或值錯(cuò)誤 : 字符串緩沖區(qū)太小

ORA-39083: 對象類型 PROCACT_SYSTEM 創(chuàng)建失敗, 出現(xiàn)錯(cuò)誤:

ORA-29371: 暫掛區(qū)未激活

失敗的 sql 為:

BEGIN

dbms_resource_manager.set_consumer_group_mapping_pri(1,7,6,9,8,10,5,4,3,2,11);

dbms_resource_manager.set_consumer_group_mapping('ORACLE_USER','"SYSTEM"','SYS_GROUP');

dbms_resource_manager.set_consumer_group_mapping('ORACLE_USER','"SYS"','SYS_GROUP');

dbms_resource_manager.set_consumer_group_mapping('ORACLE_FUNCTION','"BACKUP"','BATCH_GROUP');

dbms_resource_manager.set_consumer_group_mapping('ORACLE_FUNCTION','"COPY"','BATCH_GROUP');

dbms_resource_manager.set_consumer_group_mapping('ORACLE_FUNCTION','"DATALOAD"','ETL_GROUP');

dbms_resource_manager.submit_pending_area;COMMIT; END;

ORA-39083: 對象類型 PROCACT_SYSTEM 創(chuàng)建失敗, 出現(xiàn)錯(cuò)誤:

ORA-04042: 過程, 函數(shù), 程序包或程序包體不存在

失敗的 sql 為:

BEGIN

SYS.DBMS_UTILITY.EXEC_DDL_STATEMENT('GRANT EXECUTE ON DBMS_DEFER_SYS TO "DBA"');COMMIT; END;

4.3、源端與目標(biāo)端進(jìn)行SPA

4.3.1、源端操作

1、環(huán)境準(zhǔn)備

創(chuàng)建SPA專用用戶

create user spa identified by spa default tablespace users;

grant dba to spa;

grant advisor to spa;

grant select any dictionary to spa;

grant administer sql tuning set to spa;

2、采集數(shù)據(jù)

a)在生產(chǎn)庫轉(zhuǎn)化AWR中SQL為SQL Tuning Set

b)在生產(chǎn)庫從現(xiàn)有SQL Tuning Set提取SQL

在生產(chǎn)端，使用Oracle SQL Tuning工具包，從AWR資料庫數(shù)據(jù)中轉(zhuǎn)化得到SQL Tuning Set，用于整個(gè)SPA測試流程中的SQL來源。

為了確保對生產(chǎn)環(huán)境影響最小，我們只對生產(chǎn)端采集AWR的SQL，具體采集步驟如下：

a、獲取AWR快照的邊界ID

set lines 188 pages 1000

col snap_time for a22

col min_id new_value minid

col max_id new_value maxid

select min(snap_id) min_id, max(snap_id) max_id

from dba_hist_snapshot

where end_interval_time > trunc(sysdate)-30

order by 1;

MIN_ID MAX_ID

---------- ----------

20 20

b、創(chuàng)建SQL Set

連接用戶：

conn spa/spa

如果之前有這個(gè)SQLSET的名字，可以這樣刪除：

EXEC DBMS_SQLTUNE.DROP_SQLSET (SQLSET_NAME => 'SOL_SQLSET_201906', SQLSET_OWNER => 'SPA');

新建SQLSET：SOL_SQLSET_201906

EXEC DBMS_SQLTUNE.CREATE_SQLSET (-

SQLSET_NAME => 'SOL_SQLSET_201906',-

DESCRIPTION => 'SQL Set Create at : '||TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'),-

SQLSET_OWNER => 'SPA');

查詢sql set信息：

col DESCRIPTION for a50

select owner,name,STATEMENT_COUNT,DESCRIPTION,CREATED from dba_sqlset;

OWNER NAME STATEMENT_COUNT DESCRIPTION CREATED

------------------------------ ------------------------------ --------------- -------------------------------------------------- ---------

SPA SOL_SQLSET_201906 0 SQL Set Create at : 2019-06-17 23:57:05 17-JUN-19

c、轉(zhuǎn)化AWR數(shù)據(jù)中的SQL數(shù)據(jù)，將其中的SQL載入到SQL Set中

注意：過濾太多的賬戶會(huì)報(bào)錯(cuò)

從AWR中提?。?/div>

DECLARE

SQLSET_CUR DBMS_SQLTUNE.SQLSET_CURSOR;

BEGIN

OPEN SQLSET_CUR FOR

SELECT VALUE(P) FROM TABLE(

DBMS_SQLTUNE.SELECT_WORKLOAD_REPOSITORY( 20, 21,

'PARSING_SCHEMA_NAME NOT IN (''SYS'', ''SYSTEM'')',

NULL, NULL, NULL, NULL, 1, NULL, 'ALL')) P;

DBMS_SQLTUNE.LOAD_SQLSET(

SQLSET_NAME => 'SOL_SQLSET_201906',

SQLSET_OWNER => 'SPA',

POPULATE_CURSOR => SQLSET_CUR,

LOAD_OPTION => 'MERGE',

UPDATE_OPTION => 'ACCUMULATE');

CLOSE SQLSET_CUR;

END;

查詢sql set信息：

col DESCRIPTION for a50

select owner,name,STATEMENT_COUNT,DESCRIPTION,CREATED from dba_sqlset;

OWNER NAME STATEMENT_COUNT DESCRIPTION CREATED

------------------------------ ------------------------------ --------------- -------------------------------------------------- ---------

SPA SOL_SQLSET_201906 5 SQL Set Create at : 2019-06-17 23:57:05 17-JUN-19

d、轉(zhuǎn)化當(dāng)前cursor cache中的SQL數(shù)據(jù)，將其中的SQL載入到SQL Set中

從當(dāng)前cursor cache中提取：排除sys、system用戶執(zhí)行的語句

DECLARE

SQLSET_CUR DBMS_SQLTUNE.SQLSET_CURSOR;

BEGIN

OPEN SQLSET_CUR FOR

SELECT VALUE(P) FROM TABLE(

DBMS_SQLTUNE.SELECT_CURSOR_CACHE(

'PARSING_SCHEMA_NAME NOT IN (''SYS'', ''SYSTEM'')',

NULL, NULL, NULL, NULL, 1, NULL,'ALL')) P;

DBMS_SQLTUNE.LOAD_SQLSET(

SQLSET_NAME => 'SOL_SQLSET_201906',

SQLSET_OWNER => 'SPA',

POPULATE_CURSOR => SQLSET_CUR,

LOAD_OPTION => 'MERGE',

UPDATE_OPTION => 'ACCUMULATE');

CLOSE SQLSET_CUR;

END;

查詢sql set信息：

col DESCRIPTION for a50

select owner,name,STATEMENT_COUNT,DESCRIPTION,CREATED from dba_sqlset;

OWNER NAME STATEMENT_COUNT DESCRIPTION CREATED

------------------------------ ------------------------------ --------------- -------------------------------------------------- ---------

SPA SOL_SQLSET_201906 36 SQL Set Create at : 2019-06-17 23:57:05 17-JUN-19

e、打包SQL Set

DROP TABLE SPA.SOL_STSTAB_201906;

EXEC DBMS_SQLTUNE.CREATE_STGTAB_SQLSET ('SOL_STSTAB_201906', 'SPA', 'USERS');

EXEC DBMS_SQLTUNE.PACK_STGTAB_SQLSET ( -

SQLSET_NAME => 'SOL_SQLSET_201906', -

SQLSET_OWNER => 'SPA', -

STAGING_TABLE_NAME => 'SOL_STSTAB_201906', -

STAGING_SCHEMA_OWNER => 'SPA');

查看spa下用戶下的表對象：

SQL> select * from tab;

TNAME TABTYPE CLUSTERID

------------------------------ ------- ----------

SOL_STSTAB_201906 TABLE

4.3.3、源端操作（導(dǎo)出SPA的數(shù)據(jù)）

打包(pack)轉(zhuǎn)化后的SQL Tuning Set，并導(dǎo)出傳輸?shù)綔y試服務(wù)器

將采集到的數(shù)據(jù)打包后，需要將其中生產(chǎn)庫導(dǎo)出，并傳輸?shù)綔y試服務(wù)器中，用于在測試數(shù)據(jù)庫中進(jìn)行SPA測試工作。

1）在操作系統(tǒng)中，導(dǎo)出打包后的SQL Set數(shù)據(jù)

[oracle@source ~]$ cat /home/oracle/export_sqlset_201903.par
USERID=spa/spa
FILE=SOL_STSTAB_201906.dmp
LOG=exp_spa_sqlset_201906.log
TABLES=SOL_STSTAB_201906
DIRECT=Y
BUFFER=10240000
STATISTICS=NONE

導(dǎo)出數(shù)據(jù)

[oracle@source ~]$   export NLS_LANG=AMERICAN_AMERICA.ZHS16GBK
[oracle@source ~]$   exp PARFILE=export_sqlset_201906.par
Export: Release 11.2.0.4.0 - Production on Tue Jun 18 00:17:57 2019
Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in ZHS16GBK character set and AL16UTF16 NCHAR character set
About to export specified tables via Direct Path ...
Table SOL_STSTAB_201906 will be exported in conventional path.
. . exporting table              SOL_STSTAB_201906        183 rows exported
Export terminated successfully without warnings.

2）將導(dǎo)出后的Dump文件傳輸?shù)綔y試服務(wù)器

將SOL_STSTAB_201906.dmp 傳輸?shù)?目標(biāo)服務(wù)器 [C:\Users\li] 下：

4.3.4、目標(biāo)端操作

1、環(huán)境準(zhǔn)備

創(chuàng)建SPA專用用戶

為了進(jìn)行SPA測試，在測試數(shù)據(jù)庫中創(chuàng)建SPA測試專用用戶，避免與其他用戶相互混淆與可能產(chǎn)生的誤操作。

create user spa identified by spa default tablespace users;

grant dba to spa;

grant advisor to spa;

grant select any dictionary to spa;

grant administer sql tuning set to spa;

2、測試準(zhǔn)備

導(dǎo)入SQL Tuning Set表，并解包(unpack)，創(chuàng)建SPA分析任務(wù)

在進(jìn)行SPA測試前需要準(zhǔn)備測試環(huán)境，包括導(dǎo)入生產(chǎn)庫中的SQL Set，對其進(jìn)行解包(unpack)操作，并創(chuàng)建SPA分析任務(wù)。

1）在操作系統(tǒng)中，執(zhí)行導(dǎo)入命令，導(dǎo)入SQL Set表

###win使用imp，進(jìn)入到dmp的文件位置

C:\Users\li>imp USERID=spa/spa FILE=SOL_STSTAB_201906.dmp LOG=imp_spa_sqlset_201906.log FULL=Y

Import: Release 19.0.0.0.0 - Production on 星期二 6月 18 15:33:34 2019

Version 19.3.0.0.0

連接到: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

Version 19.3.0.0.0

經(jīng)由直接路徑由 EXPORT:V11.02.00 創(chuàng)建的導(dǎo)出文件

已經(jīng)完成 ZHS16GBK 字符集和 AL16UTF16 NCHAR 字符集中的導(dǎo)入

IMP-00403:

警告: 此導(dǎo)入生成了單獨(dú)的 SQL 文件 "imp_spa_sqlset_201906_sys.sql", 其中包含了由于權(quán)限問題而失敗的 DDL。

. 正在將 SPA 的對象導(dǎo)入到 SPA

IMP-00015: 由于對象已存在, 下列語句失敗:

"CREATE PUBLIC SYNONYM "ANYDATA" FOR "SYS"."ANYDATA""

. . 正在導(dǎo)入表 "SOL_STSTAB_201906"導(dǎo)入了 183 行

成功終止導(dǎo)入, 但出現(xiàn)警告。

2）連接到spa

C:\Users\li>sqlplus spa/spa

3）解包(unpack)SQL Set

EXEC DBMS_SQLTUNE.UNPACK_STGTAB_SQLSET (-

SQLSET_NAME => 'SOL_SQLSET_201906', -

SQLSET_OWNER => 'SPA', -

REPLACE => TRUE, -

STAGING_TABLE_NAME => 'SOL_STSTAB_201906', -

STAGING_SCHEMA_OWNER => 'SPA');

4）創(chuàng)建SPA分析任務(wù)

VARIABLE SPA_TASK VARCHAR2(64);

EXEC :SPA_TASK := DBMS_SQLPA.CREATE_ANALYSIS_TASK( -

TASK_NAME => 'SPA_TASK_201906', -

DESCRIPTION => 'SPA Analysis task at : '||TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'), -

SQLSET_NAME => 'SOL_SQLSET_201906', -

SQLSET_OWNER => 'SPA');

建議設(shè)置設(shè)置超過時(shí)間，超過1800秒還未執(zhí)行完成就跳過處理：

exec dbms_sqlpa.set_analysis_default_parameter('LOCAL_TIME_LIMIT',1800);

select parameter_value from dba_advisor_def_parameters where advisor_name='SQL Performance Analyzer' and parameter_name='LOCAL_TIME_LIMIT';

PARAMETER_VALUE

--------------------------------------------------------------------------------

1800

exec dbms_sqlpa.set_analysis_default_parameter('BASIC_FILTER','1akvyr72fsyyj');

有些sql可能存在問題，可以把這些條sql從基表WRI$_SQLSET_STATEMENTS中刪除或者在創(chuàng)建分析任務(wù)時(shí)加上過濾：

VARIABLE SPA_TASK VARCHAR2(64);

EXEC :SPA_TASK := DBMS_SQLPA.CREATE_ANALYSIS_TASK( -

TASK_NAME => 'SPA_TASK_201903', -

BASIC_FILTER=>'sql_id not in(''1akvyr72fsyyj'',''cjjb62udz141p'')',-

DESCRIPTION => 'SPA Analysis task at : '||TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'), -

SQLSET_NAME => 'SOL_SQLSET_201903', -

SQLSET_OWNER => 'SPA');

為了刪除掉有問題的SQL

查看分析任務(wù)信息：

set linesize 400 pagesize 9999

col owner for a20

col task_name for a20

alter session set nls_date_format='yyyy-mm-dd hh34:mi:ss';

select owner,task_id,task_name,created,last_modified,status from dba_advisor_tasks where task_name='SPA_TASK_201906' order by 2;

OWNER TASK_ID TASK_NAME CREATED LAST_MODIFIED STATUS

-------------------- ---------- -------------------- ------------------- ------------------- -----------

SPA 62 SPA_TASK_201906 2019-06-18 15:38:41 2019-06-18 15:38:42 INITIAL

3、前期性能

從SQL Tuning Set中轉(zhuǎn)化得出11g的性能Trail

EXECUTION_TYPE參數(shù)介紹：

Type of the action to perform by the function. If NULL it will default to the value of the DEFAULT_EXECUTION_TYPE parameter. Possible values are:

1）[TEST] EXECUTE – test-execute every SQL statement and collect its execution plans and execution statistics. The resulting plans and statistics will be stored in the advisor framework. This is default.

2）EXPLAIN PLAN – generate explain plan for every statement in the SQL workload. This is similar to the EXPLAIN PLAN command. The resulting plans will be stored in the advisor framework in association with the task.

3）COMPARE [PERFORMANCE] – analyze and compare two versions of SQL performance data. The performance data is generated by test-executing or generating explain plan of the SQL statements. Use this option when two executions of type EXPLAIN_PLAN or TEST_EXECUTE already exist in the task

4）CONVERT SQLSET – used to read the statistics captured in a SQL Tuning Set and model them as a task execution. This can be used when you wish to avoid executing the SQL statements because valid data for the experiment already exists in the SQL Tuning Set.

在測試服務(wù)器中，可以直接從SQL Tuning Set中轉(zhuǎn)化得到所有SQL在11g數(shù)據(jù)庫中的執(zhí)行效率，得到11g中的SQL Trail。

EXEC DBMS_SQLPA.EXECUTE_ANALYSIS_TASK( -

TASK_NAME => 'SPA_TASK_201906', -

EXECUTION_NAME => 'EXEC_11G_201906', -

EXECUTION_TYPE => 'CONVERT SQLSET', -

EXECUTION_DESC => 'Convert 11g SQLSET for SPA Task at : '||TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'));

4、后期性能

在19c測試數(shù)據(jù)庫中執(zhí)行SQL Tuning Set中SQL，生成19c性能Trail

在測試服務(wù)器（運(yùn)行19據(jù)庫）中，需要在本地?cái)?shù)據(jù)庫（19c）測試運(yùn)行SQL Tuning Set中的SQL語句，分析所有語句在19c環(huán)境中的執(zhí)行效率，得到19c中的SQL Trail。

腳本內(nèi)容如下：

vi /home/oracle/spa2.sh

echo "WARNING: SPA2 Start @`date`"

sqlplus spa/spa << EOF!

EXEC DBMS_SQLPA.EXECUTE_ANALYSIS_TASK( -

TASK_NAME => 'SPA_TASK_201906', -

EXECUTION_NAME => 'EXEC_19C_201906', -

EXECUTION_TYPE => 'TEST EXECUTE', -

EXECUTION_DESC => 'Execute SQL in 19c for SPA Task at : '||TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'));

exit

EOF!

echo "WARNING:SPA2 OK @`date`"

腳本賦予執(zhí)行權(quán)限：

chmod +x spa2.sh

后臺(tái)執(zhí)行腳本：

nohup sh spa2.sh &

腳本執(zhí)行日志如下：

cat nohup.out

可以通過如下方式暫停、恢復(fù)、刪除分析任務(wù)，過濾執(zhí)行sql：

conn spa/spa

exec dbms_sqlpa.interrupt_analysis_task('SPA_TASK_201906');

中斷的任務(wù)可以恢復(fù)：

exec dbms_sqlpa.resume_analysis_task('SPA_TASK_201906');

刪除分析任務(wù)：

exec dbms_sqlpa.drop_analysis_task('SPA_TASK_201906');

此次win直接使用命令

EXEC DBMS_SQLPA.EXECUTE_ANALYSIS_TASK( -

TASK_NAME => 'SPA_TASK_201906', -

EXECUTION_NAME => 'EXEC_19C_201906', -

EXECUTION_TYPE => 'TEST EXECUTE', -

EXECUTION_DESC => 'Execute SQL in 19c for SPA Task at : '||TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'));

5、對比報(bào)告

執(zhí)行對比分析任務(wù)，分別按執(zhí)行時(shí)間，CPU時(shí)間和邏輯讀三個(gè)維度進(jìn)行

得到兩次SQL Trail之后，可以對比兩次Trial之間的SQL執(zhí)行性能，可以從不同的維度對兩次Trail中的所有SQL進(jìn)行對比分析，主要關(guān)注的維度有：SQL執(zhí)行時(shí)間，SQL執(zhí)行的CPU時(shí)間，SQL執(zhí)行的邏輯讀。

注意：在spa用戶下執(zhí)行

1）對比兩次Trail中的SQL執(zhí)行時(shí)間

EXEC DBMS_SQLPA.EXECUTE_ANALYSIS_TASK( -

TASK_NAME => 'SPA_TASK_201906', -

EXECUTION_NAME => 'COMPARE_ET_201906', -

EXECUTION_TYPE => 'COMPARE PERFORMANCE', -

EXECUTION_PARAMS => DBMS_ADVISOR.ARGLIST( -

'COMPARISON_METRIC', 'ELAPSED_TIME', -

'EXECUTE_FULLDML', 'TRUE', -

'EXECUTION_NAME1','EXEC_11G_201906', -

'EXECUTION_NAME2','EXEC_19C_201906'), -

EXECUTION_DESC => 'Compare SQLs between 11g and 19c at :'||TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'));

說明：默認(rèn)情況下SPA若涉及到DML語句則只有查詢部分Query會(huì)被執(zhí)行，但是從11.2開始可以執(zhí)行完全的DML了，需要加入?yún)?shù)EXECUTE_FULLDML，但是該參數(shù)目前有一些BUG:

Bug 10428438 : WITH EXECUTE_FULLDML ROWS IS ALWAYS SET TO 0 11.2.0.1

Bug 14635522 : SPA SHOULD CAPTURE AND REPLAY TRANSACTIONS 11.2.0.3

By default, only the query portion of DMLs is executed. Using APIs, you can execute the full DML by using the EXECUTE_FULLDML task parameter.EXECUTE_FULLDML when set to TRUE executes DML statement fully, including acquiring row locks and modifying rows; When EXECUTE_FULLDML is set to FALSE (the default value is false) to execute only the query part of the DML without modifying data. When TRUE, SQL Performance Analyzer will issue a rollback following DML execution to prevent persistent changes from being made by the DML. So SPA does not make make any change to the data in the tables.

2）對比兩次Trail中的SQL執(zhí)行的CPU時(shí)間

EXEC DBMS_SQLPA.EXECUTE_ANALYSIS_TASK( -

TASK_NAME => 'SPA_TASK_201906', -

EXECUTION_NAME => 'COMPARE_CT_201906', -

EXECUTION_TYPE => 'COMPARE PERFORMANCE', -

EXECUTION_PARAMS => DBMS_ADVISOR.ARGLIST( -

'COMPARISON_METRIC', 'CPU_TIME', -

'EXECUTION_NAME1','EXEC_11G_201906', -

'EXECUTION_NAME2','EXEC_19C_201906'), -

EXECUTION_DESC => 'Compare SQLs between 11g and 19c at :'||TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'));

3）對比兩次Trail中的SQL執(zhí)行的邏輯讀

EXEC DBMS_SQLPA.EXECUTE_ANALYSIS_TASK( -

TASK_NAME => 'SPA_TASK_201906', -

EXECUTION_NAME => 'COMPARE_BG_201906', -

EXECUTION_TYPE => 'COMPARE PERFORMANCE', -

EXECUTION_PARAMS => DBMS_ADVISOR.ARGLIST( -

'COMPARISON_METRIC', 'BUFFER_GETS', -

'EXECUTION_NAME1','EXEC_11G_201906', -

'EXECUTION_NAME2','EXEC_19C_201906'), -

EXECUTION_DESC => 'Compare SQLs between 11g and 19c at :'||TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'));

6、匯總報(bào)告

取出對比報(bào)告，對每個(gè)維度分別取出All，Unsupport，Error 3類報(bào)告

執(zhí)行對比分析任務(wù)之后，就可以取出對應(yīng)的對比分析任務(wù)的結(jié)果報(bào)告，主要關(guān)注的報(bào)告類型有：匯總SQL報(bào)告，錯(cuò)誤SQL報(bào)告以及不支持SQL報(bào)告。

1）獲取執(zhí)行時(shí)間全部報(bào)告（已完成，耗時(shí)11小時(shí)）