Des fois on galère :    jjoly@rutamerestion001:~$ ssh -X rutorac001 [jjoly@rutorac001 ~]$ xauth listrutorac001/unix:10 MIT-MAGIC-COOKIE-1 76dfdf9d53979sdfdsfsf10467a7a3020649df [jjoly@rutoracrm001 ~]$ sudo -iEu oracle [oracle@rutorac001:CRM] $ xauth add rutorac001/unix:10 MIT-MAGIC-COOKIE-1 76dfdf9d53979sdfdsfsf10467a7a3020649df [oracle@rutorac001:CRM] $. read more…

https://access.redhat.com/solutions/305663

Trouver le SQL avec sa hash value… col sql_text for a60 wrapset verify offset pagesize 999set lines 155col username format a13col prog format a22col sid format 999col child_number format 99999. read more…

Savoir si la pga est assez grande? sinon exécution dans TBS temp pas bon. col PGA_SIZE for a45 SELECT CASE WHEN low_optimal_size < 1024*1024THEN to_char(low_optimal_size/1024,’999999′) ||‘kb <= PGA < ‘. read more…

http://www.br8dba.com/how-to-install-sqlt/     All About the SQLT Diagnostic Tool (Doc ID 215187.1)

Scripts to deal with SQL Plan Baselines, SQL Profiles and SQL Patches script à lancer sous SQLT :  coe_xfr_sql_profile.sql http://kerryosborne.oracle-guy.com/2010/07/24/sqlt-coe_xfr_sql_profilesql/ https://carlos-sierra.net/2018/12/15/scripts-to-deal-with-sql-plan-baselines-sql-profiles-and-sql-patches/ https://www.bobbydurrettdba.com/2013/07/10/using-coe_xfr_sql_profile-sql-to-force-a-good-plan/

Méthode classique :  select * from table(dbms_xplan.display_awr(sql_id => ‘drur701xgm5nd’, format => ‘ALL’));

spool hist_sess.htmlset markup html onalter session set nls_timestamp_format=’YYYY-MM-DD HH24:MI’;select * from DBA_HIST_ACTIVE_SESS_HISTORY where sample_time between ‘2020-03-09 18:00’ and ‘2020-03-12 17:01’; set markup html offspool off

set serveroutput on size unlimited spool awr_8408_8478.txt declare   dbid number := 644588240; — a remplacer par ton dbid   instance_id number := 1;   l_premier number := 8408;  . read more…

tracer un sql id : exec dbms_sqldiag.dump_trace(p_sql_id=>’tamere’,p_child_number=>0,p_component=>’Compiler’,p_file_id=> »);