标签：Set staging Tuning sqlset STS test table 错误处理 name

STS导入或导出错误处理

环境模拟：

create directory d1 as '/home/oracle/scripts';

grant read,write on  directory d1 to public;

create user apps identified by Apps1234;

grant dba ,ADMINISTER ANY SQL TUNING SET to apps;

conn apps/Apps1234

create table apps.ta_lhr as select * from dba_objects;

create table apps.tb_lhr as select * from dba_objects;

select * from apps.ta_lhr where object_id=100;

select * from apps.tb_lhr where object_name='TA_LHR';

使用EM创建system用户的PS_STS的调优集，然后导出使用system进行导出，否则报错：

Tue Nov 28 09:43:53 2017

Errors in file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_j001_10289.trc:

ORA-12012: error on auto execute of job 78165

ORA-19381: cannot create staging table in SYS schema

ORA-06512: at "SYS.DBMS_SQLTUNE", line 3170

ORA-06512: at "SYS.DBMS_SQLTUNE", line 6397

ORA-06512: at line 1

MOS解释：

Error ORA-19381 When DBMS_SQLTUNE.UNPACK_STGTAB_SQLPROF IS EXECUTED as SYS (文档 ID 2131916.1)

This is expected behavior.  STS staging tables cannot be created in SYS schema by design.

Any other user (with the right privileges) should be able to create the staging table and pack STS in it.

导入如果报错：

Errors in file

/u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_j000_20653.trc:

ORA-12012: error on auto execute of job 78166

ORA-19377: no "SQL Tuning Set" with name like "%" exists for owner like "SYS"

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95

ORA-06512: at "SYS.DBMS_SQLTUNE", line 6868

ORA-06512: at line 1

Errors in file /u01/app/oracle/diag/rdbms/prod1/PROD1/trace/PROD1_j000_9955.trc:

ORA-12012: error on auto execute of job 78689

ORA-00942: table or view does not exist

ORA-06512: at line 1

解决： 使用SYSTEM进行导入，或执行以下SQL后再导入：

impdp system/oracle directory=d1 dumpfile=appsstg.dmp

exec dbms_sqltune.remap_stgtab_sqlset(old_sqlset_name =>'STS_PS',old_sqlset_owner => 'SYSTEM', new_sqlset_name => 'STS_PS',new_sqlset_owner => 'SYS', staging_table_name => 'STS_PS_STGTAB',staging_schema_owner => 'SYSTEM');

----删除STS,staging table为STS_PS_STGTAB

SELECT * FROM Dba_Objects d WHERE d.object_name='STS_PS_STGTAB';

SELECT * FROM Dba_Sqlset;

SELECT *

FROM dba_sqlset_statements  

WHERE sqlset_name = 'STS_PS';

DELETE FROM WRI$_SQLSET_DEFINITIONS;

DELETE FROM WRI$_SQLSET_STATEMENTS;

DELETE FROM WRI$_SQLSET_MASK;

DELETE FROM WRI$_SQLSET_STATISTICS;

COMMIT;

 SELECT * FROM WRI$_SQLSET_STATEMENTS;

 SELECT * FROM WRI$_SQLSET_MASK;

 SELECT * FROM WRI$_SQLSET_STATISTICS;

 SELECT * FROM WRI$_SQLSET_STATEMENTS;

How to Move a SQL Tuning Set from One Database to Another (文档 ID 751068.1)  

In this Document

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later  
Information in this document applies to any platform.  
***Checked for relevance on 26-MAR-2013***   

GOAL

This document explains how to transfer the SQL Tuning Set (STS) from one database to another and demonstrates some issues regarding the transfer of STS and their resolution.

SOLUTION

Actions to Perform the Transfer:

1. Create/load STS test_set owned by SYS
2. Create stgtab SQLSET_TAB
3. Pack test_set into the stgtab
4. Export/import into test system, conn as scott
5. Attempt to unpack an STS named 'testtarget_test_set'

Preliminary Setup:

• Create User,  Create and Populate the table and collect statistics
  
  

  SQL> connect test/test 
  
  create table hold (id number, col_val varchar2(10)); 
  insert into hold values ('1', 'more'); 
  
  declare v_id number := 1; 
  v_col_val varchar2(10); 
  begin 
  while v_id < 100 loop 
  v_id:=v_id + 1; 
  v_col_val:=v_id||'_more'; 
  insert into hold values(v_id, v_col_val); 
  end loop; 
  end; 
  /
  
  commit; 
  
  exec dbms_stats.gather_table_stats(user, 'hold', cascade => true);

• Check the data

  SQL> select count(*) from hold where id <=100; 
  
  COUNT(*) 
  ---------- 
  100 
  
  SQL> select col_val from hold where id = 100; 
  
  COL_VAL 
  ---------- 
  100_more 
  
  SQL> select max(id) from hold; 
  
  MAX(ID) 
  ---------- 
  200

Actions to Perform the Transfer: Detail

1. Create/load STS test_set owned by SYS

   sqlplus / as sysdba 
   
   exec dbms_sqltune.create_sqlset(sqlset_name => 'test_set', description =>'11g workload'); 
   
   declare 
   mycur dbms_sqltune.sqlset_cursor; 
   begin 
   open mycur for 
   select value (P) 
   from table(dbms_sqltune.select_cursor_cache('parsing_schema_name <> ''SYS'' and elapsed_time > 250', null, null, null, null,1, null, 'ALL')
              ) P;
   
   dbms_sqltune.load_sqlset(sqlset_name => 'test_set', populate_cursor => mycur); 
   end; 
   /

   
   Display the SQL Stored in the STS:
   
   

   select sql_text from dba_sqlset_statements where sqlset_name='test_set';

2. Create stgtab sqlset_tab table in TEST schema:

   BEGIN 
   DBMS_SQLTUNE.create_stgtab_sqlset(table_name => 'SQLSET_TAB', 
   schema_name => 'TEST', 
   tablespace_name => 'USERS'); 
   END; 
   /

3. Pack test_set into the stgtab

   From SYS
   

   BEGIN 
   DBMS_SQLTUNE.pack_stgtab_sqlset(sqlset_name => 'test_set', 
   sqlset_owner => 'SYS', 
   staging_table_name => 'SQLSET_TAB', 
   staging_schema_owner => 'TEST'); 
   END; 
   /

4. Transfer the table containing the SQL SET (SQLSET_TAB) table to the TEST system

   The staging table SQLSET_TAB cand be exported and imported to the TEST schema of the test system using datapump. See information on export datapump for details of how to do this : 
   
   

   Document 556636.1  Oracle Server - Export Data Pump and Import DataPump FAQ

5. Export/import into test system, connect as scott

   conn scott/tiger EXEC DBMS_SQLTUNE.create_sqlset(sqlset_name => 'testtarget_test_set');

   
   

   NOTE: Scott should have DBA privilege because unpacking is done under SCOTT where as the staging table is imported to TEST schema. Without the DBA privilege scott will not be able to access the test schema.

6. Attempt to unpack an STS named 'testtarget_test_set'

   
   

   BEGIN 
   DBMS_SQLTUNE.unpack_stgtab_sqlset(sqlset_name => 'testtarget_test_set', 
   sqlset_owner => 'SCOTT', 
   replace => TRUE, 
   staging_table_name => 'SQLSET_TAB', 
   staging_schema_owner => 'TEST'); 
   END; 
   /

   
   This will end up with the following error:- 
   
   

   BEGIN 
   * 
   ERROR at line 1: 
   ORA-19377: no "SQL Tuning Set" with name like "testtarget_test_set" exists for 
   owner like "TESTTARGET" 
   ORA-06512: at "SYS.DBMS_SQLTUNE", line 5422 
   ORA-06512: at line 2

   The above unpack procedure fails because there is no STS in the staging table named 'testtarget_test_set', owned by SCOTT (or by any other user). Unpack expects you to pass it the name of an STS as it is in the staging table. 
   
   

7. MAPPING

   If you are trying to rename the STS and change its owner before it is unpacked (reconstituted on the test system), use the remap_stgtab_sqlset API as follows, for example:

   exec dbms_sqltune.remap_stgtab_sqlset(old_sqlset_name => 'test_set', 
   old_sqlset_owner => 'SYS', new_sqlset_name => 'testtarget_test_set', 
   new_sqlset_owner => 'SCOTT', staging_table_name => 'SQLSET_TAB', 
   staging_schema_owner => ' ');

   Here the staging table is imported to TEST schema of TEST system:

   exec dbms_sqltune.remap_stgtab_sqlset(old_sqlset_name =>'test_set',old_sqlset_owner => 'SYS', new_sqlset_name => 'testtarget_test_set',new_sqlset_owner => 'SCOTT', staging_table_name => 'SQLSET_TAB',staging_schema_owner => 'TEST');

8. UNPACK THE SQLSET_TAB TABLE IN THE TEST SYSTEM

   BEGIN 
   DBMS_SQLTUNE.unpack_stgtab_sqlset(sqlset_name => 'testtarget_test_set', 
   sqlset_owner => 'SCOTT', 
   replace => TRUE, 
   staging_table_name => 'SQLSET_TAB', 
   staging_schema_owner => 'TEST'); 
   END; 
   /

   Now the SQL Tuning Set is transferred successfully to another database without any issues.

9. Then load the plans:
   

   set serveroutput on
   declare
   my_int pls_integer;
   begin
   my_int := dbms_spm.load_plans_from_sqlset (sqlset_name => 'testtarget_test_set',
   sqlset_owner => 'SCOTT',
   fixed => 'YES',
   enabled => 'YES');
   DBMS_OUTPUT.PUT_line(my_int);
   end;
   /

    

Error ORA-19381 When DBMS_SQLTUNE.UNPACK_STGTAB_SQLPROF IS EXECUTED as SYS (文档 ID 2131916.1)  

In this Document

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later  
Information in this document applies to any platform.  

SYMPTOMS

• When unpacking the sqlprofiles using DBMS_SQLTUNE.UNPACK_STGTAB_SQLPROF, following error is seen:
  

  BEGIN DBMS_SQLTUNE.UNPACK_STGTAB_SQLPROF(replace => TRUE,staging_table_name => 'TEST'); END;
  Error at line 1
  ORA-19381: cannot create staging table in SYS schema
  ORA-06512: at "SYS.DBMS_SMB", line 1051
  ORA-06512: at "SYS.DBMS_SQLTUNE", line 6357
  ORA-06512: at line 1

CAUSE

 This is expected behavior.  STS staging tables cannot be created in SYS schema by design.

SOLUTION

Any other user (with the right privileges) should be able to create the staging table and pack STS in it.

标签：Set,staging,Tuning,sqlset,STS,test,table,错误处理,name
来源： https://blog.51cto.com/lhrbest/2702364

本站声明： 1. iCode9 技术分享网（下文简称本站）提供的所有内容，仅供技术学习、探讨和分享；
2. 关于本站的所有留言、评论、转载及引用，纯属内容发起人的个人观点，与本站观点和立场无关；
3. 关于本站的所有言论和文字，纯属内容发起人的个人观点，与本站观点和立场无关；
4. 本站文章均是网友提供，不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属；如您发现该文章侵犯了您的权益，可联系我们第一时间进行删除；
5. 本站为非盈利性的个人网站，所有内容不会用来进行牟利，也不会利用任何形式的广告来间接获益，纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。