SRDC - ORA-1552: Checklist of Evidence to Supply (Doc ID 1681333.1)

SRDC - ORA-1552: Checklist of Evidence to Supply (Doc ID 1681333.1)

Action Plan

1. Execute srdc_db_undo_config.sql  as sysdba and provide the spool output  以sysdba身份执行脚本

--srdc_db_undo_config.sql
REM srdc_db_undo_config.sql REM collect Undo parameters,segment and transaction details for troubleshooting high Undo space usage issues define SRDCNAME='DB_Undo_Space' set pagesize 200 verify off sqlprompt "" term off entmap off echo off set markup html on spool on COLUMN SRDCSPOOLNAME NOPRINT NEW_VALUE SRDCSPOOLNAME select 'SRDC_'||upper('&&SRDCNAME')||'_'||upper(instance_name)||'_'|| to_char(sysdate,'YYYYMMDD_HH24MISS') SRDCSPOOLNAME from v$instance; spool &&SRDCSPOOLNAME..htm select 'Diagnostic-Name : ' "Diagnostic-Name ", '&&SRDCNAME' "Report Info" from dual union all select 'Time : ' , to_char(systimestamp, 'YYYY-MM-DD HH24MISS TZHTZM' ) from dual union all select 'Machine : ' , host_name from v$instance union all select 'Version : ',version from v$instance union all select 'DBName : ',name from v$database union all select 'Instance : ',instance_name from v$instance / set echo on --***********************Run Time********************** select sysdate from dual; -- ********************** Parameters ********************** select a.inst_id, a.ksppinm "Parameter", b.ksppstvl "Session Value", c.ksppstvl "Instance Value" from x$ksppi a, x$ksppcv b, x$ksppsv c where a.indx = b.indx and a.indx = c.indx and a.inst_id=b.inst_id and b.inst_id=c.inst_id and a.ksppinm in ('_undo_autotune', '_smu_debug_mode', '_highthreshold_undoretention', 'undo_tablespace','undo_retention','undo_management') order by 2 / -- ********************** Undo Segments ********************** select count(*),status,tablespace_name from dba_rollback_segs group by status,tablespace_name / set echo off set sqlprompt "SQL> " term on set verify on spool off set markup html off spool off

2. If the error is reproducible:   如果错误是可重现的

SQL> conn user/pass
SQL> ALTER SESSION SET EVENTS '1552 trace name errorstack level 3';
SQL> ALTER SESSION set MAX_DUMP_FILE_SIZE= unlimited ;
SQL> ALTER SESSION set TIMED_STATISTICS = true;
SQL> ALTER SESSION set TRACEFILE_IDENTIFIER = "ORA-1552";
SQL> Reproduce the error  --重现错误

SQL> ALTER SESSION SET EVENTS '1552 trace name errorstack off';

Then upload resulting tracing in the directory specified by user_dump_dest  or the diagnostic_dest parameter .

然后将结果跟踪上传到user_dump_dest或diagnostic_dest参数指定的目录中

3. If the error is not reproducible:  如果错误无法重现

SQL> CONN / AS SYSDBA
SQL> ALTER SYSTEM SET EVENTS '1552 trace name errorstack level 3';
SQL> ALTER SYSTEM set MAX_DUMP_FILE_SIZE= unlimited ;
SQL> ALTER SYSTEM set TIMED_STATISTICS = true;

Wait until the error (ORA-1552) occurs again .  --等待直到再次出现错误(ORA-1552)

Note When the ALTER SYSTEM SET EVENTS command is used only new sessions see the events set by this command.
--注意当仅使用ALTER SYSTEM SET EVENTS命令时,新的会话将看到此命令设置的事件 SQL> ALTER SYSTEM SET EVENTS '1552 trace name errorstack off';

Then upload resulting tracing in the directory specified by user_dump_dest  or the diagnostic_dest parameter .

然后将结果跟踪上传到user_dump_dest或diagnostic_dest参数指定的目录中

4. Attach all of the above evidence to the Service Request at SR creation time. The evidence can all be placed into a single ZIP or similar compressed archive or can be attached as separate files.

4. 在创建SR时,将以上所有证据附加到服务请求中。证据可以全部放入单个ZIP或类似的压缩档案中,也可以作为单独的文件附加

posted @ 2019-11-30 10:02  ZYLONG-SYS  阅读(242)  评论(0编辑  收藏  举报