Script to Collect Data Guard Diagnostic Information

简介:
Overview -------- This script is intended to provide an easy method to provide information necessary to troubleshoot Data Guard issues. Script Notes ------------- This script is intended to be run via sqlplus as the SYS or Internal user. Script -------
?
1
2
3
- - - - - - - - - - - - - - - - Script begins here - - - - - - - - - - - - - - - -
 
-- NAME: dg_prim_diag.sql


本文转自maclean_007 51CTO博客,原文链接:http://blog.51cto.com/maclean/1276737
相关文章
|
2月前
|
JavaScript
Error loading saved preferences: ~/.vuerc may be corrupted or have syntax errors. Please fix/delete
Error loading saved preferences: ~/.vuerc may be corrupted or have syntax errors. Please fix/delete
MGA (Managed Global Area) Reference Note (Doc ID 2638904.1)
MGA (Managed Global Area) Reference Note (Doc ID 2638904.1)
294 0
|
SQL 关系型数据库 Oracle
ORA-01466: unable to read data - table definition has changed
1. Oracle建议我们等待大约5分钟之后再进行flashback query新创建的表,否则可能会碰到这个错误ORA-01466: unable to read data - table definition has changed.
1762 0
|
前端开发
Warning: This synthetic event is reused for performance reasons.
Warning: This synthetic event is reused for performance reasons.
503 0
Warning: This synthetic event is reused for performance reasons.
why process type for MyOpportunity creation is empty
why process type for MyOpportunity creation is empty
94 0
why process type for MyOpportunity creation is empty
How to resolve warning message Access restriction -The type Resource is not accessible
How to resolve warning message Access restriction -The type Resource is not accessible
How to resolve warning message Access restriction -The type Resource is not accessible
|
中间件
IBASE change and save - Middleware related
IBASE change and save - Middleware related
IBASE change and save - Middleware related
How to analyze the dump MESSAGE_TYPE_X when modifying an attachment
Created by Jerry Wang, last modified on Mar 04, 2014 The real problem could be reproduced by following the four steps below:
How to analyze the dump MESSAGE_TYPE_X when modifying an attachment
How to find where settype DB table COMM_PRMAT is accessed without debugging
How to find where settype DB table COMM_PRMAT is accessed without debugging
How to find where settype DB table COMM_PRMAT is accessed without debugging